When attempting to generate a 'User Mapping File' and the 'AD Object Name', on the 'Object Mapping' tab, is not in 'Matched/Migrated' in the current project, the mapping will fail even if the user account is 'Matched/Migrated' in another project.
Symptoms may include:
- User will get a default profile when logging into domain after mapping of the account.
- The user mapping file is blank after creating the User Mapping File:
Location: c:\program files\quest software\nds migrator\tools\mapping\COMPUTERNAME\
The file is blank.
The workstation updater log file may contain the following:
Location: c:\program files\quest software\nds migrator\logs\workstation updater\
Status: *************Start Workstation Updater*************
Status: Start to generate user mapping files
10:20:55 : Status: Start to generate: .\tools\mapping\COMPUTERNAME\map.usr
10:20:55 : Status: user1 is not a local user account.
10:20:55 : Status: user2 is not a local user account.
10:20:55 : Status: End to generate user mapping files
This is a known issue where overall, the available list of target objects to map to is based upon the current project. The data migration is not project specific and will use all objects that have been 'Matched/Migrated' in all projects, so the creating of the 'User Mapping File' should behave in the same manner and not be project specific.
There are two current workarounds for this issue:
1. The user must return to the original project where the user was 'Matched/Migrated' to successfully generate a 'User Mapping File'.
2. Open the original project where the user was 'Matched/Migrated' successfully, and from the File Menu, select Edit | Move Object Mapping and select the project where the mapping should be moved to.
Waiting for fix in a future release of NDS Migrator.