AD Synchronizer Problem

Hello Will,

Can you do the following:
- Open the profiler (help tab > Profiler)
- Go in the debug only tab
- Set the debug level to Debug (press the button next to the debug level for a choice)

Then, keep this window open and execute your synchronizer. You should see a lot of information in regards to what values it used and what computers it synchronized. There should be the resolved domain there and you can check if it is the right one.

Regards,

Thank you for that. I did as you said and the results were very enlightening. While it says that it will contact the second domain, when it starts processing computers, it first runs through all of the computers in the first domain. Once it completes all of the computers in the first domain, RDM stops responding while it actually creates those connections. Once those connections are created, I can see them and navigate the tree while I could see the Debug log still working. So at this point, it has all the wrong domain synced. However, Debug log is still running and now is processing the correct machines from the second domain. It gets through all of those and RDM stops responding again while creating them. Then right after that, it starts going through all of the machines in the first domain with 'Deleting connection due to no match'. RDM is not responding during this whole time. Ultimately, when it is done I had to switch tabs to private vault, and back so that I could force it to refresh. When I did, the correct connections where in the folder where I wanted them.

So it looks like for the second domain, it read through the entire first domain, created connections, THEN read through the second domain, created connections, then went back through the first domain and deleted connections. I then ran the synchronizer for the first domain, which ran normally. It only read connections from the first domain and created them in the folder I designated.

Thanks for the info Will, this is strange. Can you try making a new datasource with only an AD synchronizer to the second domain and see if the same behavior happens?

Regards,

This was with a fresh datasource. I made another SQL database so as to not impact our existing database the other engineers are using.

Another thing I noticed is after getting both synchronizers to run, searching for a machine name is VERY slow. Locks up RDM for a good 60 seconds. Is there any information regarding performance numbers? Number of connection records before slowdown occurs? Things like that? I imported all computer accounts so that we could enable iLO on the servers and Intel AMT on the clients so there are somewhere in the region of 15,000 records in that database now.

Just to make sure, did you uncheck the "Synchronize automatically" property in the synchronizer entries? That could explain why when starting the second sync, it would also sync the first one's domain (the automatic sync happening at the same time as the one you started manually). But if you tested with only one sync on the datasource, I'm not sure what could have caused this.

As for the performance issues, it would be good to have 5000 or less entries or else it might cause slow downs. We're currently working on a feature that can help manage large amounts of entries more easily, but for now there isn't much to do unfortunately. You could try to use the "Department" feature if you're on a SQL Server datasource. http://help.remotedesktopmanager.com/index.html?file_datasources_mssql.htm If you split your 15000 entries into 3 groups of 5000 and then create a datasource with a department for each group, it would improve performances.

Regards,

I just checked and Sync Automatically was disabled for the first domain (the one that ran when it shouldn't have), but was enabled on the second domain (the one I wanted to sync). So according to the log it ran for the domain that wasn't set to automatic, then ran for the domain that was set to automatic and removed the entries for the first domain when it ran. I'm going to delete all entries, and run it again to see if I get the same results in the Debug log.

If 5000 entries is where you start seeing performance problems, then we would probably put servers in one datasource, and clients in another. We don't need the clients that often and usually we us SCCM remote control. We'd only open them with RDM if we wanted to Intel AMT connection. Our server datasource would be less than 5000, but the client datasource would be large. Since we won't be using it that often, we can accept a bit of slowdown for that one.

So running it with Sync Automatically turned off for domain B now only syncs results for domain A and quits. So now I don't have any results for domain B.

This is strange, in our environment it doesn't do this so we must be missing something either in the AD sync entry or in AD itself. Could you send me both the logs seen through the profiler as well as the two AD sync entries if possible? Be sure to remove sensitive information. You can email me at hmireault (at) devolutions.net

Regards,

Hello,

Hubert is not able to reproduce your issue with our multiple domains.

If think it may go faster if we do a remote session to see if something in your environment is different than what we expect.


Just send you contact info to support@devolutions.net if you agree.

Best regards,