Impact of 8.1 update on 2012 R2 Essentials

A note from Joe Raby about the impact of 8.1 update on 2012 R2 Essentials:

 You might want to post this note about updating “Windows Server Essentials 2012 R2 with Update”:

Manual upgraders might want to update their Client Restore Service WinPE images on WDS (and USB sticks) so that they match the new baseline code version.  A folder must be deleted for it to recreate the WinPE images, and it’s located at ProgramData\Microsoft\Windows Server\Data\ClientRestore\(big long version string)\(codepage language), eg:

C:\ProgramData\Microsoft\Windows Server\Data\ClientRestore\8.100.25984_8_100_25984_6.3.9600.16384409

After updating WSe to “Update 1”, you need to get the new version of the ADK.  When you run the installer on the server, it just checks to see what’s installed and only current components will be updated by default (nothing else is checked – I know you like that, Sue).  When the ADK is updated, just delete the codepage folder in it’s entirety, delete the WinPE Boot images in WDS, and then go back into the Dashboard, to Home|Setup|Set up Client Restore Service, and click the Restart button.  It will use the new ADK to create new WinPE images and put them into WDS for you just like it always did, but now they’ll have the new codebase revision (WinPE 5.1).

Note: MSDN does NOT have an updated ISO for “WSe 2012 R2 with Update” yet – only the single image for Standard & Datacenter.  The update package with the supplemental updates are available now.

Also note: I only mention this because I DID upgrade my server already….no don’t start screaming yet.  My server only has tech stuff on it (OS’s and Office installation files and such), so I want it to be bleeding edge (without being in beta) to cater to customers with all the new tech goodies from day one.  There is no “business data” on it in the conventional sense.  My “line-of-business software” is software deployment packages.

One Thought on “Impact of 8.1 update on 2012 R2 Essentials

  1. Tommy on April 15, 2014 at 3:50 pm said:

    I tried this on my WS2012E R2 server but now, the Client Restore Service won’t work. I get an error every time I click on Restart service.


Post Navigation