Optimize protection and migration of Windows user state data

Windows user state data includes certain types of personalized settings for the operating system, most web browsers, and particular applications. Using Microsoft's User State Migration Tool (USMT), you can export this data to a .mig file on behalf of users, or they can do it themselves. By protecting this data with Connected, users who replace or re-image their computer can then restore it in addition to their Connected data.

To optimize the protection and migration of Windows user state data for devices running Agent 4.9.0, or later, Connected provides specific backup policy and restore options. The Back up Windows user state files (.mig) policy option configures the Agent to back up all .mig files except those excluded by drive or Smart Scan, regardless of any admin or user rules that exclude them. Then, when starting a restore request that includes a .mig file backed up per this option, users can select the Import Windows User State restore option to import the file automatically when the restore completes. This expanded protection and automated import of .mig files help simplify the protection and migration of Windows users state data.

Agents without the Back up Windows user state files (.mig) policy option enabled or those that do not support it, back up .mig files only if allowed by admin or explicit user rules. However, Connected does not support automated import of a .mig file backed up based on rules, so after the restore completes, either you or the user must import it.

Before you begin

Ensure that you are familiar with USMT, including how to install, configure, and use it. For technical information about USMT, including how to download it, see Microsoft's User State Migration Tool (USMT) Technical Reference. For information about how to use USMT, see Microsoft's User State Migration Tool (USMT) Overview.

To configure optimized protection of Windows user state data

  1. Update existing backup policies or create new ones that have the Back up Windows user state files (.mig) option enabled.

    TIP: When this option is enabled, the Backup Status report includes a column that identifies the last time Connected backed up a .mig file for each device. You can monitor this column to identify users with missing or outdated user state data.

  2. Install USMT on each Windows-based computer that Connected supports.

    USMT provides two command-line applications for migrating settings (ScanState for data export and LoadState for data import), which must each run with administrative privileges. Either you or the user can install USMT directly on the user's computer, or you can install it on an administrative computer and then install it remotely for each user.

    NOTE: If you install USMT outside of the default install path, you must specify its location in the Windows PATH environment variable.

  3. Determine which user state data to protect for migration and how to configure USMT for its export.

    USMT can migrate many types of user data, as defined by command-line parameters or XML files. Determine which data you want to export and how to specify your choices. Typically, you should export data users are most likely to customize, such as user-specific OS settings and application settings. There is no need to export user files, folders, or ACLs because Connected backups already include this data.

  4. Perform a test migration using USMT directly, using the command-line parameters or XML files you plan to deploy.

    Test user data migration using the USMT ScanState application to export the data from one computer and the LoadState application to import it into a different computer. Testing migration before initiating it through Connected enables you to verify your USMT export configuration and ensures that you migrate the data you need.

  5. Implement a method to trigger the export of user state data into a .mig file using the USMT ScanState application.

    Connected does not generate .mig files, so you must implement a custom solution. Possible options include:

    • Export user state data automatically on a set schedule, such as once per day or week.

    • Provide users instruction on how and when to manually export their user state data.

    • Remotely trigger the export of user state data based on specific criteria.

    Factor in the pros and cons of each option when creating a solution, keeping in mind that Connected backs up .mig files only if they change. For example, frequent automated exports might require many backups if user state changes often but provide the best chance for current data. In contrast, on-demand exports do not require many backups but might be out of date when needed.

    NOTE: If an Agent supports multiple users on one computer, export the data for each user separately.

To trigger automated migration of Windows user state data

If the backup policy for a device running Agent 4.9.0, or later, has the Back up Windows user state files (.mig) option enabled, when you start a restore request that includes a .mig file backed up per this option, you can select that file for automatic import when the restore completes. Before using this feature for the first time, review the complete set of its requirements.