1

We have a relatively small environment, with a mixture of Server 2016, 2019, and 2022. We use SCCM to deploy Microsoft updates. We have a single SCCM server, one domain, on boundary group, etc. All servers are (more or less) on the same subnet.

The problem that we’re running into is that on our 3 Server 2022 endpoints, they are not installing any Windows updates. They are downloading them into the CCMCACHE folder, but the automatic installation during their maintenance window never happens. FYI all servers are in the same maintenance window, and udpates are working fine on our 2016 and 2019 machines.

This problem has me baffled. So far the only way we can get them to install any updates is by going to the Microsoft catalog and manually downloading / installing. Simply going to Settings - Windows Update doesn’t help because it acts like no updates are found.

Anyone run across this before? Any tips / tricks for getting 2022 to work well with SCCM?

2 Spice ups
2

Are the 2022 machines in the same subnet as working machines?

1 Spice up
4

Hi Patrick, yes the 2022 machines are in the same subnet

1 Spice up
5

My first thought was the the boundary didn’t cover the IPs the servers were in but I wouldn’t expect the files in the CCMcache then either, just wanted to rule that out.

It has been a hot minute since I’ve used SCCM. Anything of interest in C:\Windows\CCM\Logs\AppEnforce.log or AppIntentEval.log?

1 Spice up
6

Doesn’t quite align with this - are you referencing other non-2022 here as well?

So they must be within a scope to get this far - check your GPOs, anything misconfigured or overriding?

1 Spice up
7

Reboot, see if that helps ?

Else you may need to clean up the Windows Update manually…

  • stop windows update service
  • Delete the logs in c:\windows\logs
  • Delete the contents in c:\windows\software distribution
  • start Windows update service
1 Spice up
8

I will elaborate. We have a bit more than 300 servers. Of those 300 servers, approx 20 or so we leave running at DR sites as a matter of habit. Of the 3 2022 servers we have in our environment, 1 of them is at a DR site and happens to be sitting in a different subnet. Of all of our servers and PCs, the only 3 that are having this problem with updates are Server 2022.

1 Spice up
9

Question? Did the 3 servers get any updates from SCCM before? Or are they new servers and not had any updates from SCCM?
If they had not any updates. Option re-push client install.
Do the updates show in the config manager but shows window expired or do they not show in config manager in control panel? That will tell us a bit
If they had updates but not receiving them anymore, then check your WUAHandle.log ( C:\Windows\CCM\Logs\WUAHandler.log) or the PachDownloader.log ( same location)
Check log WindowsUpdate.log (C:\windows\logs\WinowUpdate)
Suggest using CMTrace to view the logs, much easier via that.

1 Spice up
10

Any update @PeteSchaub ? Are you still having issues or has it been resolved?
Other possibilities to check.
a) are the 3 2002 servers in the same collection or are they in a different collection or maintenance window?
b) is the MW open long enough for the install to take place?
c) is the deployment set to “required” and not “available”
d) check RebootCoordinator.log to see if the servers dont need a reboot ?