Skip to main content
Contact Support

Who is this article for?

CrashPlan Cloud
CrashPlan for Small Business
CrashPlan On-Premises

Find your product plan in the Code42 console on the Account menu.
Not a CrashPlan On-Premises customer? Search or browse Incydr and Instructor, CrashPlan Cloud, or CrashPlan for Small Business.

Instructor, no.

Incydr Professional, Enterprise, Horizon, and Gov F2, no.

Incydr Basic, Advanced, and Gov F1, no.

CrashPlan Cloud, no.

Retired product plans, yes.

CrashPlan for Small Business, no.

HOME
GETTING STARTED
RELEASE NOTES
FAQs
APIs
SYSTEM STATUS
Code42 Support

Windows XP end-of-life options with Code42 CrashPlan

  1. Last updated
  2. Save as PDF

Who is this article for?

CrashPlan Cloud
CrashPlan for Small Business
CrashPlan On-Premises

Find your product plan in the Code42 console on the Account menu.
Not a CrashPlan On-Premises customer? Search or browse Incydr and Instructor, CrashPlan Cloud, or CrashPlan for Small Business.

Instructor, no.

Incydr Professional, Enterprise, Horizon, and Gov F2, no.

Incydr Basic, Advanced, and Gov F1, no.

CrashPlan Cloud, no.

Retired product plans, yes.

CrashPlan for Small Business, no.

Overview

Code42 CrashPlan is an indispensable part of a safe, secure, and reliable migration of your Windows XP devices to Windows 7, 8, 8.1, or 10 now that Windows XP has reached its official end of support. Code42 CrashPlan serves as a secure repository of user data while devices are re-imaged, or while users move between devices.

Even more importantly, CrashPlan is a failsafe: in the event that the automated user migration process fails or stalls, user data will not be lost. Critical user data is restorable with just a few clicks of the mouse.

This article discusses a number of approaches to using CrashPlan as part of your migration strategy.

Newer version of this article
Version 4 is no longer supported. See Platform retirement for Windows XP and Windows Vista for the latest version of this content. 

Considerations

  • Allow enough time for a complete backup of user data before starting your migration process.
  • Consider including multiple destinations in your backup strategy to add extra layers of protection against data loss.
  • If you are upgrading your operating system but not re-imaging, you do not need the external software tools described in this article. Backing up user data with CrashPlan is still recommended to prevent data loss.

Before you begin

  • Plan a comprehensive migration strategy.
  • Test the procedures described in this article thoroughly before implementing.
  • Contact sales if you need assistance with your migration.

Definitions

This article frequently uses the following terms:

old device

The device being replaced or re-imaged. This article generally assumes that the old device is running Windows XP, but the concepts presented apply to all operating systems.

new device

The device that replaces the old device. This may be a brand new device, or it may be the old device after it has been re-imaged with a newer operating system.

Option 1: Use Code42 CrashPlan with Windows easy transfer

CrashPlan is a convenient and safe way to transfer a Windows Easy Transfer .MIG archive file from an old device to a new device.

Considerations

  • Best for small deployments or upgrades
  • Requires manual intervention by the user or IT staff
  • Extra layer of assurance: user data is backed up by CrashPlan in the event Windows Easy Transfer fails

Before you begin

This method requires the Microsoft Windows Easy Transfer program, which you can download from Microsoft.

Step 1: Run Windows easy transfer on the old device

  1. Run Windows Easy Transfer on the old device.
  2. Click This is my old computer at the prompt reading Which computer are you using now?
  3. Save the archive file (with the file extension .MIG) to a local folder that is backed up by CrashPlan.

Step 2: Confirm archive file is backed up

Confirm that the .MIG archive file has been successfully backed up using one of the following two methods:

Step 3: Prepare the new device

Prepare your new device as needed for your environment. Your preparations may include:

  • Re-imaging the old device with a newer operating system.
  • Installing a newer version of the operating system, if your new device does not have the appropriate operating system installed.

Step 4: Install CrashPlan on the new device

  • Install the Code42 app on the new device.
  • Register the Code42 app under the same Code42 environment username as the old device.
Do not Adopt The Old Device
Adopting the old device before you restore to the new device can cause files to be removed from the backup archive. See Restoring After An Adoption for more details.

Step 5: Restore .mig archive file

Restore the .MIG archive to the new device. You can restore the .MIG file to any location on the new device that is accessible to the Windows Easy Transfer program, such as the Desktop.

Restore the .MIG archive using one of these options:

Step 6: Run Windows easy transfer on the new device

Click This is my new computer when prompted with Which computer are you using now?

Step 7: Restore files if necessary

Use CrashPlan to restore any missing files or folders to the new device.

Restoring files can be performed by:

Reasons to restore

Files may need to be restored in three cases:

  • Windows Easy Transfer's migration of user data failed or was incomplete.
  • Windows Easy Transfer was configured to transfer only settings, and not files (in order to save time during the migration process).
  • Initial restore of user data was performed by IT staff, but user data on the old device changed before the new device was delivered to the user.

Restore location

Files can be restored to one of three places:

  • Desktop
  • Original location
  • Any selected folder
Restoring files to their original location
We recommend that you use caution when restoring to the original file locations, as application settings and default file locations may have changed in the new operating system.

Step 8: Adopt the old device (optional)

Adopting the old device saves time, bandwidth, and storage space, because the backup archives of the old device are assigned to the new device.

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

Option 2: Use CrashPlan with user state migration tool

CrashPlan works with Microsoft's User State Migration Tool (USMT) and, optionally, the Windows System Center Configuration Manager (SCCM) to migrate large deployments. USMT can be configured to transfer user data, or to transfer settings only (in order to reduce migration time).

