Deploy Windows 10 with System Center 2012 R2 Configuration Manager

For more details on the setup for this topic, please see Deploy Windows 10 with the Microsoft Deployment Toolkit.

Figure 1. The machines used in this topic.

In this section

• Integrate Configuration Manager with MDT
• Prepare for Zero Touch Installation of Windows with Configuration Manager
• Create a custom Windows PE boot image with Configuration Manager
• Add a Windows 10 operating system image using Configuration Manager
• Create an application to deploy with Windows 10 using Configuration Manager
• Add drivers to a Windows 10 deployment with Windows PE using Configuration Manager
• Create a task sequence with Configuration Manager and MDT
• Finalize the operating system configuration for Windows 10 deployment with Configuration Manager
• Deploy Windows 10 using PXE and Configuration Manager
• Monitor the Windows 10 deployment with Configuration Manager
• Refresh a Windows 7 SP1 client with Windows 10 using Configuration Manager
• Replace a Windows 7 SP1 client with Windows 10 using Configuration Manager

Components of Configuration Manager operating system deployment

Operating system deployment with Configuration Manager is part of the normal software distribution infrastructure, but there are additional components. For example, operating system deployment in Configuration Manager may use the State Migration Point role, which is not used by normal application deployment in Configuration Manager. This section describes the Configuration Manager components involved with the deployment of an operating system, such as Windows 10.

• State migration point (SMP). The state migration point is used to store user state migration data during computer replace scenarios.
• Distribution point (DP). The distribution point is used to store all packages in Configuration Manager, including the operating system deployment-related packages.
• Software update point (SUP). The software update point, which is normally used to deploy updates to existing machines, also can be used to update an operating system as part of the deployment process. You also can use offline servicing to update the image directly on the Configuration Manager server.
• Reporting services point. The reporting services point can be used to monitor the operating system deployment process.
• Boot images. Boot images are the Windows Preinstallation Environment (Windows PE) images Configuration Manager uses to start the deployment.
• Operating system images. The operating system image package contains only one file, the custom .wim image. This is typically the production deployment image.
• Operating system installers. The operating system installers were originally added to create reference images using Configuration Manager. Instead, we recommend that you use MDT Lite Touch to create your reference images. For more information on how to create a reference image, see Create a Windows 10 reference image.
• Drivers. Like MDT Lite Touch, Configuration Manager also provides a repository (catalog) of managed device drivers.
• Task sequences. The task sequences in Configuration Manager look and feel pretty much like the sequences in MDT Lite Touch, and they are used for the same purpose. However, in Configuration Manager the task sequence is delivered to the clients as a policy via the Management Point (MP). MDT provides additional task sequence templates to Configuration Manager.
  Note Configuration Manager SP1 along with the Windows Assessment and Deployment Kit (ADK) for Windows 10 are required to support management and deployment of Windows 10.

See also

• Microsoft Deployment Toolkit downloads and resources
• Windows deployment tools
• Deploy Windows 10 with the Microsoft Deployment Toolkit
• Upgrade to Windows 10 with the Microsoft Deployment Toolkit
• Deploy Windows To Go in your organization
• Sideload Windows Store apps
• Windows ADK for Windows 10

https://docs.microsoft.com/en-us/windows/deployment/deploy-windows-sccm/deploy-windows-10-with-system-center-2012-r2-configuration-manager