-
Title
What attributes can be safely skipped when doing migration and directory synchronization -
Description
What are the recommendations on skipping some attributes when running migration sessions and when doing directory synchronization with Quest Migration Manager (QMM) for AD?
-
Resolution
The following attributes should not be skipped. Otherwise, you may experience problems during directory synchronization or when running migration session:
DSA service attributes (extensionAttribute15, extensionAttribute14, adminDescription, AdminDisplayName), objectClass, objectGUID, userAccountControl, objectCategory, objectSID, msExchMasterAccountSid, msExchMailboxSecurityDescriptor.
Attribute 'name' should be used to skip instead of skipping the following attributes:
distinguishedName, cn, ou, aDsPath.
NOTE: If SAMAccountName and name attributes are skipped, the objects will not be created on the target (Windows 2000 DC) or may be created with the same display name, but with randomly generated SamAccountName (Windows 2003 DC). Therefore it is not recommended to skip these attributes when running migration sessions and when directory synchronization is configured to create new accounts. However when further performing directory synchronization of already matched accounts the source SamAccountName will overwrite target SAMAccountName. In this case skipping SAMAccountName can be considered as valid workaround. -
Additional Information
This article applies to all versions of QMM for AD. In addition please see the following solutions related to skipping attributes. SOL31860 - Script to skip all attributes in the QMM for Exchange migration scenarios. - https://support.quest.com/Search/SolutionDetail.aspx?id=SOL31860SOL9898">https://support.quest.com/Search/SolutionDetail.aspx?id=SOL31860 SOL9898 - Is it possible to simply match source accounts to target accounts, without synchronizing attributes? - https://support.quest.com/Search/SolutionDetail.aspx?id=SOL9898 https://support.quest.com/Search/SolutionDetail.aspx?id=SOL9898