CU Patching Issue

CU Patching Issue

I feel Desktop Central is deprecating superseded patches too quickly. I have two machines failing to install 2019-08 CU for Windows Server 2016. 2019-07 CU was approved tested and partially deployed in my environment when it got disabled by the Patch DB Update Wednesday after Patch Tuesday.

I had opened a case about this awhile back that Patches that superseded other patches shouldn't disable the prior patch till the new one is approved. Other tools like Altiris handle patching this way. That way you can make sure the patches you test with are deployed in a timely matter. I was told this was MS way and that I should change when I patch my systems to fall more in line with Patch Tuesday. Wasn't having it.

So for these two systems that are having issues I manually ran windows update and see that windows update is download and will install both CU 2019-07 and CU 2019-08.

How are other people handling patching with Desktop Central? I am finding I have to constantly babysit the system. For instance, when systems patch and I tell it in the patch policy to force the reboot. I still find systems not rebooting. I have to manually force. I give my systems a 4 to 6 hour window to patch which should be sufficient as all patches are pre-staged on the windows machines ahead of time.

                New to ADSelfService Plus?