A few users have noticed that if they get updates, snooze BigFix reboot, and restart on their own through the Windows OS, that BigFix still needs a reboot once it comes back up, sometimes it’s forced after a few minutes. It’s almost as if BigFix doesn’t recognize the non-BigFix “Take Action” reboot.
I notice that machines since upgrading to 9.5.8 take roughly 30 seconds from the time users click “Take Action” to when the machine starts it’s reboot process. This is much better than the 2-3 minutes we’ve seen on 9.5.2, but it still sometimes snags users. They think their machine isn’t doing anything, start doing some work, and then it promptly reboots.
Anyone experience this? Anything to test or best practices for reboots?
The agent will check the same items when it starts back up again after a reboot (there are several posts about this on the forum which registry items are looked at) and will keep the “Pending Reboot” state if they aren’t cleared. A single reboot will often not clear out the updates especially if multiples were applied at once so it can take more than one reboot to clear it.
Regarding the restart times, it can take a while depending on what is occurring in the machine, and often the delay can be Windows shutting things down. If a report happens to be being generated it will need to finish that work etc before it notices the client ui message to tell it to do the work. The answer is generally “it depends” on how long it will take.