Brandon Linton - System Center and OS Deployment Blog

The Do's, Don'ts and what did i do's of System Center and OS Deployment...

How to Create and Import a WinPE 3.1 Boot image for use in ConfigMgr 2012 SP1 CU2

How to Create and Import a WinPE 3.1 Boot image for use in ConfigMgr 2012 SP1 CU2

  • Comments 21
  • Likes

 1) Install the WAIK 3.0 package on a remote system 

      NOTE: It is not recommended to have the ADK and WAIK installed on the same system.

2) Install the WAIK 3.1 Supplement update package

3) To install the supplemental update open a command prompt and perform the following command.

      NOTE: 1131 Files should be copied.



4) Open the Deployment Tools Command Prompt



5) Follow the How to Create a Custom Windows PE Image guide to create the custom boot image.

NOTE: add required components:





6) Optionally add drivers to the wim image before completing step 5.


7) Copy the boot.wim file created in step 5 to your ConfigMgr server.

8) Name the boot image appropriately for good house keeping “WinPE 3.1 Boot Image x86

9) Open the ConfigMgr Console and Navigate to Software Library à Operating Systems à Boot images.

10) Select Add Boot Image


11) Specify the UNC Path to your custom boot image and select Next.



12) Supply the Name and Version of your boot image and select Next.



13)  Select Next on the Summary Screen.



14) Next let’s deploy the boot image to PXE enabled DP’s by selecting the following option in the boot image properties.



15) You should now have a functional WinPE 3.1 boot image to use with your legacy systems.

NOTE: Some tabs will appear greyed out in the Boot image properties this is normal as the following options are NOT supported with WinPE 3.1 boot images.

Adding drivers

◦Setting scratch space

◦Configuring prestart command

◦Configuring background image file

◦Enabling and disabling command prompt support (debug mode)


** Lastly you might also be able to copy your existing WinPE 3.1 boot images from your ConfigMgr RTM or ConfigMgr 2007 site for import into ConfigMgr 2012 SP1 CU2 but i have yet to test this...


Disclaimer: The information on this site is provided "AS IS" with no warranties, confers no rights, and is not supported by the authors or Microsoft Corporation. Use of included script samples are subject to the terms specified
in the
Terms of Use.


  • Do you know why my drop down won't populate with the newly created wim file at the beginning of the import stage? I followed your instructions exactly and have applied CU2 successfully.

  • Did you ensure to apply the WinPE 3.1 Supplemental Update?  Did you supply a valid UNC Path to the boot image that ConfigMgr can access?  I would take a look at the smsprov.log on the site server and or the distmgr.log to see if there are any errors.

  • This was probably just stupidity on my part but it seems that I had to import the boot image on the site server itself not a remote console, which is what I was trying. Forgive me...your tutorial works great and exactly what I needed so thank you!

  • Glad it helped appreciate the feedback!

  • Tested and working in my 2012 SP1 CU2 lab, I'm really glad MS have made this tweak in CU2 it really helps us Admins that have to look after a few remaining bits of much older kit that don't support 4.0 Many thanks!

  • I get to step 13 (trying to add the boot.wim to the boot images in SCCM) and get the error message "You can not import this boot image. Only finalized boot images are supported. For more information press F1." when I try to finish the process. I have unmounted/ committed the wim and it is named "boot.wim".

    I see other people historically had this problem ( but there's not much help there. Do I need to have WAIK installed on the SCCM server (I thought that conflicts with the new WADK install?)

  • @herbuveaux No you do not need to have WAIK installed on the server and it should not be or you will have problems.  Many things could cause this but first i would verify you don't have Mcafee installed on the server or any other AV blocking this action from happening.  You can validate the distmgr.log and or smsprov.log to see if there are any errors during the process.  what Windows ADK version do you have installed on the server and where are you performing these steps on the server itself or from a remote console?



  • smsprov.exe throws errors like: "failed to insert OSD binaries into WIM file", and ERROR> Error -2146498530 returned to execute the command line: "C:\Program Files (x86)\Windows Kits\8.0\Assessment and Deployment Kit\Deployment Tools\amd64\DISM\dism.exe" /Image:"C:\Windows\TEMP\BootImages\{67F77DE0-0762-4FAF-9F17-D9768EB7D22E}\mount" /Add-Package /PackagePath:"C:\Program Files (x86)\Windows Kits\8.0\Assessment and Deployment Kit\Windows Preinstallation Environment\amd64\WinPE_OCs\" 8/13/2013 2:05:15 PM 8044 (0x1F6C)

    Failed to install required components into the boot image C:\Windows\TEMP\BootImages\{67F77DE0-0762-4FAF-9F17-D9768EB7D22E}\mount 8/13/2013 2:05:15 PM 8044 (0x1F6C)

    *~*~e:\qfe\nts\sms\siteserver\sdk_provider\smsprov\sspbootimagepackage.cpp(3687) : Failed to insert OSD binaries into the WIM file~*~* 8/13/2013 2:05:36 PM 8044 (0x1F6C)

  • I am performing this from the server itself, and I don't have McAfee installed, but I'll turn off my AV and see...

  • Just turned off AV; it didn't help. No errors in distmgr. Some other errors from smsprov: ************ WBEM Missing property TransformAnalysisDate 8/13/2013 2:13:58 PM 8044 (0x1F6C)

    ************ WBEM Missing property TransformReadiness 8/13/2013 2:13:58 PM 8044 (0x1F6C)

  • ADK on the server is version 8.59.25584.

  • Am I right that this looks like SCCM is trying to add packages to my boot image, when all I'm trying to do is add the boot image itself? Why are there those lines about adding the scripting package? Didn't I just do that by hand, and wouldn't that mean it's trying to add WinPE 4.0 packages into a 3.1 image?

  • correct are you positive that you have CU2 installed on the server itself and on the admin console on the server?

  • Thank you for the quick help. Looks like I'm on CU1. Do I have to have CU2 for this to work?

  • Yes ConfigMgr 2012 SP1 CU2 is required for this to work.



Your comment has been posted.   Close
Thank you, your comment requires moderation so it may take a while to appear.   Close
Leave a Comment