Deploy Windows 10 With Sccm

-->

Deploy Windows 10 With Sccm Free
Deploying Windows 10 With Sccm Step By Step

Deploy In-Place Windows 10 via SCCM. Hello everyone, I really hope you are good because this article goes to show you how to deploy Windows 10 “In-Place” Task Sequence via SCCM. The in-place image allows you to upgrade Windows 7/8 to Windows 10 with keeping all personal information and programs, the second type is scratch which is most. Upgrade to Windows 10 with System Center Configuration Manager. The simplest path to upgrade PCs currently running Windows 7, Windows 8, or Windows 8.1 to Windows 10 is through an in-place upgrade. You can use a System Center Configuration Manager task sequence to completely automate the process. Prerequisites: SCCM 2012 R2 SP1 Cu1.

Applies to

Windows 10 versions 1507, 1511

Important

For instructions to deploy the most recent version of Windows 10 with Configuration Manager, see Scenarios to deploy enterprise operating systems with System Center Configuration Manager.Configuration Manager 2012 and 2012 R2 provide support for Windows 10 versions 1507 and 1511 only. Later versions of Windows 10 require an updated Configuration Manager release. For a list of Configuration Manager versions and the corresponding Windows 10 client versions that are supported, see Support for Windows 10 for System Center Configuration Manager.

If you have Microsoft System Center 2012 R2 Configuration Manager in your environment, you will most likely want to use it to deploy Windows 10. This topic will show you how to set up Configuration Manager for operating system deployment and how to integrate Configuration Manager with the Microsoft Deployment Toolkit (MDT).

For the purposes of this topic, we will use four machines: DC01, CM01, PC0003, and PC0004. DC01 is a domain controller and CM01 is a machine running Windows Server 2012 R2 standard. PC0003 and PC0004 are machines with Windows 7 SP1, on which Windows 10 will be deployed via both refresh and replace scenarios. In addition to these four ready-made machines, you could also include a few blank virtual machines to be used for bare-metal deployments. DC01, CM01, PC003, and PC0004 are all members of the domain contoso.com for the fictitious Contoso Corporation. 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

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.

In this guide

This guide provides end-to-end instructions to install and configure System Center Configuration Manager, and use it to deploy a Windows 10 image. Depending on the speed of your Hyper-V host, the procedures in this guide will require 6-10 hours to complete.

Topics and procedures in this guide are summarized in the following table. An estimate of the time required to complete each procedure is also provided. Time required to complete procedures will vary depending on the resources available to the Hyper-V host and assigned to VMs, such as processor speed, memory allocation, disk speed, and network speed.

Topic	Description	Time
Install prerequisites	Install prerequisite Windows Server roles and features, download, install and configure SQL Server, configure firewall rules, and install the Windows ADK.	60 minutes
Install System Center Configuration Manager	Download System Center Configuration Manager, configure prerequisites, and install the package.	45 minutes
Download MDOP and install DaRT	Download the Microsoft Desktop Optimization Pack 2015 and install DaRT 10.	15 minutes
Prepare for Zero Touch installation	Prerequisite procedures to support Zero Touch installation.	60 minutes
Create a boot image for Configuration Manager	Use the MDT wizard to create the boot image in Configuration Manager.	20 minutes
Create a Windows 10 reference image	This procedure can be skipped if it was done previously, otherwise instructions are provided to create a reference image.	0-60 minutes
Add a Windows 10 operating system image	Add a Windows 10 operating system image and distribute it.	10 minutes
Create a task sequence	Create a Configuration Manager task sequence with MDT integration using the MDT wizard	15 minutes
Finalize the operating system configuration	Enable monitoring, configure rules, and distribute content.	30 minutes
Deploy Windows 10 using PXE and Configuration Manager	Deploy Windows 10 using Configuration Manager deployment packages and task sequences.	60 minutes
Replace a client with Windows 10 using Configuration Manager	Replace a client computer with Windows 10 using Configuration Manager.	90 minutes
Refresh a client with Windows 10 using Configuration Manager	Use a task sequence to refresh a client with Windows 10 using Configuration Manager and MDT	90 minutes

Install prerequisites

Before installing System Center Configuration Manager, we must install prerequisite services and features. Type the following command at an elevated Windows PowerShell prompt on SRV1:
If the request to add features fails, retry the installation by typing the command again.
Download SQL Server 2014 SP2 from the Microsoft Evaluation Center as an .ISO file on the Hyper-V host computer. Save the file to the C:VHD directory.
When you have downloaded the file SQLServer2014SP2-FullSlipstream-x64-ENU.iso and placed it in the C:VHD directory, type the following command at an elevated Windows PowerShell prompt on the Hyper-V host:
This command mounts the .ISO file to drive D on SRV1.
Type the following command at an elevated Windows PowerShell prompt on SRV1 to install SQL Server:
Installation will take several minutes. When installation is complete, the following output will be displayed:
Type the following commands at an elevated Windows PowerShell prompt on SRV1:
Download and install the latest Windows Assessment and Deployment Kit (ADK) on SRV1 using the default installation settings. The current version is the ADK for Windows 10, version 1703. Installation might require several minutes to acquire all components.

Install System Center Configuration Manager

