BES client 9.5.4 on Win 7 Enterprise, I’m having repeated issues with post-action restarts having very long delays. I’m watching the BES Client logs on 8 workstations now, all are reporting along the lines of
At 15:05:48 -0500 -
IBM BigFix Restart (Force count:25) from ActionID 934924
At 15:07:19 -0500 -
IBM BigFix Restart (Force count:26) from ActionID 934924
At 15:08:50 -0500 -
IBM BigFix Restart (Force count:27) from ActionID 934924
At 15:09:21 -0500 -
Report posted successfully
At 15:10:21 -0500 -
IBM BigFix Restart (Force count:28) from ActionID 934924
At 15:11:52 -0500 -
IBM BigFix Restart (Force count:29) from ActionID 934924
At 15:13:23 -0500 -
IBM BigFix Restart (Force count:30) from ActionID 934924
At 15:14:19 -0500 -
Report posted successfully
At 15:14:54 -0500 -
IBM BigFix Restart (Force count:31) from ActionID 934924
I’ve seen this get as high as Force count:40. It looks like eventually they might restart on their own, but are there any suggestions as to where I should look to explain this delay?
These workstations do not have any logged-on users at the moment.
This might be because I’m also trying to trigger a reboot in the Action Script itself, in addition to the Post-Action Restart.
I’m trying to work-around the condition where the BES Post-Action Restart doesn’t take effect (usually due to logged-on but disconnected RDP sessions, or Windows Core installations). So I thought I’d let the BES Post-Action Restart handle “really logged-on cases” with a nice reboot timer, but also use the hammer of shutdown.exe in case BESClient gets confused. So my actionscript includes
runhidden shutdown.exe /R /T 86400 /C "BigFix is initiating a restart of the system in 24 hours to complete patching"
What I suspect is happening is that because there’s already a restart in progress (based on shutdown.exe), that BESClient cannot trigger the restart itself.
The doc above says “The delayed restart is a forced restart. It will not prompt the user to save changes to documents. The machine will restart without further prompting.” but I haven’t found that to be the case. When I have used it I still got a BigFix UI telling me it was going to reboot with an option to snooze the notification for a short time until the timeout.
I’m not sure what would happen if you tried to use both.
I’m pretty sure that: IBM BigFix Restart (Force count:31) means that bigfix attempted to force a reboot 31 times and failed, which it seems like you have come to a similar conclusion.
Understood. I was using the OS command because the built-in ‘restart’ command was failing to reboot the machine in some cases - which I believe is due to the disconnected Remote Desktop user and resolved via _BESClient_ActionManager_UIMissingHoldMode