Thursday, May 23, 2013

No ConfigMgr boot images created during installation

Last month I did a new ConfigMgr 2012 SP1 installation. During installation there were no boot images (based on WinPE 4.0) created. This because McAfee VirusScan was active during the installation & configuration. I saw that before doing another installation when upgrading from ConfigMgr 2012 to SP1. That post can be found here: Boot images not updated after upgrading to ConfigMgr 2012 SP1. This time no boot images were created at all.

Let's have a look how to create them manually. The steps are different then before, so a new blogpost is needed.
  • Rename the boot.wim and the default boot wims in each architecture folder of the <smsinstall>OSD\boot\ folder – both the i386 and x64 to <wim>.bak
  • Starting with the i386 folder first...Find the install folder of the ADK, which should be here if you installed with the defaults: “C:\Program Files (x86)\Windows Kits\8.0\Assessment and Deployment Kit\Windows Preinstallation Environment\x86\en-us\winpe.wim”. You will need to copy the winpe.wim to the <smsinstall>OSD\boot\i386 folder. Rename it to boot.wim.
  • Import the boot images in ConfigMgr with the following lines: Name: Boot image (x86), Version: 6.2.9200.16384, Image path: \\<SCCM server>\<SCCM Site code>\OSD\Boot\i386\boot.wim and for the second one: Name: Boot image (x64), Version: 6.2.9200.16384, Image path: \\<SCCM server>\<SCCM Site code>\OSD\Boot\x64\boot.wim
  • Don't forget to check "Deploy this boot image from the PXE-enabled distribution point" and press Apply. After that a new boot image is created in the <smsinstall>OSD\boot\ folder, with the PackageID in the name. This will be copied to the RemoteInstall folder (WDS) also.

Just do an "Distribute Content" to add them both to the Distribution point, and boot images are there again!

No comments:

Post a Comment