User State Migration Tool (USMT)

To capture and restore the user state as part of your operating system deployment, you will need a USMT package that points to the USMT source files. Create this package in the Packages node under Application Management in the Software Library workspace.

Note
When you install Configuration Manager SP1 at the top-level site, Setup automatically creates the USMT 5.0 package.

The required version of USMT is dependent on the operating system version that you deploy. The following table provides information about the required USMT versions.

¹You can only deploy Windows 8 from a site server that is running Configuration Manager SP1.

You can install the USMT versions at the following locations:

• USMT 5.0 is distributed in Windows Assessment and Deployment Kit (Windows ADK) to capture the user state from one operating system and then restore it on another operating system. For a description of different migration scenarios for USMT 5.0, see Common Migration Scenarios.
  
  
• USMT 4.0 is distributed in Windows Automated Installation Kit (Windows AIK), to capture the user state from one operating system and then restore it to another operating system. For a description of different migration scenarios for USMT 4.0, see Common Migration Scenarios.
  
  
• USMT 3.0.1 is available from the Microsoft Download Center.
  
  

For more information about capturing and restoring user state, see How to Manage the User State in Configuration Manager.

Windows PE

Windows PE is a Windows operating system with limited services that is used during the pre-installation and deployment of Windows operating systems. For more information about the boot images that provide Windows PE, see Planning for Boot Image Deployments in Configuration Manager.

• For Configuration Manager SP1 only:
  
  Configuration Manager uses Windows PE 4, which is built on the Windows 8 operating system platform. Windows PE 4 is distributed as part of the Windows ADK for Windows 8.
  
  
• For Configuration Manager with no service pack only:
  
  Configuration Manager uses Windows PE 3, which is built on the Windows 7 operating system platform. Windows PE 3 is distributed as part of the Windows AIK for Windows 7.
  
  

For Configuration Manager SP1 only:

Windows Assessment and Deployment Kit (Windows ADK) for Windows 8

Windows ADK is a set of tools and documentation that support the configuration and deployment of Windows operating systems. Starting in Configuration Manager SP1, Configuration Manager uses Windows ADK to automate Windows installations, capture Windows images, migrate user profiles and data, and so on.

The following features of the Windows ADK must be installed on site server of the top-level site of the hierarchy, and on the site server of each primary site in the hierarchy:

• User State Migration Tool (USMT)
  
  
• Windows Deployment Tools
  
  
• Windows Preinstallation Environment (Windows PE)
  
  

Note
You must manually install the Windows ADK on each computer that will host a central administration site or primary site server before you install the Configuration Manager site. Before you can upgrade Configuration Manager with no service pack, you must first uninstall the Windows Automated Installation Kit (Windows AIK) before you can install the Windows ADK.

For more information about Windows ADK, see Windows Deployment with the Windows ADK..

For Configuration Manager with no service pack only:

Windows Automated Installation Kit (Windows AIK) for Windows 7

Windows AIK is a set of tools and documentation that support the configuration and deployment of Windows operating systems. Configuration Manager with no service pack, uses Windows AIK to automate Windows installations, capture Windows images, migrate user profiles and data, and so on. For more information about Windows AIK, see Windows Automated Installation Kit for Windows 7.

Note
When you use Configuration Manager without service pack to install a central administration site or primary site, Configuration Manager automatically installs the Windows AIK on the site server if Windows AIK is not already installed.

Internet Information Services (IIS) on the site system servers to run the distribution point, state migration point, and management point

For more information about this requirement, see the Prerequisites for Site System Roles section in the Supported Configurations for Configuration Manager topic.

Windows Deployment Services (WDS)

WDS is needed for PXE deployments and when you use multicast to optimize bandwidth in your deployments. For more information, see Windows Deployment Services (WDS) in this topic.

Dynamic Host Configuration Protocol (DHCP)

