Product Documentation

Server Policy Settings

Oct 09, 2015

The Server Settings section contains policy settings for configuring access control, DNS address resolution, icon handling, and XenApp edition.

Connection access control

This setting specifies the types of client connections from which users can start sessions.

When adding this setting to a policy, select an option:
  • Any connections (selected by default) allows access to published applications through any connection.
  • Citrix Access Gateway, Citrix online plug-in, and Web Interface connections only allows access to published applications through the listed connections, including any version of Access Gateway. This option denies access through any other connection.
  • Citrix Access Gateway connections only allows access to published applications only through Access Gateway Advanced Edition servers (Version 4.0 or later).

DNS address resolution

This setting enables or disables the server to return fully qualified domain names to clients using the Citrix XML Service.

DNS address resolution works only in server farms that contain servers running MetaFrame XP Feature Release 1 or later, and clients must be using Presentation Server Client Version 6.20.985 or later or Citrix XenApp Plugin for Hosted Apps version 11.x.

Full icon caching

This setting enables or disables the caching of larger, high resolution published application icons on farm servers. By default, icons are cached.

To ensure only specific farm servers are affected by this setting, configure a worker group that includes only the servers you specify. Then, include the worker group in the filter you add to the policy. If no filter is specified, this setting affects all farm servers.

Consider disabling this setting if caching icons impacts performance of the server. However, do not disable this setting on servers acting as XML brokers for the farm.

XenApp product edition

This setting specifies the XenApp product edition.

Setting the product edition activates the features available with a particular edition. The product edition also determines which type of license a server requests from the license server. Make sure the edition you set matches the licenses that are installed.

Connection Limits Policy Settings

The Connection Limits section contains policy settings for controlling user and administrator sessions and logon event logging.

Limit user sessions

This setting specifies the maximum number of connections that users can establish, in the range 0-8192. A value of 0 indicates no connections.

When a user tries to establish a connection in excess of this limit, a message tells the user the connection is not allowed. When a connection request is denied, the server records the user’s name and time in the System log.

Related Policy Settings
Concurrent logon limit

Limits on administrator sessions

This setting enables or disables connection limit enforcement for Citrix administrators. Limiting connections for Citrix administrators can adversely affect their ability to shadow other users. By default, administrators are exempt from connection limits.

Logging of logon events

This setting enables or disables the logging of events (to the server event log) about connection attempts that were denied because they exceeded logon limits. By default, these events are not logged.

Health Monitoring and Recovery Policy Settings

The Health Monitoring and Recovery section contains policy settings for configuring Health Monitoring and Recovery tests and server load balancing exclusions.

Health monitoring

This setting allows or prevents running Health Monitoring and Recovery tests on the farm servers. By default, Health Monitoring and Recovery tests are allowed to run.

Health monitoring tests

This setting specifies which Health Monitoring Tests to run. You can add or remove tests. You can also edit the configuration of a test (name, location, description, interval, threshold, time-out and recovery action). By default, the following Citrix tests are run:
  • Citrix IMA Service
  • Logon Monitor
  • XML Service
  • Remote Desktop Services

Maximum percent of offline servers

This setting specifies the maximum percentage of servers that Health Monitoring and Recovery can exclude from load balancing. By default, ten percent of servers are excluded.

Memory Optimization Policy Settings

The Memory/CPU section contains policy settings for managing CPU utilization and memory optimization.

CPU management server level

This setting specifies the level of CPU utilization management on the server. Managing CPU resources can normalize CPU peaks and reduce the resources required to handle CPU spikes. By default, CPU utilization is not managed.

When adding this setting to a policy, select an option:
  • No CPU utilization management disables CPU utilization management on the server.
  • Fair sharing of CPU between sessions ensures that CPU resources are equitably shared among users by having the server allocate an equal share of CPU to each user.
  • Preferential Load Balancing allocates more CPU resources to one user over another based on the resource allotment for each session. The resource allotment is determined by the importance levels of both the published application running in the session and the session itself.
Note: To use CPU Utilization Management, ensure the Fair Share CPU Scheduling (DFSS) feature of Remote Desktop Services is disabled on the server.
Related Policy Settings
Session importance

Memory optimization

This setting enables or disables memory optimization. Enabling memory optimization improves the ability to manage DLL allocation in both real and overall virtual memory by creating shared DLLs for applications that are open in multiple sessions. By default, this setting is disabled.

Memory optimization application exclusion list

This setting specifies the applications that memory optimization should ignore. You can add, edit, or delete applications in the list.

Memory optimization interval

This setting specifies the interval for running memory optimization. By default, memory optimization runs daily.

When adding this setting to a policy, make sure the Memory optimization setting is present and set to Enabled.

Memory optimization schedule: day of month