On SRV1, temporarily disable IE Enhanced Security Configuration for Administrators by typing the following commands at an elevated Windows PowerShell prompt:
Download System Center Configuration Manager and Endpoint Protection on SRV1 (download the executable file anywhere on SRV1), double-click the file, enter C:configmgr for Unzip to folder, and click Unzip. The C:configmgr directory will be automatically created. Click OK and then close the WinZip Self-Extractor dialog box when finished.
Before starting the installation, verify that WMI is working on SRV1. See the following examples. Verify that Running is displayed under Status and True is displayed next to TcpTestSucceeded:
You can also verify WMI using the WMI console by typing wmimgmt.msc, right-clicking WMI Control (Local) in the console tree, and then clicking Properties.
If the WMI service is not started, attempt to start it or reboot the computer. If WMI is running but errors are present, see WMIDiag for troubleshooting information.
To extend the Active Directory schema, type the following command at an elevated Windows PowerShell prompt:
Temporarily switch to the DC1 VM, and type the following command at an elevated command prompt on DC1:
Right-click ADSI Edit, click Connect to, select Default (Domain or server that you logged in to) under Computer and then click OK.
Expand Default naming context>DC=contoso,DC=com, and then in the console tree right-click CN=System, point to New, and then click Object.
Click container and then click Next.
Next to Value, type System Management, click Next, and then click Finish.
Right-click CN=system Management and then click Properties.
On the Security tab, click Add, click Object Types, select Computers, and click OK.
Under Enter the object names to select, type SRV1 and click OK.
The SRV1 computer account will be highlighted, select Allow next to Full control.
Click Advanced, click SRV1 (CONTOSOSRV1$) and click Edit.
Next to Applies to, choose This object and all descendant objects, and then click OK three times.
Close the ADSI Edit console and switch back to SRV1.
To start Configuration Manager installation, type the following command at an elevated Windows PowerShell prompt on SRV1:
Provide the following in the System Center Configuration Manager Setup Wizard:
- Before You Begin: Read the text and click Next.
- Getting Started: Choose Install a Configuration Manager primary site and select the Use typical installation options for a stand-alone primary site checkbox.
  - Click Yes in response to the popup window.
- Product Key: Choose Install the evaluation edition of this Product.
- Microsoft Software License Terms: Read the terms and then select the I accept these license terms checkbox.
- Prerequisite Licenses: Review license terms and select all three checkboxes on the page.
- Prerequisite Downloads: Choose Download required files and enter c:windowstemp next to Path.
- Site and Installation Settings: Site code: PS1, Site name: Contoso.
  - use default settings for all other options
- Usage Data: Read the text and click Next.
- Service Connection Point Setup: Accept the default settings (SRV1.contoso.com is automatically added under Select a server to use).
- Settings Summary: Review settings and click Next.
- Prerequisite Check: No failures should be listed. Ignore any warnings and click Begin Install.
There should be at most three warnings present: WSUS on site server, configuration for SQL Server memory usage, and SQL Server process memory allocation. These warnings can safely be ignored in this test environment.
Depending on the speed of the Hyper-V host and resources allocated to SRV1, installation can require approximately one hour. Click Close when installation is complete.
If desired, re-enable IE Enhanced Security Configuration at this time on SRV1:

Download MDOP and install DaRT

Important

This step requires an MSDN subscription or volume licence agreement. For more information, see Ready for Windows 10: MDOP 2015 and more tools are now available.If your organization qualifies and does not already have an MSDN subscription, you can obtain a free MSDN subscription with BizSpark.

Download the Microsoft Desktop Optimization Pack 2015 to the Hyper-V host using an MSDN subscription. Download the .ISO file (mu_microsoft_desktop_optimization_pack_2015_x86_x64_dvd_5975282.iso, 2.79 GB) to the C:VHD directory on the Hyper-V host.
Type the following command at an elevated Windows PowerShell prompt on the Hyper-V host to mount the MDOP file on SRV1:
Type the following command at an elevated Windows PowerShell prompt on SRV1:
Install DaRT 10 using default settings.
Type the following commands at an elevated Windows PowerShell prompt on SRV1:

Prepare for Zero Touch installation

This section contains several procedures to support Zero Touch installation with System Center Configuration Manager.

Create a folder structure

Type the following commands at a Windows PowerShell prompt on SRV1:

Enable MDT ConfigMgr integration

On SRV1, click Start, type configmgr, and then click Configure ConfigMgr Integration.
Type PS1 next to Site code, and then click Next.
Verify The process completed successfully is displayed, and then click Finish.

Configure client settings

On SRV1, click Start, type configuration manager, right-click Configuration Manager Console, and then click Pin to Taskbar.
Click Desktop, and then launch the Configuration Manager console from the taskbar.
If the console notifies you that an update is available, click OK. It is not necessary to install updates to complete this lab.
In the console tree, open the Administration workspace (in the lower left corner) and click Client Settings.
In the display pane, double-click Default Client Settings.
Click Computer Agent, next to Organization name displayed in Software Center type Contoso, and then click OK.

Configure the network access account

In the Administration workspace, expand Site Configuration and click Sites.
On the Home ribbon at the top of the console window, click Configure Site Components and then click Software Distribution.
On the Network Access Account tab, choose Specify the account that accesses network locations.
Click the yellow starburst and then click New Account.
Click Browse and then under Enter the object name to select, type CM_NAA and click OK.
Next to Password and Confirm Password, type pass@word1, and then click OK twice.

Configure a boundary group

In the Administration workspace, expand Hierarchy Configuration, right-click Boundaries and then click Create Boundary.
Next to Description, type PS1, next to Type choose Active Directory Site, and then click Browse.
Choose Default-First-Site-Name and then click OK twice.
In the Administration workspace, right-click Boundary Groups and then click Create Boundary Group.
Next to Name, type PS1 Site Assignment and Content Location, click Add, select the Default-First-Site-Name boundary and then click OK.
On the References tab in the Create Boundary Group window select the Use this boundary group for site assignment checkbox.
Click Add, select the SRV1.contoso.com checkbox, and then click OK twice.

Add the state migration point role

In the Administration workspace, expand Site Configuration, click Sites, and then in on the Home ribbon at the top of the console click Add Site System Roles.
In the Add site System Roles Wizard, click Next twice and then on the Specify roles for this server page, select the State migration point checkbox.
Click Next, click the yellow starburst, type C:MigData for the Storage folder, and click OK.
Click Next, and then verify under Boundary groups that PS1 Site Assignment and Content Location is displayed.
Click Next twice and then click Close.

