Rob,
Yes, sir. Thanks, I must have overlooked that! I've highlighted the tl;dr text below. Windows PE 5.1 The Windows ADK for Windows 8.1 Update still includes Windows PE 5.0 (including the Windows PE 5.0 optional components and language packs), the same as the previous versions of the Windows ADK for Windows 8.1. The Windows PE documentation references Windows PE 5.1 for supporting WimBoot deployments. (Remember, Configuration Manager does not yet support WimBoot.) Windows PE version 5.1 is not needed for Configuration Manager and can actually be problematic if you try to use it. 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. Keep reading if you want more details about this, otherwise skip to the next section. 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. OK, but we now support importing alternate versions of Windows PE, right? Yes, but the OS version of Windows PE 5.1 is still 6.3 (specifically 6.3.9600.17031 or similar version, compared to 6.3.9600.16384 for the Windows 8.1 General Availability version), which is the extent of our determination for in-console servicing. So, if you manually create a Windows PE 5.1 boot image and import it into Configuration Manager, you can still perform servicing operations on that boot image, including adding optional components. By servicing the boot image, or even just updating the boot image for any other reason, you introduce the need to rebuild the image from source files. Configuration Manager will inject the four Optional Components that it requires along with any additional modifications that you have requested. As mentioned above, because we have no ability to inject the Windows 8.1 Update package and cleanup the boot image, it will either be completely reverted back to Windows PE 5.0 or will be a Windows PE 5.1 boot image with older Windows PE 5.0 optional components, which is obviously problematic. Cheers, Trevor Sullivan From: [email protected] [mailto:[email protected]] On Behalf Of Robert Marshall Sent: Monday, April 14, 2014 9:39 AM To: [email protected]; [email protected] Subject: RE: [mssms] WinPE 5.1 w/ ConfigMgr 2012 R2 This help? http://blogs.technet.com/b/configmgrteam/archive/2014/04/03/understanding-th e-adk-for-windows-8-1-update-and-configmgr-osd.aspx http://blogs.technet.com/b/msdeployment/archive/2014/04/03/understanding-the -adk-for-windows-8-1-update-and-mdt-2013.aspx Robert From: [email protected] <mailto:[email protected]> [mailto:[email protected]] On Behalf Of Trevor Sullivan Sent: 14 April 2014 15:23 To: [email protected] <mailto:[email protected]> ; [email protected] <mailto:[email protected]> Subject: [mssms] WinPE 5.1 w/ ConfigMgr 2012 R2 Hello folks, Is it currently supported to update WinPE 5.0 boot images to WinPE 5.1 using the process outlined on Microsoft TechNet <http://technet.microsoft.com/en-us/library/dn613859.aspx> , when running ConfigMgr 2012 R2 (with or without Cumulative Update 1)? Cheers, Trevor Sullivan Microsoft PowerShell MVP
