The Migration Manager RUM Controller service stores all information about its functions in its log file. The log file is called RUMController.log and stored in the %ProgramFiles(x86)%\Common Files\Aelita Shared\Migration Tools\Resource Updating folder (on 64-bit Windows) or in the %ProgramFiles%\Common Files\Aelita Shared\Migration Tools\Resource Updating folder (on 32-bit Windows) on the console computer
The Migration Manager RUM Agent service also stores all information about its activity in its log file. This log file is called RUMAgent.log and stored in the %WINDOWS%\Quest Resource Updating Agent folder on the computer where the agent is installed.
As soon as all the agents have finished performing the specified tasks, Resource Updating Manager will collect the logs from the computers. To view the collected logs right-click the computer in the right pane of the Resource Updating Manager console and select View Logs.
To interrupt all tasks for a specific collection or category, right-click the collection or category node in the Resource Updating Manager console and select Cancel Tasks.
Resource Updating Manager behaves as follows in situations where processing is interrupted:
To ensure zero user impact and zero help desk involvement when user accounts are migrated, the target user accounts must have the same profiles as the corresponding source accounts.
For this to occur, two tasks need to be accomplished:
Migration Manager manages these tasks for both local and roaming profiles, and ensures that at every migration phase, users have access to their personal profiles and settings.
A user profile consists of two parts: the key in system registry and the folder on a hard disk which contains user-specific data and desktop settings.
A user profile can be either local or roaming:
When migrating accounts from one Active Directory domain to another, you can use the Add SIDHistory option to specify that the new accounts should automatically gain all privileges of the source accounts, so no resource update is required for users to start using their new accounts. When the coexistence period is over, you can process all resources, granting the target accounts explicit access, and then clean up SIDHistory and remove the source accounts.
However, adding SIDHistory does not cause the target accounts to use the source profiles. This task requires registry changes, which can be accomplished by using Resource Updating Manager or Resource Kit utilities.