Enable PXE on the distribution point

Important

Before enabling PXE in Configuration Manager, ensure that any previous installation of WDS does not cause conflicts. Configuration Manager will automatically configure the WDS service to manage PXE requests. To disable a previous installation, if it exists, type the following commands at an elevated Windows PowerShell prompt on SRV1:

Determine the MAC address of the internal network adapter on SRV1. To determine this, type the following command at an elevated Windows PowerShell prompt on SRV1:
If the internal network adapter, assigned an IP address of 192.168.0.2, is not named 'Ethernet' then replace the name 'Ethernet' in the previous command with the name of this network adapter. You can review the names of network adapters and the IP addresses assigned to them by typing ipconfig.
In the System Center Configuration Manager console, in the Administration workspace, click Distribution Points.
In the display pane, right-click SRV1.CONTOSO.COM and then click Properties.
On the PXE tab, select the following settings:
- Enable PXE support for clients. Click Yes in the popup that appears.
- Allow this distribution point to respond to incoming PXE requests
- Enable unknown computer support. Click OK in the popup that appears.
- Require a password when computers use PXE
- Password and Confirm password: pass@word1
- Respond to PXE requests on specific network interfaces: Click the yellow starburst and then enter the MAC address determined in the first step of this procedure.
  See the following example:
Click OK.
Wait for a minute, then type the following command at an elevated Windows PowerShell prompt on SRV1, and verify that the files displayed are present:
If these files are not present in the C:RemoteInstall directory, verify that the REMINST share is configured as C:RemoteInstall. You can view the properties of this share by typing 'net share REMINST' at a command prompt. If the share path is set to a different value, then replace C:RemoteInstall with your REMINST share path.You can also type the following command at an elevated Windows PowerShell prompt to open the Configuration Manager Trace Log Tool. In the tool, click File, click Open, and then open the distmgr.log file. If errors are present, they will be highlighted in red:
The log file will updated continuously while Configuration Manager is running. Wait for Configuration Manager to repair any issues that are present, and periodically re-check that the files are present in the REMINST share location. Close the Configuration Manager Trace Log Tool when done. You will see the following line in distmgr.log that indicates the REMINST share is being populated with necessary files:
Running: WDSUTIL.exe /Initialize-Server /REMINST:'C:RemoteInstall'
Once the files are present in the REMINST share location, you can close the cmtrace tool.

Create a branding image file

If you have a bitmap (.BMP) image for suitable use as a branding image, copy it to the C:SourcesOSDBranding folder on SRV1. Otherwise, use the following step to copy a simple branding image.
Type the following command at an elevated Windows PowerShell prompt:
You can open C:SourcesOSDBrandingcontoso.bmp in MSPaint.exe if desired to customize this image.

Create a boot image for Configuration Manager

In the Configuration Manager console, in the Software Library workspace, expand Operating Systems, right-click Boot Images, and then click Create Boot Image using MDT.
On the Package Source page, under Package source folder to be created (UNC Path):, type SRV1Sources$OSDBootZero Touch WinPE x64, and then click Next.
- The Zero Touch WinPE x64 folder does not yet exist. The folder will be created later.
On the General Settings page, type Zero Touch WinPE x64 next to Name, and click Next.
On the Options page, under Platform choose x64, and click Next.
On the Components page, in addition to the default selection of Microsoft Data Access Components (MDAC/ADO) support, select the Microsoft Diagnostics and Recovery Toolkit (DaRT) checkbox, and click Next.
On the Customization page, select the Use a custom background bitmap file checkbox, and under UNC path, type or browse to SRV1Sources$OSDBrandingcontoso.bmp, and then click Next twice. It will take a few minutes to generate the boot image.
Click Finish.
In the console display pane, right-click the Zero Touch WinPE x64 boot image, and then click Distribute Content.
In the Distribute Content Wizard, click Next, click Add and select Distribution Point, select the SRV1.CONTOSO.COM checkbox, click OK, click Next twice, and then click Close.
Use the CMTrace application to view the distmgr.log file again and verify that the boot image has been distributed. To open CMTrace, type the following command at an elevated Windows PowerShell prompt on SRV1:
In the trace tool, click Tools on the menu and choose Find. Search for 'STATMSG: ID=2301'. For example:
You can also review status by clicking the Zero Touch WinPE x64 image, and then clicking Content Status under Related Objects in the bottom right-hand corner of the console, or by entering MonitoringOverviewDistribution StatusContent Status on the location bar in the console. Double-click Zero Touch WinPE x64 under Content Status in the console tree and verify that a status of Successfully distributed content is displayed on the Success tab.
Next, in the Software Library workspace, double-click Zero Touch WinPE x64 and then click the Data Source tab.
Select the Deploy this boot image from the PXE-enabled distribution point checkbox, and click OK.
Review the distmgr.log file again for 'STATMSG: ID=2301' and verify that there are three folders under C:RemoteInstallSMSImages with boot images. See the following example:
The first two images (*.wim files) are default boot images. The third is the new boot image with DaRT.

Create a Windows 10 reference image

If you have already completed steps in Deploy Windows 10 in a test lab using Microsoft Deployment Toolkit then you have already created a Windows 10 reference image. In this case, skip to the next procedure in this guide: Add a Windows 10 operating system image. If you have not yet created a Windows 10 reference image, complete the steps in this section.

