XenApp 6.5 AppCenter missing hotfixes

Ran into a problem while creating a XenApp 6.5 report, where some hosts did not show any hotfixes installed in AppCenter. 


  • Windows 2008 R2
  • Citrix XenApp 6.5 Hotfix Rollup Pack 1
  • PVS 6.1.16


  • Close AppCenter
  • Open command line on the affected hosts (in my case, our XML brokers)
  • Recreate the Local Host Cache by typing dsmaint recratelhc
  • Reopen AppCenter

Running dsmaint recratelhc performs three actions:

  • Sets the value of the registry key HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Citrix\IMA\ RUNTIME\PSRequired to 1.
  • Deletes the existing local host cache (Imalhc.mdb)
  • Creates an empty local host cache (Imalhc.mdb) for the IMA Service on a server to synchronize correctly with the data store (XenApp DB)

Refreshing the Local Host Cache

You can also force a manual refresh of a server’s local host cache by executing dsmaint refreshlhc from a command prompt. This action forces the local host cache to read all changes immediately from the farm’s data store. Refreshing the local host cache is useful, for example, if the Citrix Independent Management Architecture (IMA) Service is running, but published applications do not appear correctly when users browse for application sets.


XenApp 6.5 image – Citrix Receiver error 2320

While working on another XenApp 6.5 upgrade, I noticed users were getting “Error number 2320” while opening legacy XenApp 5 (4.5 really) applications.

In addition, I was seeing a MSI repair popup when they connected via the internal Citrix Web Interface site.



  • Windows 2008 R2
  • Citrix XenApp 6.5 FP1
  • PVS 6.1.16
  • Citrix Receiver 11.2 (Please read this article as to why I decided to go with 11.2 on the XenApp 6.5 image, vs Receiver 3.x)


It seems the issue was caused by removing the 3.x client and installing 11.2 as an incorrect settings remained in the registry.

Fix: (In my case, I created a Computer policy to import the regkeys below)

Error 2320:

Open the Windows registry editor by going to START/Run/regedit.
Navigate to the HK Local Machine registry key below and see if the registry key ClientHostedApps exists; remove it if it is present.

  • 64-Bit System (XenApp 6.5 image)

HKLM\SOFTWARE\Wow6432Node\Citrix\ICA Client\Engine\Lockdown Profiles\All Regions\Lockdown\Virtual Channels\Control

  • Navigate to the HK Current User registry key below and see if the registry key ClientHostedApps exists; remove it if present.

HKCU\SOFTWARE\Citrix\ICA Client\Engine\Lockdown Profiles\All Regions\Lockdown\Virtual Channels\Control

Re-installing client issue: 64-Bit System (XenApp 6.5 image)

  • Navigate to the HK Local Machine registry key below and create a REG_SZ key called ConnectionCenter


“ConnectionCenter”=”\”C:\\Program Files (x86)\\Citrix\\ICA Client\\concentr.exe\” /startup”



XenApp 6.5 STAID (ctxsta.conf) not updating when using PVS

Been working on yet another XenApp 6.5 upgrade.  I started noticing  issues with the ctxsta.conf file normally located under C:\Program Files (x86)\Citrix\system32\, where the unique STAID does not update when using Citrix Provisioning Services after the host is rebooted on a XenApp 6.5FP1 host.

This could result in issues with applications failing to open when launched via Access Gateway . Please note I only saw this behavior when using the affected servers as a STA on the Access Gateway (in my case AGEE on NetScaler)


  • Windows 2008 R2
  • Citrix XenApp 6.5 FP1
  • PVS 6.1.16
  • Citrix Receiver 13.4


Install this limited hotfix from Citrix (XA650R01W2K8R2X64094) which is now part of  Hotfix Rollup Pack 2 for Citrix XenApp 6.5 for Microsoft Windows Server 2008 R2

Once this the patch is applied, the and the STA will get configured correctly with your provisioned XenApp 6.5FP1 targets.

This issue does not seem to occur if you don’t utilize PVS


XenApp 6.5 – Remote Desktop display settings can’t be changed

Not sure how I missed this one during my last XenApp 6.5 implementation.

The option of “Make text and other items larger or smaller” while in a Windows 2008 RDS session is no longer available as it was in a Windows 2003 TS session. This option is now greyed out and displays “The display settings can’t be changed from a remote session”.


  • Windows 2008 R2
  • Citrix XenApp 6.5
  • PVS 6.1.16
  • Citrix Receiver 13.4


If you want this option available during a session, download a hotfix from Microsoft that will re-enable this setting.

Note The DPI setting enables you to change the size of all fonts and other UI elements on the computer. For example, you change the setting to increase the legibility of the UI.



Hide Client Drive mappings for ICA sessions

Client Drive mappings is a great feature of XenApp / XenDesktop, although this presents a security concern depending on the environment, it is sometimes necessary to allow local file access for your XenApp and/or XenDesktop as part of the work flow.

While assisting an old coworker at my last company, he was presented with the challenge of allowing client drive mappings, however only allow to show specific drive.


  • Windows 2003 SP3/Windows 2008 R2
  • Citrix XenApp 5.0 / 6.5
  • PVS 6.1.16
  • Citrix Receiver 13.x
  • Web Interface 5.4


Disable specific Client Drive Mappings from enumerating within an ICA session.



  • Log on to a client machine with Receiver 13.x installed, as a user with administrative rights.
  • For 64bit operating systems, navigate to registry path: HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Citrix\ICA Client\Engine\Configuration\Advanced\Modules\ClientDrive
  • For 32bit operating systems, navigate to registry path: HKEY_LOCAL_MACHINE\SOFTWARE\Citrix\ICA Client\Engine\Configuration\Advanced\Modules\ClientDrive
  • At the DisableDrives string value, add the value data as the Client Drive letter\s to be disabled. Do not add commas between drive letters while disabling multiple drives.



Web Interface Site

  • Navigate to C:\inetpub\wwwroot\Citrix\NAME OF SITE\conf.
  • Open default.ica with notepad.
  • Under the section [WFCLIENT] add DisableDrives=DriveLetter.
  • All ICA sessions launched from the corresponding Web Interface Browser Site has the specified Client Drive disabled.