Patching failure - MECM 2103

Question

Hi, two days ago ADR for Windows Server 2016/2019 updates ran and now I see bunch of servers not being updated/restarted with following errors:

ConfigMgr is no longer managing WindowsDO GPO. Set to default values. Mode = LAN. GroupID = empty LocationServices 8/16/2021 4:02:50 AM 5552 (0x15B0)
Calling back with empty distribution points list LocationServices 8/16/2021 4:02:50 AM 5552 (0x15B0)
CCTMJob::UpdateLocations - Received empty location update for CTM Job {A7662E15-9AFA-4DFC-BC3C-BA9F645455F6} ContentTransferManager 8/16/2021 4:02:50 AM 5552 (0x15B0)

Patching had been working flawlessly of all 100+ servers here but now it is completely different story. Only change made in the meantime was adding Windows Server 2019 to SUP sync product list, ADR and renaming SUG/deployment package (last week) but that should not have anything to do with this behavior. Boundaries/Boundary Groups/Reference System ... nothing was changed. Defender Definition updates installation, on the other hand, is working without issues. This is PCI environment so having it up to date is very important.

Answer 1

Hi @Bojan Zivkovic ,

Only change made in the meantime was adding Windows Server 2019 to SUP sync product list, ADR and renaming SUG/deployment package (last week) but that should not have anything to do with this behavior.

Yes, in fact, if we just change it, there is no effect or error in SCCM.

According to these errors provided, it seems like a boundary group issue. Even through boundaries/boundary Groups/reference System ... nothing was changed, Please try to run forest discovery and creating IP range boundaries. Then recreate the boundary group and reassign the DP. Kindly check if it works.

---

If the response is helpful, please click "Accept Answer" and upvote it.
Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.

Answer 2

We have tons of VLANs in environment hence boundaries based on AD site were used right from the start. I just added IP ranges pulled from AD into corresponding boundary groups and see progress - number of systems with status downloading updates is dropping and number of systems with status pending system restart is going up. Will keep monitoring how situation is unfolding. It seems that putting AD sites as BG members is not a best idea - it can work for some time and then issues can pop up.

Thank you very much.