How to add Setup.exe drivers during HII in LDMS 9.0

Applies to LANDesk Management Suite 9.0

LANDesk Management Suite 9.5 adds the ability to point to driver setup packages

One of the problems that I have seen with LANDESK 9 HII is the inability to load Setup.exe drivers during the HII process.  To many this is a big deal because a lot of drivers these days require applications to run them, One example is the HP Quicklaunch buttons for laptops. Which have drivers embedded in the executable and the application is required to use the driver like On Screen Display messages.  I personally like to have those installed on my models.

Here is a workaround that I have found that is quite successful in getting this job done with a little AutoIT scripting.  Wmi_model.exe will detect your System Model and deploy another script based off of that system.

• Modify the wmi_model.au3 to address your specific model types and build the wmi_model.exe with autoIT.
• Create a batch file to deploy your setup.exe driver files

• Place your driver setup files in your image (im my example i have them in c:\drivers\setup)

     (Optional:  You don't have to place these files in your image if you want to conserve image space, you can copy them over during the HII imaging      process if you want.  How you get the files to that location is up to your preference as long as they are there when sysprep runs)

• Sort them by application: ie:  c:\drivers\setup\quicklaunch, c:\drivers\setup\3ddriveguard, etc
• Place the wmi_model.exe in c:\drivers\setup
• Place your system .bat files in c:\drivers\setup  (ie: c:\drivers\setup\rp5700.bat)

• Modify your Sysprep file and add the following line to your sysprep.inf (XP) or modify unattend.xml (Win7) with WSIM (Windows System Image Manager)

Now you can deploy your image the following process will take place:

• Image is Deployed
• LANDESK takes care of the hal, msd and pnp drivers
• sysprep will take place then launch wmi_model.exe at first log on
• wmi_model.exe which will detect its System Model thru a WMI call and based on its System Model will point to your batch file that will apply your setup.exe driver applications.

About Wmi_model.exe

Determines WMI_Model, then deploys appropriate Drivers

Change History:
v1.2 - April 27, 2011 - Added Wildcard LIKE support for model names

You will need ScITE editor to modify and build the application
Download: http://www.autoitscript.com/autoit3/downloads.shtml

Source Code:

; AutoIt Version: 3.0
; Language:       English
; Platform:       Win9x/NT
;
; Script Function:
;   Determines WMI_Model, Then Deploys Appropriate Drivers
;   Change History:
;   v1.2 - April 27, 2011 - Added Wildcard LIKE support for model names

#AutoIt3Wrapper_Au3Check_Parameters=-q -d -w1 -w2 -w3 -w4 -w5 -w6
Local $sPC = ".", $sScript, $model

Local $oWMIService = ObjGet("WinMgmts:\\" & $sPC & "\root\CIMV2")
If IsObj($oWMIService) Then    Local $colItems = $oWMIService.ExecQuery('SELECT * FROM Win32_ComputerSystem', 'WQL', 0x30)    If IsObj($colItems) Then        For $oItem In $colItems            $model = $oItem.Model            Switch $model                Case StringInstr ( $model, "System Model" ) <> 0                    MsgBox(64,"Image Configuration", "The PC Model is:  " & " " & $model,3)                    RunWait("C:\drivers\setup\name.bat")                Case StringInstr ( $model, "System Model" ) <> 0                    MsgBox(64,"Image Configuration", "The PC Model is:  " & " " & $model,3)                    RunWait("C:\drivers\setup\name.bat")                Case StringInstr ( $model, "System Model" ) <> 0                    MsgBox(64,"Image Configuration", "The PC Model is:  " & " " & $model,3)                    RunWait("C:\drivers\setup\name.bat")                Case StringInstr ( $model, "System Model" ) <> 0                    MsgBox(64,"Image Configuration", "The PC Model is:  " & " " & $model,3)                    RunWait("C:\drivers\setup\name.bat")                Case Else                    MsgBox(16, "", "The PC Model is: " & $model & @CRLF & " There is no configuration for this model",5)                    Exit            EndSwitch        Next    EndIf
EndIf

Attached is the source code and I will explain what you need to do to modify.

• Modify the line Case StringInstr ( $model, "System Model" ) <> 0 with your System Model.  This new modified script will allow more of a WildCard type expressions to matched.  Before you had to have exact match, but I had issues with System Models having multiple System Names like HP Compaq 6000 Pro Small Form Factor and HP Compaq 6000 Pro SFF.  Now you only have to put in HP Compaq 6000 Pro  and it will detect both models.

       Example:Case StringInstr ( $model, "HP Compaq 6000 Pro" ) <> 0

• Modify RunWait("C:\drivers\setup\name.bat") with the .bat, .vbs,.exe, etc. that you will be calling that holds all the setup.exe launch commands.     

       Example:RunWait("C:\drivers\setup\6445b.bat")

• Add more Case items per model you want to use. I supplied 4 examples, but you can just add/remove as many as you want.
• Optional - If you don't want the MSG box to pop up and want it completely silent, remove the  MsgBox lines
  

Example of a Batch Script to run:

6445b.bat

 

::6445b.bat

::Install applications for HP 6445b

@ECHO OFF

 

:Install QuickLaunch Buttons

Start /wait C:\Drivers\setup\quicklaunch\Disk1\setup.exe -s

 

:Install 3D Drive Guard

Start /wait msiexec /i C:\Drivers\setup\3ddriveguard\HPMDPAI32.msi /qn /norestart

 

Exit