VMware vSphere 5.5 – Citrix Known IssuesCTX140135

  • CTX140135
  • Created onMar 26, 2014
  • Updated onJan 16, 2015

Symptoms or Error

Citrix is committed to ensuring compatibility with the latest VMware products. Citrix supports VMware vSphere 5.5 and VMware vSphere 5.5 Update 1, and VMware vSphere 5.5 Update 2.

This article outlines issues and their known solutions that users of vSphere 5.5 vSphere 5.5 Update 1, and vSphere 5.5 Update 2 must be aware of in conjunction with the following Citrix products:

  • Citrix XenDesktop 5.0 Service Pack 1
  • Citrix XenDesktop 5.5
  • Citrix XenDesktop 5.6
  • Citrix XenDesktop 5.6 Feature Pack 1
  • Citrix XenDesktop 7.0, including App Edition
  • Citrix XenDesktop 7.1, including App Edition
  • Citrix XenDesktop 7.5


The following information outlines the issues and their solutions:

Issue 1

Adding VMware vSphere Server 5.5 host using HTTP connection fails with an Error ID: XDDS:09246D12. VMware vSphere 5.0 U3 and vSphere 5.5 require HTTPS connection. XenDesktop will no longer be able to connect to vSphere 5.0 U3 and vSphere 5.5 using HTTP, and HTTPS would be required.

Solution 1

The workaround in CTX125578 – XenDesktop Error: The hosting infrastructure could not be reached at the specified address will not be applicable for vSphere 5.5 and 5.0 U3.

Issue 2

Machine Creation fails intermittently using vSphere 5.5 and XenDesktop 7.1. The issue is because of network latency.

Solution 2

Set the DiskUploadReponseTimeout to 8:0:0.

  1. Go to Hypervisor Connection Properties located under Citrix Studio > Hosting.
  2. Select the VMware vCenter 5.5 connection and choose Edit Connection.
  3. Go to Advanced > Connection options, type the value DiskUploadReponseTimeout=8:0:0.
    This sets the timeout to 8 hours.

Issue 3

The display of HDX 3D Pro enabled VDA hosted on ESXi 5.5 with vShared Graphics Acceleration fails to connect from a Multi Monitor Setup.

Solution 3

Only Single monitor configuration is currently supported.

Issue 4

Citrix Display Adapter is not installing on Microsoft Windows Vista Service pack 2 after installing Citrix Virtual Desktop Agent for XenDesktop 7.1 on a machine with the VMware Tools installed.

Solution 4

This issue has been resolved in Hotfix Rollup XD560VDAWX64400 or XD560VDAWX86400 (Version 5.6.300). Refer to one of the following:

Replace XdsAgent_x(86/64).msi (Version 5.6.200) present in XenDesktop 7.1 DVD with 5.6.300’s XdsAgent_x(86/64).msi, then run themetainstaller on a machine with the VMware Tools installed.

Issue 5

The CPU usage reaches 100% upon desktop launch in Citrix VDA client with HDX 3D Pro and VMware Dedicated Graphics Acceleration (vDGA) feature enabled.

Solution 5

The issue is observed if only one CPU core is assigned to the Citrix VDA client. The recommended minimum is to have two or more cores assigned to Citrix VDA client.

Issue 6

Virtual Machine creation fails intermittently while creating Streamed VDA Catalog using Provisioning Services (PVS) 7.1.

Solution 6

The behavior has been resolved in Provisioning Services 7.1 Hotfix CPVS71003.
By default, PVS 7.1.3 provides 3 seconds of wait time during target creation using the wizard. If the target virtual machine fails to create, adjust the wait timeout by changing the following registry in small intervals:

Caution! Refer to the Disclaimer at the end of this article before using Registry Editor.HKEY_LOCAL_MACHINESOFTWARECitrixProvisioningServices
Name: ESXVMCreationInterval
Value: <range of 0 to 60 seconds>

Issue 7

Deleting Provisioned Virtual Desktop Agent Catalog from XenDesktop 5.6 Delivery Controller (Controller) fails.

Solution 7

This issue has been resolved in XenDesktop Hotfixes Update 9. Refer to one of the following:

Issue 8

