Patch Install Policy Pitfalls

Dominic White

 
Random Entry: Windows Update for Linux
< Anti-CAPTCHA Advances | OSS vs Proprietry Patching >

Patch Install Policy Pitfalls

At two minutes past five, the group policy settings on Beeta's computer made it reboot to complete a patch installation. Being a geek he tried to stop it and had no success. Hopefully he had the option to snooze to save and close everything. I think a 3am reboot with a warning on logoff that it would occur would have been more appropriate.

17:02 <Beesta> how does one cancel an automatic windows reboot?
17:02 <Discus> . /shutdown abort or something
17:02 <Discus> from cmd window
17:02 <Discus> or run
17:03 <Discus> google
17:03 <mithrandi> shutdown -a
17:03 <Discus> shutdown /abort
17:03 * Beesta applies windows task manager
17:03 <Beesta> HAH!
17:03 <mithrandi> -a Abort a system shutdown
17:03 <mithrandi> task manager can't do anything about that, can it?
17:03 <Beesta> shit
17:03 <Beesta> relief was temporary
17:04 <Discus> start run shutdown -a
17:04 <Discus> save save save
17:05 Signoff Beesta: #rucus (Quit: leaving)

Wednesday, June 1. 2005
Posted by Dominic White in Masters
Comments (0) | Trackbacks (0)

Last modified on 2005-06-01 17:13
 

Trackbacks
Trackback specific URI for this entry

No Trackbacks

Comments
Display comments as (Linear | Threaded)

No comments

Add Comment

E-Mail addresses will not be displayed and will only be used for E-Mail notifications.

To prevent automated Bots from commentspamming, please enter the string you see in the image below in the appropriate input box. Your comment will only be submitted if the strings match. Please ensure that your browser supports and accepts cookies, or your comment cannot be verified correctly.
CAPTCHA