7 Replies Latest reply on Nov 14, 2014 9:38 AM by PaulPretorius

    HII Package Drivers being Missed

    Rookie

      Hi Guys

       

      Our OS Deployment works a treat on Most of our Dell Models.

       

      The Deployment Script calls HII twice.  It gets called during POST-OS to inject NIC drivers for when windows loads (as without the NIC driver, the build falls over when it loads windows due to not being able to communicate with the Core) ... This works fine.  It also gets called in SYSTEM CONFIGURATION so that it can install driver packages using the Package distribution method.  This seems to do the trick for most of our machines.

       

      The devices have been flagged in HII and relevant packages assigned ... However during a build it seems to ignore all the packages that are assigned.  The HiiClient.log shows it reapplying the NIC inf, then it finishes as though it thinks its done.

       

      I have checked the drivers.db3 and all the device ID's are assigned with the correct packages.    One thing i did notice was that the NIC Device ID doesnt appear in drivers.db3 ... But somehow its being installed.

       

      I logged this with LANDesk before who advised to create a Package Bundle for the Drivers which we need to run after the machine is built.  Although this work-around installs the drivers, im still trying to figure out why HII is not jumping into action to install the Package drivers during the build.

      Has anyone else seen this behavior and if so, did you ever manage to get it fixed ?   Any ideas where else to look ?

       

      Look forward to your responses,

       

      Paul.

        • 1. Re: HII Package Drivers being Missed
          jhackett SupportEmployee

          Paul,

          Is it possible that these drivers that are being skipped are unsigned? Also what version of LANDESK are you on? If you are on 9.6 you can now check a box to install unsigned drivers.

          If you aren't on 9.6 please try this.

          Issue: Unsigned drivers not working in Hardware Independent Imaging (HII)

           

          Thanks

           

          Jared

          • 2. Re: HII Package Drivers being Missed
            Rookie

            Hi Jared,

             

            Appreciate your response. We are running 9.5 SP2

             

            Thanks a stack for that link about dism ...  I looked through the hiiclient.log but it doesn't seem to be running any disms commands ?  Should i be examining the log during POST-OS?

             

            The Drivers are all assigned ...  

             

            Screenshot of the NIC inf

            Drivers.PNG

             

            Screenshot of the Assigned Package Drivers

            DriversPackages.PNG

             

            Here is the HiiClient.Log to show you what its actually doing

             

             

            *****************  Starting HIIClient *****************

            Command line args: /uncpath /taskid 745

            Running in Windows

            GetImageSystemDirectory: c:\Windows

            GetImageSystemDirectory: c:\Windows

            HII Proxy Location: http://LANDESK95CORE1/LANDesk/ManagementSuite/Core/Core.WebServices/hii.asmx

            Driver path found: \\LANDESK95CORE1.ad.london.inspiredbroadcast.net\ldmain\landesk\files\drivers

            Determining OS version and architecture.

            OS Major version: 6

             

             

            OS Minor version: 1

             

             

            OS Product type: 0

             

             

            Major and Minor version and product type gathered.

            GetImageSystemDirectory: c:\Windows

            Architecture is: AMD64

             

             

            source path to download: \\LANDESK95CORE1.ad.london.inspiredbroadcast.net\ldmain\landesk\files\drivers\drivers.db3

            dest path for download: c:\Windows\LDDriverStore\drivers.db3

            Fri, 14 Nov 2014 04:32:17 About to call DownloadFiles (1 files) with these settings:

            Fri, 14 Nov 2014 04:32:17 m_allowedBandwidthWAN: 100

            Fri, 14 Nov 2014 04:32:17 m_allowedBandwidthLAN: 100

            Fri, 14 Nov 2014 04:32:17 m_maxDiscoveryThreads: 15

            Fri, 14 Nov 2014 04:32:17 m_discardPeriodSeconds: 604800

            Fri, 14 Nov 2014 04:32:17 m_preserveDirectoryStructure: 1

            Fri, 14 Nov 2014 04:32:17 m_bUseWanBWForPush: 0

            Fri, 14 Nov 2014 04:32:17 m_bSynchronize: 0

            Fri, 14 Nov 2014 04:32:17 m_downloadControl: SourceOnly

            Fri, 14 Nov 2014 04:32:17 m_preferredServerControl: AttemptPreferredServer

            Opening SQLite3 database at location: c:\Windows\LDDriverStore\drivers.db3

             

             

            Device manufacturer discovered as:

            Device model discovered as:

            filename: E1d62x64.INF filePath: E5440 - NIC\Intel 825x\WINDOWS7-x64\

            filename: e1d62x64.cat filePath: E5440 - NIC\Intel 825x\WINDOWS7-x64\

            filename: e1dmsg.dll filePath: E5440 - NIC\Intel 825x\WINDOWS7-x64\

            filename: NicInstD.dll filePath: E5440 - NIC\Intel 825x\WINDOWS7-x64\

            filename: NicCo36.dll filePath: E5440 - NIC\Intel 825x\WINDOWS7-x64\

            filename: e1d62x64.din filePath: E5440 - NIC\Intel 825x\WINDOWS7-x64\

            filename: e1d62x64.sys filePath: E5440 - NIC\Intel 825x\WINDOWS7-x64\

            filename: E1d62x64.INF filePath: E5440 - NIC\Intel 825x\WINDOWS7-x64\

            filename: e1d62x64.cat filePath: E5440 - NIC\Intel 825x\WINDOWS7-x64\

            filename: e1dmsg.dll filePath: E5440 - NIC\Intel 825x\WINDOWS7-x64\

            filename: NicInstD.dll filePath: E5440 - NIC\Intel 825x\WINDOWS7-x64\

            filename: NicCo36.dll filePath: E5440 - NIC\Intel 825x\WINDOWS7-x64\

            filename: e1d62x64.din filePath: E5440 - NIC\Intel 825x\WINDOWS7-x64\

            filename: e1d62x64.sys filePath: E5440 - NIC\Intel 825x\WINDOWS7-x64\

            filename: iaStorAC.inf filePath: E6540 - DiskController\

            filename: iaStorAC.cat filePath: E6540 - DiskController\

            filename: iaStorA.sys filePath: E6540 - DiskController\

            filename: iaStorF.sys filePath: E6540 - DiskController\

            Downloading from downloadfiles!

            source path to download: \\LANDESK95CORE1.ad.london.inspiredbroadcast.net\ldmain\landesk\files\drivers\E5440 - NIC\Intel 825x\WINDOWS7-x64\E1d62x64.INF

            dest path for download: c:\Windows\LDDriverStore\E5440 - NIC\Intel 825x\WINDOWS7-x64\E1d62x64.INF

            source path to download: \\LANDESK95CORE1.ad.london.inspiredbroadcast.net\ldmain\landesk\files\drivers\E5440 - NIC\Intel 825x\WINDOWS7-x64\e1d62x64.cat

            dest path for download: c:\Windows\LDDriverStore\E5440 - NIC\Intel 825x\WINDOWS7-x64\e1d62x64.cat

            source path to download: \\LANDESK95CORE1.ad.london.inspiredbroadcast.net\ldmain\landesk\files\drivers\E5440 - NIC\Intel 825x\WINDOWS7-x64\e1dmsg.dll

            dest path for download: c:\Windows\LDDriverStore\E5440 - NIC\Intel 825x\WINDOWS7-x64\e1dmsg.dll

            source path to download: \\LANDESK95CORE1.ad.london.inspiredbroadcast.net\ldmain\landesk\files\drivers\E5440 - NIC\Intel 825x\WINDOWS7-x64\NicInstD.dll

            dest path for download: c:\Windows\LDDriverStore\E5440 - NIC\Intel 825x\WINDOWS7-x64\NicInstD.dll

            source path to download: \\LANDESK95CORE1.ad.london.inspiredbroadcast.net\ldmain\landesk\files\drivers\E5440 - NIC\Intel 825x\WINDOWS7-x64\NicCo36.dll

            dest path for download: c:\Windows\LDDriverStore\E5440 - NIC\Intel 825x\WINDOWS7-x64\NicCo36.dll

            source path to download: \\LANDESK95CORE1.ad.london.inspiredbroadcast.net\ldmain\landesk\files\drivers\E5440 - NIC\Intel 825x\WINDOWS7-x64\e1d62x64.din

            dest path for download: c:\Windows\LDDriverStore\E5440 - NIC\Intel 825x\WINDOWS7-x64\e1d62x64.din

            source path to download: \\LANDESK95CORE1.ad.london.inspiredbroadcast.net\ldmain\landesk\files\drivers\E5440 - NIC\Intel 825x\WINDOWS7-x64\e1d62x64.sys

            dest path for download: c:\Windows\LDDriverStore\E5440 - NIC\Intel 825x\WINDOWS7-x64\e1d62x64.sys

            source path to download: \\LANDESK95CORE1.ad.london.inspiredbroadcast.net\ldmain\landesk\files\drivers\E5440 - NIC\Intel 825x\WINDOWS7-x64\E1d62x64.INF

            dest path for download: c:\Windows\LDDriverStore\E5440 - NIC\Intel 825x\WINDOWS7-x64\E1d62x64.INF

            source path to download: \\LANDESK95CORE1.ad.london.inspiredbroadcast.net\ldmain\landesk\files\drivers\E5440 - NIC\Intel 825x\WINDOWS7-x64\e1d62x64.cat

            dest path for download: c:\Windows\LDDriverStore\E5440 - NIC\Intel 825x\WINDOWS7-x64\e1d62x64.cat

            source path to download: \\LANDESK95CORE1.ad.london.inspiredbroadcast.net\ldmain\landesk\files\drivers\E5440 - NIC\Intel 825x\WINDOWS7-x64\e1dmsg.dll

            dest path for download: c:\Windows\LDDriverStore\E5440 - NIC\Intel 825x\WINDOWS7-x64\e1dmsg.dll

            source path to download: \\LANDESK95CORE1.ad.london.inspiredbroadcast.net\ldmain\landesk\files\drivers\E5440 - NIC\Intel 825x\WINDOWS7-x64\NicInstD.dll

            dest path for download: c:\Windows\LDDriverStore\E5440 - NIC\Intel 825x\WINDOWS7-x64\NicInstD.dll

            source path to download: \\LANDESK95CORE1.ad.london.inspiredbroadcast.net\ldmain\landesk\files\drivers\E5440 - NIC\Intel 825x\WINDOWS7-x64\NicCo36.dll

            dest path for download: c:\Windows\LDDriverStore\E5440 - NIC\Intel 825x\WINDOWS7-x64\NicCo36.dll

            source path to download: \\LANDESK95CORE1.ad.london.inspiredbroadcast.net\ldmain\landesk\files\drivers\E5440 - NIC\Intel 825x\WINDOWS7-x64\e1d62x64.din

            dest path for download: c:\Windows\LDDriverStore\E5440 - NIC\Intel 825x\WINDOWS7-x64\e1d62x64.din

            source path to download: \\LANDESK95CORE1.ad.london.inspiredbroadcast.net\ldmain\landesk\files\drivers\E5440 - NIC\Intel 825x\WINDOWS7-x64\e1d62x64.sys

            dest path for download: c:\Windows\LDDriverStore\E5440 - NIC\Intel 825x\WINDOWS7-x64\e1d62x64.sys

            source path to download: \\LANDESK95CORE1.ad.london.inspiredbroadcast.net\ldmain\landesk\files\drivers\E6540 - DiskController\iaStorAC.inf

            dest path for download: c:\Windows\LDDriverStore\E6540 - DiskController\iaStorAC.inf

            source path to download: \\LANDESK95CORE1.ad.london.inspiredbroadcast.net\ldmain\landesk\files\drivers\E6540 - DiskController\iaStorAC.cat

            dest path for download: c:\Windows\LDDriverStore\E6540 - DiskController\iaStorAC.cat

            source path to download: \\LANDESK95CORE1.ad.london.inspiredbroadcast.net\ldmain\landesk\files\drivers\E6540 - DiskController\iaStorA.sys

            dest path for download: c:\Windows\LDDriverStore\E6540 - DiskController\iaStorA.sys

            source path to download: \\LANDESK95CORE1.ad.london.inspiredbroadcast.net\ldmain\landesk\files\drivers\E6540 - DiskController\iaStorF.sys

            dest path for download: c:\Windows\LDDriverStore\E6540 - DiskController\iaStorF.sys

            Fri, 14 Nov 2014 04:33:07 About to call DownloadFiles (18 files) with these settings:

            Fri, 14 Nov 2014 04:33:07 m_allowedBandwidthWAN: 100

            Fri, 14 Nov 2014 04:33:07 m_allowedBandwidthLAN: 100

            Fri, 14 Nov 2014 04:33:07 m_maxDiscoveryThreads: 15

            Fri, 14 Nov 2014 04:33:07 m_discardPeriodSeconds: 604800

            Fri, 14 Nov 2014 04:33:07 m_preserveDirectoryStructure: 1

            Fri, 14 Nov 2014 04:33:07 m_bUseWanBWForPush: 0

            Fri, 14 Nov 2014 04:33:07 m_bSynchronize: 0

            Fri, 14 Nov 2014 04:33:07 m_downloadControl: SourceOnly

            Fri, 14 Nov 2014 04:33:07 m_preferredServerControl: AttemptPreferredServer

            Download return count: 18

            OS Version: 6.1

            GetImageSystemDirectory: c:\Windows

            Applying drivers at "c:\Windows\LDDriverStore"

            GetImageSystemDirectory: c:\Windows

            *****************  Finish HIIClient *****************

            • 3. Re: HII Package Drivers being Missed
              Rookie

              I think its going wrong here :

               

              Device manufacturer discovered as:

              Device model discovered as:


              Both fields appear to be blank

              • 4. Re: HII Package Drivers being Missed
                Rookie

                I have narrowed this behavior down to "Windows Updates" !!!!!

                 

                About 2 week ago, we refreshed our WIM to include all windows updates ... Seems since doing this, HII is unable to determine the Manufacturer and Model.   

                 

                I reverted back to the old image (without Windows Updates integrated),  and now HII is able to determine Manufacturer and Model and deploy the appropriate Driver Packages. 

                • 5. Re: HII Package Drivers being Missed
                  jhackett SupportEmployee

                  Paul,

                  Nice work. It good to know it been resolved.

                   

                  Thanks

                   

                  Jared

                  • 6. Re: HII Package Drivers being Missed
                    Apprentice

                    Were you able to narrow down which windows updates were creating this problem? From the date range seems like something during October? I am in a similar situation, USB3 drivers were working now they aren't

                    • 7. Re: HII Package Drivers being Missed
                      Rookie

                      Sadly I have not had time today to work through it to figure out which one(s) exactly is/are the culprit.

                       

                      With regards to the USB3, I've seen this before but to be honest, I have always assumed its down to the order which the drivers are being installed.    eg, HII tries to install USB3 before the Chipset is installed ... But without the Chipset driver, the USB device is not yet visible so the USB driver install fails.  In my case, i always find the USB Driver package in the sdmcache suggesting it did pass over the USB Package that is assigned. 

                       

                      You could be right though ... Your issue may well be down to windows updates too!

                       

                      Good luck, and if you ever find the culprit please let us know