search

MSEndpointMgr / ModernDriverManagement

Official repo of Modern Driver Management from MSEndpointMgr.com
https://www.msendpointmgr.com
MIT License
133 stars 80 forks source link

Sporadic Issue downloading drivers using AdminService #222

Open Amg399 opened 1 year ago

Amg399 commented 1 year ago

We're seeing a sporadic issue where devices hang on applying drivers during OSD. Looking at the ApplyDriverPackage.log, the last entry in the log is "Starting package content download process (WinPE), this might take some time." In the steps before, it properly identifies the driver package needed. There is also a folder created under "C:_SMSTaskSequence\Packages" that matches the package ID for the driver pack. However, the folder itself is empty. If the same device with the issue is reimaged, sometimes it will download the package properly and image successfully. Packages prior to the driver package download with no issues. The issue doesn't seem to be model or driver package specific.

Outside of the ApplyDriverPackage.log, anywhere else to look to determine what the issue is?

bbeckerftc commented 1 year ago

Thank you for posting this Amg399, we're seeing the same thing where devices will just hang trying to download driver packages, then another deployment to the same machine works fine. I've been trying look into Distribution Point issues, re-distributing driver packages, redistributing the MDM script package, etc., but I've been running in circles - it'll seem to be solved one day, then fail again the next. I agree this doesn't seem to be specific to any make/model, although it seems to be more common for us with HP ZBook 14 G9's. That could be simply because that's a very common model in our environment though. I'm running ConfigMgr 2207 with Hotfix 15152495, and I'm one version back on the Invoke-CMApplyDriver Package script, which is 4.2.0, I believe..?

Amg399 commented 1 year ago

Glad I'm not the only one. We're on 2203, using Invoke-CMApplyDriver Package script 4.2.1. We recently switched from webservice to adminservice, and are noticing this now. Packages are identical, and never had issues with driver packs downloading when on webservice.

bbeckerftc commented 1 year ago

It seemed that, at least for us, it may have started fairly soon after I upgraded to 2207, but I also added two new DPs right after that - so I was chasing multiple things that changed at the same time. When we do see issues, it's consistently with driver packages - deployments to VMs always seem to work fine. I was just assuming the driver packages had gotten corrupted when they were pushed/pulled out to the new DPs, but then we started seeing failures with packages that I had re-distributed, so I'm starting to rule that out.

Amg399 commented 1 year ago

Just figured out our issue. The boundary group being used had three site servers associated with it. Two of which shouldn't have been associated with the group. Not sure why we were only seeing an issue with downloading driver packages, never seemed to be a problem with the webservice method. Once we pulled those two servers out of the boundary group properties, the issue looks to be resolved. That explained the randomness, as the client was most likely randomly pulling packages from one of the three sites associated with the boundary group, and two of which were problematic.

bbeckerftc commented 1 year ago

Very interesting, thank you for sharing your findings! I will go back through my boundary groups and look for errors. Thanks!