You need to reboot the servers after you patch so that the changes take effect, so SA (sys-adms) not rebooting the systems after a patch cycle isn't going to fly, because the fixes didn't go in place.
EZ Edward E. Ziots, CISSP, CISA, Security +, Network + Security Engineer Lifespan Organization [email protected]<mailto:[email protected]> Work:401-255-2497 This electronic message and any attachments may be privileged and confidential and protected from disclosure. If you are reading this message, but are not the intended recipient, nor an employee or agent responsible for delivering this message to the intended recipient, you are hereby notified that you are strictly prohibited from copying, printing, forwarding or otherwise disseminating this communication. If you have received this communication in error, please immediately notify the sender by replying to the message. Then, delete the message from your computer. Thank you. [cid:[email protected]] From: [email protected] [mailto:[email protected]] On Behalf Of Maglinger, Paul Sent: Thursday, February 27, 2014 9:01 AM To: '[email protected]' Subject: RE: [NTSysADM] Maintenance Reboots of Guest VM's. We reboot our servers once a month, both VMs and physicals. The thought around here is that we would rather have a scheduled reboot than an unscheduled one and we have found we have less unscheduled reboots doing it this way. How can a SA justify not rebooting after a patching? Most patches aren't loaded until after a reboot so they're essentially not patched. -Paul From: [email protected]<mailto:[email protected]> [mailto:[email protected]] On Behalf Of John Matteson Sent: Thursday, February 27, 2014 6:08 AM To: [email protected]<mailto:[email protected]> Subject: RE: [NTSysADM] Maintenance Reboots of Guest VM's. I'm not looking to reboot systems just for the heck of it either. But I've heard SA's go "Nope, no way, nada, niet, don't reboot for anything no way no how", even after OS level patching. And there have been the people on the other side of that fence that say to treat it like you would a physical server. I'm trying to get a feel for what happens in the real world, not the theoretical world of test labs and sales meetings. John M. From: [email protected]<mailto:[email protected]> [mailto:[email protected]] On Behalf Of Ken Schaefer Sent: Tuesday, February 25, 2014 5:18 PM To: [email protected]<mailto:[email protected]> Subject: RE: [NTSysADM] Maintenance Reboots of Guest VM's. We don't reboot servers just for the sake of rebooting servers. Cheers Ken From: [email protected]<mailto:[email protected]> [mailto:[email protected]] On Behalf Of John Matteson Sent: Tuesday, 25 February 2014 11:35 PM To: [email protected]<mailto:[email protected]> Cc: [email protected]<mailto:[email protected]> Subject: [NTSysADM] Maintenance Reboots of Guest VM's. I'm trying to get some straight information on doing maintenance reboots of virtual systems. Some people I've talked to say yes, others say no. I've been doing systems admin work for a long time now, but only recently have had to get up close and personal with VM's on ESX hosts. Yes? No? Why or why not? Learning new stuff is a good thing. John M.
<<inline: image001.png>>
