Client Automation Standard Practitioners Forum
cancel
Showing results for 
Search instead for 
Did you mean: 

Patches that require reboots

Highlighted
BILL FOSTER_3
Occasional Advisor

Patches that require reboots

I was just curious as to how everyone handles patches that require reboots. Do you force a reboot after a patch connect? Do you put up the reboot box and let the user decide? Please let me know. Thanks!
4 REPLIES
Biju V George!
Honored Contributor

Re: Patches that require reboots

Hi Bill,

Based on customer requirement we can either suppress or User can decide the reboot status. Also remember that the compliance report will not change until reboot.

Hope this helps !!

Thanks
Biju

Re: Patches that require reboots

Because compliance is not reported till reboot, we've decided on putting up a reboot dialog with a five minute timeout, after which a hard reboot occurs.

Re: Patches that require reboots

Bill,

Again it normally depends on client requirements, but most of ours have the reboot completely suppressed and rely on the box being restarted on a regular basis (most machines seem to be shut down overnight for the majority of clients).

Regards,

Kelvin
www.kn3.co.uk
Thompson, Jim
Honored Contributor

Re: Patches that require reboots

Compliance is reported immediately. Not all patches require a reboot and their status is updated on the compliance report as soon as the patch has finished installing (if you allow for any lag time introduced by RIM or RMS). Even patches that require reboots update the compliance information immediately - to show that a 'reboot is required'.

The fact is that a device itself is not compliant (in some cases) until a reboot has been performed - but this fact is certainly updated in close to real-time within the Patch Vulnerability reports.

Having said all that...I agree with the approach of forcing a reboot. In some cases failing to reboot after a patch application can leave the machine in an indeterminate state. (some files have been applied, others are waiting to be applied on the reboot)

Suppressing required reboots has the potential to cause problems or stability issues until the reboot has been performed.
"Well...it depends..."
//Add this to "OnDomLoad" event