Planning for a User Profile Migration

Applies To: Windows Server 2003, Windows Server 2003 R2, Windows Server 2003 with SP1, Windows Server 2003 with SP2

User profiles store user data and information about the desktop settings of the user. User profiles can either be roaming or local. The migration process is different for local and for roaming profiles.

Profile translation is one type of security translation, and profiles are translated during the migration process. If you perform security translation in add mode, the SIDs in the target and the source domains both have access to the profile. Therefore, if you need to roll back to the source environment, the SID in the source domain can use the profile. If you perform security translation in replace mode, you must retranslate the profile by using a SID mapping file (undoing the security translation) to roll back to the source environment.

Important

  • In the event that you need to roll back to your original configuration, notify users that profile changes made in the target domain are not reflected in the source domain.

Some organizations might choose not to migrate user profiles. Other organizations might choose to replace users’ workstations during the user account migration process, and use a tool such as the User State Migration Tool (USMT) to migrate user data and settings to the users' new computers. Table 11.1 summarizes the migration requirements for user profiles.

Table 11.1   Migration Requirements for User Profiles

Type Description Migration Requirements

Roaming profiles

User profiles are stored centrally on servers. Profiles are available to the user, regardless of the workstation in use.

Migrate local user profiles for a batch of users before migrating those users. Then select the profile migration option during the user account migration process to migrate the roaming profile.

Local profiles

User profiles are stored locally on the workstation. When a user logs on to another workstation, a unique local user profile is created.

Migrate as a separate step from the user account migration process. Migrate local user profiles for a batch of users before migrating those users.

Profiles not managed

Same as local profiles.

No migration requirements. Users lose their existing profiles when their user accounts are migrated.

Hardware refresh

User state information is stored locally on the workstation.

Migrate as a separate step from the user account migration. Migrate the profiles to the user’s new computer by means of a tool such as USMT.