MED1975
New Member
- Messages
- 3
- Reaction score
- 0
- Points
- 1
Hi - hope someone can help me with an issue I am having patching Serve 2016 Standard servers...
Using SCCM CB. Windows 7/10 clients patch perfectly. Server 2012 etc the same. None of our Server 2016 servers are patching from SCCM. In fact if I look at the Windows Update GUI on a Server 2016 client it does not show the expected red message that some settings are managed by my organisation.
The SUP is configured to download patches for 2016. I have added 2016 patches to a deployment and targeted it to a collection containing 2016 servers.
If I run a compliance report for the deployment it shows that the 2016 server is already compliant, however if I look in the Windows Update GUI it shows updates that are available that include those patches I have deployed to the server.
The ccmcache folder on the Server 2016 servers is empty except for the initial client deployment.
One final element that confuses things, is this seems to only be an issue for OS patches. I have one 2016 Server that I have targeted a SQL patch too, and that did download the patch from the distribution point, add to the ccmcache folder and install during the maintenance window.
What haven't I done - I'm sure it's something obvious.
Thanks in advance for help....
Using SCCM CB. Windows 7/10 clients patch perfectly. Server 2012 etc the same. None of our Server 2016 servers are patching from SCCM. In fact if I look at the Windows Update GUI on a Server 2016 client it does not show the expected red message that some settings are managed by my organisation.
The SUP is configured to download patches for 2016. I have added 2016 patches to a deployment and targeted it to a collection containing 2016 servers.
If I run a compliance report for the deployment it shows that the 2016 server is already compliant, however if I look in the Windows Update GUI it shows updates that are available that include those patches I have deployed to the server.
The ccmcache folder on the Server 2016 servers is empty except for the initial client deployment.
One final element that confuses things, is this seems to only be an issue for OS patches. I have one 2016 Server that I have targeted a SQL patch too, and that did download the patch from the distribution point, add to the ccmcache folder and install during the maintenance window.
What haven't I done - I'm sure it's something obvious.
Thanks in advance for help....