Citrix Chained Reboot Scripts, now supporting Citrix Cloud, Citrix Virtual Apps and Desktops (CVAD), and XenApp/XenDesktop 5, 6, 6.5, and 7.x!

Share Button

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.

Share Button
  1. Michael WoodwardMichael Woodward09-04-2014

    Dane, wanted to send you a note and say thanks for your work on this. I maintain about 12 farms across 8 domains (XenApp 5, 6.0, 6.5 and soon 7.6) While your scripts didn’t fit our exact needs. I was able to make some significant modifications and combine all into one script that i can pretty much pickup just drop on a server in one of our farms and then set it up a scheduled task and walk away. Your work has made managing our complex environment a lot easier. Keep up the good work!

  2. MarkMark08-14-2014

    Hi Dane,

    First of all thank you for this awesome script.
    I also have the same problem as above people that the script reboots the servers once, after that it stays in a waiting loop. I was wondering if you have some more idea’s about this. I thought maybe a quick and dirty trick was to close the script after the last reboot since task schedular restarts it anyway when the next reboot cycle needs to be started. Just a idea.

    -Mark

  3. Kim ClausenKim Clausen07-07-2014

    Great script.

    I have a problem with the farm loop, after reboot of all servers it starts counting towards next reboot loop. When it gets to 24 hours it just starts counting from 0 with no reboot loop executet. Please advice on how to sort this out. The farm is 6.2, so we are using the XenApp6_Citrix_Chained_Reboot.ps1

    • JaanJaan09-25-2014

      Hi Kim,

      Did you mange to sort out the loop issue, I am also having the same issue, it does not loop

  4. RonRon06-19-2014

    Nice script!

    I changed line 192:

    “‘ from delivery group ‘” + $deliverygroupname

    into

    “‘ from worker group ‘” + $workergroupname

    Regards!

  5. Dennis ReimerDennis Reimer04-29-2014

    Thanks for the great script,

    i have only one general question: If you are using PVS with XenApp6.5 or Xendesktop 7.5, what are you doing with a vDisk Update for a Client Application, with the first launch of the client application, the server component is upgraded. In this case all users on terminalservers with the old client application version can no longer work with the server component. Have you got any ideas other than rebooting all terminalservers manually.

    Regards

    Dennis

1 13 14 15 16 17 25

Leave a Reply