Citrix Server Reboot best practice

I am planning to schedule reboot on citrix xenapp 6.5 server. Need help on best practice to schedule on all the xeanpp 6.5 server.

- Without impacting users need to reboot
- have to wait for users session to logoff
- disable logon
- reboot citrix serves
- enable logon
LVL 26
Sekar ChinnakannuStaff EngineerAsked:
Who is Participating?
Mohammed KhawajaConnect With a Mentor Manager - Infrastructure:  Information TechnologyCommented:
Login to the server
Disable logins
Ask active users too logoff and login to different server(s)
Reboot the server
Rick HobbsRETIREDCommented:
Unless you have a farm where you can transfer active users to another server you are not rebooting, you will need to wait for the users to logoff or they will lose the data in their current session.
Ayman BakrConnect With a Mentor Senior ConsultantCommented:
The best practice is where you have a service level agreement with your users to dedicate some time, preferably during weekends, for maintenance. This means that your users will not log on during this period of time and they will have to ensure they save their work and log off before that time. This way you can schedule a safe reboot staggered over the period of the maintenance window.

If your organization is not yet that mature, you can use the Citrix Reboot Behaviour Policy settings. Note that for this to get activated you need to have Enterprise or higher edition of XenApp. In this scenario, I suggest the following:

-> Reboot your servers on phases so that you ensure availability all the time and servers always exist to accept user connections. You can arrange your servers in worker groups and create a policy for each worker group staggering the reboot schedule over a period of time, e.g. 30 servers over 20 min. In this case, you will disable the logons on the phase which will undergo the reboot first. Alternatively, you can use the Reboot Logon Disable Time to set the number of minutes before scheduled restart whereby the servers become disabled for logon. I suggest this to be at least 60 min. If you use this setting then it would be best to set the Reboot Warning Start Time less than the Reboot Logon Disable Time to ensure that the servers are disabled for logon before the users start logging off and back in. Otherwise, they might land on those servers again.

-> Enable Reboot Custom Warning setting and disable the standard warning by disabling the Reboot Warning to Users setting

-> Keep the default 15 min setting on the Reboot Warning Interval. This way the user will be annoyed until he eventually will save his work and log off. Otherwise, users tend to ignore IT and will never log off. But after they log off, they can immediately logon and will be served by other servers because the servers scheduled for reboot will have been set for disabling logon

-> Specify the other settings related to start date and time and frequency.

Note that the above will not ensure waiting for the users to log off before the reboot. The users will have to save their work and log off or else they will risk losing their work when the reboot starts.

If you want to ensure that all users have logged off before a server will reboot, you will need a special script or third party tool or something. Back in 2011, there was a script developed by Dane Young built on load evaluators which could achieve this. Its name was Citrix XenApp Rolling Reboot Script. It was available until some time on his blog, but unfortunately it is no longer available there. Perhaps you can google it if you are interested.
Free Tool: ZipGrep

ZipGrep is a utility that can list and search zip (.war, .ear, .jar, etc) archives for text patterns, without the need to extract the archive's contents.

One of a set of tools we're offering as a way to say thank you for being a part of the community.

joharderConnect With a Mentor Commented:
You may wish to reconsider whether to use the Reboot Logon Disable Time.  If your reboot time is set for the wee hours of the morning, it doesn't really matter if you disable logons anyway because the chances of users logging in at that time is pretty slim.

The issue is that occasionally logons may continue to stay disabled after the reboot.  I've seen this happen a only very small percentage of the time, and it's frustrating.  There doesn't seem to be a good reason why.  Better safe than sorry and not disable logons prior to reboot.
Sekar ChinnakannuStaff EngineerAuthor Commented:
our users working on 24\7, also could you please let me know benefits for schedule reboots
Ayman BakrSenior ConsultantCommented:
The only thing I find as a benefit from scheduled reboot is automation of the reboots, making intervention by me as an admin minimal. With a large number of servers, in the order of hundreds you can imagine the benefits. However watching process and post reboot monitoring would be necessary to ensure everything goes fine and rectify any issues.
Sekar ChinnakannuStaff EngineerAuthor Commented:
ok how regular reboot makes advantage to citrix
Ayman BakrSenior ConsultantCommented:
Regular reboots ensures freeing up the RAM, eliminating memory leaks and thereby allowing the servers to start fresh. This is especially for 32 bit servers. Obviously, XenApp 6.5 is a 64-bit server, therefore with sufficient RAM should be suffering less from these memory leaks.

Other benefits would be unloading the users' registry hives. In addition if your XenApp servers are provisioned using a provisioning server, regular reboots will ensure write caches do not grow above their limits.
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.