Skip to main content
Code42 Support

Use Code42 to migrate Windows user profiles and data

Applies to:
  • Code42 CrashPlan (previously CrashPlan PROe)

Overview

Windows devices running version 4.4 of the Code42 CrashPlan app can back up and transfer Windows user profile data. Microsoft's User State Migration Tool (USMT) assists in migrating system settings and application data to a new device, or replacing a device. This tutorial assumes you are already familiar with USMT and explains how to configure and deploy Windows user profile backup with the CrashPlan app.

These instructions advise administrators working with USMT and CrashPlan apps earlier than version 5.4. If you are not working with USMT, or have CrashPlan app version 5.4 or later, select the appropriate article from Use Code42 to simplify device migration

Windows user profile support

The Code42 platform version 5.0 and later supports backing up Windows user profiles.

Compatible With Windows User Profile Backup
  • Code42 server
  • CrashPlan app version 4.4 and later for Windows installed for everyone (Default)
  • CrashPlan app version 5.0 and later for Windows installed for everyone (Default)
  • Administration console
Not Compatible With Windows User Profile Backup
  • CrashPlan app installed per user
  • CrashPlan app for OS X and Linux
  • CrashPlan mobile app

Considerations

CrashPlan and USMT
Our Customer Champions are available to assist you with configuring, backing up, and restoring user profile data in the administration console and the CrashPlan app. However, since USMT is not a Code42 product, our Customer Champions cannot provide direct assistance with USMT-specific features such as deploying USMT to devices, creating the necessary .XML files, or selecting ScanState options. For assistance with USMT, consult Microsoft's documentation.

Before you begin

Confirm user devices are backed up

From the administration console, confirm that all devices being migrated or upgraded have completed a backup.

Create USMT XML files

USMT requires .XML files to determine what is included in the profile backup. The default .XML files for USMT are not included in the administration console and you must supply them for profile backups to occur.

When creating or editing your .XML files, consider what you have selected for backup with the CrashPlan app. Excluding user data from USMT saves time when migrating to a new or reformatted system. To prevent backing up duplicate data, customize your .XML files to only include the user profile data that the CrashPlan app does not back up, such as application data and registry settings. Exclude any user files backed up by CrashPlan from your USMT .XML files, such as photos, documents, music, and videos.

Install USMT on each device

For the CrashPlan app to back up user profile data, USMT must be installed or deployed on each device backing up to the Code42 server. By default, the CrashPlan app looks for USMT in the following location:
C:\Program Files\CrashPlan\USMT\

If USMT is already installed in a different location, you can specify the different USMT location from the CrashPlan app command-line interface:

  1. Open the CrashPlan app.
  2. Double-click the CrashPlan logo in the upper-right corner.
    The CrashPlan command-line area opens.
  3. Enter: prop.set c42.user.migration.usmtBinPath <filepath> save
    Replace <filepath> with the specific location where USMT is installed.
  4. Press Enter.

Run ScanState commands

ScanState options allow you to use some USMT syntax commands when backing up your user profile data. The following syntax is allowed in the administration console:

  • ScanState: /o, /vsc, /hardlink, /nocompress, /localonly, /c, /all
  • LoadState: Deprecated - no effect

To use multiple ScanState commands, leave a single space between commands.

Configure Windows user profile backup

Follow the steps below to configure Windows user profile backup using USMT.

Step 1: Prepare devices for user profile backup

To back up or transfer user profile data, each device that will back up user profile data must have installed:

  • Version 4.4 or later of the CrashPlan app
  • The appropriate version of USMT for your version of Windows

For the CrashPlan app to utilize USMT, install or deploy USMT in the following location: C:\Program Files\CrashPlan\USMT\

Step 2: Enable user profile backup

You can choose to enable user profile backup for all organizations in your Code42 environment, or for a specific organization. Once enabled, user profile backups do not occur immediately. The first user profile backup takes place based on the selected Backup Frequency (7 days by default).

Option A: Enable user profile backup for all organizations

To view or modify Windows user profile backup settings for all organizations in your Code42 environment:

  1. Sign in to the administration console.
  2. Go to Settings > Device Backup.
  3. Click Backup.
  4. If File Selection is locked:
    1. At Included files, add
      :main/ProgramData/CrashPlan/user_settings
    2. (Optional) Click the push icon Push settings icon to apply these settings to existing users.
  5. Select Enable User Profile Backup.
    User Profile Backup Enabled
  6. For each .XML file for your environment, click Select File and add your customized file.
    The filename of your .XML displays to the left.
    • You must supply at least one .XML file for user profile backups to occur.
    • You do not need to supply one of each type of .XML file.
    • For assistance with your .XML files, see Microsoft's documentation.
  7. (Optional) Enter ScanState options.
  8. (Optional) Click the push icon Push settings icon to apply these settings to existing users.
  9. Click Save.

