When pushing patches, users are getting patch notification and request to reboot repeatedly.
Patching is set to 3 attempts but some people are getting patch notifications 4 and 5 times. If a patch fails will the kbox continue to try to push it regardless of the set number of attempts?
Pushing windows patches every Wednesday at 11:00. User click continue to let patches install, then yes to reboot. Then they get prompted again for patch installs. Some users are getting patch installs and reboot request 4 and 5 times. Patch schedule is set for 3 attempts.
Answers (3)
I believe this has to do with selecting "Detect and Deploy" rather than breaking them out into separate "Detect" and "Deploy" cycles.
"Detect and Deploy" will detect needed patches, then begin deploying. When it arrives at a patch which requires a reboot, it attempts to deploy that patch, then reboots. It then verifies the patch has been installed, and continues. If you have several patches that require reboots, you may see more than 3 reboots, especially if you have 3 patches and one of those patch deployments fail. It will try to install KBXXXXXXX 3 times, with 3 reboots, then move on to the next patch. Or, if you have 5 patches and they all require reboots, you will see 5 reboots.
If you separate out the detect / deploy cycles, (do one "Detect Only" cycle, followed by a "Deploy Only" cycle) it should detect all needed patches, deploy all needed patches, then request a single reboot. This should give you a single reboot.
Patching may require multiple reboots, especially when first patching out of date systems. I usually cut down the message window getting it out of the way of the customer.
You need to setup a schedule for detect and then deploy. This will detect all patches for you labels and then deploy them this way it will only ask them to reboot once. My users were getting the same message and once I created a schedule for detect and then another one for deploy they only get asked once.
