RDP within XenDesktop is Slow

I ran into an issue today, where a user was reporting that their Xen Desktop session was nearly unusable once they launched remote desktop to another system. I found that if a user has an effective available bandwidth of approximately 300 kbps (in our environment) or less while there is an active RDP session within the XenDesktop session, the connection is nearly unusable. I tried to enable some heavy compression in my tests, but it didn’t drastically improve anything. I was hoping that since RDP is screen painting to the XenDesktop session that I could compress this traffic more and have better results. As far as graphical performance tweaks, there wasn’t much we could do. After some extensive Googling however, I found the cause was Aero mouse pointers active in the RDP session (the Windows Default). See here: Slow or Jerky Mouse Movement from Published RDP Session
Continue reading

Advertisements

Display hostname to XenDesktop 5.6 users

By default, XenDesktop 5.6 uses the Desktop Group display name to display to the end user. This is intended so that when you are using pooled desktop, the user can randomly get a VDI. However, if you are using XenDesktop to broker to dedicated virtual machines, it may be helpful to display the hostname to the user rather than the Desktop Group name. I personally prefer to have all of these computers in one desktop group. Here is a script to set this display property for all the computers in that desktop group:
Continue reading

Import Vmware ESX machines into a Xen Desktop “existing” catalog with a script

If you don’t feel like browsing your Vmware infrastructure everytime you add a virtual machine into Xen Desktop, you can use this script to find the virtual machine in Vmware, add it to a catalog, add it to a desktop group, add a user assignment, and set the display name of the assignment to the machine name.

Caveats:

Requires a catalog of the type “existing”.
Requires you to add one assignment to the machine. (You may add or remove users via the console as well)
Requires the quest AD powershell tools to verify the computer name and username
Requires that the virtual machine is named the same in VMWare as it is in Active Directory…adjust as necessary
Requires the Xen Desktop console is installed on the computer you are running the script from
Continue reading