reboot failure ?

[doug]

Hard to tell exactly what happened here. You can normally use ‘Get last boot time’ in BatchPatch to quickly see the last start time of the computer, which would answer the question of whether or not it was actually rebooted. But since you already rebooted it again, you would need to look in the event log to confirm whether or not it was rebooted by BP on Wed night. To me it looks like it *was* rebooted, based on the following two events.

Wed-20:47:16> COMPUTER ONLINE

Wed-20:47:12> COMPUTER OFFLINE

In this case you used ‘Reboot (force always).’ However, the ‘force’ method does not guarantee that the computer will return a ‘success’ message to indicate that it accepted and is processing the reboot command, which is why the ‘RPC server is unavailable’ or other error/failure messages can occur in that case, even when the machine is actually rebooted successfully. Generally speaking, I would recommend always using ‘force, if required’ which will always first try a normal reboot. It will only use ‘force’ if the normal reboot cannot be initiated. There is nothing wrong with using the ‘force always’ option, but since it doesn’t guarantee a return value, it can add confusion in the cases where it doesn’t return ‘success’ but still reboots successfully. This is not a BP issue. It’s how Microsoft designed the ‘force’ method.

The one piece of the puzzle that does not make sense is the Error 1623. This should be investigated independently because it normally should only occur if there is a pre-existing Windows Update process running on the computer. From your log there does not appear to be a previous attempt to initiate Windows Update, so it’s unclear to me why you would receive this error, unless you had already initiated Windows Update from a different BP grid. Considering that you already rebooted the machine and find that it is working properly/normally, there is nothing else really to do. We won’t be able to determine why that error occurred anymore.

-Doug

[Author]

Posts