2 Replies Latest reply on Dec 17, 2008 4:54 AM by scottunify

    Driver download/injection incomplete - drivers missing.

    Apprentice

      Hi all

       

      We have successfully created many LANDesk imaging scripts with driver injection (using image.exe v1.74) for a whole host of HP/Dell/Toshiba laptops and desktops.  We're now trying to create a LANDesk imaging with driver injection for a HP7900DC.  The image works but only a portion of the drivers are downloaded to the local drive.  This is the first time this has ever happened.  We have changed the order in which the drivers are downloaded but it makes no difference.  Is there a size limit to the amount of drivers downloaded to the local PC?  Perhaps a timeout is exceeded that cuts the download process midway through?  Not ideal, but we may be forced to try removing all drivers from the driver download/injection process and just leave the NIC driver then install the remaining drivers via a GuiRunOnce script.

       

      Any advice would be welcome please.

       

      Thanks

      Scott

        • 1. Re: Driver download/injection incomplete - drivers missing.
          Apprentice

          We also tried image.exe v1.97 from our LDMS 8.8 core install but made no difference.  However, renaming the drivers effectively moves the problem so it could be a file length problem, so we've removed one of the drivers with 44 characters in the MSI filename and will re-image the machine again...

           

          Thanks

          Scott

          • 2. Re: Driver download/injection incomplete - drivers missing.
            Apprentice

            It appears that removing the video driver from driver injection worked because a few of the files exceeded the 8.3 file format DOS limitation and the driver couldn't install because it was looking for the full filename not the shortened 8.3 file format.  So we moved it to the GuiRunOnce script and installed fine.  However, the side-effect of doing so is that the display resolution is set to the lowest (640x480), I assume because the injected sysprep.inf has already processed the display resolution before the GuiRunOnce script. So it would be ideal if we could change this to 1024x768 or the screen's native resolution automatically with a script.  Does anyone know how best we can achieve this please?  I've had a look but there doesn't appear to be a script utility with the Intel video driver to do this...?

             

            Thanks

            Scott