search

MSEndpointMgr / ConfigMgr

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

OSUpgrade does not pull the Driver Package from local DP #319

Open Ickis99 opened 3 years ago

Ickis99 commented 3 years ago

So, when the "Invoke-CMApplyDriverPackage.ps1" runs with the OSUpgrade Option he identifies the correct Driver Packages but downloads it directly from the Distribution Point on the Primary Site Server even though there is a local Distribution Point that has the Package deployed. It works eventually but due to very small bandwidth in some locations the step runs for several hours.

At first i checked the Boundaries, which are correct. Also i could verify that the W10 Upgradefiles for instance are correctly downloaded from the local distribution point and also all other packages that are included in the Task Sequence.

I verified and redistributed the package just in case but it didnt change anything. I even added a program to the package just to test what happens if i use the very same package without the ApplyDriverPackage Script and here he pulls it correctly from the local distribution point.

Have i missed some prerequisites needed for the script to access the right distribution group?

Thank you

cincydash commented 2 years ago

Did you ever figure this one out? I think I'm having this issue suddenly with BareMetal in one location and I'm pulling my hair out.

Ickis99 commented 2 years ago

I did not, unfortunately. It seems like this problem does no longer occur on the sccm where i encountered it. There have been updates to sccm, the primary site os, the boundary settings and so forth but i have no idea what fixed it.

Ar5had07 commented 2 years ago

This is an SCCM issue not this tool.

Ickis99 commented 2 years ago

Why are you so sure?

Ar5had07 commented 2 years ago

Why are you so sure?

Because that's how ConfigMgr/SCCM works. It's the basics.

Ickis99 commented 2 years ago

Its the basics that every Package gets pulled from the Distribution Point, including OS, Applications and Packages with multiple Powershell-Scripts except when it comes from the Invoke-CMApplyDriverPackage.ps1 Script? Then it gets pulled from the Primary Site Server? How so?

Ar5had07 commented 2 years ago

Its the basics that every Package gets pulled from the Distribution Point, including OS, Applications and Packages with multiple Powershell-Scripts except when it comes from the Invoke-CMApplyDriverPackage.ps1 Script? Then it gets pulled from the Primary Site Server? How so?

The script doesn't control where Packages gets downloaded from. ConfigMgr & Boundaries do. So please check ClientLocation, ContentTransfer, DataTransfer and LocationServices logs for troubleshooting.

Ickis99 commented 2 years ago

We already did. The very same package gets pulled from the correct DP if it is used by another Task Sequence Step.

But it has to be tested by cindydash anyway because like i stated above, the issue does not occur anymore at the company where i initially encountered it for unknown reasons.