VMware SVGA adapter is preferred instead of NVIDIA display adapter, which results in NVIDIA display adapter not being used in HDX 3D Pro VDA 5.6 session.
The default display adapter can be changed to use NVIDIA adapter within the VDA session but it would result in Virtual Machine Console display becoming blank.

Solution 8

Apply one of the following:


Caution! 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.



I was working on a new Citrix PVS image for one of my current projects and the test before running the P2PVS.exe were good, all my apps worked like they should so I prepped the server for the imaging (preparing antivirus, last PVS optimizations and a full pre-scan of my VM) and I ran P2PVS.

After a successful P2PVS I ran into a couple of problems: The RES Workspace Manager Service didn’t start and one of the key components of this image (an outlook plugin) gave a weird error that didn’t show up at first. I did some troubleshooting and found that the RES Software WM Service couldn’t start because the executable wasn’t found, I could browse to the directory and the res.exe was there. Luckily Barry Schiffer came up with the idea to check the shortnames which are used to start the RES WM Service and a lot of software still use the shortnames for the Office folder as well so apparently we had shortname issues with Citrix XenApp and Citrix PVS.

I soon realized that I used the XenApp 6.x (Windows 2008 R2) – Optimization Guide to optimize the image and one of the recommendations was to disable the NTFSDisable8dot3NameCreation:


Note: Even in 2012 some applications still rely on 8.3 names. Scanning the for commonly used director names (i.e. C:PROGRA~1) can help revealing affected programs.

After changing this value back to “0” we were able to run a successful P2PVS and the errors in RES Workspace Manager and the key application were gone. Here’s somebackground info on why to disable shortnames and how to check this from the command line.

To disable/enable 8.3 naming convention, users can issue the set command as follows:

C:Windowssystem32>fsutil 8dot3name set /?
usage : set [0 through 3] | [<Volume Path> 1 | 0]

I also received this MS page on 8.3 name creation with the following sample commands

The following command disables 8dot3 name creation on all volumes:

fsutil 8dot3name set 1

The following command disables 8dot3 name creation on the C drive:

 fsutil 8dot3name set C: 1

Kees Baggerman

Kees Baggerman is a senior performance and solution engineer for desktop and application virtualization solutions at Nutanix. Kees has driven numerous Microsoft and Citrix, and RES infrastructures functional/technical designs, migrations, implementations engagements over the years.

One comment


Best Practices Preparing a Provisioning Services vDisk

Let’s say you’re going to run Windows Updates. Well since you’ve already launched the Target Optimizer tool, that services is disabled and you need to head into services, enable and start it. Run Windows update and all good. When the update is finished you shutdown the machine and switch from Private to Standard Mode.

What you didn’t remember was to reboot the server for Windows Update to complete it’s updates. What happens now, is that every time your servers reboot, Windows Update will kick in and finish it’s things.

So being only one administrator doing all the procedures is one thing, but when you hand over the solution to your customer or maintenance team, everybody would probably do this differently, forgetting to flush DNS and so on.

So this script will do all these thing for you. Just teach your staff to always run the script after maintenance.

Prerequisites :

Copy Wuinstall to C:Windows. Run XenAppCloning tool, add your free license and then configure your settings and save the settings to the configuration file.

Extract the XAUpdate script to C:XA65Update, rename the script to XA65Update.cmd and configure the settings required inside that script.

Copy the content below into C:Program FilesCitrixPrepare for PVS.cmd

To get ride of this annoying boot screen

you just added HKLMSoftwareCitrixProvisioningServicesSkipBootMenu to your PVS servers. Now your maintenance / test machine will automatically boot to the newest version of the vDisk.

Please be aware that this doesn’t work on Provisioning Services 6.2 hosted on Windows 2012. The good news though, the KMS bug has finally been fixed in Provisioning Services 6.2 (part of Project Excalibur Tech Preview).

So when you e.g. want to patch your Provisioning Services image with the latest Citrix Hotfixes, you just select that option and off you go. The server is rebooted automatically and when it comes back online you just run through the script another time and this time the server will be shutdown ready for you switching from private to standard mode.

If you have any other Best Practices for Provisioning Services, please leave a comment below and share with the community.