In Step by step guide: Deploy Windows 10 in a test lab the Windows 10 Enterprise .iso file was saved to the c:VHD directory as c:VHDw10-enterprise.iso. The first step in creating a deployment share is to mount this file on SRV1. To mount the Windows 10 Enterprise DVD on SRV1, open an elevated Windows PowerShell prompt on the Hyper-V host computer and type the following command:
Verify that the Windows Enterprise installation DVD is mounted on SRV1 as drive letter D.
The Windows 10 Enterprise installation files will be used to create a deployment share on SRV1 using the MDT deployment workbench. To open the deployment workbench, click Start, type deployment, and then click Deployment Workbench.
In the Deployment Workbench console, right-click Deployment Shares and select New Deployment Share.
Use the following settings for the New Deployment Share Wizard:
- Deployment share path: C:MDTBuildLab
- Share name: MDTBuildLab$
- Deployment share description: MDT build lab
- Options: click Next to accept the default
- Summary: click Next
- Progress: settings will be applied
- Confirmation: click Finish
Expand the Deployment Shares node, and then expand MDT build lab.
Right-click the Operating Systems node, and then click New Folder. Name the new folder Windows 10. Complete the wizard using default values and click Finish.
Right-click the Windows 10 folder created in the previous step, and then click Import Operating System.
Use the following settings for the Import Operating System Wizard:
- OS Type: Full set of source files
- Source: D:
- Destination: W10Ent_x64
- Summary: click Next
- Confirmation: click Finish
For purposes of this test lab, we will not add applications, such as Microsoft Office, to the deployment share. For information about adding applications, see the Add applications section of the Create a Windows 10 reference image topic in the TechNet library.
The next step is to create a task sequence to reference the operating system that was imported. To create a task sequence, right-click the Task Sequences node under MDT Build Lab and then click New Task Sequence. Use the following settings for the New Task Sequence Wizard:
- Task sequence ID: REFW10X64-001
- Task sequence name: Windows 10 Enterprise x64 Default Image
- Task sequence comments: Reference Build
- Template: Standard Client Task Sequence
- Select OS: click Windows 10 Enterprise Evaluation in W10Ent_x64 install.wim
- Specify Product Key: Do not specify a product key at this time
- Full Name: Contoso
- Organization: Contoso
- Internet Explorer home page: http://www.contoso.com
- Admin Password: Do not specify an Administrator password at this time
- Summary: click Next
- Confirmation: click Finish
Edit the task sequence to add the Microsoft NET Framework 3.5, which is required by many applications. To edit the task sequence, double-click Windows 10 Enterprise x64 Default Image that was created in the previous step.
Click the Task Sequence tab. Under State Restore click Tatto to highlight it, then click Add and choose New Group. A new group will be added under Tattoo.
On the Properties tab of the group that was created in the previous step, change the Name from New Group to Custom Tasks (Pre-Windows Update) and then click Apply. To see the name change, click Tattoo, then click the new group again.
Click the Custom Tasks (Pre-Windows Update) group again, click Add, point to Roles, and then click Install Roles and Features.
Under Select the roles and features that should be installed, select .NET Framework 3.5 (includes .NET 2.0 and 3.0) and then click Apply.
Enable Windows Update in the task sequence by clicking the Windows Update (Post-Application Installation) step, clicking the Options tab, and clearing the Disable this step checkbox.
Note: Since we are not installing applications in this test lab, there is no need to enable the Windows Update Pre-Application Installation step. However, you should enable this step if you are also installing applications.
Click OK to complete editing the task sequence.
The next step is to configure the MDT deployment share rules. To configure rules in the Deployment Workbench, right-click MDT build lab (C:MDTBuildLab) and click Properties, and then click the Rules tab.
Replace the default rules with the following text:
Click Apply and then click Edit Bootstrap.ini. Replace the contents of the Bootstrap.ini file with the following text, and save the file:
Click OK to complete the configuration of the deployment share.
Right-click MDT build lab (C:MDTBuildLab) and then click Update Deployment Share.
Accept all default values in the Update Deployment Share Wizard by clicking Next. The update process will take 5 to 10 minutes. When it has completed, click Finish.
Copy c:MDTBuildLabBootLiteTouchPE_x86.iso on SRV1 to the c:VHD directory on the Hyper-V host computer. Note that in MDT, the x86 boot image can deploy both x86 and x64 operating systems, except on computers based on Unified Extensible Firmware Interface (UEFI).
Hint: Top copy the file, right-click the LiteTouchPE_x86.iso file and click Copy on SRV1, then open the c:VHD folder on the Hyper-V host, right-click inside the folder and click Paste.
Open a Windows PowerShell prompt on the Hyper-V host computer and type the following commands:
In the Windows Deployment Wizard, select Windows 10 Enterprise x64 Default Image, and then click Next.
Accept the default values on the Capture Image page, and click Next. Operating system installation will complete after 5 to 10 minutes and then the VM will reboot automatically. Allow the system to boot normally (do not press a key). The process is fully automated.
Additional system restarts will occur to complete updating and preparing the operating system. Setup will complete the following procedures:
- Install the Windows 10 Enterprise operating system.
- Install added applications, roles, and features.
- Update the operating system using Windows Update (or WSUS if optionally specified).
- Stage Windows PE on the local disk.
- Run System Preparation (Sysprep) and reboot into Windows PE.
- Capture the installation to a Windows Imaging (WIM) file.
- Turn off the virtual machine.
This step requires from 30 minutes to 2 hours, depending on the speed of the Hyper-V host and your network's download speed. After some time, you will have a Windows 10 Enterprise x64 image that is fully patched and has run through Sysprep. The image is located in the C:MDTBuildLabCaptures folder on SRV1. The file name is REFW10X64-001.wim.

Add a Windows 10 operating system image

