For those not interested in the complete DirSync Report published last week, you can now run just the Password Hash Sync portion using a script published here: Dirsync: Determine if Password Sync is Enabled. For deployments with remote SQL installations: As with the previous report, note that the script uses the SQL PowerShell Module, which must be present on the computer. If you like this post, you may like my others on DirSync: DirSync tag.
If you administer DirSync for your organization, you likely have seen emails like this, indicating some of your users didn’t sync. It can be a frustrating email, since the “error description” is for some reason blank and the “On-premises object ID” column is not something that’s easy to correlate to a user account within your Active Directory. There are also application event log entries (FIMSynchronizationService #6111 and Directory Synchronization #0), but again these aren’t exactly rich with detail. ...
Azure Active Directory Sync (DirSync) seems so simple on the surface doesn’t it? “Next, Next, Finish”, right? Ha! If you’ve ever had to revisit your DirSync server to troubleshoot or make a configuration change, you know there can be more than meets the eye. A lot of useful information happens to be scattered across various registry keys, SQL tables and XML files. If you’re not familiar with the FIM Management Console, and these other locations it might be hard to see what’s going on. ...
Detailed installation walkthrough of the new 64-bit Office 365 DirSync, including prerequisites, configuration wizard, and FIM exploration.
Microsoft announces the availability of a 64-bit DirSync for Office 365, based on Forefront Identity Manager 2010.