DirSync 1.0.6567.0018 Has Been Released

As some of us noticed, last week, Microsoft quietly removed the latest version of DirSync without so much as a tweet explaining why. Word on the street is that there were issues in the “Export” stage in the synchronization process (see KB 2906832). Today it would appear those issues have been resolved, as v1.0.6567.0018 just hit the web. You can download it here, though I’d advise caution, given Microsoft’s approach to communicating (lack-thereof) bugs.

As stated in the updated Wiki, the following improvements exist in this version:

New features:

  • DirSync can be installed on a Domain Controller (must log-off/log-on AFTER installation and BEFORE configuration wizard)
    • Documentation on how to deploy can be found here

Contains fixes for:

  • Sync Engine memory leak issue
  • Sync Engine export issue (FIM 2010 R2 hotfix 4.1.3493.0)
  • “Staging-Error” during large Confirming Imports from Windows Azure Active Directory
  • password sync behavior when sync’ing from Read-Only Domain Controllers (RODC)
  • DirSync setup behavior for domains with ‘@’ symbol in NetBois names
  • Fix for Hybrid Deployment Configuration-time error:
    • EventID=0
    • Description like “Enable-MsOnlineRichCoexistence failed. Error: Log entry string is too long.  A string written to the event log cannot exceed 32766 characters.”

11 thoughts on “DirSync 1.0.6567.0018 Has Been Released

  1. Pingback: Upgrading DirSync to the Latest Version | Mike Crowley's Whiteboard
  2. I have an SBS 2008 Exchange 2007 with FOPE dirsync installed and working from the recent migration from Microsoft Forefront to Office 365 FOPE. Now, I am migrating exchange to Office 365 and want to implement password sync. It appears Azure Dirsync for password sync is different than FOPE dirsync for forefront. Can I install & sync both on the server at the same time without causing issues? If not, do you have any suggestions?

    • You’re combining a lot of things here, so lets break it down. I assume they moved you from FOPE to EOP. EOP is part of Office 365 and relies on the Office 365 / Azure Dirsync as I wrote about above. Prior to this FOPE had it’s own dirsync software, which is no longer needed. *IF* you are actually using FOPE and not yet moved to EOP, you can use both, but i would just use the Azure Dirsync, since FOPE is going away soon. (all of my customers have been moved to EOP). You can read more at the FOPE transition center: http://technet.microsoft.com/en-us/library/jj723146(v=exchg.150).aspx

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )

Connecting to %s