Getting the Most out of Citrix XenClient Enterprise 4.1
XenClient Enterprise Engine:
- Select Compatible PCs – business-class PCs with Intel components (CPU, GPU, networking) and 7200+ RPM drives preferred.
- Ensure sufficient memory – 4GB recommended; 2GB is the minimum; more memory means better performance.
- Install PV drivers – they are critical for local VMs for USB support, networking, and good performance.
- Check BIOS settings – make sure that Intel VT-x is turned on and Nvidia Optimus (if available) is turned off.
- Use Windows VMs – Windows 7 or XP work best. Linux virtual machines are primarily for experimental use.
- Manage Networking through XenClient Enterprise – Wireless/wired networking is managed through the XenClient Enterprise
- Use Ctrl-Down-Arrow – this is used to access the XenClient Enterprise Engine launcher and settings.
- Connect to XenClient Enterprise Synchronizer – the greatest value of XenClient Enterprise is centralized management – enabled through XenClient Enterprise Synchronizer.
XenClient Enterprise Synchronizer:
- Use Win 2008 R2 64bit – Win 2008 R2 64bit (Standard, Enterprise, or DataCenter) is required to run the Synchronizer.
- Use Hyper-V Role for publishing – Hyper-V version 6.1 or higher is required for publishing (even with an ESX installation).
- Ensure sufficient Hyper-V permissions – Being in the local or domain Administrators group is not sufficient.
- Allocate sufficient storage & memory – We recommend 200GB disk and 8GB RAM as a baseline.
- Build a clean VM & avoid P2V conversion – Clean Windows VM images perform best.
- Build VM images incrementally – start with a base Windows install with no applications (including antivirus software).
- Confirm Active Directory Settings – Use AD Explorer to facilitate the configuration; see the Synchronizer Installation Guide for more information.
- Clear your browser cache if needed – Clear your browser cache and restart the browser if you see anomalies in the Synchronizer.
- Use IE 8 or 9 with required components – Microsoft .NET Framework 2.0 must be installed and RDP ActiveX control enabled