Resolution
fact
Domain Migration Administrator 7.x
symptom
Changes made in the modeling database do not apply when performing a migration in Test mode
symptom
When using the modeling database to create an account conflict, a new account gets created in the target instead of the 2 merging together
cause
fix
The product is working as designed
Domain Migration Administrator 7.x
symptom
Changes made in the modeling database do not apply when performing a migration in Test mode
symptom
When using the modeling database to create an account conflict, a new account gets created in the target instead of the 2 merging together
cause
The way DMA handles conflicting accounts and the "Replace and Update" functionality is this:
- DMA attempts to create the account no matter what the settings are, the only difference is how the error message is handled
- In the case of Replace and Update mode (as specified in the "Specify Migration Settings" option), we are expecting AD to return an error of "account already exists"
- Once DMA receives that error, it then starts reading the properties from the source object and starts to apply those properties to the target object
- In the case of test mode, we do not actually execute the call to create the object, therefore, we do not get the "account already exists" error message which would kick the migration into the Replace and Update code/operation.
fix
The product is working as designed
Additional Information
Formerly known as NETIQKB56173