Upgrading DirSync to the Latest Version
EDIT (Nov. 22 2013): DirSync 1.0.6567.0018 Has Been Released
EDIT (Nov. 11 2013): DirSync 1.0.6553.2 has been removed from Microsoft’s download site and version history comment removed from the Wiki. Not sure why.
Early this morning, Microsoft released an updated version of Windows Azure Active Directory Sync tool (DirSync to you and me). Version 1.0.6553.2 (or later) can be downloaded from the usual link. It comes with 4 known improvements:
- Fix to address Sync Engine memory leak
- Fix to address “staging-error” during full import from Azure Active Directory
- Fix to handle Read-Only Domain Controllers in Password Sync
- DirSync can be installed on a Domain Controller. Documentation on how to deploy can be found here.
I am most excited about #4, as this enables me to build more interesting labs from my laptop, now that I don’t need a dedicated “DirSync Server”. You should note however, this is recommended only for “development” environments. After some further testing, I’d consider recommending this configuration for shops with multiple domain controllers and 50 or fewer users.
If you’re already running DirSync, and want to upgrade, you’re likely in one of two camps:
- You want to move DirSync from a dedicated server to a DC.
- You don’t want to move the DirSync server to a DC (or elsewhere), you just want the latest version.
If you’re in the first scenario, I’m going to assume you’re working in a lab or very small environment. This means you don’t need to worry about a lengthy synchronization process, and can easily take advantage of the built-in soft-match capability of the product. Your upgrade process is easy:
- Throw away your existing DirSync server.
- Install Dirsync on a DC.
- Run the Directory Sync Configuration Wizard
As soon as you finish the 3rd step, the initial synchronization will rebuild the database (and re-sync passwords), returning to where you left off!
NOTE: If you’re a big shop, you should consider that a full sync takes roughly 1 hour per 5,000 objects synced, according to a recent webcast by Lucas Costa. Soft-matches would likely go faster, but you’ve been warned…
Now, if you’re just looking to upgrade your version of DirSync to the latest version, you need to first ensure you are running versoin 6385.0012 or later. In-place upgrades aren’t supported on earlier versions. If this is you, refer to the soft-match advice I gave above. This is your upgrade path.
For those that are running 6385.0012 or later, upgrading is as simple as a few clicks of the mouse. For the nervous, here are some screenshots:
|NOTE: The installer detects an existing installation.|
|This is the default path, but it should reflect your installation directory.|
Hmm, that’s not good! Fortunately a reboot cleared this up for me, but if you’re not so lucky, you can examine the following logs:
…which are located in the earlier discussed installation directory.
|For an upgrade, you’ll want to run this right away, since not doing so leaves you without a functioning DirSync server.|
|Global Office 365 Administrator credentials go here. This is stored on your DirSync server, so make sure PasswordNeverExpires attribute is set to $true on the Office 365 account (or your on-premises account, if you’re using a federated user)|
|On-Premises Enterprise Admin credentials go here:|
|Checking this box allows some attributes to be written back to your Active Directory, which is necessary for a Hybrid Exchange Server scenario.|
|Enable Password Sync… or Don’t.|
|NOTE: Upgrades and new installs require a Full Sync.|
|This post wouldn’t be complete without a plug for my free DirSync Report script!|