Deploying windows 10 image with drivers - 0x80070032 (SCCM R2 SP1 CU1)

[wing5wong]

Have just updated to CU1 and attempting to deploy a TS with windows 10 drivers. (Optiplex 3020) but it fails with 0x80070032 when applying the driver package.

It is my understanding that the CU1 update would resolve win 10 driver deployment.

 

Im deploying this to a 2nd Gen hyperV machine currently - i dont remember having issues with the drivers being applied to VMs with 7

 

Is there something additional i need to do to get drivers deployed?

 

 

 

here is the smsts.log from the client:

<![LOG[Calling Package manager to add drivers to the offline driver store.]LOG]!><time="13:41:15.896-720" date="08-13-2015" component="OSDDriverClient" context="" type="0" thread="1680" file="sysprepdriverinstaller.cpp:512">
<![LOG[Command line for extension .exe is "%1" %*]LOG]!><time="13:41:15.912-720" date="08-13-2015" component="OSDDriverClient" context="" type="0" thread="1680" file="commandline.cpp:229">
<![LOG[Set command line: "X:\WINDOWS\system32\dism.exe" /image:"C:" /windir:"WINDOWS" /apply-unattend:"C:\_SMSTaskSequence\PkgMgrTemp\drivers.xml" /logpath:"C:\_SMSTaskSequence\PkgMgrTemp\dism.log"]LOG]!><time="13:41:15.912-720" date="08-13-2015" component="OSDDriverClient" context="" type="0" thread="1680" file="commandline.cpp:732">
<![LOG[Executing command line: "X:\WINDOWS\system32\dism.exe" /image:"C:" /windir:"WINDOWS" /apply-unattend:"C:\_SMSTaskSequence\PkgMgrTemp\drivers.xml" /logpath:"C:\_SMSTaskSequence\PkgMgrTemp\dism.log"]LOG]!><time="13:41:15.912-720" date="08-13-2015" component="OSDDriverClient" context="" type="1" thread="1680" file="commandline.cpp:828">
<![LOG[Process completed with exit code 50]LOG]!><time="13:41:16.146-720" date="08-13-2015" component="OSDDriverClient" context="" type="1" thread="1680" file="commandline.cpp:1124">
<![LOG[uExitCode == 0, HRESULT=80070032 (e:\nts_sccm_release\sms\client\osdeployment\osddriverclient\sysprepdriverinstaller.cpp,548)]LOG]!><time="13:41:16.146-720" date="08-13-2015" component="OSDDriverClient" context="" type="0" thread="1680" file="sysprepdriverinstaller.cpp:548">
<![LOG[Dism failed with return code 50]LOG]!><time="13:41:16.146-720" date="08-13-2015" component="OSDDriverClient" context="" type="3" thread="1680" file="sysprepdriverinstaller.cpp:548">
<![LOG[AddPnPDriverToStore( pszSource, sTargetSystemDrive, sTargetSystemRoot, wProcessorArchitecture), HRESULT=80070032 (e:\nts_sccm_release\sms\client\osdeployment\osddriverclient\sysprepdriverinstaller.cpp,658)]LOG]!><time="13:41:16.146-720" date="08-13-2015" component="OSDDriverClient" context="" type="0" thread="1680" file="sysprepdriverinstaller.cpp:658">
<![LOG[Failed to add driver to driver store. Code 0x80070032]LOG]!><time="13:41:16.146-720" date="08-13-2015" component="OSDDriverClient" context="" type="3" thread="1680" file="sysprepdriverinstaller.cpp:658">
<![LOG[InstallDriver( iInstallParams->sContentId, iInstallParams->sSource, iInstallParams->pBootCriticalInfo ), HRESULT=80070032 (e:\nts_sccm_release\sms\client\osdeployment\osddriverclient\driverinstaller.cpp,557)]LOG]!><time="13:41:16.146-720" date="08-13-2015" component="OSDDriverClient" context="" type="0" thread="1680" file="driverinstaller.cpp:557">
<![LOG[ReleaseSource() for C:\_SMSTaskSequence\Packages\WH100164.]LOG]!><time="13:41:16.146-720" date="08-13-2015" component="OSDDriverClient" context="" type="1" thread="1680" file="resolvesource.cpp:3873">
<![LOG[reference count 1 for the source C:\_SMSTaskSequence\Packages\WH100164 before releasing]LOG]!><time="13:41:16.146-720" date="08-13-2015" component="OSDDriverClient" context="" type="1" thread="1680" file="resolvesource.cpp:3883">
<![LOG[Released the resolved source C:\_SMSTaskSequence\Packages\WH100164]LOG]!><time="13:41:16.146-720" date="08-13-2015" component="OSDDriverClient" context="" type="1" thread="1680" file="resolvesource.cpp:3921">
<![LOG[pDriverInstaller->InstallDriverPackage( sPackageId, pBootCriticalInfo ), HRESULT=80070032 (e:\nts_sccm_release\sms\client\osdeployment\osddriverclient\osddriverclient.cpp,380)]LOG]!><time="13:41:16.146-720" date="08-13-2015" component="OSDDriverClient" context="" type="0" thread="1680" file="osddriverclient.cpp:380">
<![LOG[Failed to provision driver. Code 0x80070032]LOG]!><time="13:41:16.146-720" date="08-13-2015" component="OSDDriverClient" context="" type="3" thread="1680" file="osddriverclient.cpp:380">
<![LOG[Exiting with return code 0x80070032]LOG]!><time="13:41:16.146-720" date="08-13-2015" component="OSDDriverClient" context="" type="1" thread="1680" file="osddriverclient.cpp:418">
<![LOG[Process completed with exit code 2147942450]LOG]!><time="13:41:16.177-720" date="08-13-2015" component="TSManager" context="" type="1" thread="1088" file="commandline.cpp:1124">
<![LOG[!--------------------------------------------------------------------------------------------!]LOG]!><time="13:41:16.177-720" date="08-13-2015" component="TSManager" context="" type="1" thread="1088" file="instruction.cxx:805">
<![LOG[Failed to run the action: Apply Driver Package - Optiplex 3020. 
The request is not supported. (Error: 80070032; Source: Windows)]LOG]!><time="13:41:16.177-720" date="08-13-2015" component="TSManager" context="" type="3" thread="1088" file="instruction.cxx:911">

