Want to have HTA support in your SCCM 2007 SP2 boot images (with WinPE 3.0), but don’t want to implement MDT 2010? Follow these short instructions to get yourself on your way! When doing this for the first time, I recommend using a copy of the boot.wim and not your production boot.wim!!
The general process for doing this:
- Ensure you have installed the WAIK for Windows 7
- Mount the base image by using the DISM tool to a local directory share. For example,
Dism /Mount-Wim /WimFile:C:\winpe_x86\winpe.wim /index:1 /MountDir:C:\winpe_x86\mount
- Add packages, and language packs as appropriate by using the Dism command with the /Add-Package option. For example, to add the HTA package you must add both the language neutral package along with the language specific package. For example:
Dism /image:C:\winpe_x86\mount /Add-Package /PackagePath:”C:\Program Files\Windows AIK\Tools\PETools\x86\WinPE_FPs\WinPE-HTA.cab”
Dism /image:C:\winpe_x86\mount /Add-Package /PackagePath:”C:\Program Files\Windows AIK\Tools\PETools\x86\WinPE_FPs\en-us\WinPE-HTA_en-us.cab”
- Commit the changes using the Dism command with the /Unmount-Wim /Commit option. For example,
Dism /Unmount-Wim /MountDir:C:\winpe_x86\mount /Commit
- Import the .wim into SCCM and, voila, you now have a boot image with HTA support!
Reference: http://technet.microsoft.com/en-us/library/dd799244.aspx
#1 by Patrick Moons on May 30, 2011 - 3:41 am
Thanx for this usefull information, i dislike the MDT2010 wizards and would like to use my own hta in my sccm task sequence. When i follow your procedure it returns a succesfull update boot.wim file, i can even import it in SCCM as a Custom boot image. I added a network driver via SCCM and enabled command support (no issues here) But when i want to boot my task sequence from this new boot image, i get Failed to run task sequence (0×80091007) . The only differece is the boot image. :( The architecture is correct (x86) I don’t get it. There is also no task sequence log i can view. Any ideas?
#2 by Nicolas Moseley on May 31, 2011 - 2:38 pm
Just a quick Bing search on the error code says that it’s related to hash error or package content mismatch. If you didn’t already do it, make sure to update your distribution points after the changes you made by adding drivers and enabling command support.
#3 by Patrick Moons on June 1, 2011 - 7:26 am
Yep that did it, i update the distribution points and it booted. Thanx a lot :)
#4 by Nicolas Moseley on June 1, 2011 - 7:27 am
Great!!