DHCP is required for PXE deployments. You must have a functioning DHCP server with an active host to deploy operating systems by using PXE.

For more information about PXE deployments, see Planning for PXE-Initiated Operating System Deployments in Configuration Manager.

Supported operating systems and hard disk configurations

For more information about the operating system versions and hard disk configurations that are supported by Configuration Manager when you deploy operating systems, see Supported Operating Systems and Hard Disk Configurations for Operating System Deployment.

Windows device drivers

Windows device drivers can be used when you install the operating system on the destination computer and when you run Windows PE by using a boot image. For more information about device drivers, see Planning a Device Driver Strategy in Configuration Manager.

Operating system image

Depending on the method that you plan to use to deploy operating system images, there are several dependencies that must be considered. For more information about these dependencies, see Determine the Operating System Deployment Method to Use in Configuration Manager.

Driver catalog

To deploy a device driver, you must import the device driver, enable it, and make it available on a distribution point that the Configuration Manager client can access. For more information about the driver catalog, see Planning a Device Driver Strategy in Configuration Manager.

Management point

Management points transfer information between client computers and the Configuration Manager site. The client uses a management point to run any task sequences that are required to complete the operating system deployment.

For more information about task sequences, see Planning a Task Sequences Strategy in Configuration Manager

Distribution point

Distribution points are used in most deployments to store the data that is used to deploy an operating system, such as the operating system image or device driver packages. Task sequences typically retrieve data from a distribution point to deploy the operating system.

For more information about task sequences, see Planning a Task Sequences Strategy in Configuration Manager

For more information about how to install distribution points and manage content, see Configuring Content Management in Configuration Manager

PXE-enabled distribution point

To deploy PXE-initiated deployments, you must configure a distribution point to accept PXE requests from clients. For more information about how to configure the distribution point, see Planning for PXE-Initiated Operating System Deployments in Configuration Manager.

Multicast-enabled distribution point

To optimize your operating system deployments by using multicast, you must configure a distribution point to support multicast. For more information about how to configure the distribution point to support multicast, see Planning a Multicast Strategy in Configuration Manager.

State migration point

When you capture and restore user state data for side-by-side and refresh deployments, you must configure a state migration point to store the user state data on another computer. For more about how to configure the state migration point, see Install Site System Roles

For information about how to capture and restore user state, see How to Manage the User State in Configuration Manager.

Reporting services point

To use Configuration Manager reports for operating system deployments, you must install and configure a reporting services point.

For more information, see Configuring Reporting in Configuration Manager.

Security permissions for operating system deployments

The Operating System Deployment Manager security role is a built-in role that cannot be changed. However, you can copy the role, make changes, and then save these changes as a new custom security role. Here are some of the permissions that apply directly to operating system deployments:

• Boot Image Package: Create, Delete, Modify, Modify Folder, Move Object, Read, Set Security Scope
  
  
• Device Drivers: Create, Delete, Modify, Modify Folder, Modify Report, Move Object, Read, Run Report
  
  
• Driver Package: Create, Delete, Modify, Modify Folder, Move Object, Read, Set Security Scope
  
  
• Operating System Image: Create, Delete, Modify, Modify Folder, Move Object, Read, Set Security Scope
  
  
• Operating System Installation Package: Create, Delete, Modify, Modify Folder, Move Object, Read, Set Security Scope
  
  
• Task Sequence Package: Create, Create Task Sequence Media, Delete, Modify, Modify Folder, Modify Report, Move Object, Read, Run Report, Set Security Scope
  
  

For more information about custom security roles, see the Create Custom Security Roles section in the Configuring Security for Configuration Manager topic.

Security scopes for operating system deployments

Use security scopes to provide administrative users with access to the securable objects used in operating system deployments, such as operating system and boot images, driver packages, and task sequence packages. For more information about security scopes, see Planning for Security Scopes in the Planning for Role-Based Administration section in the Planning for Security in Configuration Manager topic.