How to switch to Windows 10 ADK on ConfigMgr 2012 R2 SP1

This article explains how to replace the Windows 8.1 ADK by the newly release Windows 10 ADK on a ConfigMgr 2012 R2 SP1 server.

Prerequisites:

  • Having upgraded ConfigMgr 2012 R2 to SP1 (or SP2)
  • Having download the Windows 10 ADK for the following site

 

Uninstalling Windows 8.1 ADK

First thing you have to do is uninstalling Windows 8.1 ADK from the SCCM site server.

To do so, go into [Programs and Features] from [Control Panel] and uninstall [Windows Assessment and Deployment Kit for Windows 8.1]

image

At this point, it doesn’t require to restart the site server. Let’s start installing Windows 10 ADK.

Installing Windows 10 ADK on site server

On the site server, run the “adksetup.exe” you downloaded from the above link.

Install the following features:

image

Wait the installer to finish and you should see in [Programs and Features] Windows 10 ADK installed on your site server.

image

At this point, you need to reboot the site server.

Create the new boot images in SCCM

First thing to do after the reboot is to copy the WIM files of both x86 and x64 versions of WinPE 10 to a shared folder.

Here are the paths to both WIM:

  • X86 WinPE: C:\Program Files (x86)\Windows Kits\10\Assessment and Deployment Kit\Windows Preinstallation Environment\x86\en-us\winpe.wim
  • X64 WinPE: C:\Program Files (x86)\Windows Kits\10\Assessment and Deployment Kit\Windows Preinstallation Environment\amd64\en-us\winpe.wim

Copied each wim in the appropriate shared folder. In my lab, those shares are:

  • \\<SiteServerFQDN><a href="file://\\\ConfigMgr\Content\OSD\BootImages\Win10PEx86">\ConfigMgr\Content\OSD\BootImages\Win10PEx86
  • \\<SiteServerFQDN><a href="file://\\\ConfigMgr\Content\OSD\BootImages\Win10PEx64">\ConfigMgr\Content\OSD\BootImages\Win10PEx64

From the SCCM console, go to [Software Library] –> [Overview] –> [Operating Systems] –> [Boot Images] and click on the [Add Boot Image] button in the ribbon menu.

In the wizard, specify the source UNC path of the WIM file. Click Next.

image

Then enter a name for the new WinPE.

image

Click next twice and you’re done!

Do the same for the 64 bits version of WinPE and don’t forget to distribute those contents to all your DPs!!

image

Last settings before playing with Windows 10 OSD

Before starting playing with Windows 10 OSD, you need make available both newly imported WinPE to the DP for PXE boot.

For both versions of WinPE 10, check [Deploy this boot image from the PXE-enabled distribution point].

image

Note: Uncheck that same settings in any other boot images that you are not using anymore! the old boot images you already had can still be used for OSD but you wont be able customize (like importing drivers) them from SCCM console.

Create USMT 10 package

If you plan to use USMT, create an USMT 10 package using the below source path.

C:\Program Files (x86)\Windows Kits\10\Assessment and Deployment Kit\User State Migration Tool

image

Select [Do not create a program] on the next page and you’re done. Distribute the content to the DP to start using it.

Start Windows 10 OSD now!

Do not forget to change the boot image settings of the existing task sequences (you can change used boot image from properties of task sequences).

Now you’re good to go!! Create new task sequences, select the new boot image and enjoy deploying Windows 10!