Type the following commands at an elevated Windows PowerShell prompt on SRV1:
In the Configuration Manager console, in the Software Library workspace, expand Operating Systems, right-click Operating System Images, and then click Add Operating System Image.
On the Data Source page, under Path:, type or browse to SRV1Sources$OSDOSWindows 10 Enterprise x64REFW10X64-001.wim, and click Next.
On the General page, next to Name:, type Windows 10 Enterprise x64, click Next twice, and then click Close.
Distribute the operating system image to the SRV1 distribution point by right-clicking the Windows 10 Enterprise x64 operating system image and then clicking Distribute Content.
In the Distribute Content Wizard, click Next, click Add, click Distribution Point, add the SRV1.CONTOSO.COM distribution point, click OK, click Next twice and then click Close.
Enter MonitoringOverviewDistribution StatusContent Status on the location bar (be sure there is no space at the end of the location or you will get an error), click Windows 10 Enterprise x64, and monitor the status of content distribution until it is successful and no longer in progress. Refresh the view with the F5 key or by right-clicking Windows 10 Enterprise x64 and clicking Refresh. Processing of the image on the site server can take several minutes.
If content distribution is not successful, verify that sufficient disk space is available.

Create a task sequence

Complete this section slowly. There are a large number of similar settings from which to choose.

In the Configuration Manager console, in the Software Library workspace expand Operating Systems, right-click Task Sequences, and then click Create MDT Task Sequence.
On the Choose Template page, select the Client Task Sequence template and click Next.
On the General page, type Windows 10 Enterprise x64 under Task sequence name: and then click Next.
On the Details page, enter the following settings:
- Join a domain: contoso.com
- Account: click Set
  - User name: contosoCM_JD
  - Password: pass@word1
  - Confirm password: pass@word1
  - Click OK
- Windows Settings
  - User name: Contoso
  - Organization name: Contoso
  - Product key: <blank>
- Administrator Account: Enable the account and specify the local administrator password
  - Password: pass@word1
  - Confirm password: pass@word1
- Click Next
On the Capture Settings page, accept the default settings and click Next.
On the Boot Image page, browse and select the Zero Touch WinPE x64 boot image package, click OK, and then click Next.
On the MDT Package page, select Create a new Microsoft Deployment Toolkit Files package, under Package source folder to be created (UNC Path):, type SRV1Sources$OSDMDTMDT (MDT is repeated here, not a typo), and then click Next.
On the MDT Details page, next to Name: type MDT and then click Next.
On the OS Image page, browse and select the Windows 10 Enterprise x64 package, click OK, and then click Next.
On the Deployment Method page, accept the default settings for Zero Touch Installation and click Next.
On the Client Package page, browse and select the Microsoft Corporation Configuration Manager Client package, click OK, and then click Next.
On the USMT Package page, browse and select the Microsoft Corporation User State Migration Tool for Windows 10.0.14393.0 package, click OK, and then click Next.
On the Settings Package page, select Create a new settings package, and under Package source folder to be created (UNC Path):, type SRV1Sources$OSDSettingsWindows 10 x64 Settings, and then click Next.
On the Settings Details page, next to Name:, type Windows 10 x64 Settings, and click Next.
On the Sysprep Package page, click Next twice.
On the Confirmation page, click Finish.

Edit the task sequence

Deploy Windows 10 With Sccm Free

In the Configuration Manager console, in the Software Library workspace, click Task Sequences, right-click Windows 10 Enterprise x64, and then click Edit.
Scroll down to the Install group and click the Set Variable for Drive Letter action.
Change the Value under OSDPreserveDriveLetter from False to True, and then click Apply.
In the State Restore group, click the Set Status 5 action, click Add in the upper left corner, point to User State, and click Request State Store. This adds a new action immediately after Set Status 5.
Configure the Request State Store action that was just added with the following settings:
- Request state storage location to: Restore state from another computer
- Select the If computer account fails to connect to state store, use the Network Access account checkbox.
- Options tab: Select the Continue on error checkbox.
- Add Condition: Task Sequence Variable:
  - Variable: USMTLOCAL
  - Condition: not equals
  - Value: True
  - Click OK.
- Click Apply
  .
In the State Restore group, click Restore User State, click Add, point to User State, and click Release State Store.
Configure the Release State Store action that was just added with the following settings:
- Options tab: Select the Continue on error checkbox.
- Add Condition: Task Sequence Variable:
  - Variable: USMTLOCAL
  - Condition: not equals
  - Value: True
  - Click OK.
- Click OK
  .

Finalize the operating system configuration

If you completed all procedures in Deploy Windows 10 in a test lab using Microsoft Deployment Toolkit then the MDT deployment share is already present on SRV1. In this case, skip the first four steps below and begin with step 5 to edit CustomSettings.ini.

In the MDT deployment workbench on SRV1, right-click Deployment Shares and then click New Deployment Share.
Use the following settings for the New Deployment Share Wizard:
- Deployment share path: C:MDTProduction
- Share name: MDTProduction$
- Deployment share description: MDT Production
- Options: click Next to accept the default
- Summary: click Next
- Progress: settings will be applied
- Confirmation: click Finish
Right-click the MDT Production deployment share, and click Properties.
Click the Monitoring tab, select the Enable monitoring for this deployment share checkbox, and then click OK.
Type the following command at an elevated Windows PowerShell prompt on SRV1:
Replace the contents of the file with the following text, and then save the file:
As noted previously, if you wish to migrate accounts other than those in the Contoso domain, then change the OSDMigrateAdditionalCaptureOptions option. For example, the following option will capture settings from all user accounts:
Return to the Configuration Manager console, and in the Software Library workspace, expand Application Management, click Packages, right-click Windows 10 x64 Settings, and then click Update Distribution Points. Click OK in the popup that appears.
In the Software Library workspace, expand Operating Systems, click Task Sequences, right-click Windows 10 Enterprise x64, and then click Distribute Content.
In the Distribute Content Wizard, click Next twice, click Add, click Distribution Point, select the SRV1.CONTOSO.COM distribution point, click OK, click Next twice and then click Close.
Enter MonitoringOverviewDistribution StatusContent StatusWindows 10 Enterprise x64 on the location bar, double-click Windows 10 Enterprise x64, and monitor the status of content distribution until it is successful and no longer in progress. Refresh the view with the F5 key or by right-clicking Windows 10 Enterprise x64 and clicking Refresh.