[anyweb]

looks like you are trying to apply a driver package in the wrong part of windows, it should occur before winpe boots into Windows, not after.

 

Exiting with return code 0x80070032]LOG]!><time="13:41:16.146-720" date="08-13-2015" component="OSDDriverClient" context="" type="1" thread="1680" file="osddriverclient.cpp:418">
<![LOG[Process completed with exit code 2147942450]LOG]!><time="13:41:16.177-720" date="08-13-2015" component="TSManager" context="" type="1" thread="1088" file="commandline.cpp:1124">
<![LOG[!--------------------------------------------------------------------------------------------!]LOG]!><time="13:41:16.177-720" date="08-13-2015" component="TSManager" context="" type="1" thread="1088" file="instruction.cxx:805">
<![LOG[Failed to run the action: Apply Driver Package - Optiplex 3020.
The request is not supported.

 

double check that the apply driver package step occurs before the setup windows and configmgr step

[HotdogSCCM]

FWIW, I don't believe SP1/CU1 addressed the issue with Apply Driver Packages actually working. It's a limitation of the version of DISM available in Windows 8.1 ADK's WinPE.

 

While that error *DOES* look a little different, the DISM of your boot image, unless you've done magical things, is still going to be sub 10, which will cause it to fail.

 

I still had to utilize these instructions:

 

http://deploymentresearch.com/Research/Post/443/Beyond-unsupported-Deploying-Windows-10-preview-including-drivers-with-ConfigMgr-2012-R2

 

To get Apply-Drivers to work. Unless you install Windows 10 ADK and re-make your boot media, which is the "better" option.

[wing5wong]

looks like you are trying to apply a driver package in the wrong part of windows, it should occur before winpe boots into Windows, not after.

 

Exiting with return code 0x80070032]LOG]!><time="13:41:16.146-720" date="08-13-2015" component="OSDDriverClient" context="" type="1" thread="1680" file="osddriverclient.cpp:418">

<![LOG[Process completed with exit code 2147942450]LOG]!><time="13:41:16.177-720" date="08-13-2015" component="TSManager" context="" type="1" thread="1088" file="commandline.cpp:1124">

<![LOG[!--------------------------------------------------------------------------------------------!]LOG]!><time="13:41:16.177-720" date="08-13-2015" component="TSManager" context="" type="1" thread="1088" file="instruction.cxx:805">

<![LOG[Failed to run the action: Apply Driver Package - Optiplex 3020.

The request is not supported.

 

double check that the apply driver package step occurs before the setup windows and configmgr step

Yup it is definitely before the setup config manager client step

 

 

FWIW, I don't believe SP1/CU1 addressed the issue with Apply Driver Packages actually working. It's a limitation of the version of DISM available in Windows 8.1 ADK's WinPE.

 

While that error *DOES* look a little different, the DISM of your boot image, unless you've done magical things, is still going to be sub 10, which will cause it to fail.

 

I still had to utilize these instructions:

 

http://deploymentresearch.com/Research/Post/443/Beyond-unsupported-Deploying-Windows-10-preview-including-drivers-with-ConfigMgr-2012-R2

 

To get Apply-Drivers to work. Unless you install Windows 10 ADK and re-make your boot media, which is the "better" option.

 

Il try the windows 10 ADK - havent upgraded that yet.

Re: remaking the boot media - just follow the steps here to get the latest images out of the Win10 ADK? http://blogs.msdn.com/b/beanexpert/archive/2015/08/05/how-to-switch-to-windows-10-adk-on-configmgr-2012-r2-sp1.aspx

[anyweb]

try this to get your site up to Windows 10 ADK

 

http://freshblog.azurewebsites.net/2015/08/13/create-and-import-windows-10-winpe-into-your-sccm-environment/

 

or import the wim's 'as is' using this method

 

http://www.niallbrady.com/2013/10/09/how-can-i-manually-add-winpe-5-boot-images-to-system-center-2012-configuration-manager-sp1-cu3/