Share via


DirSync: Frequently Asked Questions

 Tip
For feedback, click here

 

 


How can I determine what version of DirSync I have?

You can check your DirSync version by running the following PowerShell command:

(GP 'hklm:SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\Microsoft Online Directory Sync').DisplayVersion

↑ Back to top

 


Where can I find the latest version of DirSync?

The latest version can be downloaded here: Windows Azure Active Directory Sync tool – 64 bit 

For more details, see Directory Sync Tool Version Release History.

↑ Back to top

 


What can I do if DirSync doesn’t work as expected after upgrading to the latest version?

The recommended best practice to address this scenario is to contact customer support.

However, if you are blocked and contacting customer support is not an option, the only alternative you have is to install a previous version of DirSync.   
DirSync does not provide a "downgrade" feature.
As a consequence of this, you need to first uninstall the current version before you can install and configure another version of DirSync.
You can download the predecessor of the latest DirSync version here

For more details, see Directory Sync Tool Version Release History

↑ Back to top

 


I have a firewall, network device, or something else that limits the maximum time connections can stay open on my network. How long should my client side timeout threshold be when using Azure AD Connect?

All networking software, physical devices, or anything else that limits the maximum time connections can remain open should use a threshold of at least 5 minutes (300 seconds) for connectivity between the server where the Azure AD Connect client is installed and Azure Active Directory.
This also applies to all previously released Microsoft Identity synchronization tools.

↑ Back to top

 


Can I install DirSync on a Domain Controller?

Yes. Installing DirSync on a domain controller is a supported scenario.
For more details, see "How To Install Dirsync on a Domain Controller".

↑ Back to top

 


See Also

↑ Back to top