AD Sync oddity

Hello,

Thank you for contacting Devolutions Support.

We've encountered similar issues in the past, and restarting the provisioning process has often served as a temporary workaround. However, before proceeding with that, we’d like to gather more information to better understand the root cause of the issue.

Please follow the steps below:

• Send us the current DB schema.
• Perform a CTRL + Refresh on the profiler trace **twice**:
- First with profiler level = 1 (Debug)
- Then with profiler level = 3 (Debug + SQL)
- Send us both trace files
• Next, keep the profiler open with the following settings:
- Profiler level = 3
- Uncheck "Auto clear"
- Clear the profiler manually
- Use RDM for a few minutes
- When you experience slowness, send us the profiler trace
- You may repeat this process each time slowness occurs

We hope this will provide better insight into the issue.

Best regards,

I have passed this along to the user having the issue..

I can say they are just using a local data source "connections.db"

Question though, how do we perform the troubleshooting steps detailed above?

Hello,

Thanks for the clarification. I initially assumed the setup was using an advanced data source, which is why I suggested those troubleshooting steps.

Since the user is instead using a local data source (connections.db), I recommend trying the following as a workaround:

Please follow this documentation to export the entries and then re-import them into the destination folder:
https://docs.devolutions.net/rdm/kb/how-to-articles/export-import-entries/

When doing this, make sure that:

• The user performing the export and import is on the same network as the resources being synced
• The import is done in the correct destination folder
• RDM is fully restarted after the import

This can help reinitialize the entries and confirm whether the issue is related to the sync process itself or the local data source behavior.

Let us know the results after trying this.

Best regards,

So to be clear, this is an issue with the AD Synchronizer Object Entry in RDM. The entry is 100% setup correctly as when we preview the results we see the expected servers however when we perform the sync nothing shows up in the destination folder.

I have rebooted the laptop, restarted RDM, and removed the AD Sync object and set it up again, i have the exact same setup on my RDM and it works as intended so not sure why this instance is any different.

We are NOT doing a static import/export but an AD Sync to a folder in RDM that on my setup works as expected.

Hello

Understood, thank you for the clarification.

To help narrow this down, could you please confirm whether all affected users are connected to the same network or VLAN when the AD Sync is executed?

This detail will help us determine if the issue could be related to network visibility or access differences during the synchronization process.

Best regard

Yes they are, i have two users in the same domian, vlan, and same RDM setup that are seeing two different results.

Like I said, the affected user, we can preview the sync, and it shows all the expected servers.. yet when we go to run it properly it imports nothing at all.

Hello,

Could you please ask the affected user to recreate the local data source and check if the issue persists?

Best regards,