Citrix XenApp Policies are settings for XenApp servers; for example, they can be rules that govern user connections and server settings, etc… Below are some facts about Citrix XenApp 6.5 Policies.
- There are two types: Computer Policies and User Policies.
- There are different 7 templates as well which cannot be edited.
- Found under: AppCenter -> Citrix Resources -> XenApp -> Policies.
- Examples: DNS Resolution and Display Memory limit policies.
- Policy that has Higher number is Less Priority.
- Example: to enable Memory Optimization Policy: Under Computer Policy, there is an Unfiltered template. Click Edit. Click Settings.
- Click Memory/CPU. Click Add near Memory Optimization. Click Enable. Click OK when done. This action enabled the Memory Optimization for the server to optimize memory usage by creating shared DLL on similar apps.
- Try to create a new Policy called MyPolicy and enable Connection Reconnection. Apply Filter to the Workergroup you created.
- WorkerGroup: group of XenApp Servers that have similar apps on them.
- To Save a Policy: Highlight Policy and choose Actions drop-down menu. Save it as template (backup / restore purposes).
- We can use default template and/or customize it to suite our needs.
- For instance, we can customize by removing some settings.
- Cache data acts as branch repeater.
- Sites represent Zones
- We can create Policies in GPMC or in Citrix console AppCenter.
- CPMC -> Citrix Policy -> You’ll see same policy management Console.
- Settings are under user or Computer Configurations.
Processing and Precedence of Policies
Recommendation: Apply Policy in XenApp, AppCenter. Keep it in one place only for simplicity. If we make a policy in XenApp, it will not appear in AD. That’s why we need to keep it in one single location.
- Run for Objects such as users.
- Find out what gets applied to which.
- In Command Prompt, type GPMC.MSC, R/C Citrix Group Policy Model. Then run the Wizard.
- Specify User/Computer/OU information. Click Next.
- Here, you can Filter Evidence Selection by inputting the IP address, Client name,, server group.
Load Evaluators (LE)
- Measure load of servers. This is for Data Collectors to know.
- Two default LE. You cannot change these LE.
- They are:
- User Log on: strain on server
- Full Load: 100 users.
- Observe that the Advanced LE, under CPU Utilization Load Rule:
- 90% CPU utilization -> no more loads allowed
- At 10%, it is considered as NO LOAD.
- Load throttling: The impact of logons on load is HIGH.
- Memory Usage: same as CPU utilization; that is: 90% is considered FULL and 10% is considered LOW.
We can create Custom Load Evaluators.
- Scheduling: when users can log on.
- Apply LE to server.
Buy Citrix (XenApp 6.5)
- Advanced Edition: ~50 Users
- Enterprise Edition: ~500 Users
- Platinum Edition: ~5000 Users.
- This is determined by the time you buy the product.
- No restrictions on the number of XenApp Server.
Assign Load Evaluator
- Go to any application, you can assign LE
- Computer settings (under Policy) we can also assign LE
- LE can only applied to servers, not users or apps???
Load Balancing Policies
- Create one LBP1
- Add WorkerGroup to it (second last option)
- Filtering off.
- Particular Workergroup orr Site down or WG fully loaded -> route to another zone. This is the use of LBP (Zone / Site level)
- Load Evaluator is more like local than Zone.
- Specify multiple WG for failover.
- Citrix gives up on AppStreaming
- MS gives free licenses for App-V
Please go through all the policies to make sure you understand them properly.