In the first part of this blog series on how to deploy Windows 10 with SCCM, we will prepare our environment for Windows 10. If you’re already deploying other operating systems with SCCM 1511, adding Windows 10 is just a matter of adding a new WIM (which our post covers in part 4). If you’re new to deploying operating system with SCCM, follow this post which will covers all steps needed before you can deploy your first systems.

Overview SCCM Windows 10 Deployment

  1. Upgrade to SCCM 1511
  2. Enable PXE Support
  3. Prepare your boot image
  4. Prepare your Operating Systems
  5. Create your SUG
  6. USMT Packages

Upgrade to SCCM 1511

It’s possible to manage Windows 10 with SCCM 2012 but when it comes to deploying Windows 10, if you want to use the full features, you need SCCM 1511 and further. Follow our guide to upgrade your SCCM server and make sure that you are upgrading your Windows ADK version which is included in the upgrade process.

Enable PXE Support

Follow these steps if you want to deploy your images using PXE boot (recommended)

  • Open the SCCM Console
  • Go to Administration / Site Configuration / Servers and Site System Roles
  • Select your distribution point and right-click on the Distribution point role on the bottom, select Properties

SCCM Windows 10 deployment

  • Select the PXE tab
  • Enable the Enable PXE support for Clients check-box and answer Yes when prompted about firewall ports (UDP ports 67, 68, 69 and 4011 )

SCCM Windows 10 deployment

  • Check the Allow this distribution point to respond to incoming PXE requests check box
  • Check the Enable unknown computer support check box
  • Ensure that the Respond to PXE request on all network interfaces is selected
  • Click Ok

SCCM Windows 10 deployment

Your distribution point will now install Windows Deployment Services (if not already installed) and will copy the necessary files on the distribution point.

You can monitor this process in the SCCM Console :

  • Go to Monitoring / Distribution Status / Distribution Point Configuration Status
  • Click your distribution point on the top and select the Details tab on the bottom
  • You will see that the distribution point PXE settings has changed

SCCM Windows 10 deployment

Prepare your boot image