This setting specifies the day of the month that memory optimization runs, in the range 1-31. By default, memory optimization is scheduled for the first day of each month.

When adding this setting to a policy, make sure the following policy settings are present:
  • Memory optimization, set to Enabled
  • Memory optimization interval, set to Monthly

If the specified day does not occur in a given month (for example, the 30th day in February, or the 31st day in April or June), memory optimization does not run in that month.

Memory optimization schedule: day of week

This setting specifies the day of the week that memory optimization runs. By default, memory optimization runs on Sundays.

When adding this setting to a policy, make sure the following policy settings are present:
  • Memory optimization, set to Enabled
  • Memory optimization interval, set to Weekly

Memory optimization schedule: time

This setting specifies the time at which memory optimization runs. The time format is H:MM TT, where H is the hour, MM is the minute, and TT is the time of day (AM or PM). By default, memory optimization runs at 3:00 AM.

When adding this setting to a policy, make sure the following policy settings are present:
  • Memory optimization, set to Enabled
  • Memory optimization interval, set to Daily, Weekly,or Monthly

Memory optimization times are scheduled in the local time zone of the server and use a 12-hour clock. If you enter a time according to a 24-hour clock, the time is converted automatically to a 12-hour clock. If you enter a time without a TT value, the time defaults to AM.

Offline Applications Policy Settings

The Offline Applications section contains policy settings for controlling offline application access, licensing, and logging.

Offline app client trust

This setting enables or disables the ability of offline application clients to recreate sessions when reconnecting, without authenticating again. By default, users must authenticate when reconnecting to offline applications.

Offline app event logging

This setting enables or disables logging of offline application events to the event log on the server. By default, offline application events are not logged.

Offline app license period

This setting specifies the number of days applications can work offline before users have to renew the license. The license period, 21 days by default, can range from 2 to 365 days. Licenses automatically renew at login and every day while logged in. Changes to the license period occur when the license is renewed.

To configure licenses, administrators can use the License Administration Console or command-line tools. They must also ensure they have a sufficient number of licenses to support the total number of users with offline access permission.

Offline app users

This setting specifies the users who have permission to access offline applications. You can add or delete users from this list.

Users in this group can continue using configured applications after disconnecting from the network for the number of days specified in the Offline app license period setting. You must configure the applications for offline access in the application properties.

The total number of users with offline access permission should not exceed the total number of licenses available for offline access.

Reboot Behavior Policy Settings

Updated: 2013-09-03

The Reboot Behavior section contains policy settings for scheduling server restarts, disabling logons, and configuring warning messages.

These policy settings are applicable to XenApp Enterprise and Platinum editions only.

Reboot custom warning

This setting enables or disables sending a custom warning message (in addition to the standard restart message) to users before a scheduled server restart. To specify the text for this warning, configure the Reboot custom warning text setting. By default, only the standard warning message is sent.

Reboot custom warning text

This setting specifies the text in the custom warning message sent to users before a scheduled server restart. To send a custom message, the Reboot custom warning setting must be enabled.

Reboot logon disable time

This setting specifies the number of minutes before a scheduled server restart that logons to the server are disabled. By default, logons are disabled 60 minutes prior to server restart.

Reboot schedule frequency

This setting specifies the frequency, in days, that scheduled server restarts occur. By default, scheduled restarts occur every 7 days (once each week).

Reboot schedule start date

This setting specifies the date on which scheduled server restarts begin, in the form MM/DD/YYYY.

Reboot schedule time

This setting specifies the time at which scheduled server restarts occur in the form H:MM TT, where H is the hour, MM is the minute, and TT is the time of day (AM or PM). Restart times are scheduled in the local time zone of the server and use a 12-hour clock.

If you enter a time according to a 24-hour clock, the time is converted automatically to a 12-hour clock. If you enter a time without a TT value, the time of day defaults to AM.

Reboot warning interval

This setting specifies how often standard and custom warning messages are sent to users before a scheduled restart. By default, messages are sent every 15 minutes.

Configure the Reboot warning start time setting to specify when to start sending the warning messages.

Reboot warning start time

This setting specifies the number of minutes before a scheduled server restart to send standard or custom warnings to users. By default, messages are sent 60 minutes prior to server restart.

Configure the Reboot warning interval setting to specify how often the warning is sent.

Reboot warning to users

This setting enables or disables sending a standard warning message to users before a scheduled server restart. By default, messages are not sent to users prior to server restarts.

To send a custom warning message (in addition to the standard message), enable the Reboot custom warning setting and specify the text in the Reboot custom warning text setting.

Scheduled reboots

This setting enables or disables scheduled server restarts. You can configure automatic restarts at specific times and frequencies, as well as the starting date of the schedule. By default, server reboots are not scheduled.