Create a deployment for the task sequence

In the Software Library workspace, expand Operating Systems, click Task Sequences, right-click Windows 10 Enterprise x64, and then click Deploy.
On the General page, next to Collection, click Browse, select the All Unknown Computers collection, click OK, and then click Next.
On the Deployment Settings page, use the following settings:
- Purpose: Available
- Make available to the following: Only media and PXE
- Click Next.
Click Next five times to accept defaults on the Scheduling, User Experience, Alerts, and Distribution Points pages.
Click Close.

Deploying Windows 10 With Sccm Step By Step

Deploy Windows 10 using PXE and Configuration Manager

In this first deployment scenario, we will deploy Windows 10 using PXE. This scenario creates a new computer that does not have any migrated users or settings.

Type the following commands at an elevated Windows PowerShell prompt on the Hyper-V host:
Press ENTER when prompted to start the network boot service.
In the Task Sequence Wizard, provide the password: pass@word1, and then click Next.
Before you click Next in the Task Sequence Wizard, press the F8 key. A command prompt will open.
At the command prompt, type explorer.exe and review the Windows PE file structure.
The smsts.log file is critical for troubleshooting any installation problems that might be encountered. Depending on the deployment phase, the smsts.log file is created in different locations:
- X:windowstempSMSTSLogsmsts.log before disks are formatted.
- x:smstslogsmsts.log after disks are formatted.
- c:_SMSTaskSequenceLogsSmstslogsmsts.log before the System Center Configuration Manager client is installed.
- c:windowsccmlogsSmstslogsmsts.log after the System Center Configuration Manager client is installed.
- c:windowsccmlogssmsts.log when the task sequence is complete.
  Note: If a reboot is pending on the client, the reboot will be blocked as long as the command window is open.
In the explorer window, click Tools and then click Map Network Drive.
Do not map a network drive at this time. If you need to save the smsts.log file, you can use this method to save the file to a location on SRV1.
Close the Map Network Drive window, the Explorer window, and the command prompt.
The Windows 10 Enterprise x64 task sequence is selected in the Task Sequenc Wizard. Click Next to continue with the deployment.
The task sequence will require several minutes to complete. You can monitor progress of the task sequence using the MDT Deployment Workbench under Deployment Shares > MDTProduction > Monitoring. The task sequence will:
- Install Windows 10
- Install the Configuration Manager client and hotfix
- Join the computer to the contoso.com domain
- Install any applications that were specified in the reference image
When Windows 10 installation has completed, sign in to PC4 using the contosoadministrator account.
Right-click Start, click Run, type control appwiz.cpl, press ENTER, click Turn Windows features on or off, and verify that .NET Framework 3.5 (includes .NET 2.0 and 3.0) is installed. This is a feature included in the reference image.
Shut down the PC4 VM.

Note: The following two procedures 1) Replace a client with Windows 10 and 2) Refresh a client with Windows 10 have been exchanged in their order in this guide compared to the previous version. This is to avoid having to restore Hyper-V checkpoints to have access to PC1 before the OS is upgraded. If this is your first time going through this guide, you won't notice any change, but if you have tried the guide previously then this change should make it simpler to complete.

Replace a client with Windows 10 using Configuration Manager

Before starting this section, you can delete computer objects from Active Directory that were created as part of previous deployment procedures. Use the Active Directory Users and Computers console on DC1 to remove stale entries under contoso.comComputers, but do not delete the computer account (hostname) for PC1. There should be at least two computer accounts present in the contoso.comComputers container: one for SRV1, and one for the hostname of PC1. It is not required to delete the stale entries, this is only done to remove clutter.

In the replace procedure, PC1 will not be migrated to a new operating system. It is simplest to perform this procedure before performing the refresh procedure. After refreshing PC1, the operating system will be new. The next (replace) procedure does not install a new operating system on PC1 but rather performs a side-by-side migration of PC1 and another computer (PC4), to copy users and settings from PC1 to the new computer.

Create a replace task sequence

On SRV1, in the Configuration Manager console, in the Software Library workspace, expand Operating Systems, right-click Task Sequences, and then click Create MDT Task Sequence.
On the Choose Template page, select Client Replace Task Sequence and click Next.
On the General page, type the following:
- Task sequence name: Replace Task Sequence
- Task sequence comments: USMT backup only
Click Next, and on the Boot Image page, browse and select the Zero Touch WinPE x64 boot image package. Click OK and then click Next to continue.
On the MDT Package page, browse and select the MDT package. Click OK and then click Next to continue.
On the USMT Package page, browse and select the Microsoft Corporation User State Migration Tool for Windows package. Click OK and then click Next to continue.
On the Settings Package page, browse and select the Windows 10 x64 Settings package. Click OK and then click Next to continue.
On the Summary page, review the details and then click Next.
On the Confirmation page, click Finish.

If an error is displayed at this stage it can be caused by a corrupt MDT integration. To repair it, close the Configuration Manager console, remove MDT integration, and then restore MDT integration.

Deploy PC4

Create a VM named PC4 to receive the applications and settings from PC1. This VM represents a new computer that will replace PC1. To create this VM, type the following commands at an elevated Windows PowerShell prompt on the Hyper-V host:

Hyper-V enables us to define a static MAC address on PC4. In a real-world scenario you must determine the MAC address of the new computer.

Install the Configuration Manager client on PC1

