Once a scan and deployment are performed and the machines reboot, scan the machines again to verify the patch is no longer listed as a missing patch.
If the patch is still missing, you may need to troubleshoot your deployment.
It may be that you performed a deployment, then machine was shut down or the Shavlik remote scheduler service was stopped.
Once the machine was booted, or the service was started, it sees the scheduled task and will run the install, then reboot (if the reboot option was selected within your deployment template).
If using agents or a Distribution server, verify the patches are downloaded and copied to your distribution server. If the patch.exe file does not exist on the distribution server, the deployment may wait, once the file exists on the distribution server (could be days later), the deployment will complete and reboot your machines.
IF it was a delayed deployment due to the things you listed, would it not log the patches being applied in either the Shavlik logs and/or the event log? There was nothing in either.
Also we NEVER deploy with a reboot option, except when configuring new computers long before they're given to real users.
Is there an AT task scheduled on the machine in question (Windows Task Scheduler)?
Please look at any old deployments to this machine to see when was this patch deployed to this machine?
Who deployed the patch and was the deployment scheduled for another time?
You can also look at the target machines c:windowspropatchesinstallfilename.HIS file.
If you did perform a deployment with a reboot, it should be listed within the .his file.
Someone reported that a Realplayer patch was buggy and ignored any reboot options within the deployment template, and rebooted the machine anyways. We have been unable to replicate this issue. Did you deploy a Real player or any other patches that may have caused the reboot? If so, please let us know so we can try contacting that vender and let them know the patch may have a bug.