Resolution
Domain Migration Administrator 7.x
symptom
Groups are not being migrated to modeled OU (Organizational Unit).
cause
Options.TargetSeverOverride' key and database modeling are both being used.
fix
Update the Model table to change the target OU (Organizational Unit) from LDAP://dns.domain.name to LDAP://<servername>, where <servername> is the same name as the server specified in the TargetServerOverride.
If the object has been previously migrated and you are using Domain Migration Administrator 7.2 or later, you will also need to update the TargetAdsPath in the MigratedObjects table of the Protar.mdb.
With the release of Domain Migration Administrator 7.2 when you perform the Modeling: Import Data step, Domain Migration Administrator imports information for non migrated accounts using a standard process of either importing the live information from the source account and populating the properties in the default fashion, or keeping the modeling information that has already been updated in the Model table (manually, or via the Modeling: Edit ...Data interface). However, for objects that have been previously migrated, it imports the information directly from the MigratedObjects table which should correspond exactly to the actual live object as it appears in Active Directory. If the objects have been moved or renamed since they were migrated, you will need to run the Refresh Migrated Objects report to update the Domain Migration Administrator database prior to executing the Modeling: Import Data process.
note
For more information regarding the Refresh Migrated Objects report, please refer to the following knowledge base article:
NETIQKB1149 - What is the 'Refresh Migrated Objects' report?
note
For more information regarding the use of the Options.TargetServerOverride key, please refer to the following Knowledge Base article:
NETIQKB925 - Which Domain Controller does Domain Migration Administrator (DMA) connect to and pull the information from when doing a migration?