SCCM 2012 R2 SP1: Boot Image issue

I recently upgraded my SCCM 2012 R2 infrastructure to SP1.

As the first step I uninstall ADK for Windows 8.1 and installed ADK for Windows 10. This is not a requirement, but I found it is much easier to replace ADK during SCCM upgrade than change it later.

I followed this guide for upgrade.

Upgrade passed smoothly, but I noted 64-bit boot image was not upgraded and still showed an old (Windows 8.1) version. I tried to update it from SCCM console, but that attempt failed.

So, I found this article recommending to set exceptions in Antivirus for c:\windows\temp\bootimage folder and <ConfigMgr Instalation folder>\osd\boot folder. After that I could create a new image for 64-bit platform, but still could not fix the default one.

Kent Agerlund recommends to re-copy winpe.wim  from ADK to replace both boot.wim and boot.<PakageID>.wim files and after that RELOAD the proble boot image. I did it and found I am missing a bunch of tabs when open Properties of a boot image! including one with reload button.

Fortunately I found another article describing how to reload the image using PowerShell. Thank you Justin, you wrote your script just in time!

Here is Justin’s script (be sure you replace site code and Package ID):

# ################# DISCLAIMER # Microsoft provides script, macro, and other code examples for illustration only, without warranty either expressed or implied, including but not # limited to the implied warranties of merchantability and/or fitness for a particular purpose. This script is provided ‘as is’ and Microsoft does not # guarantee that the following script, macro, or code can be used in all situations. # Replace line 9 with your SiteCode # Replace line 10 with the boot image PackageID to Reload $SiteCode = “PR1” $BootImage = Get-WmiObject -Namespace “root\SMS\site_$($SiteCode)” -Class SMS_BootImagePackage -Filter “PackageID = ‘PR100003′” -ErrorAction Stop $BootImage.ReloadImageProperties()

 

I also need to set Exectution policy to allow the script to be ran:

Set-ExecutionPolicy -Scope Process -ExecutionPolicy Bypass

As soon as the script finished necessary tabs reappeared in SCCM console right OS version was indicated for the boot image and I could distribute the image to DPs successfully.

WinPE: The following processor architecture was not found: amd64.

Problem:

I am trying to create a WinPE bootable flash drive for WinPE 4.0 provided by Windows Assessment and Deployment Kit 8.1

to prepare WinPE Source directory I navigate to “C:\Program Files (x86)\Windows Kits\8.1\Assessment and Deployment Kit\Windows Preinstallation Environment” folder (default installation for ADK) and run

copype amd64 d:\WinPE_amd64

The installation fails with error:

ERROR: The following processor architecture was not found: amd64.

 

Resolution:

after digging copype.cmd I found that some variables are missing. I guess they were set up with older version of WAIK, when we had a chance to start “WAIK” command prompt; but now we (at least I) do not have this customized command prompt in Windows 8/8.1 and the variables are not set.

So, I added the variables manually and change a line in the batch file (copype.cmd)

Here are variables I added (there are two variables, each on its own line, depending on your installation path – mine are default):

set WinPERoot=C:\Program Files (x86)\Windows Kits\8.1\Assessment and Deployment Kit\Windows Preinstallation Environment
set OSCDImgRoot=C:\Program Files (x86)\Windows Kits\8.1\Assessment and Deployment Kit\Deployment Tools

and I also changed FWFILESROOT line to:

set FWFILESROOT=%OSCDImgRoot%\%WINPE_ARCH%\Oscdimg    (I added a variable and removed “\..\..”)

At the end the changed part of copype.cmd looks like (changes are in red):

rem
rem Set environment variables for use in the script
rem
set WINPE_ARCH=%1
set WinPERoot=C:\Program Files (x86)\Windows Kits\8.1\Assessment and Deployment Kit\Windows Preinstallation Environment
set OSCDImgRoot=C:\Program Files (x86)\Windows Kits\8.1\Assessment and Deployment Kit\Deployment Tools
set SOURCE=%WinPERoot%\%WINPE_ARCH%
set FWFILESROOT=%OSCDImgRoot%\%WINPE_ARCH%\Oscdimg
set DEST=%~2
set WIMSOURCEPATH=%SOURCE%\en-us\winpe.wim

After that I saved the changed copype.cmd and reran it – It generated source WinPE folder structure for me successfully.

Speed up graphics in Windows Servers running on VMWare platform

Found an article explaining procedure of speeding up graphics on VMWare-based VMs (in addition to VMWare Tools installation). The matter in face even with installed VMWare tools the machines are mot using WDDM driver. Bust they can be installed manually from C:\Program Files\Common Files\VMware\Drivers\wddm_video. The drivers can also be injected in WinPE images.

Setting resolution in WinPE 4.0

Windows 8 uses a new version of WinPE. Apparently the Winpe4.0 does not support 16-bit color depth anymore. So to change resolution you have to add the following to your unattend.xml:

<Display>
  <ColorDepth>32</ColorDepth>
  <HorizontalResolution>1024</HorizontalResolution>
  <RefreshRate>60</RefreshRate>
  <VerticalResolution>768</VerticalResolution>
</Display>

 

The solution is found here