This is the personalized installation I do when I deploy vmtools on the VMs with VDA to install on it. Don't forget to install vmtools before Citrix Virtual Desktop Agent ! It always good to have this information shared because I had a lot of question regarding vmware vmtools installation with Citrix XenDesktop VDAs. Toolbox – Enable – Used for functions like time synchronization and clean shutdown of guest. Memory Control Driver – Enable - Driver for improved memory management in the virtual machine. This driver is available and recommended if you use VMware vSphere. Excluding this driver hinders the memory management capabilities of the virtual machine in a vSphere deployment. Thin Print Driver – Disable - Handled by Citrix printing in VDA. Paravirtual SCSI – Disable – Used in high I/O operation with SAN and mostly is applicable to Server VMs and not VDA. This driver is for PVSCSI adapters, which enhance the performance of some virtualized applications. Mouse Driver – Enable – Needs the mouse driver as it improves fixes in glitches with the mouse. File System Sync Driver – Disable - Driver for the synchronization of the file system within the virtual machine. For example, for preparation of backups. Only used if you have dedicated VMs and used agents in VMs to backup VMs. In VDA environments most common settings is profile management in which data is moved to a share as opposed to being local on VMs. Shared Folders – Disable – Directory for data exchange between host system and guest system. Currently only works with VMware Workstation and have seen it cause a lot of synchronization issues. SCSI Driver – Enable – Installs and improves BusLogic SCSI driver. If you use LSI Logic this driver is not required. SVGA Driver – Disable – We want to use the Citrix VGA adapter and not the VMware VGA. Use CTX 123952 (below) as work around if using Windows 7. Audio Driver – Enable – Needs audio driver to playback sound. This sound driver is required for all 64-bit Windows guest operating systems and 32-bit Windows Server 2003, Windows Server 2008, and Windows Vista guest operating systems if you use the virtual machine with VMware Server, Workstation, or Fusion. VMXNet NIC Driver – Enable - Network card driver for the VMXNet VMware network card. Improves network performance of the virtual machine, especially in gigabit environments. Furthermore the CPU…

After many years going from a customer to another, speaking with people all around the world, I wanted to share my experience regarding application integration. This is not a new topic but there are so many way to deliver applications today it can become very messy very fast. In a lot of companies I worked with, I had to face many different situations with different technologies and solutions. What I explain in this blog is just one way to get things done, maybe not the best one but I think this is the most efficient way to leverage Citrix / Microsoft solutions when it's about application delivery. I made a simple diagram to materialize my though when I plan to integrate or migrate new application into a VDI environment. When I write VDI, I mean : VDI = Virtual Desktops + Shared (Virtual) Desktops (SBC) For example, when I need to free a XenDesktop golden image from all the applications installed over the years, I need to understand : Is this application still in use ? Who need this application ? Why they need it ? How they use it ? How many users need this application ? Is there enough license for this application ? What is the update cycle of this application ? What are the prerequisite of this application ? Etc etc... Then I need to to know if I want or need to "virtualize" this application or not : First thing first : is this application working on a regular OS with a "normal" installation process ? Do you need to virtualize this application ? time & cost vs deployment & number of users What are the prerequisite for this application ? (XenApp silo needed or not, specific Streaming profile / AppV) Is this application need to be use offline, ie roaming users ? What is the application size (Mb, Gb) once it's installed ? Is this application supported on a 64bit Operating System ? All these point are what I'm asking myself before doing anything. There are a lot more question you need to ask yourself, it depend of each customer's environment and technologies in use. The more I look this diagram the more I find some other step to add, this is like a never-ending construction and a new puzzle at each customer's place. We could continue this schema with application compatibility between each…