Export (0) Print
Expand All

Refresh a Windows 7 Computer with Windows 8.1

Published: May 9, 2014

Applies To: Windows 8.1

This topic will show you how to use Microsoft Deployment Toolkit (MDT) 2013 Lite Touch Installation (LTI) to upgrade a Windows 7 computer to a Windows 8.1 computer using the computer refresh process. The refresh scenario, or computer refresh, is a reinstallation of an operating system on the same machine. You can refresh the machine to the same operating system as it’s currently running or to a later version.

For the purposes of this topic, we will use three machines: DC01, MDT01, and PC0001. DC01 is a domain controller and MDT01 is a Windows Server 2012 R2 Standard server. PC0001 is a machine with Windows 7 Service Pack 1 (SP1) that is going to be refreshed into a Windows 8.1 machine, with data and settings restored. MDT01 and PC0001 are members of the domain contoso.com for the fictitious Contoso Corporation. For more details on the setup for this topic, please see Proof-Of-Concept Environment.

Figure 1

Figure 1. The machines used in this topic.

Even though a computer will appear, to the end user, to be upgraded, a computer refresh is not, technically, an in-place upgrade. A computer refresh also involves taking care of user data and settings from the old installation and making sure to restore those at the end of the installation.

For a computer refresh with Microsoft Deployment Toolkit (MDT) 2013, you use the User State Migration Tool (USMT), which is part of the Windows Assessment and Deployment Kit (Windows ADK) for Windows 8.1, to migrate user data and settings. To complete a computer refresh you will:

  1. Back up data and settings locally, in a backup folder.

  2. Wipe the partition, except for the backup folder.

  3. Apply the new operating system image.

  4. Install other applications.

  5. Restore data and settings.

During the computer refresh, USMT uses a feature called Hard-Link Migration Store. When you use this feature, the files are simply linked in the file system, which allows for fast migration, even when there is a lot of data.

noteNote
In addition to the USMT backup, you can enable an optional full Windows Imaging (WIM) backup of the machine by configuring the MDT rules. If you do this, a .wim file is created in addition to the USMT backup. The .wim file will contain the entire volume from the computer, and helpdesk personnel can extract content from it if needed. Please note that this is a data WIM backup only. Using this backup to restore the entire machine is not a supported scenario.

By default, ScanState in USMT backs up all profiles on the machine, including local computer profiles. If you have a machine that has been in your environment for a while, it likely has several domain-based profiles on it, including those of former users. You can limit which profiles are backed up by configuring command-line switches to ScanState (added as rules in MDT 2013).

As an example, the following line configures USMT to migrate only domain user profiles and not profiles from the local SAM account database: ScanStateArgs=/ue:*\* /ui:CONTOSO\*

noteNote
You also can combine the preceding switches with the /uel switch, which excludes profiles that have not been accessed within a specific number of days. For example, adding /uel:60 will configure ScanState (or LoadState) not to include profiles that haven’t been accessed for more than 60 days.

In MDT 2013, there is a built-in script (ZTIAppXmlGen.wsf) that generates an USMT template on the fly during deployment. That template (ZTIAppXmlGen.xml) configures USMT to automatically capture user data (documents) that are associated with installed applications.

The script does this by parsing the HKEY_CLASSES_ROOT\Software\Classes registry key, and the resulting XML template configures USMT to capture files associated with all applications it finds. The exceptions are the following extensions: .mp3, .mov, .wma, .wmv, .chm, .evt, .evtx, .exe, .com, and .fon. The script is hardcoded to exclude these extensions.

In addition to the command-line switches that control which profiles to migrate, the XML templates control exactly what data is being migrated. You can control data within and outside the user profiles

In this section, you learn to migrate additional data using a custom template. You configure the environment to use a custom USMT XML template that will:

  1. Back up the C:\Data folder (including all files and folders).

  2. Scan the local disk for PDF documents (*.pdf files) and restore them into the C:\Data\PDF Documents folder on the destination machine.

The custom USMT template is named MigContosoData.xml, and you can find it in the sample files for this documentation, which include:

In order to use the custom MigContosoData.xml USMT template, you need to copy it to the MDT Production deployment share and update the CustomSettings.ini file. In these steps, we assume you have downloaded the MigContosoData.xml file.

  1. Using File Explorer, copy the MigContosoData.xml file to the E:\MDTProduction\Tools\x64\USMT5 folder.

  2. Using Notepad, edit the E:\MDTProduction\Control\CustomSettings.ini file. After the USMTMigFiles002=MigUser.xml line add the following line:

    USMTMigFiles003=MigContosoData.xml
    
  3. Save the CustomSettings.ini file.

After adding the additional USMT template and configuring the CustomSettings.ini file to use it, you are now ready to refresh a Windows 7 SP1 client to Windows 8.1. In these steps, we assume you have a Windows 7 SP1 client named PC0001 in your environment that is ready for a refresh to Windows 8.1.

noteNote
MDT 2013 also supports an offline computer refresh. For more info on that scenario, see the USMTOfflineMigration property in the MDT 2013 documentation.

  1. On PC0001, log on as CONTOSO\Administrator. Start the Lite Touch Deploy Wizard by executing \\MDT01\MDTProduction$\Scripts\Litetouch.vbs. Complete the deployment guide using the following settings:

    1. Select a task sequence to execute on this computer: Windows 8.1 Enterprise x64 RTM

    2. Computer name: <default>

    3. Specify where to save a complete computer backup: Do not back up the existing computer

      noteNote
      Skip this optional full WIM backup. The USMT backup will still run.

  2. Select one or more applications to install: Install - Adobe Reader XI - x86

  3. The setup now starts and does the following:

    1. Backs up user settings and data using USMT.

    2. Installs the Windows 8.1 Enterprise x64 operating system.

    3. Installs the added application(s).

    4. Updates the operating system via your local Windows Server Update Services (WSUS) server.

    5. Restores user settings and data using USMT.

Figure 2

Figure 2. Starting the computer refresh from the running Windows7 SP1 client.

Was this page helpful?
(1500 characters remaining)
Thank you for your feedback

Community Additions

ADD
Show:
© 2014 Microsoft