Late Monday, Microsoft released another update to the DirSync software, this time with a build number of 6593.0012. You can download it in from the usual link.
As with previous DirSync updates, there has been no official announcement of the release, however the “use at your own risk” Wiki does mention one of the new features:
New features:
Attributes documented here |
The new attributes referenced in the link are userCertificate and userSMIMECertificate. Interestingly pwdLastSet was also added, however there is no mention of that one in the article. These additions serve an unknown purpose for now, however one might speculate that they are in support of new capabilities soon to be available in the service?!
Before you upgrade, you may wish to get a “before and after” review of the attribute inclusion list. The best way to review this is in the “Configure Attribute Flow” area of each management agent. At the end of this post, I have also shared an experimental PowerShell method of getting this information.
It is noteworthy that the author of this update, a Microsoft Program Manager for DirSync, is linking to yet another community wiki page instead of the seemingly defunct Knowledge Base article KB-2256198. Sadly, it would appear that the crumbling integrity of the TechNet/Support documentation may be latest casualty in a growing list of IT Pro-related cuts Microsoft has made along their quest to the cloud…
<# Description: This script counts and dumps the attribute inclusion lists from each MA. It does not evaluate attribute flow or applicable object types. February 3 2014 Mike Crowley http://mikecrowley.us #> #Import Modules Import-Module SQLps -WarningAction SilentlyContinue #Get SQL Info $SQLServer = (gp 'HKLM:SYSTEM\CurrentControlSet\services\FIMSynchronizationService\Parameters').Server if ($SQLServer.Length -eq '0') {$SQLServer = $env:computername} $SQLInstance = (gp 'HKLM:SYSTEM\CurrentControlSet\services\FIMSynchronizationService\Parameters').SQLInstance $MSOLInstance = ($SQLServer + "\" + $SQLInstance) #Get Management Agent Attribute Info [xml]$OnPremAttributes = (Invoke-Sqlcmd -MaxCharLength 10000 -ServerInstance $MSOLInstance -Query "SELECT attribute_inclusion_xml FROM [FIMSynchronizationService].[dbo].[mms_management_agent] WHERE [ma_name] = 'Active Directory Connector'").attribute_inclusion_xml [xml]$CloudAttributes = (Invoke-Sqlcmd -MaxCharLength 10000 -ServerInstance $MSOLInstance -Query "SELECT attribute_inclusion_xml FROM [FIMSynchronizationService].[dbo].[mms_management_agent] WHERE [ma_name] = 'Windows Azure Active Directory Connector'").attribute_inclusion_xml $ADAttributes = $OnPremAttributes.'attribute-inclusion'.attribute $AzureAttributes = $CloudAttributes.'attribute-inclusion'.attribute #Output to Screen Write-Host $ADAttributes.count "Attributes synced from AD to the Metaverse" -F Cyan Write-Host $AzureAttributes.count "Attributes synced from the Metaverse to Azure" -F Cyan Write-Host "See" $env:TEMP\DirSyncAttributeList.txt "for detail" -F Cyan #Output to File "******AD Attributes******" | Out-File $env:TEMP\DirSyncAttributeList.txt $ADAttributes | Out-File $env:TEMP\DirSyncAttributeList.txt -Append " "| Out-File $env:TEMP\DirSyncAttributeList.txt -Append "******Azure Attributes******" | Out-File $env:TEMP\DirSyncAttributeList.txt -Append $AzureAttributes | Out-File $env:TEMP\DirSyncAttributeList.txt -Append ##END
seems, 1.0.6694.0086 is out.
Also do you know what happen with the max pw lengh. O365 native is 16 characters only. But local AD allows much more
I’m not sure I understand the question. Azure Active Directory, which supports Office 365, does have a 16 character limit for passwords. NOTE: passwords are only evaluated when they are set. Because DirSync copies password hashes from AD to Azure, the number of characters is irrelevant; only the hash matters. Therefore you can have passwords of any length when using DirSync’s Password hash sync feature.
The download points to the latest version. I need to have this version 6593.0012. Any idea how to obtain this version?
Sorry, I’m not sure that Microsoft makes previous builds available. What’s wrong with the current version?