Resources are not processed for users who are part of delegated migration (4254877)

Users are migrated using QMM service account. Later, a delegated migration is set up, then delegated account is used to log on to Migration Manager console and more users are migrated. Resource Updating is performed and permissions are updated, but only for the users that were part of the first migration. Any user who was a part of delegated migration is not stored in the account mapping .ini file and as a result target accounts for these users do not receive any permissions on files, folders, profiles etc.

This issue is caused by a bug in the mapping file generation algorithm. When the mapping is built, delegated migrations are disregarded.

A workaround is to use custom map functionality. Right click the group in RUM that is used to process resources and select the option "Specify Custom Map". In the new window a list of all migration sessions and synchronizations is displayed, select all necessary sessions, making sure that delegated migration sessions container is included. Click OK and a list of all migrated users will be displayed, use the interface to select all again (button on the left side of the toolbar) and click OK.

This will save the current selection of users and groups whose permissions need to be updated when resource processing runs, including the accounts that were part delegated migration.

Please note, if more users are migrated and synchronized later, the selection needs to be re-done to include newly migrated users. Right-click the group, select "Delete custom map" and then redo the selection as per procedure above. Custom mapping is a static set of objects and does not change automatically when new accounts are added to migration database.

Defect id for this issue is ST74662 to be addressed in future versions of Migration Manager.