Citrix Consulting have released this awesome whitepaper that is a most read if you are an consultant, architect, administrator or you would like to learn how to design, implement XenApp / XenDesktop with the best practise advise from citrix consulting.
The foundation of any good XenDesktop or XenApp enterprise design should be adherence to a collection of best practices which are based upon knowledge gathered from previous enterprise deployments, lab validations, and lessons learned in the field. Such best practices are just a starting point for a design, as an organization’s specific design requirements will often necessitate deviation from the recommended path. By using the following recommendations as a starting point, the foundation of the design will be robust enough to support many different deployment scenarios.
This document consolidates and summarizes the best practices for XenApp and XenDesktop environments. As products evolve, best practices also change, which is why each best practice discussed in this document is associated with a specific product and version, which includes the
- XenDesktop 5.0, 5.5, 5.6
- XenApp 6.0, 6.5
Additional best practices are provided for those products which provide complimentary functionality to both XenDesktop and XenApp, including:
- Citrix Provisioning Services
- Citrix XenServer
- Citrix Profile Manager
- Microsoft Hyper-V
- VMware vSphere
For further guidance and more detailed information, please refer to the XenDesktop Design Handbook.
The recommendations provided within this document may not be appropriate for every environment. Therefore, all best practices within this document should be evaluated in an isolated test environment prior to being implemented in production.
Caution: Some of the best practices in this document will require you to edit the registry. Using Registry Editor incorrectly can cause serious problems that might require you to reinstall your operating system. Citrix cannot guarantee that problems resulting from the incorrect use of Registry Editor can be solved. Use Registry Editor at your own risk. Be sure to back up the registry before you edit it