Support does not officially approve schema changes in the middle of migration project.
It may lead to various problems and should be avoided, if possible, and postponed until migration is finished.
If changing the AD schema (Not adding Exchange) in the middle of migration is absolutely needed then the following workaround can be tried:
1. Stop all migration or synchronization jobs before extending schema and proceeding the next step.
2. Backup ADAM (Important!)
2. Upon the schema change, on the domain pair properties make some modifications, for example change the domain controller name in the source or target domain fields (depending where an upgrade was performed) between FQDN, NETBIOS, IP address formats, while actually leaving the DC the same, or just change the accounts credentials. This will trigger QMM to re-read the schema version from AD.
NOTE: Pointing to a different DC on domain pair dialog, provided that no preferred DC is defined on DSA properties, can introduce some issues while Directory Sync is in progress. Specifically MVHandler, FeedBack handler and few more that rely on obtaining data from DSA cache can malfunction. It is not recommended to change the DC name while directory Sync is in progress. In this case Full Resync is also recommended in the next step to avoid any possible issues.
3. DSA is going to dynamically generate a new schema mapping XML here....\Quest Software\Migration Manager\DSA\CONFIGS\Schemas every time new migration or synchronization session starts. Please initiate Full Resync on any synchronization jobs.
Note: in order to see the newly added attributes in QMM the dirsync needs to to be stopped and started and the console needs to be closed and then opened again.
In a case when the mode was changed from mixed to native and new attribute like InetOrgPerson was introduced DSA will report the following:
8/17/2011 3:09:44 PM (GMT-07:00) Configurator Error 0xec000053. Mapper: cannot find special attributes for class: 'InetOrgPerson' Exiting.
the following can be tried:
back up ADAM
then you can try and delete the container CN=SourceSpecialAttrContainer (if source has changed) and CN=TargetSpecialAttrContainer if the change occurred in the target.
Explanation from dev:
In a situation when a new class was introduced (not just an attribute) just changing the DC is not enough, one needs to go and remove the mentioned above container under the domain pair in ADAM. Then, after you change the DC under the domain pair in the GUI, the console will rebuild those containers with new classes and attributes. Also see attached screenshot.
© ALL RIGHTS RESERVED. Terms of Use Privacy Cookie Preference Center