Good afternoon.
I've been doing SCCM for two years, wrapped it up in our distributed company. Thank you very much Prajwal, thanks to his articles I learned a lot. But there is one problem, the answer to which I have not yet been able to find.
It has something in common with this topic (https://forums.prajwaldesai.com/threads/kb5037765-windows-server-2019-may-update-sccm.6629 ) but if it describes an isolated case with one update, and then by mistake from Microsoft, then my problem is massive.
Windows Server 2022. Updates are downloaded using SCCM. But the servers "don't see it." If you create a Compiance based on update numbers, then they are "not applicable" for Server 2022. The client does not see them, he sees them in the log, but does not apply them. There are no such problems with other server versions (2019, 2016), the servers are updated normally.
At the same time, if you run the same update manually from powershell, then it is installed without problems. I.e., using DISM, I specify exactly this package, which was downloaded using SCCM and which is "not applicable" - and it is installed.
What could be the reason?
Thanks!
PS. sorry for the Google translation
I've been doing SCCM for two years, wrapped it up in our distributed company. Thank you very much Prajwal, thanks to his articles I learned a lot. But there is one problem, the answer to which I have not yet been able to find.
It has something in common with this topic (https://forums.prajwaldesai.com/threads/kb5037765-windows-server-2019-may-update-sccm.6629 ) but if it describes an isolated case with one update, and then by mistake from Microsoft, then my problem is massive.
Windows Server 2022. Updates are downloaded using SCCM. But the servers "don't see it." If you create a Compiance based on update numbers, then they are "not applicable" for Server 2022. The client does not see them, he sees them in the log, but does not apply them. There are no such problems with other server versions (2019, 2016), the servers are updated normally.
At the same time, if you run the same update manually from powershell, then it is installed without problems. I.e., using DISM, I specify exactly this package, which was downloaded using SCCM and which is "not applicable" - and it is installed.
What could be the reason?
Thanks!
PS. sorry for the Google translation
