Author: Aaron Czechowski, Senior Program Manager
This post applies to customers using System Center 2012 R2 Configuration Manager, or customers using System Center 2012 Configuration Manager SP1 that have installed the Windows Assessment and Deployment Kit (ADK) for Windows 8.1 on a standalone system in order to acquire the Windows PE 5.0 boot image or the USMT 6.3 package. (Do not install the Windows ADK for Windows 8.1 on System Center 2012 Configuration Manager SP1 site servers.). If you are also using the Microsoft Deployment Toolkit (MDT) see this post.
A revision to the Windows ADK for Windows 8.1 Update is now available. See this post for more information.
We recommend all customers of System Center 2012 Configuration Manager upgrade to the latest ADK, but this upgrade is not required. You can continue to use an existing version of the Windows 8.1 ADK or the Windows 8.1 Update revision to service and deploy all Windows 8.1 (including Windows 8.1 Update), Windows 8, and Windows 7 images. If you do upgrade, you don’t have to uninstall the previous version first; running the ADK setup will update the existing components of the ADK installation.
After upgrading the ADK to the latest version, here are a few general items of note for Configuration Manager:
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.
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:
If your images and deployments include language packs, be sure to consider the following:
We’ve been working closely with Windows engineering on streamlining this process as much as possible. I’m always interested in your feedback, or feel free to post your questions below, especially if there are Configuration Manager deployment scenarios not covered here.
-- Aaron Czechowski, Sr. Program Manager
Configuration Manager Resources
Documentation Library for System Center 2012 Configuration Manager
System Center 2012 Configuration Manager Forums
System Center 2012 Configuration Manager Survival Guide
System Center Configuration Manager Support
This posting is provided "AS IS" with no warranties and confers no rights.
How is update 1 beinv deployed for vl windows 8 ? Will it need to be a upgrade like 8.0 to 8.1 ? Or will it be windows update/wsus ?
@Matt - hit the link above to the Windows Springboard blog that talks to that. Basically, it will be published as an update next week during the normal cycle.
Will the 8.1 language pack still Work for the "8.1 update" Wim? First thing I do is add .net and add language packs before CM12R2 ever gets to see the Wim file, then offline update it from the CM consoleDism /Image:C:\Temp\Image /enable-feature /featurename:NetFX3 /All /Source:C:\Temp\sxs /LimitAccessDism /Image:C:\Temp\Image /ScratchDir:C:\temp\Scratch /Add-Package /PackagePath:"C:\Language Pack\xx-xx\lp.cab"
I'll rewrite my question... On MSDN I can download "Windows 8.1" and "Windows 8.1 with Update". If I choose "Windows 8.1" I also see Language Packs. If I choose "Windows 8.1 with Update" I see NO Language Packs. Does the "Windows 8.1" Language Packs Work with "Windows 8.1 with Update" or are we still waiting for the "Windows 8.1 with Update" Language Packs to become available?
Which version of ADK should we use when deploying ConfigMgr from Scratch?
@DennisThe DISM Funktion to add Language Packes still running the same way And are still the same Packages from 8.1 http://support.microsoft.com/kb/2839636 no update for the Update 1 ;-), to add the .Net4 Feature i am not shure at this Moment...@ Kennethi think if you use Config Mgr R2 (CU1) from scratch you have to use the ADK without update, in case of deploying the Win8.1 U1 release then you have to update the ADK but you have to prepare the WinPE 5.1 manualy to us it in Config Manger...
@Dennis - I would suggest following the link at the top of the article to the Windows Springboard blog and posting your question re language packs there. I wanted to call out that there are considerations for ConfigMgr admins around Windows 8.1 Update and language packs, but the details were not finalized by the date of this post. @Kenneth - good question which I should have addressed in the post. Assuming you're referring to System Center 2012 R2 Configuration Manager, your only option today is the latest Windows 8.1 ADK, there is only one available for download. But for a new install it should function just the same.
Thanks for the help :o)Maybe this is not the place to bark but I found this article http://technet.microsoft.com/en-us/library/dn613858.aspx that as an example uses a German language pack update "Windows8.1-KB2938327-x64.msu" to update the 8.1 Update 1 wim file AFTER the 8.1 RTM language pack has been addedAnyone knows how to find KB2938327? I've checked Volume Licensing Service Center and my MDSN Ultimate download page and can not find itArticle above says "The Windows 8.1 Update language pack updates are available to OEMs only" - where does that leave huge enterprise customers trying to deploy Windows 8.1 with update 1 and multiple languages?
Answering my own question here :o)http://technet.microsoft.com/en-us/library/dn613858.aspx states that "The following language pack updates will be available to OEMs" so I went to http://oem.microsoft.com and registered... In the download section "windows_8.1_update_64bit_lip_multi_language.img" was available containing all the needed files:KB2938323, KB2938324, KB2938325, KB2938326, KB2938327, KB2938328, KB2938329, KB2938322, KB2938330, KB2938332, KB2938333, KB2938334, KB2938335, KB2938336, KB2938339, KB2938340, KB2938341, KB2938344, KB2938345, KB2938347, KB2938348, KB2938258, KB2938296, KB2938298, KB2938301, KB2938304, KB2938307, KB2938308, KB2938306, KB2938311, KB2938312, KB2938313, KB2938315, KB2938317, KB2938318, KB2938320Someone must think that Enterprise customers do not need these updates...