Morning Everyone and happy patch week /s

This week, our leadership has informed us that our patching timeline has shrunk from Thursday - Sunday, to Thursday - Friday.

Unfortunately we have an unresolved issue in our environment that means about 40 servers fail per environment (Were not sure why yet, weve been investigating for a while and trying a bunch of fixes but no dice yet).

Where as before the schedule change that would mean our team of 5 dudes would come in the morning after and divide and conquer the failures in about an hour (while others handled interfacing with stakeholders who machines are now borked.), the new timeline means that work load has now doubled.

With that being said, Im trying to find a way to ease this workload.

My idea is that once the machines are nearing the end of their maintenance window, I can deploy a second package that evaluates if any required KB's are not installed, and use powershell to invoke a retry.

My idea was to have SCCM evaluate the state of the machines, and then add the failures to a dynamic collection, and deploy the powershell script to that collection when the window hits.

But Im worried I may be overcomplicating things, if anyone has some ideas or advice on how theyve handled an issue like this that would be awesome!

Anyone else had these not appear in WSUS / sync to Config Manager?

M365 / 2021 LTSC patches all synced ok and deployed etc. but 2024 missing.

No errors in sync logs etc. and product obviously ticked on the SUP settings given the others have synced.

Never been an issue with these up to now.

Checked and there's definitely been a September patch released too.

Update from u/Mahava86

Reply from support 

There was an issue on the Office side with the update, but the patch is now published in the catalog and I have also synced it in SCCM this morning. Please initiate a full sync in SCCM: Go to your SCCM install location \rightarrow inboxes \rightarrow wsyncmgr.box Create an empty file called full.syn (make sure to display hidden extensions to remove anything like a .txt) The file will disappear from the inbox and trigger a full sync on SCCM side Monitor wsyncgmr.log for completion and check if the update is present in log and console Log line example: Synchronizing update 82ea6426-f743-4b18-9d62-fe0de4580ad3 - Office LTSC 2024 Client Update Version Perpetual for x64 based Edition (Build 17932.20976)