Citrix Chained Reboot Scripts, now supporting Citrix Cloud, Citrix Virtual Apps and Desktops (CVAD), and XenApp/XenDesktop 5, 6, 6.5, and 7.x!
Updated 2018.12.22: Revision 1.9 Now Supports Citrix Cloud!
One script now works with all current and modern versions of XenApp, XenDesktop, Citrix Virtual Apps and Desktops (CVAD), and Citrix Cloud Virtual Apps and Desktops Service from 7.0 and later, through 1811.
In zero-downtime 24/7 environments with shift employees, customers rarely want users to be notified of scheduled or mandatory XenApp server reboots. As a result, most of these environments have reboots disabled or this process is done manually. Unfortunately, this isn’t a good process since the XenApp servers are susceptible to memory leaks which can lead to failure and poor performance. By utilizing the included Chained reboot scripts, environments can take advantage of N+1 overallocation by processing a single server reboot while maintaining the user load on remaining systems. This has been done in such a way that users are not kicked off the system for scheduled reboots. Instead, the server is removed from load balancing until all sessions have been logged off. Once all sessions have been logged off, the server will go down for a reboot.
Hi,
How can i exclude some servers from rebooting policy?
Getting the same problem as Andre
(One we start running the script it reboots all the servers once as planned (24hrs cycle). But after the first cycle of 24 hrs we get the following msgs )
Quick fix is RebootThisServer variable set to true.
And one more thing could you give the option to have the nologon variable with 6.5 farms. When you run published applications. You do not want a new session/logon on a diffrent server for new application the users starts. You only want to avoid new logins of new users.
– Released XenApp 6.5 compatible version utilizing the ProhibitNewLogOnsUntilRestart and removing syntax for the NoLogon load evaluator.
This is good if you do published desktops you do not want this behavior on published apps. You want them to stay on the same server in the same session. So the nologon variable would be better since published apps keep starting on the same server for the already loged on users.
Thanks for a excellent script.
Regards
/Ossian Ericson
Awesome feedback Ossian! I’m still working on tracking down the root cause for the loop failure. I will release a new version once I’ve determined the root cause and fix. Thanks!
–youngtech
Hi Dane
I’m getting the same issues as some of the above responders. I have it set to 150 hour reboot cycle.
In the event log I get all of the 511 events counting down, however when it gets to 23 hours the event says waiting for another 127 hours. The next event says 0 hours since the last loop, waiting for another 150 hours.
It is never doing another reboot after the first one
Any ideas?
Thanks
Jon
(great script BTW)
Still working on tracking this down. Thanks for your patience Jon.
–youngtech
Hi Jon,
This issue has been resolved, please test out the latest Rev8.
Thanks,
Dane