[su_box title=”Important note” style=”glass” title_color=”#F0F0F0″]If you have created any custom boot images in previous version, you won’t be able to manage it (customize, add drivers, ect…) through the SCCM console. The only manageable version would be PE10 images. Other version could still be used but you’ll have to manage them outside the console using DISM.[/su_box]


Before launching your first boot image you must include your Windows 10 drivers into the boot image. Our rule of thumb about drivers is to try to boot a certain model and if it fails, add the drivers. Do not add all your NIC drivers to your boot image, it’s overkill and unnecessary increase the size of the boot image.

To add drivers to the boot image :

  • Open the SCCM Console
  • Go to Software Library / Operating Systems / Boot Images
  • Right-click your Boot Image, select Properties
  • Select the Drivers tab

SCCM Windows 10 deployment

  • Click the Star icon
  • Select the desired drivers and click OK

SCCM Windows 10 deployment

  • The selected drivers are added to the boot image, once you click OK, SCCM will inject the driver in your boot image

SCCM Windows 10 deployment


We will now make a couple customization to the boot image to enable command support (F8) and add a custom background image to the deployment

  • Open the SCCM Console
  • Go to Software Library / Operating Systems / Boot Images
  • Right-click your Boot Image
  • Select the Customization tab
  • Check the Enable command support checkbox. This allows to have the F8 command line support during deployment
  • Specify a custom background if needed by checking Specify the custom background image file checkbox

SCCM Windows 10 deployment

  • If you’re using a PXE-enable distribution point, select the Data Source tab and check the Deploy this boot image from the PXE-Enabled distributon point checkbox

  • Click Apply and Yes to the warning, close the window

SCCM Windows 10 deployment

Distribute your boot image

Since you’ve upgraded your ADK to version 10 and made modifications to your boot image, you need to redistribute it to your distribution points.

  • Right click your boot image and select Update Distribution Points

SCCM Windows 10 deployment

Prepare your Operating Systems

We will now import the Windows 10 WIM file for Windows 10 deployment.

[su_box title=”Important” style=”glass” title_color=”#F0F0F0″]You’ll see both Operating System Images and Operating System Upgrade Packages. One is to import .WIM files and the other one is for Full Media. We will need both for different scenarios. In the case of a vanilla deployment or after a build and capture, you use Operating System Images to import the WIM files. In an Upgrade task Sequence, you will need to have the Full media imported in Operating System Upgrade Packages.[/su_box]

We will start by importing the default Install.Wim from the Windows 10 media for a “vanilla” Windows 10 deployment. You could also import a WIM file that you’ve created through a build and capture process.

  • Open the SCCM Console
  • Go to Software Library / Operating Systems / Operating System Images
  • Right click Operating System Images and select Add Operating System Image

SCCM Windows 10 deployment

  • On the Data Source tab, browse to your WIM file. The path must be in UNC format

SCCM Windows 10 deployment

  • In the General tab, enter the Name, Version and Comment, click Next

SCCM Windows 10 deployment

  • On the Summary tab, review your information and click Next

SCCM Windows 10 deployment

  • Complete the wizard and close this window

SCCM Windows 10 deployment

Distribute your Operating System Image

We now need to send the Operating System Image (WIM file) to our distribution points.

  • Right click your Operating System Image, select Distribute Content and complete the Distribute Content wizard

SCCM Windows 10 deployment

We will now import the complete Windows 10 media in Operating System Upgrade Packages. This package will be used to upgrade a Windows 7 (or 8.1) device to Windows 10 using an Upgrade Task Sequence.

  • Open the SCCM Console
  • Go to Software Library / Operating Systems / Operating System Upgrade Packages
  • Right click Operating System Upgrade Packages and select Add Operating System Upgrade Packages

SCCM Windows 10 deployment

  • In the Data Source tab, browse to the path of your full Windows 10 media. The path must point on an extracted source of a ISO file. You need to point at the top folder where Setup.exe reside

SCCM Windows 10 deployment

SCCM Windows 10 deployment

  • In the General tab, enter the Name, Version and Comment, click Next

SCCM Windows 10 deployment

  • On the Summary tab, review your information and click Next

SCCM Windows 10 deployment

  • Complete the wizard and close this window

SCCM Windows 10 deployment

Distribute your Operating System Upgrade Packages

We now need to send the Operating System Upgrade Package to your distribution points.

  • Right click your Operating System Upgrade Package, select Distribute Content and complete the Distribute Content wizard

SCCM Windows 10 deployment

Create Software Update Group

One important thing in any OSD project, is to make sure that every machines deployments are up to date. Before deploying Windows 10, make sure that your Software Update Point is configured to include Windows 10 patches.

Once Windows 10 is added to your Software Update Point, we will create a Software Update Group that will be deployed to our Windows 10 deployment collection. This way, all patches released after the Windows 10 media creation (or your Capture date) will be deployed during the deployment process.

To create a Windows 10 Software Update Group :

  • Open the SCCM Console
  • Go to Software Library / Software Updates / All Software Updates
  • On the right side, click Add Criteria, select Product, Expired and Superseded
    • Product : Windows 10
    • Expired  : No
    • Superseded : No

SCCM Windows 10 deployment

  • Select all patches and select Create Software Update Group

SCCM Windows 10 deployment

  • Once created, go to Software Library / Software Updates / Software Update Groups
  • Right-click your Windows 10 SUG and deploy it to your OSD deployment collection

USMT Package

If you are planning to use USMT to capture and restore user settings and files, you need to make sure that the USMT package is created and distributed.

  • Open the SCCM Console
  • Go to Software Library / Application Management / Packages
  • Right-click the User State Migration Tool for Windows 10 package and select Properties
  • On the Data Source tab, ensure that the package is using the ADK 10 – Which is per default C:\Program Files\Windows Kits\10\Assessment and Deployment Kit\User State Migration Tool
  • Right-click the User State Migration Tool for Windows 10 package and select Distribute Content

SCCM Windows 10 deployment

That’s it ! You have everything that’s needed to create your first Windows 10 deployment. Read the next parts of this blog series to successfully deploy Windows 10.

Comments (16)

Aaron Ross

03.17.2019 AT 11:23 AM
Let me guess.... another blog that simply copies and pastes material from other blogs. If you read the book, which you clearly did not, you would have noticed that the host system only contain native drivers. I am going to teach you something here; If the server is a VM, it will contain NO drivers. Why not be helpful, stop being a plagiarist and maybe go through your work and fix it.


07.27.2018 AT 09:22 AM
Hi. I see that you don't update your blog too often. I know that writing content is boring and time consuming. But did you know that there is a tool that allows you to create new posts using existing content (from article directories or other pages from your niche)? And it does it very well. The new articles are high quality and pass the copyscape test. You should try miftolo's tools


02.13.2018 AT 03:12 AM
Hiya, nice post🙂 Just wanted to check,, I am going for a vanilla Windows 10 plus everything else delivered by ththe task sequence. Therefore making it easier to drop in a new default install.wim in th future. Is there any reason why I cannot use the default install.wim to deploy this way in production or is that fine/supported ? Thanks


08.25.2017 AT 01:14 PM
Hi I follow the procedure but my version is 1702 , when a make a osd task sequence build and capture Windows 10 I always revceive a error on the hyper-v vm i try different vm scenario try gen 1 and gen 2 also with legacy network adapter th vm boot on pxe after I see the task sequence wizard asking me for the password, after I select the task sequence to run... after I received a message Failed to Run Task Sequence "this task sequence cannot be run because the program files for xxx00005 cannot be located on a distribution point.......the xxx00005 it,s the boot image package all the package content is distribute what I do wrong ?


03.13.2017 AT 11:27 AM
So far I found your guides really helpful and to the point, this step-by-step however is missing some essential steps, like: - Creating a task sequence for the built-in collection "All Unknown Computers" collection. - How to exactly configure your DHCP server (or references where to find this config) - and some more which I seem to have forgotten already 😮 Nice to haves: - a guide on how to deploy windows 10 to Generation 2 VM's, very handy for test-labs. Will there be an update for the latest SCCM 1610 ? Any how, keep up the good work.


09.23.2016 AT 12:51 PM
I'm having an issue adding my windows 10 image to the upgrade package wizard. I keep getting the error "The specified path does not contain a valid operating system or you do not have permissions to access it. Specify a valid path" I've checked permissions, redownload and extracted the Windows 10 anniversary image from the MS VLC, upgraded to the latest 1606 WADK. I'm at a loss here. I'm running System Center Configuration Manager v1606. The site server is running version 5.00.8412.1000 Build number 8412. Anyone got any ideas?

star wars the old republic 240 cartel coins free

04.20.2017 AT 01:48 PM
I'm amazed at all the places you've been. I love your suggestion of Turkey (which isn't a real vacation hot spot). That has to be one of my favorite places to visit in the world--beautiful, welcoming people.


07.27.2016 AT 02:17 AM
Hi, Quick question about Windows 10 Deployment and SCCM. We are running SCCM 2012 R2 CU4 right now and the Windows 10 deployment breaks on almost every step. Things like a CMD step with TIMEOUT /t 60 breaks the installation. Error log shows "The system cannot find the file specified (Error: 80070002. Source: Windows), yet this is a simple command line action without sources. Before this step i had a reboot and it crashes on that aswell. Is this to blaim on SCCM 2012 R2 CU4 or could this be something else? Windows 7 and Windows 8.1 installations run without any problems with this exact TS, all i did was switch the OS and added the drivers. Thank you in Advance.

Jonathan Lefebvre

07.27.2016 AT 08:26 AM
Hi Chris, You may want to take a look at this posts on how to manage and deploy Windows 10, using SCCM 2012 thanks Jonathan


06.02.2016 AT 12:55 AM
Dear Benoit , In my lab that include a CAS and a Primary Site I already upgrade from SCCM 2012 R2 SP1 to ConfigMgr 1511 and updated to 1602, and all was fine. In this article your refer to add drivers, to boot files, but after upgrade I can not see that option in my 6.3.9600.16384 Boot images. Until upgrade CAS and PRI sites, I uninstall ADK 8.1 reboot, install ADK 10 RTM version 10.0.26624.0, due to the known issue with ADK10 for ConfigMgr-1511 v10.1.10586.0 that need to apply Hot Fix 3143760 or still with RTM Supported path. Any clue about why is missing* not lucky in my searching about this Cheers Juan


06.02.2016 AT 10:52 AM
My auto answer to missing tabs I did not deploy ADK10 ConfigMgr 1511-v10.1.10586.0 and HotFix-3143760, so I was working with ADK W10 RTM version 10.0.26624.0 that do not upgrade Window PE from version 6.3.9600.16384 to ADK 10 version WinPE 10.0.10240.16384, so after some search and with a mix of following post and work I recover back the missing functionality, now booting on PXE a have new error The details bellow show the information relating to the PXE boot request for this computer. Please Provide these details to your Windows Deployment Services Administrador so that this request can be approved. Pending Request ID:3 Message from Administrator: Configuration Manager is looking for policy Contacting Server TFTP Download: smsbooy\x64\ PXE Boot aborted. Booting to next device So searching again

John Ferragamo

04.04.2016 AT 12:56 PM
I'm having an issue addin the Windows 10 Upgrade Package. I have extracted the ISO but when I point to it to add, I get the following error; "The specified path does not contain a valid operating system or you do not have permission to access it. Specify a valid path." I do have access to the path, since I created it. Not sure what else to try. Any ideas?


01.16.2017 AT 10:44 AM
I had this problem because i put my .WIM in the same location as my setup. I moved it to a different location and it worked.

Benoit Lecours

04.06.2016 AT 11:31 AM
Are you sure that you point at the top folder where Setup.exe reside ? If so, copy the content of the ISO on a network location and try again.


03.10.2016 AT 07:32 PM
Thanks a lot for this and all the other great guides, realy makes SCCM a pleasure to use. Where can I get the latest WIM build of windows 10. I have been on the insider program from the start so not sure on the latest official build, is there a location where we can download the Iso of windows 10 that will always be updated when new builds come out? Windows 10 has built in features for upgrading, that have been improved by a large margin compared to previous versions. Do we still need to use the user state migration tool when windows 10 can upgrade without it when on a stand-alone client?