Verify that the PC1 VM is running and in its original state, which was saved as a checkpoint and then restored in Deploy Windows 10 in a test lab using Microsoft Deployment Toolkit.
If a PC1 checkpoint has not already been saved, then save a checkpoint by typing the following commands at an elevated Windows PowerShell prompt on the Hyper-V host:
On SRV1, in the Configuration Manager console, in the Administration workspace, expand Hierarchy Configuration and click on Discovery Methods.
Double-click Active Directory System Discovery and on the General tab select the Enable Active Directory System Discovery checkbox.
Click the yellow starburst, click Browse, select contosoComputers, and then click OK three times.
When a popup dialog box asks if you want to run full discovery, click Yes.
In the Assets and Compliance workspace, click Devices and verify that the computer account names for SRV1 and PC1 are displayed. See the following example (GREGLIN-PC1 is the computer account name of PC1 in this example):
If you do not see the computer account for PC1, try clicking the Refresh button in the upper right corner of the console.
The Client column indicates that the Configuration Manager client is not currently installed. This procedure will be carried out next.
Sign in to PC1 using the contosoadministrator account and type the following at an elevated command prompt to remove any pre-existing client configuration, if it exists. Note: this command requires an elevated command prompt not an elevated Windows PowerShell prompt:
If PC1 still has Configuration Manager registry settings that were applied by Group Policy, startup scripts, or other policies in its previous domain, these might not all be removed by CCMSetup /Uninstall and can cause problems with installation or registration of the client in its new environment. It might be necessary to manually remove these settings if they are present. For more information, see Manual removal of the SCCM client.
On PC1, temporarily stop Windows Update from queuing items for download and clear all BITS jobs from the queue:
Verify that both services were stopped successfully, then type the following at an elevated command prompt:
Verify that BITSAdmin displays 0 jobs.
To install the Configuration Manager client as a standalone process, type the following at an elevated command prompt:
On PC1, using file explorer, open the C:Windowsccmsetup directory. During client installation, files will be downloaded here.
Installation progress will be captured in the file: c:windowsccmsetuplogsccmsetup.log. You can periodically open this file in notepad, or you can type the following command at an elevated Windows PowerShell prompt to monitor installation progress:
Installation might require several minutes, and display of the log file will appear to hang while some applications are installed. This is normal. When setup is complete, verify that CcmSetup is existing with return code 0 is displayed on the last line of the ccmsetup.log file and then press CTRL-C to break out of the Get-Content operation (if you are viewing the log in Windows PowerShell the last line will be wrapped). A return code of 0 indicates that installation was successful and you should now see a directory created at C:WindowsCCM that contains files used in registration of the client with its site.
On PC1, open the Configuration Manager control panel applet by typing the following command:
Click the Site tab, click Configure Settings, and click Find Site. The client will report that it has found the PS1 site. See the following example:
If the client is not able to find the PS1 site, review any error messages that are displayed in C:WindowsCCMLogsClientIDManagerStartup.log and LocationServices.log. A common reason the site code is not located is because a previous configuration exists. For example, if a previous site code is configured at HKLMSOFTWAREMicrosoftSMSMobile ClientGPRequestedSiteAssignmentCode this must be deleted or updated.
On SRV1, in the Assets and Compliance workspace, click Device Collections and then double-click All Desktop and Server Clients. This node will be added under Devices.
Click All Desktop and Server Clients and verify that the computer account for PC1 is displayed here with Yes and Active in the Client and Client Activity columns, respectively. You might have to refresh the view and wait few minutes for the client to appear here. See the following example:
It might take several minutes for the client to fully register with the site and complete a client check. When it is complete you will see a green check mark over the client icon as shown above. To refresh the client, click it and then press F5 or right-click the client and click Refresh.

Create a device collection and deployment

On SRV1, in the Configuration Manager console, in the Asset and Compliance workspace, right-click Device Collections and then click Create Device Collection.
Use the following settings in the Create Device Collection Wizard:
- General > Name: Install Windows 10 Enterprise x64
- General > Limiting collection: All Systems
- Membership Rules > Add Rule: Direct Rule
- The Create Direct Membership Rule Wizard opens, click Next
- Search for Resources > Resource class: System Resource
- Search for Resources > Attribute name: Name
- Search for Resources > Value: %
- Select Resources > Value: Select the computername associated with the PC1 VM
- Click Next twice and then click Close in both windows (Next, Next, Close, then Next, Next, Close)
Double-click the Install Windows 10 Enterprise x64 device collection and verify that the PC1 computer account is displayed.
In the Software Library workspace, expand Operating Systems, click Task Sequences, right-click Windows 10 Enterprise x64 and then click Deploy.
Use the following settings in the Deploy Software wizard:
- General > Collection: Click Browse and select Install Windows 10 Enterprise x64
- Deployment Settings > Purpose: Available
- Deployment Settings > Make available to the following: Configuration Manager clients, media and PXE
- Scheduling > Click Next
- User Experience > Click Next
- Alerts > Click Next
- Distribution Points > Click Next
- Summary > Click Next
- Verify that the wizard completed successfully and then click Close

Associate PC4 with PC1

On SRV1 in the Configuration Manager console, in the Assets and Compliance workspace, right-click Devices and then click Import Computer Information.
On the Select Source page, choose Import single computer and click Next.
On the Single Computer page, use the following settings:
- Computer Name: PC4
- MAC Address: 00:15:5D:83:26:FF
- Source Computer: <type the hostname of PC1, or click Search twice, click the hostname, and click OK>
Click Next, and on the User Accounts page choose Capture and restore specified user accounts, then click the yellow starburst next to User accounts to migrate.
Click Browse and then under Enter the object name to select type user1 and click OK twice.
Click the yellow starburst again and repeat the previous step to add the contosoadministrator account.
Click Next twice, and on the Choose Target Collection page, choose Add computers to the following collection, click Browse, choose Install Windows 10 Enterprise x64, click OK, click Next twice, and then click Close.
In the Assets and Compliance workspace, click User State Migration and review the computer association in the display pane. The source computer will be the computername of PC1 (GREGLIN-PC1 in this example), the destination computer will be PC4, and the migration type will be side-by-side.
Right-click the association in the display pane and then click Specify User Accounts. You can add or remove user account here. Click OK.
Right-click the association in the display pane and then click View Recovery Information. Note that a recovery key has been assigned, but a user state store location has not. Click Close.
Click Device Collections and then double-click Install Windows 10 Enterprise x64. Verify that PC4 is displayed in the collection. You might have to update and refresh the collection, or wait a few minutes, but do not proceed until PC4 is available. See the following example:

