1 Reply Latest reply on Jun 8, 2009 7:18 AM by jimski

    Vista Hardware Independent Imaging - Answers

    Apprentice

      I've noticed a lack of Vista HII support on these forums, and I have decided to share what I have been able to figure out so far using the droppedpackets.org HII utilities, and Vista OSD in LANDesk.

       

      I have had some luck with Vista using the new HII tools from droppedpackets.org.  There are some caveats though.  First, here is the relevent portion of the OSD script that I am using:

       

      ;this causes LANDesk to only copy the specific drivers necessary for the specific platform…****HII Imaging*****
      REMEXEC411=drvmap.exe user 11111PASSHASH111111111111 Z: \\Server\Drivers, STATUS FACILITY=3513
      ;REMEXEC413=z:\tools\halconfig.exe
      REMEXEC414=cmd /c z:\tools\copydrivers.exe /c
      REMEXEC415=reg load HKLM\Software1 C:\Windows\system32\config\software
      REMEXEC417=z:\tools\ldprep /c /reg=Software1 /path=c:\drivers
      

       

      And, I add this to the bottom of the sysprep.xml that the LANDesk OSD wizard creates (there are actually two more sections with the exact same lines for different architectures, ia64 and amd64):

       

      <settings pass="offlineServicing">
              <component name="Microsoft-Windows-PnpCustomizationsNonWinPE" processorArchitecture="x86" publicKeyToken="31bf3856ad364e35" language="neutral" versionScope="nonSxS" xmlns:wcm="http://schemas.microsoft.com/WMIConfig/2002/State" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
                  <DriverPaths>
                      <PathAndCredentials wcm:action="add" wcm:keyValue="1">
                          <Path>C:\Drivers</Path>
                      </PathAndCredentials>
                  </DriverPaths>
              </component>
      </settings>
      

       

      Note that the "halconfig.exe" line is commented out in the OSD script.  I have read that Vista is supposed to be "HAL dependent", and I haven't played too much with this yet.

       

      Now, for the caveats.

       

      1. The image must be a sysprep image, as per the HII instructions.
      2. For me, using a Ghost image did not work, which is unfortunate because we enjoy using GhostCast Server for speedy imaging.  Target machines of different hardware configurations enter an endless reboot when using a Ghost image. 
      3. So far for me, only a Microsoft Image (.wim file created by imagex.exe) has worked.  Microsoft images are quite a bit different than "normal" snapshot images.  I'd suggest reading the Microsoft documentation on their new image format.  I have not yet tried imagew.exe.
      4. I have only tried this on a few different hardware configurations, and not a wide range of hardware.  It has worked so far with an image built on an HP xw4600 Workstation, and imaged on a Dell GX620 Workstation.

       

      Good resources that helped me figure this stuff out:

       

      1. The good, ol' HII documentation is a good place to start: http://www.droppedpackets.org/osd/hii-winpe.zip/view?searchterm=hii
      2. For LANDesk's advice on Sysprep for Vista: http://community.landesk.com/support/docs/DOC-5779
      3. One of the best Vista deployment articles I've come across: http://firegeier.unattended-sponsor.de/en/inject_drivers_into_image.html

       

      I would like to hear if anyone else has had success or failure with using the HII tools with Vista and Sysprep.  Has anyone been able to get Ghost images to work properly with Vista and sysprep?

       

      Thanks,
      Dan Pixley