Best Practices Guide › DMM Best Practices › Tips to Optimize Time and Resources › Reduce Time of Multiple User Migrations

Reduce Time of Multiple User Migrations

In some migration scenarios, you might increase the speed of your migration by changing the Detect scripts as every selected user option to false on the Advanced tab of the DMM Options file. This setting is true by default. CA DMM detects scripts for each user profile selected for migration unless you change this option to false.

Loading user profiles for all users selected for migration can be a time consuming process. On the source system, CA DMM must verify the accounts exist on the domain or Active Directory for use later in the migration process. Then each user profile selected for migration must also be loaded and detection for the scripts evaluated for each user in succession.

On the destination computer, CA DMM must verify each account exists, and if necessary, create any user accounts or profiles for the selected users. Then, CA DMM must detect application scripts for each user on the destination to resolve application destination paths. The application detection occurs when opening a DNA file on the destination or when opening the Application Destination page.

In contrast, when you are migrating only the current user, detection is much faster for the following reasons:

• Current user migrations are using the currently loaded user profile.
• The current user is already resolved, and there are no additional users to verify.
• The Detect function included in the scripts only needs to run once for each script for the one user profile. Additional user profiles are not loaded.

Because current user detection runs much faster, it can be substituted for multi-user detection in most cases because the majority of scripts Detect functions are based only on the local computer registry settings and do not vary from user to user. Additionally the majority of the scripts detect functions do not change the state of the computer during detection.

The exceptions to this rule that makes multi-user detection necessary for some scripts are:

• Some scripts (listed below) use current user settings and shortcuts to resolve application paths and detect system features. Each user must be loaded to resolve the shortcuts and application paths.
• Some scripts change the state of the computer to migrate settings from the source to the destination in real-time migrations.

The scripts that use multi-user detection to migrate settings are like:

• The Internet Explorer script exports user certificates for each user.
• The Dial Up system script migrates phonebook information in the registry for each user.
• The Printers system script migrates the printer setup and is dependent on user specific files on the source system.

If you are not migrating the settings for Internet Explorer, Dial Up system settings, or Printers for multiple users, or performing real time migrations, you can safely turn off the multi-user detection option, and increase the performance of CA DMM.

More information:

Requirements for Migrating Users with a Crossover Cable