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.
When a user logs on to a workstation the first time, a local profile is created on that workstation in the Documents and Settings folder.
When a user connects to a server with Terminal Services Client the first time, a local profile is created on that server in the Documents and Settings folder as well.
If a user is configured to use a roaming profile (that is, the settings in either the Profile or Terminal Services Profile tab in the user account properties contain valid paths to centrally stored profiles), the user data stored in the central profile folder is copied to the local profile folder on the workstation (if the user is logged on locally) or server (if the user is connected to the server with Terminal Services Client). All changes made to the profile during a session are saved in the local profile folder and uploaded into the central profile folder at the end of the session.
When a user logs on to a workstation, the following logic determines which user profile is used:
When a user initiates a new terminal session to a server, the following logic determines which user profile is used:
If a computer has both local and roaming profiles, you should perform all actions described in the Local Profile Update topic first and then perform the additional actions described in the Roaming Profile Update topic.