I recently encountered a situation where an Active Directory domain was set up using non-standard conventions.
The AD domain was named dev.mycompany.com but the NetBIOS name for the domain was called mycompanydev!
Unfortunately, because Windows (and SharePoint) generally expects the NetBIOS name to be the same as the first part of the FQDN, this was causing the User Profile Service to fail when attempting to distinguish user accounts for importing.
Microsoft Support then pointed me to these articles:
http://blogs.technet.com/b/sykhad-msft/archive/2013/04/30/sharepoint-2010-user-profile-synchronization-service-decoded-part-2.aspx
http://blogs.technet.com/b/steve_chen/archive/2010/09/20/user-profile-sync-sharepoint-2010.aspx#How%20to%20grant%20the%20Replicate%20Directory%20Change%20on%20the%20domain%20configuration%20partition
It basically involved changing the setting for the User Profile Synchronization Service to support NetBIOS names through a PowerShell script as well as some manual settings for Active Directory.
The AD domain was named dev.mycompany.com but the NetBIOS name for the domain was called mycompanydev!
Unfortunately, because Windows (and SharePoint) generally expects the NetBIOS name to be the same as the first part of the FQDN, this was causing the User Profile Service to fail when attempting to distinguish user accounts for importing.
Microsoft Support then pointed me to these articles:
http://blogs.technet.com/b/sykhad-msft/archive/2013/04/30/sharepoint-2010-user-profile-synchronization-service-decoded-part-2.aspx
http://blogs.technet.com/b/steve_chen/archive/2010/09/20/user-profile-sync-sharepoint-2010.aspx#How%20to%20grant%20the%20Replicate%20Directory%20Change%20on%20the%20domain%20configuration%20partition
It basically involved changing the setting for the User Profile Synchronization Service to support NetBIOS names through a PowerShell script as well as some manual settings for Active Directory.
No comments:
Post a Comment