Since we have a maintenance window of opportunity when we patch where we are free to reboot at will, we reboot all servers that are scheduled to get the automated patch process, hoping that it will minimize the number of patch failures, but also because if someone tries to say that our patching broke their app, we should be able to show in the logs that the problem actually surfaced at reboot, not because of patching.
There are a large number of exception servers, such as domain controllers and some database servers. These are patched manually in a specific order by logging on interactively and are not rebooted beforehand. Charlie Sullivan Sr. Windows Systems Administrator -----Original Message----- From: [email protected] [mailto:[email protected]] On Behalf Of Michael Leone Sent: Tuesday, February 25, 2014 8:32 AM To: [email protected] Subject: Re: [NTSysADM] Maintenance Reboots of Guest VM's. On Tue, Feb 25, 2014 at 7:35 AM, John Matteson <[email protected]> wrote: > 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. If by "maintenance reboot", you mean reboot the VM every so many days, just on general principles and just in case, I would say no. You would of course have to reboot after applying patches, etc. (I also try to reboot, whether the patch says it requires it or not. That is a "just to be sure" reboot) Mostly you treat a VM just like you would treat a physical box, at least in terms of maintenance.
