7 Replies Latest reply on Jul 1, 2014 1:34 PM by RickDavie

    HII issues

    Apprentice

      I am trying to deploy to a Dell 7010 using provisiong and HII. Everything goes well until you get to the HII part. It will install all the drivers and then get to the end and say it failed. Does anyone have any clue what would be causing this?

       

      CMD screenshot:

      hiierror.png

      HIIHandler Log:

      2013-12-20 00:16:07(1856-896) HIIHandler.exe:Going to excute HIIClient  /uncpath /taskid 100

      2013-12-20 00:16:59(1856-896) HIIHandler.exe:Failed to execute HIIClient  /uncpath /taskid 100

      2013-12-20 15:23:03(1352-2004) HIIHandler.exe:Failed to execute HIIClient  /uncpath /taskid 101

      2013-12-20 15:34:05(1332-1328) HIIHandler.exe:Failed to execute HIIClient  /uncpath /taskid 102

       

      I have also attached the dism.log

       

      any help would be great.

        • 1. Re: HII issues
          Employee

          Looks like it is trying to install an unsigned boot critical driver.  A boot critical driver would be something like a hard drive controller that obviously Windows can't run without.  Can you find a signed driver to use instead of the unsigned one for whatever hardware is the problem?  In that log you attached you can just search for unsigned to find the affected drivers.

          • 2. Re: HII issues
            jwood8 Apprentice

            I'm having a similar experience with a Dell E5520, I can see the error on the screen though - it is:

             

            Error - The driver package contains x64 boot-critical drivers, but the drivers are not properly signed. Use the /forceunsigned option to install the drivers.

             

            The particular driver this is referencing is O2MicroMSPRO\O2MDRw8x64.inf which I believe might be a card reader.

             

            I thought that DISM was run with /forceunsigned anyway? Sure I saw that on here somewhere.

             

            Meanwhile, I have disabled that driver on that model to allow the build to continue hopefully.

            • 3. Re: HII issues
              jwood8 Apprentice

              That didn't work BTW, so in the end I had to untick 'Stop processing the template if this action fails' in the build template, and add the driver later as it was a rush job. To be continued...!

              • 4. Re: HII issues
                Apprentice

                I still contuine to have the same problem. I just delete all of my dirvers and rebuild my driver store and it seems to fix it. I am wokring with LANDesk support to get a better answer of to why it is happening but if you find out any more that would be great.

                • 5. Re: HII issues
                  jwood8 Apprentice

                  Here's what mine has in the dism.log in case it helps:

                   

                  2014-01-03 11:27:38, Info                  DISM   DISM Provider Store: PID=1400 Getting Provider DriverManager - CDISMProviderStore::GetProvider

                  2014-01-03 11:27:38, Info                  DISM   DISM Provider Store: PID=1400 Provider has previously been initialized.  Returning the existing instance. - CDISMProviderStore::Internal_GetProvider

                  2014-01-03 11:27:39, Info                  DISM   DISM Driver Manager: PID=1400 Driver j:\Windows\LDDriverStore\E5520_Win864\IntelManagementEngine\HECI.inf is boot-critical. - CDriverPackage::FillInPackageDetails

                  2014-01-03 11:27:39, Info                         IsDriverPackageSigned: File [j:\Windows\LDDriverStore\E5520_Win864\IntelManagementEngine\HECI.inf] is signed by a catalog [j:\Windows\LDDriverStore\E5520_Win864\IntelManagementEngine\HECI.cat]

                  2014-01-03 11:27:39, Info                  DISM   DISM Driver Manager: PID=1400 Signature status of driver j:\Windows\LDDriverStore\E5520_Win864\IntelManagementEngine\HECI.inf is: SIGNED - CDriverPackage::InitSignatureStatus

                  2014-01-03 11:27:39, Info                  DISM   DISM Driver Manager: PID=1400 Driver j:\Windows\LDDriverStore\E5520_Win864\O2MicroMSPRO\O2MDRw8x64.INF is boot-critical. - CDriverPackage::FillInPackageDetails

                  2014-01-03 11:27:39, Info                  DISM   DISM Driver Manager: PID=1400 Signature status of driver j:\Windows\LDDriverStore\E5520_Win864\O2MicroMSPRO\O2MDRw8x64.INF is: UNSIGNED - CDriverPackage::InitSignatureStatus

                  2014-01-03 11:27:39, Info                  DISM   DISM Driver Manager: PID=1400 Driver j:\Windows\LDDriverStore\E5520_Win864\STMicroFreefallSensor\accelern.inf is boot-critical. - CDriverPackage::FillInPackageDetails

                  2014-01-03 11:27:39, Info                         IsDriverPackageSigned: File [j:\Windows\LDDriverStore\E5520_Win864\STMicroFreefallSensor\accelern.inf] is signed by a catalog [j:\Windows\LDDriverStore\E5520_Win864\STMicroFreefallSensor\accelern.cat]

                  2014-01-03 11:27:39, Info                  DISM   DISM Driver Manager: PID=1400 Signature status of driver j:\Windows\LDDriverStore\E5520_Win864\STMicroFreefallSensor\accelern.inf is: SIGNED - CDriverPackage::InitSignatureStatus

                  2014-01-03 11:27:55, Info                  DISM   DISM Driver Manager: PID=1400 Successfully proccessed driver package 'j:\Windows\LDDriverStore\E5410_Win764\IntelWireless\Netwsw00.INF'. - CDriverPackage::Install

                  2014-01-03 11:27:55, Info                  DISM   DISM Driver Manager: PID=1400 Successfully proccessed driver package 'j:\Windows\LDDriverStore\E5520_Win864\IntelManagementEngine\HECI.inf'. - CDriverPackage::Install

                  2014-01-03 11:27:55, Error                 DISM   DISM Driver Manager: PID=1400 Cannot install non-signed boot-critical drivers on amd64 images. Use /forceunsigned switch to override.

                   

                  As you can see, it seems to say that the .cat files are providing the signing, but the one that fails does have a .cat file so don't know why it fails.

                  • 6. Re: HII issues
                    Employee

                    This log indicates that the O2MDRw8x64.INF driver package is unsigned.  x64 Windows after Vista and some x86 Windows have the requirement that the driver be signed.  There are some ways to try and bypass that.  Because of the strict recommendation that Microsoft gave to not allow unsigned drivers the decision was made to not run the /forceunsigned switch with DISM when we run the driver install process.

                     

                    A quick workaround that should be valid after 9.5 SP1 (and possibly 9.5) would be to set that action as not required (ie, uncheck the box that says "Fail template if action fails" or whatever the wording is) and add an action immediately after that runs

                     

                    DISM /image:C:\Windows /add-driver /driver:C:\Windows\LDDriverStore /recurse /forceunsigned

                     

                    (where C: is the drive Windows is installed to).  We are discussing options such as making this configurable.  I would like to know from those on this thread what you would think of having that option back vs. the severe security warnings given by Microsoft about the use of unsigned drivers.  Would you like the option to take on that risk or do you believe that a hardware manufacturer should provide the signed driver for all circumstances?

                     

                    Thanks!

                    • 7. Re: HII issues
                      Expert

                      We need it BACK!!