DirSync: Directory Sync Tool Version Release History

DirSync: Directory Sync Tool Version Release History

  Tip
For feedback, click here

The Windows Azure Active Directory team regularly updates the DirSync client with new features and functionality. Not all additions are applicable to all audiences.

This article is designed to help you keep track of the versions that have been released, and to understand whether you need to update to the newest version or not.

 Note
There may be interim releases between those listed below for specific purposes.
Only major releases are posted in this article.

 

 

  


Version 7020.0000

Released 7/31/2014
Fixes
  • Fix for some failures in certain locales.

 

↑ Back to top


Version 6985.0000

Released 7/22/2014
Fixes
  • Fix for installation failure in certain locales.
New Features
  • .Net 4.5.1 has become a prerequisite for installing DirSync.

 

 

↑ Back to top


Version 6862.0000

Released 6/5/2014
Fixes
  • Fix for requiring Windows Management Framework 3.0 or Powershell 3.0
  • Integer overflow issue in Password sync that caused the same users’ passwords to be synced
New Features
  • Change in how DirSync calls the PowerShell module.
    Now you can call it using the following commands:
    • Open PowerShell and type Import-Module DirSync

 

 

 Important

Installing on Windows Server 2012 or Windows Server 2012 R2 with regional settings that use comma as decimal delimiter will return an error "The minimum version of Windows Powershell required is 2.0" during installation.

The solution is to set the Windows number regional format in control panel to "English (United States)" and log off and back on. After this, you can continue with installing it.

The problem has been identified with the latest Directory Sync Version and it has been fixed.

The next version of the Directory Sync Tool will work fine and will be available when we push this out to Prod.

source http://social.technet.microsoft.com/Forums/en-US/bb65d68d-790b-4a47-b721-e60f1fceebd8/dirsync-6862-instalation-failed?forum=windowsazureaditpro

 

↑ Back to top


Version 6765.0006

Released 4/18/2014
Fixes
  • Password sync behavior when the replication epoch of the domain controllers in the forest changes.
  • Integer overflow issue in Password sync that caused the same users’ passwords to be synced
New Features

 

 Important
It is required to update to Windows Management Framework 3.0 or Powershell 3.0 if you are installing DirSync on Windows 2008 R2.

 

↑ Back to top


Version 6694.0086

Released 4/18/2014
Fixes

 

↑ Back to top


Version 6593.0012

Released 2/3/2014
New Features
  • Additional Attributes are synchronized on User and Contact objects
    • Attributes documented here

 

↑ Back to top


Version 6567.0018

Released 11/22/2013
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
Fixes
  • 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."

 

↑ Back to top


Version 6467.0010

Released 08/19/2013
Fixes
  • DirSync can be configured to use aFederated Windows Azure Active Directory User (specified during Configuration Wizard)
  • Fix to address issue with handlingAuthoritatively Restored users in Password Sync
  • Fix to prevent theDuplicate Attribute issue from blocking Password Sync progress (NOTE: the updated behavior will skip the offending user and allow Password Sync to proceed.  The offending users password will not be synchronized to the cloud. To resolve this issue, have the user update their on-premises password.)
    • EventID=611
    • Description like "System.ArgumentException:An item with the same key has already been added." 

 

↑ Back to top


Version 6455.0815

Released 08/12/2013
Fixes
  • Fix to address issue with Win32 FileTime Conversion in Password Sync:
    • EventID=611
    • Description like "Password synchronization failed for domain: <name of your AD domain>. Details: System.ArgumentOutOfRangeException: Not a valid Win32 FileTime. " 

 

↑ Back to top


Version 6455.0807

Released 08/07/2013
Fixes
  • Fix to address issue with Domain Rename/Epoch in Password Sync:
    • EventID=611
    • Description like "Microsoft.Online.PasswordSynchronization.DirectoryReplicationServices.DrsException: RPC Error 8593 : The directory service cannot perform the requested operation because the servers involved are of different replication epochs (which is usually related to a domain rename that is in progress)"
  • Fix to address issue with Server Busy in Password Sync

 

↑ Back to top


Version 6438.0003

Released 07/24/2013
New Features
Fixes
  • Fix to prevent double logging of event log entries when an error is encountered on export
  • Minor fix to underlying engine for multi-domain configuration issue

 

↑ Back to top


Version 6411.0007

Released 06/25/2013
Fixes
  • Fix for "recovery task failed" issue when running Password Sync against Windows 2003 domain controllers
  • Fixed issue with Set-CoexistenceConfiguration cmdlet as reported by some customers

 

↑ Back to top


Version 6385.0029

Released 06/06/2013
Fixes
  • Updates for Cross-Premises Public Delegates feature

 

↑ Back to top


Version 6385.0012

Released 05/31/2013
New Features
  • Added Password Sync feature
  • Uses SQL 2012 Express SP1

 

↑ Back to top


Sort by: Published Date | Most Recent | Most Useful
Comments
  • We have photos in AD that are not showing up in SharePoint online. How can i troubleshoot the sync processes to determine where the problem is in order to identify a possible solution?

  • We have photos in AD on premise, the accounts are syncing to Office 365 but the photos are not showing up in SharePoint online. How can i troubleshoot this?

  • The URL in the most current update appears to be missing.

    Version 6593.0012

    Date Released 2/3/2014

    Notable Changes

    New features:

       Additional Attributes are synchronized on User and Contact objects

    Attributes documented here (Here = http://)

  • It looks like there is a 6635.0043 version available now.

  • We are running DirSync tool on Windows Server 2003 32-bit, using Windows Powershell 1.0.

    Can we upgrade to the latest DirSync tool in this environment? Do we need to upgrade PowerShell to 2.0 before upgrade DirSync tool?

    Thanks

  • hi, great wiki, was just about to start one.

    I notice that version 1.0.6694.0086 is out

  • So is it a) "Windows Azure Active Directory Sync" tool, b) "Microsoft Azure Active Directory Sync" tool, or c) DirSync. I see all 3 referenced in this article.

  • When I attempt to run/install dirsync.exe, I get the following message:  "The application has failed to start because its side-by-side configuration is incorrect.  Please view the application event log or use the command line sxtrace.exe tool for more detail."

    Sxtrace gives the following:

    =================

    Begin Activation Context Generation.

    Input Parameter:

    Flags = 0

    ProcessorArchitecture = AMD64

    CultureFallBacks = en-US;en

    ManifestPath = N:\temp\dirsync.exe

    AssemblyDirectory = N:\temp\

    Application Config File =

    -----------------

    INFO: Parsing Manifest File N:\temp\dirsync.exe.

    INFO: Manifest Definition Identity is (null).

    ERROR: Line 0: XML Syntax error.

    ERROR: Activation Context generation failed.

    End Activation Context Generation.

    Can anyone help?  

    Thanks.

  • Feedback to latest version (6862.0000):

    1. The embedded version of Sign-in Assistant is still outdated. If customer installs a newer version first, setup will fail. Please consider embedding the latest RTW.

    2. TechNet-docs regarding /fullsql needs to be updated, the first step should be to import-module, not call the ps1.

    Thanks,

    Jesper Ståhle

  • Feedback to latest version (6862.0000):

    1. The embedded version of Sign-in Assistant is still outdated. If customer installs a newer version first, setup will fail. Please consider embedding the latest RTW.

    2. TechNet-docs regarding /fullsql needs to be updated, the first step should be to import-module, not call the ps1.

    Thanks,

    Jesper Ståhle

Page 1 of 2 (13 items) 12