DISM and imaging Windows with HP scripting toolkit for Windows 10.10

Adding drivers for WinPE boot image to get all drivers for HP Scripting toolkit for Windows loaded  is not correctly documented in its UserGuide. First of all download HP scripting tools for Windows and extraxt it to some folder. Use next commands for DISM tool (Deployment Image Servicing and Management). Use winpe.wim file you can find under Windows Preinstalation Enviroment folder in WADK. Use platform you need x86 or x64

#mount image to already created folder
dism /mount-wim /wimfile:c:\winpe\winpe.wim /index:1 /mountdir:e:\temp
#add drivers
dism /image:e:\temp /add-driver /driver:c:\swsetup\sp67765\x64\drivers\winpe50 /recurse /forceunsigned 
#copy HPSTKIO.SYS driver
copy c:\swsetup\sp67765\x64\drivers\winpe50\system\hpsstkio\hpsstkio.sys e:\temp\windows\system32\drivers
#copy tools folder to image
md e:\temp\tools
copy c:\swsetup\sp67765\x64\tools\*.* e:\temp\tools
#save changes to image and unmount it
dism /unmount-wim /mountdir:e:\temp /commit

image

If you want to see a list off all 3rd party drivers mount image again and type

dism /image:e:\temp /get-drivers

image

I assume you use MDT 2013 for creating bootable ISO file. To create it thick this options on Properties od Deployment Share for x64 and x86 platform. After you changed winpe.wim file with procedure above you need to run update deployment share,  it will create new LiteTouchPE_x64.iso file with changes in winpe.wim file.

image

image

Boot HP Proliant server with LiteTouchPE_x64.iso . Press F8 to open command prompt. Ping some computer to check for network connectivity. Map network share where you will save hp configuration files. You can save ILO, system BIOS setting and storage adapter configuration. I am only saving storage configuration because I need only that, and for all other settings consult HP Scripting Toolkit User Guide Smile. Navigate to tools folder, map network share, and then save array configuration.

net use k:\ \\serveripaddress_orname\share
hpssascripting -c k:\dl360g8storagearray.ini

image

For changing Keyboard layout to choose you local edit bootstrap.ini file, and update Deployment share after that.  Line to add is KeyboardLocalePE=041a:0000041a (for my keyboard code)

image

For Deployment wizard you will usually have some default value you will have (Time zone, User Locale etc.) To fill wizard with already predefined values edit Rules windows in MDT 2013. This is my setup

image

If you want to have you local keyboard code page in command prompt you need to set it by DISM tool on your winpe.wim image. You have short example on picture down for setting keyboard layout but if you need more info consult this page. After setup please update Deployment share to update iso file.

image

For getting all settings type next command

image

After that login to reference computer to create image. Open deploymentshare on MDT server from windows explorer and run Litetouch script from scripts folder. You will get this windows and chose sysprep and capture sequence you created on MDT server. Fill in other needed info and capture will begin.

image

 

image

Procedure to restore it to another computer is:

  1. Boot PC from LiteTouchPE_x64.iso  image
  2. Press F8 on Microsoft Deployment Toolkit to enter command prompt
  3. Navigate to Tools folder and run commands to restore storage array configuration on computer
net use k:\ \\serveripaddress_orname\share
hpssascripting -i k:\dl360g8storagearray.ini

After that close command prompt, reboot and continue to deploy image on target computer. I hope article  helped. I am sorry if it is missing real step by step approach, because I was writing it during longer period of time.

Advertisements

Leave a Reply

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

WordPress.com Logo

You are commenting using your WordPress.com 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 )

Google+ photo

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

Connecting to %s