CABraunIV
commented
3 years ago I have opted to create 2 task sequences for OSD. One for 1809 and the other for 20H2. Both only contain their specific OS for the apply OS step so there is no longer multiple OSes referenced in the task sequence. However when deploying 1809 the Dynamically Apply Drivers step is still failing.
The error is:
The task sequence execution engine failed executing the action (Dynamically Apply Drivers) in the group (Install Operating System) with the error code 1 Action output: ... plyDriverPackage.ps1 range 0-101148 Downloaded file from http://SCCM-FQDN:80/SMS_DP_SMSPKG$/SC2001BF/sccm?/Invoke-CMApplyDriverPackage.ps1 to C:_SMSTaskSequence\Packages\SC2001BF\Invoke-CMApplyDriverPackage.ps1 VerifyContentHash: Hash algorithm is 32780 Content successfully downloaded at C:_SMSTaskSequence\Packages\SC2001BF. Resolved source to 'C:_SMSTaskSequence\Packages\SC2001BF' Working dir 'C:_SMSTaskSequence\Packages\SC2001BF' Command line for extension .exe is "%1" %* Set command line: Run PowerShell Script PowerShell command line is NOT shown in the log ('OSDLogPowerShellParameters' is NOT set to 'True') Executing command line: Run PowerShell Script with options (0, 4) Process completed with exit code 1 PowerShell command line returned code 1 ReleaseSource() for C:_SMSTaskSequence\Packages\SC2001BF. reference count 1 for the source C:_SMSTaskSequence\Packages\SC2001BF before releasing Released the resolved source C:_SMSTaskSequence\Packages\SC2001BF. The operating system reported error 1: Incorrect function.
Again, the command parameters I am running are: -URI "http://SCCM-FQDN/configmgrwebservice/configmgr.asmx" -SecretKey "My-Secret-Key-Here" -Filter "Drivers"
Why, all of a sudden are these 1809 machines no longer able to successfully run the dynamically apply drivers step?
In Task Sequence using Dynamically Apply Drivers as below: -URI "http://mysccmserver/configmgrwebservice/configmgr.asmx" -SecretKey "xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx" -Filter "Driver"
Task Sequence Log Error: The task sequence execution engine failed executing the action (Dynamically Apply Drivers) in the group (Install Operating System) with the error code 9 Action output: ... CMApplyDriverPackage.ps1 range 0-68020 Downloaded file from http://MySecondaryDP:80/SMS_DP_SMSPKG$/SC2001BF/sccm?/Invoke-CMApplyDriverPackage.ps1 to C:_SMSTaskSequence\Packages\SC2001BF\Invoke-CMApplyDriverPackage.ps1 VerifyContentHash: Hash algorithm is 32780 Content successfully downloaded at C:_SMSTaskSequence\Packages\SC2001BF. Resolved source to 'C:_SMSTaskSequence\Packages\SC2001BF' Working dir 'C:_SMSTaskSequence\Packages\SC2001BF' Command line for extension .exe is "%1" %* Set command line: Run PowerShell Script PowerShell command line is NOT shown in the log ('OSDLogPowerShellParameters' is NOT set to 'True') Executing command line: Run PowerShell Script with options (0, 4) Process completed with exit code 9 PowerShell command line returned code 9 ReleaseSource() for C:_SMSTaskSequence\Packages\SC2001BF. reference count 1 for the source C:_SMSTaskSequence\Packages\SC2001BF before releasing Released the resolved source C:_SMSTaskSequence\Packages\SC2001BF. The operating system reported error 9: The storage control block address is invalid.
The ApplyDriverPackage log contains the following: <![LOG[===== SCConfigMgr Invoke-CMApplyDriverPackage Version 2.2.3 ====]LOG]!>
<![LOG[Driver download package process initiated]LOG]!>
<![LOG[Manufacturer determined as: Hewlett-Packard]LOG]!>
<![LOG[Computer model determined as: HP ProDesk 600 G4 DM (TAA)]LOG]!>
<![LOG[Computer SKU determined as: 83EF]LOG]!>
<![LOG[Retrieved a total of 33 driver packages from web service]LOG]!>
<![LOG[Attempting to detect OS Image data from task sequence, running in DeploymentType: BareMetal]LOG]!>
<![LOG[Multiple OS Image objects detected and OSImageTSVariableName was not specified. Selecting the first OS Image object from web service call]LOG]!>
<![LOG[Translated OSName from OSImageVersion: Windows 10]LOG]!>
<![LOG[Translated OSVersion from OSImageVersion: ]LOG]!>
<![LOG[Translated OSImageArchitecture: x64]LOG]!>
<![LOG[Using computer detection method: SystemSKU]LOG]!>
<![LOG[Attempting to find a match for driver package: Script - Dynamically Apply Drivers (SC2001BF)]LOG]!>
<![LOG[Unable to match computer model using detection method: SystemSKU (83EF)]LOG]!>
<![LOG[Driver package does not meet computer model, manufacturer and operating system and architecture criteria: Script - Dynamically Apply Drivers (SC2001BF)]LOG]!>
<![LOG[Computer model detection logic failed for all detected driver packages]LOG]!>
I think maybe the (TAA) that is part of the Computer Model is not being interpreted correctly as the drive package as downloaded via the Driver Automation Tool does not have a model with (TAA) in the name.
Any thoughts on how I can get this working again? I have updated the Invoke-CMApplyDrivePackage.ps1 to 3.1.0 but that didn't resolve the issue. In fact that is now generating a different error which I will make a different post about.
EDIT-1) Based on some other things that I have read, I would like to add that I recently added the option of Windows 10 20H2 as an OS available for deployment to the task sequence. So there are 2 Windows 10 versions available in the TS for our Service Center that handles OSD operations to choose from. 1809 and 20H2. I have looked back through the logs of OSD's prior to adding 20H2 and the "Dynamically Apply Drivers" step was successful even on these devices with (TAA) in the model name.
So I now think that this is nothing to do with (TAA) in the name but seems more linked with the addition of 20H2 wim in the task sequence along with 1809.
I added 20H2 as an option for when our SC folks are imaging HP Probook 640 G8 because I could not find 1809 drivers for that machine type using the driver automation tool. So I downloaded the 2004 driver pack (the most recent version available) using the driver automation tool and added a 20H2 OS option for them to choose when deploying one of these new laptops.
Am I missing something that I need to do since adding a 2nd OS possibility?