One of Microsoft’s main feature claims for DirSync is that it has an appliance like setup. I have probably installed 100 DirSync servers, and can confirm that the install process for DirSync is as appliance like as it gets. The process of uninstalling DirSync is, however, nowhere near appliance like.
In a recent Office 365 migration project we had an issue with DirSync that turned out to be a conflict with a Tivoli product the customer had installed. During the troubleshooting process we retied uninstalling and reinstalling DirSync several times, and found out the process is rather a pain.
Here are the steps I followed.
- Programs and features – uninstall Dir sync
- Stop all SQL services
- Stop Dirsync services
- Uninstall SQL - Programs and features
- Uninstall windows azure active directory sync - Programs and features – uninstall Dir sync
- Delete dir on c drive – c:/program files/windows azure active dir sync.
- Delete Dir in C drive – c:/programfiles/SQL
- Delete all local FIM groups
- Remove MSOL-account from AD
- Log on as dir sync service account
- Disable any virus protection.
- Reinstall DirSync
Your mileage may vary as new versions of DirSync are released.