Updating to ADK10 after Sp1 updgrade

If you install the ADK for Windows 10 after you upgrade to ConfigMgr 2012 R2 SP1, existing boot images won’t be upgraded and as a result you will be missing a few tabs on the properties of the boot image, such as adding Drivers and Customize.

2015-08-17 13_30_20-Coretech - ctcm01.coretech.intra - [SCCM 2012 server] - Royal TS

This happens because SCCM compares the version of the installed ADK to the version of the boot image, and if these do not match the tabs to modify the boot image will be hidden. When we update the distribution points the version is not checked and image just rebuild and redistributed.

the fix

Well, if you haven’t installed the SP1 yet, you can simply make sure to uninstall the old ADK and install the new one before installing SP1. The installer will update the boot image for you.

If you have already installed SP1 luckily there is a fix:

First you need to update the boot.wim file that SCCM uses for the default boot images.

Copy the winpe.wim file from the installation folder of the ADK such as: (make sure the architecture is the same, in this case 64-bit)

C:\Program Files (x86)\Windows Kits\10\Assessment and Deployment Kit\Windows Preinstallation Environment\amd64\en-us”

Copy the file to your OSD folder in the installation directory of your ConfigMgr such as:

“D:\Program Files\Microsoft Configuration Manager\OSD\boot\x64”

Delete the old boot.wim and rename the winpe.wim to boot.wim

Do the same for the 32-bit image.

If you have custom boot images, replace the source media in these as well.

Now we need to refresh the image data that ConfigMgr uses to decide whether or not to show the extra tabs on the options dialog.

Create a new PowerShell script with the following content:

1 $SiteCode = "PS1" 2 $PackageID = "PS100005" 3 $BootImage = Get-WmiObject -Namespace "root\SMS\site_$($SiteCode)" -Class SMS_BootImagePackage -Filter "PackageID = '$($PackageID)'" -ErrorAction Stop 4 $BootImage.ReloadImageProperties()

Make sure to specify the correct site code and package ID for the Boot Image to update.

Now run the script with administrative privileges.

Voilà your boot image is now updated to Windows 10 ADK, and you can add drivers and customize to you image again.

2015-08-17 13_55_58-Coretech - ctcm01.coretech.intra - [SCCM 2012 server] - Royal TS

Remember to update your distribution points to build the image and redeploy content.

source : http://blog.coretech.dk/hra/missing-tabs-on-boot-image-after-installing-adk-for-windows-10-in-configmgr/


Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s

Blog at WordPress.com.

Up ↑

%d bloggers like this: