locked
OSD HP driver install problem RRS feed

  • Question

  • I cannot get this driver to install. Intel Active Management Technology SOL. Version 5.5.1.1012, 7/6/2009. It's the correct driver. The TS just will not install it during OSD. I've removed it and imported it again but no difference.

    Resource Explorer to another identical PC shows the same driver installed. But it shows the driver on COM3... Not sure what's missing. I only have the one version.

    SMSts log looks as though it installs the driver. Definately no errors related to it that I can identify.

    Any ideas?

    • Moved by Kent AgerlundMVP Wednesday, November 24, 2010 5:30 PM (From:Configuration Manager Setup/Deployment)
    Wednesday, November 24, 2010 5:01 PM

All replies

  • Do you mean task sequence driver installation?

    I'm not femiliar with this Intel driver you are trying to use, but is it setup program or .inf/cab/dll folder? Have you created driver package or did you import driver to SCCM database?

    Does task sequence give any errors at Advertisement Status?

    Thursday, November 25, 2010 8:06 AM
  • No, by all accounts it appears to install. I import it along with all of the other drivers from the HPSoftPaq downloads. It's enabled. The drive source location is valid. I have to install the driver manually pointing it to the package location. Not sure what the deal is.

    I do get this error in the Adv Status. Is it really a path length issue? I'm only having problems with one driver...

    The task sequence execution engine failed executing the action (Apply Driver Package) in the group (Install Operating System) with the error code 2147500037
    Action output: cePath( sTargetPath ), HRESULT=80004005 (e:\nts_sms_fre\sms\client\osdeployment\osddriverclient\sysprepdriverinstaller.cpp,714)
    InstallDriver( iInstallParams->sContentId, iInstallParams->sSource, iInstallParams->pBootCriticalInfo ), HRESULT=80004005 (e:\nts_sms_fre\sms\client\osdeployment\osddriverclient\driverinstaller.cpp,557)
    Entering ReleaseSource() for \\chisms01.fiservip.net\SMSPKGE$\FCO000A7reference count 1 for the source \\chisms01.fiservip.net\SMSPKGE$\FCO000A7\ before releasing
    Maximum DevicePath length (4096) exceeded.
    Failed to update device path in offline registry. Code 0x80004005
    Released the resolved source \\chisms01.fiservip.net\SMSPKGE$\FCO000A7pDriverInstaller->InstallDriverPackage( sPackageId, pBootCriticalInfo ), HRESULT=80004005 (e:\nts_sms_fre\sms\client\osdeployment\osddriverclient\osddriverclient.cpp,409)
    Unloading offline SOFTWARE registry hive
    Failed to provision driver. Code 0x80004005
    Unloading offline SYSTEM registry hive
    Exiting with return code 0x80004005. The operating system reported error 2147500037: Unspecified error

    Friday, November 26, 2010 6:17 PM
  • As a test, I would create a Driver Package with nothing but the Driver in it you are having trouble with.  I'd run the driver package right after the current Driver install step in your task sequence.

    Also, are you using Auto Apply Drivers or Apply Driver Package?  If it's a Driver Package, do you have a separate Driver Package for each model or do you use one big Driver Package with every driver in it?

    Thanks,

    Will

    • Proposed as answer by Garth JonesMVP Saturday, August 26, 2017 3:10 PM
    Saturday, November 27, 2010 8:46 AM