Description
Hardware Independent Imaging allows drivers to be injected during the imaging process specific to the destination hardware. During hardware migration planning, driver decisions must be made. In order to assist with that migration planning a preview option has been added to HII, enabling IT to review driver assignments prior to upgrading to a new OS.
Running HIIClient in Windows
- On the Client machine, create the directory C:\Windows\LDDriverStore\
- Copy HIIClient.exe to the new directory (LDDriverstore) on the client, from the core. The file can be found in the %LDMS_HOME%\landesk\files directory.
- Copy driver.db3 file to newly created folder on the client (C:\Windows\LDDriverStore) from the core. The file can be found in the HII library path. The default path is C:\Program Files\LANDesk\ManagementSuite\landesk\files\drivers
- Run HIIClient with the appropriate preview options (See below).
- Review the logs for driver assignment and detection found in the directory where HIIClient was run.
- HIIClient.log
- HIIPreview.log
Note: If HIIClient.exe is ran from a directory that the log is unable to be wrote to (i.e. C:\HiiClient.exe) it will write to C:\Windows\Temp\HIIClient.log
If your HIIPreview.log only shows the following, check the C:\Windows\Temp\HIIClient.log
***************** Starting HIIClient Preview *****************
Running in Windows
Running HIIClient in WinPE
- In WinPE HIIClient.exe already exists in x:ldprovision.
- The driver.db3 will need to be downloaded from the core. Use the "net use" command to map a drive to your HII library location on the core.
- Run HIIClient with the appropriate preview options (See below).
- Review the logs for driver assignment and detection found in the directory where HIIClient was run.
HIIClient options
hiiclient [/?] [/uncpath] [/taskid <taskid>] [/preview | /previewall] [/os <os> /arch <architecture>]
/? - Shows standard help and syntax information
/uncpath - Specifies if HII should use unc based paths to drivers
/taskid - Specifies the <taskid> to use to ask for SWD snippet when processing packaged drivers
/preview - Specifies if HII should run in preview only mode.
/previewall - Specifies if HII should run in preview only mode with debug information.
/os - Only valid with both /preview and /arch.
Specifies which OS the preview should be run for.
Valid options are: winxp, win7, win8, server2003, server2008r2, server2012
If not specified the currently detected OS will be used.
/arch - Only valid with both /preview and /os. Specifies which architecture the preview should be run for.
Valid options are: x86, x64.
If not specified the currently detected Architecture will be used for the preview.
HII Preview - Natural Driver Selection
Hardware device discovered. Device number 149:
Device name: Intel(R) 82574L Gigabit Network Connection
Primary device ID: PCI\VEN_8086&DEV_10D3&SUBSYS_07D015AD&REV_00
Additional device ID: PCI\VEN_8086&DEV_10D3&SUBSYS_07D015AD
Additional device ID: PCI\VEN_8086&DEV_10D3&CC_020000
Additional device ID: PCI\VEN_8086&DEV_10D3&CC_0200
Additional device ID: PCI\VEN_8086&DEV_10D3&REV_00
Additional device ID: PCI\VEN_8086&DEV_10D3
Automatically detected INF match discovered using device id PCI\VEN_8086&DEV_10D3.
Matching File: Windows 10 vm\Net\Intel(R) 82574L Gigabit Network Connection\net1ic64.inf
Additional device ID: PCI\VEN_8086&CC_020000
Additional device ID: PCI\VEN_8086&CC_0200
Additional device ID: PCI\VEN_8086
Additional device ID: PCI\CC_020000&DT_0
Additional device ID: PCI\CC_020000
Additional device ID: PCI\CC_0200&DT_0
Additional device ID: PCI\CC_0200
HII Preview - Driver Assignment
Hardware device discovered. Device number 149:
Device name: Intel(R) 82574L Gigabit Network Connection
Primary device ID: PCI\VEN_8086&DEV_10D3&SUBSYS_07D015AD&REV_00
Manually assigned INF match discovered using primary device id (PCI\VEN_8086&DEV_10D3&SUBSYS_07D015AD&REV_00).
Matching File: Hp OSD\network\hp\sp65585\Win7X64\ew_busfilter.inf
Provisioning Template Actions to assist in debugging HII issues
The Actions within this template are designed to run HIIClient.exe /previewall and consolidate the results into a C:\Logs folder so that they can be viewed after the device reboots during CTOS. With HIIClient in preview mode, it will list the device ID's that are discovered and what drivers in the HII Library associate with those ID's. This information is passed to DISM and DISM determines which driver to install. Looking at these logs will help you to determine which drivers are needed and help you build your HII library accordingly.
Note: With HIIClient in preview mode will not call DISM so an HII action is still needed. After copying these actions to your template, make sure that the drive letter on the Create Logs Directory and the Copy actions match the active drive that Windows is installed on.