Patching with "no reboot", yet computers reboot
Our decision on patching was to set our "Detect and Deploy" patches to no prompts, and no reboots, and train our users to shut down their comptuers every night (or reboot them sometime during each day if they couldn't shut them down at night). We felt that would be the least disruptive, and while it might take several days to get older machines caught up, after that people would get their updates within a day or two of their release. Works pretty well, we think, but we have seen at least two instances of computers restarting without warning or explanation. If that is going to happen often, we have a real problem.
Interestingly, both of those users had administrative rights on their own Windows 7 computers, which most users do not. On one machine we were able to find what appeared to be the System Event that triggered the unexpected reboot:
The process c:\3a20a4124cc3bae1189a14\Setup.exe (COMPUTERNAME) has initiated the restart of computer COMPUTERNAME on behalf of user NT AUTHORITY\SYSTEM for the following reason: Other (Planned)
Reason Code: 0x80000000
Shutdown Type: restart
Comment:
Does this look like something that KACE might have caused? Or do I need to look elsewhere for the cause of the reboot?
Answers (5)
Submit a ticket with support. I had one machine where this happened but we couldn't find anything in the logs. I'd suggest turning on debug mode (which support will have you do as well).
Does the directory c:\3a20a4124cc3bae1189a14\ still exist on the machine. If so Id cehck to see if there is an install log. Also check the vents near this for installs. You could also check the time against the patchlog of the kace client to see if patching was occuring.
I've seen where a patch takes longer then normal to install, and reboots the machine out of the maintenaince window, but that was one out of 3000.
We have the same issue with multiple machines. Which is the solution? and first, which is it the problem cause?.
