On a XenApp server, a weekly reboot is probably not enough. Most I've seen are on 48-hour or even 24-hour reboot schedules. The multi-user nature of the things (which means users invariably leave hung sessions, abandoned sessions, runaway processes) more or less necessitates this as a support function.
So XenApp would get rebooted (physical or virtual) but I wouldn't do it for any other server. My two cents' worth. JR On 25 February 2014 14:51, J- P <[email protected]> wrote: > I inherited a VM on an ESX host, and it has the Sunday night 1 am reboot > scheduled (2008 xenapp/ts) > > I figured if thats they way they had it for years why change it. > > I will add that I have since deployed a number of hyper-v guests (DC's, > File Servers Exchange, on 2012 servers and have no reboots scheduled > > > > > ------------------------------ > From: [email protected] > To: [email protected] > CC: [email protected] > Subject: [NTSysADM] Maintenance Reboots of Guest VM's. > Date: Tue, 25 Feb 2014 07:35:26 -0500 > > > 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. > -- *James Rankin* --------------------- RCL - Senior Technical Consultant (ACA, CCA, MCTS) | The Virtualization Practice Analyst - Desktop Virtualization http://appsensebigot.blogspot.co.uk
