Supporting a XenDesktop environment is not just about being able to collect and consume detailed log files and traces. The fact is, it is much more than this. A good understanding of the FMA architecture and expected behavior can go a long way to resolving various technical issues. Join Kimberly Ferrie and Mick Glover as they discuss and demonstrate how to apply this knowledge when supporting a XenDesktop environment.
What you will learn
- How the various FMA services interact with each other and the Site Database
- How to check the true state of FMA services and validate site functionality through PowerShell
- How to create various types of Service and Database Schema scripts
- How to configure Site policies to control access to resources
Focus Point: To be able to support XenDesktop successfully, you first must understand the architecture and itâs capabilities.
How the various FMA services interact with each other and the Site Database
How to check the true state of FMA services and validate site functionality through PowerShell
How to create various types of Service and Database Schema scripts
How to configure Site policies to control access to resources
Here is an example of PoSH being used to validate the status of the Super 6.
Careful, as these naming conventions are not overly institutive.
Click
Basically, for frontlineâŠ
the value you are looking for is OK
If you get anything other than OK, there is a problem.
Citrix Studio offers administrators the opportunity to generate two of the 4 service scripts:
1.FullDatabase
2.Login
The above policies (Entitlement & Assignment) control access to resources and also the conditions (Access Policy) under which resources can be accessed.
Assignment policies are useful if you are assigning users on first use at the Delivery Group level. No impact if you exclude the same user that you pre-assign to a desktop as the pre-assignment will override the exclusion.