Introduction
Microsoft have released Windows 8.1 update and a corresponding version of the Windows Assessment and Deployment Kit (Windows ADK) for Windows 8.1 Update.
This new version of the ADK was released to support the new update to Windows 8.1 called Windows 8.1 Update.
The Blogs
As a result they have written the following blogs regarding Windows 8.1 Update and the revised Windows Assessment and Deployment Kit (ADK), and what these mean for Configuration Manager Operating System Deployment and MDT.
- http://blogs.technet.com/b/msdeployment/archive/2014/04/03/understanding-the-adk-for-windows-8-1-update-and-mdt-2013.aspx
- http://blogs.technet.com/b/configmgrteam/archive/2014/04/03/understanding-the-adk-for-windows-8-1-update-and-configmgr-osd.aspx
What does it all mean ?
After upgrading the ADK to the latest version, here are a few general items of note for Configuration Manager:
- There are some bug fixes to the User State Migration Tool (USMT) in this revision, so the USMT package should be updated.
- Your existing Windows PE 5.0 boot images do not need to be updated after upgrading the Windows ADK. Windows PE 5.0 can be used to deploy Windows 8.1 Update images.
- We recommend using the latest full installation source (also known as “slipstreamed” or “refresh” media) for Windows 8.1 Update from the Volume Licensing Service Center (VLSC) as the starting point for your OS deployments. This media should be available on or about 14 April 2014.
- A Windows 8.1 Update OS image (refresh media or offline serviced) can be applied with the deployment tools natively present in Windows PE 5.0.
- Configuration Manager does not support the new WimBoot functionality at this time. We are investigating adding support for WimBoot to a future release.
What about WinPE 5.1
Windows PE 5.0 can continue to be used to deploy Windows 8.1 Update. There is a documented process to upgrade Windows PE to version 5.1, but this should be considered incompatible with Configuration Manager at this time.
Why can’t Configuration Manager use Windows PE 5.1? The process to create Windows PE 5.1 requires injecting the Windows 8.1 Update package into the Windows PE image, and if it also includes optional components or language packs these must be done in a specific order. The process then requires using the DISM /Cleanup-Image option with the /ResetBase parameter to cleanup and optimize the image before unmounting the image and committing the changes. Configuration Manager doesn’t currently support this sort of process during boot image servicing.
Windows 8.1 Update Servicing
As stated above, we recommend using the latest Windows 8.1 Update full media. If you need to service an existing Windows 8.1 image here are some tips:
- Windows 8.1 Update (KB2919355) requires a servicing stack update (KB2919442) to be installed as a prerequisite. This prerequisite update was released in March.
- Configuration Manager’s offline servicing functionality cannot guarantee the order in which updates are applied to an image. Process KB2919442 first and then rerun the offline servicing wizard to process KB2919355. (Note, this only applies to System Center 2012 R2 Configuration Manager; Windows 8.1 images cannot be serviced in-console with System Center 2012 Configuration Manager SP1.)
- Alternatively, these updates can be manually applied to an image using DISM /Add-Package commands, ensuring the correct order is followed.
- If applying the updates online, for example during a build and capture task sequence, they should first be created as packages and programs. This allows them to be added to the task sequence as explicit steps for proper ordering.
- Be sure to fully test the outcome of these actions before deploying your serviced image to clients.
- Did I mention that we recommend using the Windows 8.1 Update refresh media?
Language Packs
If your images and deployments include language packs, be sure to consider the following:
- As is always the case, per existing documentation, always install language packs before installing updates.
- Review the Windows 8.1 Update documentation for language packs to learn about additional details regarding any additional processing that must occur when applying language packs.
MDT 2013
After upgrading the ADK to the latest version, here are a few general items of note for MDT:
- There are some bug fixes to the User State Migration Tool (USMT) in this revision, so if you use USMT be sure to update the deployment share to refresh the USMT content.
- You do not need to update the deployment share to update boot images. Windows PE 5.0 can be used to deploy Windows 8.1 Update images.
- We recommend using the latest full installation source (also known as “slipstreamed” or “refresh” media) for Windows 8.1 Update from the Volume Licensing Service Center (VLSC) as the starting point for your OS deployments. This media should be available on or about 14 April 2014.
- A Windows 8.1 Update OS image (refresh media or offline serviced) can be applied with the deployment tools natively present in Windows PE 5.0.
- MDT does not support the new WimBoot functionality at this time. We are investigating adding support for WimBoot to a future release.
Summary
The new update to Windows 8.1 (referred to as the Windows 8.1 Update) adds new functionality and bugfixes however care should be taken to review the changes/effects of using it in conjunction with Configuration Manager 2012 R2 and/or MDT 2013.
- The updated ADK is not required, so you don’t have to install it.
- If you do install it you won’t have to uninstall the previous ADK, just let the installer upgrade it.
- If you intend to deploy Windows 8.1 Update using these tools then it’s recommended to use the new refreshed media when it becomes available (April 14th, 2014 or so).
- If you want to service existing Windows 8.1 images apply this Servicing Stack update.
