CA Desktop Migration Manager Online Help › CA DMM › Deferred Migration › Select Users for Migration › User Migration Details

User Migration Details

CA DMM contains a powerful feature that lets you migrate all of the Windows user profiles from a source machine to a destination machine. To perform a multiple user migration, you must be logged into Windows as a user who is part of the Administrators group.

Supported user migrations are as follows:

From NT domains to NT domains

Migrates directly to the same user on the new system, or redirected to different domains or user names.

From NT domains into Active Directory

Migrates users from NT domains into an Active Directory container by redirecting the user on the destination. If the user is not already a member of the target Active directory, an Active Directory account will be created for the user as long as the machine is connected to the network. User profiles will be migrated as local user profiles (not roaming profiles in this release).

From Active Directory to Active Directory

Migrates users from one Active Directory to another.

The User Migration Details page contains sections on:

• User Migration Methods
• Multiple User Migration
• Current User Migration
• Passwords
• Security Migration
• User Account Creation
• User Priority

User Migration Methods

You can select users to migrate in the following methods:

• From the CA DMM user interface
• Using a DMM Template
• Passing a user command line

Note: If you pass users on the user command line, it will override any other method of selection.

Multiple User Migration

CA DMM supports the migration of multiple users, which lets you migrate users that are not currently logged in. This feature lets you log in with administrative rights and migrate one or more user profiles of the people that use this workstation.

Current User Migration

In this mode, all settings migrated from the source machine are selected from the currently logged in user and migrated to the user logged in on the destination.

Passwords

For any accounts that are created by CA DMM as part of a multi-user migration, you can specify passwords.

To specify passwords, follow these steps:

1. Click Passwords on the User Destinations page.

   The Password Options for New Accounts dialog appears.

2. Do one of the following:
   • Click the Use No Passwords option if you do not want to change the users' password on the destination system. (This is selected by default.)
   • Click the Use a Common Password option if you want to assign a common password for all users on the destination system.

     Note: This should only be used if you also check the Users must change password at next logon check box.

3. Click Specify to enter and confirm the common password entry.
4. Click the Use Randomly Generated Passwords option if you want CA DMM to randomly assign a password for the destination users.
5. Click Specify to choose the options that will generate the passwords.

   Note: If you select randomly generated passwords you must also enter the location to save the password log. The password log defaults to the currently logged on user's My Documents folder. However, you should change the location to a secure location.

6. Click OK on the Password Options for New Accounts dialog.

Note: CA DMM limits the length of the password to that of the operating system. For instance, in Windows XP, the maximum password length is 256 characters.

Security Migration

If the Migrate group memberships option is set to True in the DMM Options file, the appropriate group memberships migrate with the users. The Migrate group memberships option is set to True by default.

If the Store and Apply NTFS security options are set to True in the DMM Options file, the appropriate file and folder security are migrated with the users. The store and apply NTFS security options are set to False by default.

The migration of group and NTFS security is associated with the users selected for migration whether the user is selected in the DMM user interface, through a template file, or from the user command line.

User Account Creation

The creation of the user account is automatic when a user is redirected to a different path. This includes all migrations from Windows 2000 to any other Microsoft operating system regardless of user redirection.

If a local account is unable to be resolved when the DNA is applied to the destination machine, the creation of the account is also automatic.

The creation of an account can succeed or fail depending on whether the logged in user performing the migration has the required privileges in the domain or directory.

The creation of an account will not occur under the following conditions:

• The account already exists by the same SID and the user was not redirected.
• The user was not redirected, and the account does not exist on the destination and the orphan account profile handling option in the DMM Options file is set to temporarily unavailable. The default orphan account profile handling option is set to assume deleted by default.

User Priority

If a user account being migrated belongs to more than one domain or directory and is being migrated to a single domain or directory on the destination system, a conflict can result. If a conflict occurs, the following priorities are followed to determine the account creation:

• Identical source and destination user paths take the highest priority.

  Example: Domain1\Michael is being migrated to Domain1\Michael

• Source user names with the same destination user name but a different domain or directory take precedence over unlike user names.

  Example: Domain1\Michael is being migrated to Domain5\Michael

• User profiles for existing user accounts take precedence over orphan user accounts.
• The search order for domains or directories give precedence to one profile over another based on the domain or directory of the source path as follows:

  1. Destination machine domain or directory

  2. Source machine domain or directory

  3. Destination login domain or directory

  4. Source login domain or directory

  5. Local account

Note: If an account is not migrated due to a redirection conflict, a message is written to the Event log.