Option B: Enable user profile backup for a specific organization

To view or modify Windows user profile backup settings for a specific organization:

  1. Sign in to the administration console.
  2. Go to Organizations and select an organization.
  3. From the action menu in the upper-right corner, select Device Backup Defaults.
  4. Deselect Use device defaults from parent.
  5. Click Backup.
  6. If File Selection is locked:
    1. At Included files, add
      :main/ProgramData/CrashPlan/user_settings
    2. (Optional) Click the push icon Push settings icon to apply these settings to existing users.
  7. Select Enable User Profile Backup.
  8. For each .XML file for your environment, click Select File and add your customized file.
    The filename of your .XML displays to the left.
    • You must supply at least one .XML file for user profile backups to occur.
    • You do not need to supply one of each type of .XML file.
    • For assistance with your .XML files, see Microsoft's documentation.
  9. (Optional) Enter desired ScanState options.
  10. (Optional) Click the push icon Push settings icon to apply these settings to existing users.
  11. Click Save.

Step 3: (Optional) Manually start a user profile backup

To immediately start a user profile backup for a device, use the steps for the administration console or the CrashPlan app:

From the Administration console

  1. Open the administration console.
  2. Double-click the Code42 logo in the upper-left corner.
    The administration console command-line area opens.
  3. Enter: cc migration.backup.run <guid>
    Replace <guid> with the GUID of the device containing the user profile data you want to back up.
  4. Press Enter.

The USMT backup runs in the background of the CrashPlan app and a folder named "user_settings" is added to the backup selection, which contains the device's .MIG files.

From the CrashPlan app

  1. Open the CrashPlan app.
  2. Double-click the CrashPlan logo in the upper-right corner.
    The CrashPlan command-line area opens.
  3. Enter: migration.backup.run
  4. Press Enter.

The USMT backup runs in the background of the CrashPlan app and a folder named "user_settings" is added to the backup selection, which contains the device's .MIG files.

Step 4: Confirm user profiles are backed up

To confirm that all devices being migrated or upgraded have completed a user profile backup:

  1. From the administration console, select Devices.
  2. Select a device.
  3. From device details, ensure the Profile Backup date is current and the checkmark is green.
    A red exclamation point indicates the last Profile Backup failed.

Profile Backup Date

You can also search for specific devices.

Step 5: Prepare new devices

Prepare your new device. Your preparations may include:

  • Re-imaging the old device with a newer operating system.
  • Installing Windows 7 or Windows 8, if your new device does not have the appropriate operating system installed.

Step 6: Restore MIG files

Restore the .MIG files to the new device. The .MIG file can be found in the archive at the following path: C:\ProgramData\CrashPlan\user_settings\

You can restore the .MIG file to any location on the new device that is accessible to USMT, such as the Desktop. Restore the .MIG archive using one of these options:

Step 7: Run loadstate tool

Run the LoadState command to migrate the user's data to the new device.

The LoadState command migrates the data and settings from the .MIG file onto the new device:

  • The LoadState command has many command line options that require customization for your environment.
  • .XML configuration files must be created as input parameters for the command.
  • LoadState must be run from an elevated Windows command-prompt.
  • See Microsoft's documentation for LoadState syntax.
Device hand-off
Once the LoadState is completed, follow the steps below to set up the CrashPlan app for the user. Alternatively, you can give the device to the user and have the user complete the installation, restore files, and adopt the previous backup.

Step 8: Install CrashPlan on the new device

If you did not install the CrashPlan app on the new device in step 6, install it now.

  • Register the CrashPlan app under the same username as the old device.
  • Use your standard installation method (for example, push install, manual installation, etc.).
Do not adopt the old device
Adopting the old device before restoring files to the new device can cause files to be removed from the backup archive. See Restoring After An Adoption for more details.

Step 9: Restore files if necessary

If necessary, use CrashPlan to restore any missing files or folders to the new device.

Restoring files can be performed by:

Step 10: (Optional) adopt the old device

Adopting the old device saves time, bandwidth, and storage space, because the existing backup archive from the old device is assigned to the new device.

You may adopt the old device using one of two methods:

External resources