Considerations

  • Best for large deployments.
  • Can be automated/scripted.
  • Extra layer of assurance: user data is backed up by CrashPlan, and settings are backed up with USMT.
  • Requires more planning, setup, and expertise than Windows Easy Transfer.

Code42 does not directly support the creation of Windows scripts or processes. This information is provided only to aid in the development of your own migration plan.

Before you begin

  • Familiarize yourself with the User State Migration Tool (USMT) before planning your own USMT-assisted migration.
  • Because this method uses command-line tools, you can automate or script the process with your Windows administration tools, or even run commands remotely.
  • Use USMT to back up settings and applications only. Excluding user data from USMT saves time when migrating to a new or re-imaged device.

Additional requirements

Windows user profile backup (Code42 app version 4.4)

Windows user profile backup using USMT requires Code42 app version 4.4. Follow these instructions to configure user profile backup and restore the profile to another computer.

Windows user profile backup (Code42 app version 5.0)

If you are using Code42 app version 5.0, follow the steps below to perform the user profile backup.

Step 1: Confirm user devices are backed up

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

Step 2: Run ScanState tool on the old device

Run the ScanState command to store your data, apps, and settings in a .MIG file:

  • The command that you use requires customization for your environment.
  • .XML configuration files must be created as input parameters for the command.
  • Verify that the .MIG file will be stored in a safe location, such as a network drive or a volume on the local computer that will not be overwritten by the operating system deployment step. Optionally, back up the .MIG file with the Code42 app.
  • See Microsoft documentation for scanstate syntax.

Step 3: Prepare the new device

Prepare your new device. Your preparations may include:

  • Re-imaging the old device with a newer operating system.
  • Installing a newer version of the operating system, if your new device does not have the appropriate operating system installed.

You can choose from a variety of migration tools. For example:

  • Windows System Center Configuration Manager (SCCM)
  • LANDesk
  • Dell Kace
  • CPMigrator
  • Dell OpenManage Deployment Toolkit

Please consult the documentation for your tools and utilities. Optionally, you can restore the .MIG file with the Code42 app.

Step 4: Run loadstate tool

Run the LoadState command to migrate the data and settings from the .MIG file to 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.
  • See Microsoft documentation for loadstate syntax.

Step 5: Install CrashPlan on the new device

Install the Code42 app on the new device.

  • Register the Code42 app under the same username as the old device.
  • Use your standard installation method (e.g., push install, manual installation, etc.).
Do not adopt the old device
Adopting the old device before you restore to the new device can cause old files to be removed from the backup archive. See Downloading Files After Replacing A Device for more details.

Step 6: Download files if necessary

If necessary, download any missing files or folders to the new device using CrashPlan.

Downloading files can be performed by:

Reasons to download files

Files may need to be restored in three cases:

  • Migration of user data failed or was incomplete.
  • Migration process was configured to transfer only settings, and not files (in order to save time during migration process).
  • Initial restore of user data was performed by IT staff, but user data on the old device changed before the new device was delivered to the user.
Download location

Files can be restored to one of three places:

  • Desktop
  • Original location
  • Any selected folder
Restoring files to their original location
We recommend that you use caution when restoring to the original file locations, as application settings and default file locations may have changed in the new operating system.

Step 7: Replace the old device (optional)

Replacing the old device saves time, bandwidth, and storage space, because the backup archives of the old device are assigned to the new device.

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

Option 3: Use CrashPlan with other migration tools or no additional tool

Considerations

  • Best for small deployments
  • Will not restore complete user state, unlike Windows Easy Transfer or USMT
  • Requires user self-service restore or IT staff intervention after the migration process

Before you begin

If user state or application settings need to be saved and restored, consider use of Windows Easy Transfer or USMT.

Step 1: Confirm CrashPlan backup is complete

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

Step 2: Prepare the new device

Prepare your new device as needed for your environment. Your preparations may include:

  • Re-imaging the old device with a newer operating system.
  • Installing a newer version of the operating system if the new device does not have the appropriate operating system installed.

You can prepare your new device without an additional migration tool.

You can also choose from a variety of migration tools. For example:

  • Windows System Center Configuration Manager (SCCM)
  • LANDesk
  • Dell Kace
  • CPMigrator
  • Dell OpenManage Deployment Toolkit

Please consult the documentation for your tools and utilities.

Step 3: Install CrashPlan on the new device

Install the Code42 app on the new or re-imaged device.

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

Step 4: Restore files if necessary

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

Restoring files can be performed by:

Reasons to restore

Files may need to be restored in three cases:

  • Migration of user data failed or was incomplete.
  • Migration process was configured to transfer only settings, and not files (in order to save time during the migration process).
  • Initial restore of user data was performed by IT staff, but user data on the old device changed before the new device was delivered to the user.

Restore location

Files can be restored to one of three places:

  • Desktop
  • Original location
  • Any selected folder
Restoring files to their original location
We recommend that you use caution when restoring to the original file locations, as application settings and default file locations may have changed in the new operating system.

Step 5: Adopt the old device (optional)

Adopting the old device saves time, bandwidth, and storage space, because the backup archives of the old device are assigned to the new device.

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

Code42 API and push restore automation

The Code42 API can be used to automate the restore process, allowing administrators to efficiently use CrashPlan to migrate large numbers of users to new devices, or to restore user data to devices after operating system upgrades or re-imaging.

You can use the API to automate the restore step in the Using CrashPlan With Other Migration Tools Or No Additional Tool section above. Remember to test your script and process before deploying on a large scale.

For more information, see the full article on Using The API To Automate Push Restores