Error Re-installing AZURE Directory Sync Tool
By using the Microsoft Azure Active Directory Sync tool, your company’s administrators can keep your on-premises Active Directory continuously synchronized with Azure AD. Directory synchronization is intended as an ongoing relationship between your on-premises environment and Azure AD. Active Directory synchronization should be considered a long-term commitment to coexistence scenarios between your on-premises Active Directory and cloud. However in case if you have directory sync tool setup in a system that for any undefined reason cease to work, you need to get the tool up and running quickly in another server – to be more precise, we need to know how we can move the dirsync to another server. Here are the steps to be followed.
Clean up dir sync tool uninstallation
The Setup Wizard has detected a previous installation of the Directory Sync tool. The previous installation is incompatible with this newer configuration of the Directory Sync tool. Please uninstall the previous version of the Directory Sync tool and run this installation wizard again.
After removing dirsync tool from Windows Add Remove Programs, the uninstallation process does not clean up all the necessary files. Hence we need to manually remove them before we can re-install the dirsync tool.
- Remove the local service account created by dirsync tool, with username starting with AAD_…….
- Delete the local user groups created by dirsync tool that starts with FIM……
- Remove the directory C:Program FilesWindows Azure Active Directory Sync
- Delete dirsync database files located at C:Program FilesMicrosoft SQL ServerMSSQL11.MSONLINEMSSQLDATA
- Restart your computer and run the dirsyn tool using alleviated administrative permission and you should be good to start now
In a nut-shell, we all must have backup plan and dirsync is a mission critical application that we all must ensure running 24×7. Hope the above steps would save our day.
1 reply on “Moving from On-Premise to Office 365 / Windows Azure – Part 2”
Lifesaver!!! UGH!!! Glad you figured this one out!!!