search

MSEndpointMgr / ConfigMgr

Microsoft Endpoint Configuration Manager scripts and tools
633 stars 282 forks source link

Nested TS error: ApplyDriverPackage.log: Call to ConfigMgr WebService returned empty OS Image data. Error message at line : #187

Open sheriffharrytruman opened 4 years ago

sheriffharrytruman commented 4 years ago

We got the "Modern Driver Management" solution working fine in a standalone baremetal OSD TS.

We then migrated our TS into a series of nested TS. This broke driver management and generates the error in ApplyDriverPackage.log "Call to ConfigMgr WebService returned empty OS Image data. Error message at line : "

Solution continues to work fine in the "all in one" TS.

Tried --Setting variable OSImageTSVariableName to package ID of OS Image being used. No change. --Also moved Apply OS/APply Driver steps into the same sub-TS. No change.

===== SCConfigMgr Invoke-CMApplyDriverPackage Version 2.2.3 ==== ApplyDriverPackage 9/27/2019 1:05:11 PM 476 (0x01DC) Driver download package process initiated ApplyDriverPackage 9/27/2019 1:05:11 PM 476 (0x01DC) Manufacturer determined as: Dell ApplyDriverPackage 9/27/2019 1:05:11 PM 476 (0x01DC) Computer model determined as: Precision 5820 Tower ApplyDriverPackage 9/27/2019 1:05:11 PM 476 (0x01DC) Computer SKU determined as: 0738 ApplyDriverPackage 9/27/2019 1:05:11 PM 476 (0x01DC) Fallback SKU determined as: 0738 ApplyDriverPackage 9/27/2019 1:05:11 PM 476 (0x01DC) Retrieved a total of 31 driver packages from web service ApplyDriverPackage 9/27/2019 1:05:13 PM 476 (0x01DC) Attempting to detect OS Image data from task sequence, running in DeploymentType: BareMetal ApplyDriverPackage 9/27/2019 1:05:13 PM 476 (0x01DC) Call to ConfigMgr WebService returned empty OS Image data. Error message at line : ApplyDriverPackage 9/27/2019 1:05:18 PM 476 (0x01DC)

ghost commented 4 years ago

I'm having this exact same issue with ConfigMgr 1906, Windows 10 1903 (no multi-index wim as source) but I'm not using nested TS. Invoke-CMApplyDriverPackage is version 2.2.3

beanmeister commented 4 years ago

Had this same issue, found a workaround. My scenario, Using either a pre-cache or an upgrade task sequence ID kept failing because we are using pre-cache to download to a variable. Which means the Upgrade Operating System step does NOT select any image, but selects the variable and index ID. This indicates to me that the script specifically uses the "Upgrade Package field" of the "Upgrade Operating System step" in the TS to determine which image and therefore which windows edition.

Not ideal, but works as a workaround; created a DISABLED upgrade operating system step which selects the desired OS image, and 'bobs your uncle', it works again.

And yes, using a single image index; Using multi-index wim doesnt work with this method. Rather than using this method of finding the OS, would it not be better if a variable of sorts is used on the script? Means we don't need other manual remediation methods.

NickolajA commented 4 years ago

Have you tried using the "OverrideTSPackageID" parameter and specifying the TS PackageID of the nested TS? It's been some time since I looked at this part of the code, but please give it a try and let me know if it works, otherwise we need to re-visit the issue.