Create a device collection for PC1

On SRV1, in the Configuration Manager console, in the Assets and Compliance workspace, right-click Device Collections and then click Create Device Collection.
Use the following settings in the Create Device Collection Wizard:
- General > Name: USMT Backup (Replace)
- General > Limiting collection: All Systems
- Membership Rules > Add Rule: Direct Rule
- The Create Direct Membership Rule Wizard opens, click Next
- Search for Resources > Resource class: System Resource
- Search for Resources > Attribute name: Name
- Search for Resources > Value: %
- Select Resources > Value: Select the computername associated with the PC1 VM (GREGLIN-PC1 in this example).
- Click Next twice and then click Close in both windows.
Click Device Collections and then double-click USMT Backup (Replace). Verify that the computer name/hostname associated with PC1 is displayed in the collection. Do not proceed until this name is displayed.

Create a new deployment

In the Configuration Manager console, in the Software Library workspace under Operating Systems, click Task Sequences, right-click Replace Task Sequence, click Deploy, and use the following settings:

General > Collection: USMT Backup (Replace)
Deployment Settings > Purpose: Available
Deployment Settings > Make available to the following: Only Configuration Manager Clients
Scheduling: Click Next
User Experience: Click Next
Alerts: Click Next
Distribution Points: Click Next
Click Next and then click Close.

Verify the backup

On PC1, open the Configuration Manager control panel applet by typing the following command:
On the Actions tab, click Machine Policy Retrieval & Evaluation Cycle, click Run Now, click OK, and then click OK again. This is one method that can be used to run a task sequence in addition to the Client Notification method that will be demonstrated in the computer refresh procedure.
Type the following at an elevated command prompt to open the Software Center:
In the Software Center , click Available Software and then select the Replace Task Sequence checkbox. See the following example:
If you do not see any available software, try running step #2 again to start the Machine Policy Retrieval & Evaluation Cycle. You should see an alert that new software is available.
Click INSTALL SELECTED and then click INSTALL OPERATING SYSTEM.
Allow the Replace Task Sequence to complete, then verify that the C:MigData folder on SRV1 contains the USMT backup.

Deploy the new computer

Start PC4 and press ENTER for a network boot when prompted. To start PC4, type the following commands at an elevated Windows Powershell prompt on the Hyper-V host:
In the Welcome to the Task Sequence Wizard, enter pass@word1 and click Next.
Choose the Windows 10 Enterprise X64 image.
Setup will install the operating system using the Windows 10 Enterprise x64 reference image, install the configuration manager client, join PC4 to the domain, and restore users and settings from PC1.
Save checkpoints for all VMs if you wish to review their status at a later date. This is not required (checkpoints do take up space on the Hyper-V host). Note: the next procedure will install a new OS on PC1 update its status in Configuration Manager and in Active Directory as a Windows 10 device, so you cannot return to a previous checkpoint only on the PC1 VM without a conflict. Therefore, if you do create a checkpoint, you should do this for all VMs.
To save a checkpoint for all VMs, type the following commands at an elevated Windows PowerShell prompt on the Hyper-V host:

Refresh a client with Windows 10 using Configuration Manager

Initiate the computer refresh

On SRV1, in the Assets and Compliance workspace, click Device Collections and then double-click Install Windows 10 Enterprise x64.
Right-click the computer account for PC1, point to Client Notification, click Download Computer Policy, and click OK in the popup dialog box.
On PC1, in the notification area, click New software is available and then click Open Software Center.
In the Software Center, click Operating Systems, click Windows 10 Enterprise x64, click Install and then click INSTALL OPERATING SYSTEM. See the following example:
The computer will restart several times during the installation process. Installation includes downloading updates, reinstalling the Configuration Manager Client Agent, and restoring the user state. You can view status of the installation in the Configuration Manager console by accessing the Monitoring workspace, clicking Deployments, and then double-clicking the deployment associated with the Install Windows 10 Enterprise x64 collection. Under Asset Details, right-click the device and then click More Details. Click the Status tab to see a list of tasks that have been performed. See the following example:
You can also monitor progress of the installation by using the MDT deployment workbench and viewing the Monitoring node under Deployment SharesMDT Production.
When installation has completed, sign in using the contosoadministrator account or the contosouser1 account and verify that applications and settings have been successfully backed up and restored to your new Windows 10 Enterprise operating system.

In this section

Components of Configuration Manager operating system deployment

See also

In this guide

Install prerequisites

Install System Center Configuration Manager

Download MDOP and install DaRT

Prepare for Zero Touch installation

Create a folder structure

Enable MDT ConfigMgr integration

Configure client settings

Configure the network access account

Configure a boundary group

Add the state migration point role

Enable PXE on the distribution point

Create a branding image file

Create a boot image for Configuration Manager

Create a Windows 10 reference image

Add a Windows 10 operating system image

Create a task sequence

Edit the task sequence

Deploy Windows 10 With Sccm Free

Finalize the operating system configuration

Create a deployment for the task sequence

Deploying Windows 10 With Sccm Step By Step

Deploy Windows 10 using PXE and Configuration Manager

Replace a client with Windows 10 using Configuration Manager

Create a replace task sequence

Deploy PC4

Install the Configuration Manager client on PC1

Create a device collection and deployment

Associate PC4 with PC1

Create a device collection for PC1

Create a new deployment

Verify the backup

Deploy the new computer

Refresh a client with Windows 10 using Configuration Manager

Initiate the computer refresh

Related Topics