Monitoring and Testing Directory Sync
Once you have the dirsync tool installed we will need to test that it works correctly. There are a couple of ways you can test and monitor dirsync, ideally what we want to do is test both forced & automatic updates.
To monitor our changes we can use the Synchronization Service Manager tool, which ships with DirSync.
Navigate to the following directory on the member server you installed the dirsync tool C:\Program Files\Windows Azure Active Directory Sync\SYNCBUS\Synchronization Service\UIShell
To summarize, in the top frame you have a list of when dirsync ran, the bottom left frame gives you finer detail of the changes, for example the number of changes, add, deletes, etc.
To test a forced sync, navigate to you on-premise Active Directory and make a simple change on an account that you have on both platforms. In this example I’ve updated the Job Title details on the account Edward Tester.
Then log onto the member server where the dirsync tool is installed.
Navigate to the following directory. C:\Program Files\Windows Azure Active Directory Sync and run DirSyncConfigShell.psc1
Type Start-OnlineCoexistenceSync. Press Enter. This will force a sync between you on-premise Active Directory and Windows Azure Directory Services.
If you now open up the Sync Service Manager and you will see the update going through.
If you click and navigate further you can see the finer detail of the updated object, in this instance the object field we are attempting to sync.
You can now check you user object in Office 365, the change has been replicated.
The default sync between Office 365 and on-premise Active Directory is 3 hours. This can be changed to what ever suits your companies need. This previous article on Changing the default Office 365 DirSync Schedule outline the steps for this.
If you found this blog post useful, and want to refer to it again, why not download it as a PDF?