search

MSEndpointMgr / ConfigMgr

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

0 Driver Packages from web service matching operational mode: Production #241

Closed mbradley101 closed 4 years ago

mbradley101 commented 4 years ago

Script keeps failing:

I have attached the log file.

A couple of key things I should note: I've had the Driver Management Tool set to "ZIP" to compress the driver packages, would that make a difference?

My SCCM installation is on E: not C: drive. Doubt this would make a difference. We have a SAN attached to our SCCM server which is setup as a different drive letter, but it contains all of our packages for SCCM. Never had a problem with permissions/etc.

I have only uploaded 1 driver package into SCCM via driver management tool to test it out. (Lenovo P52s Laptop).

As you can see it connects to the web service just fine....can anyone help me out? I'm gonna start pulling my hair out.

image

ApplyDriverPackage.log

mbradley101 commented 4 years ago

I changed the config mgr web service installation to reside on the E: drive, same as where all my SCCM source files are. But now I'm getting this:

image

It picked up the P52s drivers but it skipped the driver package since only 3/4 of the checks were matched.

mbradley101 commented 4 years ago

It thought that the target operating system was 1903, instead of 1909. I double checked what we had in SCCM and we definitely were deploying a windows 10 x64 1909 OS.

Fix is located here: https://github.com/MSEndpointMgr/ConfigMgr/issues/226#issuecomment-620820372

You have to use a parameter to tell it that is in fact a 1909 OS:

Quote from NickolajA:

We introduced a fix for this a couple of versions back, so simply add the following to your 1909 TS step parameters for Modern Driver Management:

-TargetOSVersion "18363"

This will override the version returned from the web service and force it to match with 1909 that's kept in a static table within the script.