- This topic has 1 reply, 2 voices, and was last updated 8 years, 4 months ago by .
-
Posts
-
Had a user’s machine reboot on him this morning — turns out the BP I had started executing the previous day just took all night to run.
Wed-09:07:28> COMPUTER ONLINE
Wed-09:06:04> COMPUTER OFFLINE
Wed-09:02:24> Job Queue: Execution complete
Wed-09:02:24> Reboot/Shutdown: Reboot (force) initiated successfully
Wed-09:02:24> Reboot/Shutdown: Attempting to initiate reboot (force)...
Wed-09:02:23> Reboot/Shutdown: Failed to initiate reboot. User is logged on.
Wed-09:02:23> Reboot/Shutdown: Attempting to initiate reboot...
Wed-09:02:23> Windows Update: Reboot Required. Overall Installation Result: SucceededWithErrors
Tue-22:29:30> Windows Update: Executing BatchPatchRemoteAgent.exe...It appears that this is partially due to my decision to use “reboot (force, if required)” — but I’ve had several instances of machines (with no active user) not rebooting if I chose a less severe level, so I do feel I need to keep this.
What would be nice is an option to set BP to timeout/abort either after X hours or at a certain timestamp; this would not only prevent this issue, but it would also avoid the issue where a slow computer is still crunching on updates when a user gets back to it.
Thanks for the suggestion. We will consider this for a future build.
In the meantime, the good news is that very slow updating of Win 7 computers appears to have finally been mostly resolved by Microsoft. So once you are up to date with updates on your Win 7 computers, it is likely you will once again start seeing completion occur within minutes instead of hours. We have posted about this here, if you’re curious: Checking for Windows Updates on Windows 7 is very slow
For now, a few other possible work-arounds are:
1. Perform the update process in one action, and then perform the reboot in a separate action only after you confirm that the update process has completed.
2. After you kick off the updates + reboot action on hosts, if they do not complete updating in a reasonable amount of time, such that you have any concern for it impacting your users, close BP. The update process will complete/finish on its own, but the reboot will never occur if BP is not running. You can re-open BP and re-add the same target hosts, and then you can use ‘Actions > Windows updates > Re-attach orphaned Windows Update process’ to re-connect to the target processes to continue monitoring their statuses. The ‘re-attach orphan’ option allows you to choose whether or not you want the reboot to occur when the update process is complete.
3. Utilize the Job Queue option to ‘Wait for host to have zero logged-on users’ before the reboot step. This may or may not be useful in your environment, depending on whether or not your users log off of their computers.
-Doug
- You must be logged in to reply to this topic.