Creating a custom SCCM boot image wizard

Assumption 1: you have MDT 2010 Update 1 installed and understand the basic principles of MDT and boot images in a WIM format
Assumption 2: you have configured MDT integration with SCCM
Assumption 3: you understand how to create and edit SCCM Task Sequences within SCCM Operating System Deployment

  1. Create a file structure for your image management (I like to create [Drive]:\Install\OSD with the following subdirectories – “BootImage”, “ISO”, “MDT2010Files”, “OperatingSystem”, and “USMT”)
  2. Share “Install” (you can decide on permissions – I only allow Domain and Local Administrators with a few functional roles as discretionary additions)
  3. Create a subfolder in ““[Drive]:\Install\OSD\BootImage\” named “PreExecutionServerx86” or “PreExecutionClientx86” and “Mount”
  4. Create a subfolder in ““[Drive]:\Install\OSD\BootImage\” named “Serverx86” or “Clientx86”
  5. Copy all of the files from “[InstallDrive]:\Program Files\Microsoft Deployment Toolkit\SCCM” to “[Drive]:\Install\OSD\BootImage\PreExecutionServerx86” OR “[Drive]:\Install\OSD\BootImage\PreExecutionClientx86”
  6. Copy all of he files from “[Drive]:\DeploymentShare\Scripts” to “[Drive]:\Install\OSD\BootImage\PreExecutionServerx86” OR “[Drive]:\Install\OSD\BootImage\PreExecutionClientx86”
  7. Open “WizardEditor.exe” from “[Drive]:\Install\OSD\BootImage\PreExecutionServerx86” OR “[Drive]:\Install\OSD\BootImage\PreExecutionClientx86”
  8. Click on “File” and then “Open” in the “Microsoft Deployment Toolkit Wizard Editor”
  9. Select “Deploy_SCCM_Definition_ENU.xml” and click “Open”
  10. Create your wizard – below are a couple of examples I am using…
  11. “OSType”



  12. TimeZoneSelect



  13. Once you have created all of your wizard settings click on “File” and then “Save”
  14. Close the wizard editor
  15. You will need to crate a custom MDT boot image within the SCCM console
  16. Within the SCCM console go to Computer Management – Operating System Deployment – Boot Images and click on “Create Boot Image using Microsoft Deployment”
  17. Type the UNC path for the location to store your boot image and click “Next” (i.e. “\\SERVER\Install\OSD\BootIMage\Serverx86”)
  18. Provide a name, version, and any comments and click “Next” (I name mine “Server Deployment Boot Image (x86)”)
  19. Put a check next to “Add media hook files to enable the Deployment Wizard for this boot media” and click “Next”
  20. Click “Next” with defaults for the rest to finish it out
  21. Once the custom boot image appears add it to a SCCM Distribution Point (DP)
  22. Open the “Deployment Tools Command Prompt” with elevated privileges
  23. Type either “imagex /mountrw [Drive]:\Install\OSD\BootImage\Serverx86\WinPE.wim 1 [Drive]:\Install\OSD\BootImage\Mount” OR “imagex /mountrw [Drive]:\Install\OSD\BootImage\Clientx86\WinPE.wim 1 [Drive]:\Install\OSD\BootImage\Mount”
  24. The image will be mounted to the temporary location of “[Drive]:\Install\OSD\BootImage\Mount”
  25. Copy “Deploy_SCCM_Definition_ENU.xml” from “[Drive]:\Install\OSD\BootImage\PreExecutionServerx86” OR “[Drive]:\Install\OSD\BootImage\PreExecutionClientx86” to “[Drive]:\Install\OSD\BootImage\Mount\Deploy\Scripts”
  26. Type “imagex /commit [Drive]:\Install\OSD\BootImage\Mount”
  27. The change will commit in the temporary location
  28. Type “imagex /unmount [Drive]:\Install\OSD\BootImage\Mount”
  29. The image with the changes committed will unmount and copy to either “[Drive]:\Install\OSD\BootImage\Serverx86” OR “[Drive]:\Install\OSD\BootImage\Clientx86”
  30. In the SCCM console update the custom boot image that you create and optionally create a bootable CD/DVD or USB drive
  31. If you do not have a “Task Sequence” (TS) created for an OS deployment yet create one
  32. An example you can follow is to edit your TS and create a group for an OS version – in this case I used “Microsoft Windows Server 2008 SP2 Ent (x86)”
  33. In the group “Options” you should add a condition “If All the conditions are true:” and specify the appropriate TS Variable
  34. The TS variable comes from the wizard that was created – in this case if the option for Windows Server 2008 SP2 (x86) was selected the TS variable is “WinSvr2k8SP2Entx86”
  35. You can use these variables to beef up your TS and empower those imaging to customize the deployment without having to mess with the SCCM console or add steps afterward
  1. No comments yet.
  1. No trackbacks yet.

Leave a Reply

Fill in your details below or click an icon to log in: Logo

You are commenting using your account. Log Out /  Change )

Google+ photo

You are commenting using your Google+ account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )


Connecting to %s

%d bloggers like this: