The following caution applies to any workaround that suggests changing a registry entry.
Caution: Editing the registry incorrectly can cause serious problems that may 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.
The XenApp and XenDesktop 7.12 release contains the following issues:
- Personal vDisk inventory may fail to update after upgrading from version 7.11 to version 7.12. For more information about this issue, refer to the article Error: "The personal vDisk inventory failed to update" after Upgrading PVD in XA/XD from 7.11 to 7.12.
- In some cases, an AppDisk cannot successfully attach to a machine catalog. In such scenarios, the AppDisk appears in the Delivery Group pane, but does not actually attach itself to the machine catalog; the following message appears in the vSphere client:
Invalid configuration for device '0'
To resolve this issue:
- Apply the mountmgr.sys update. Refer to the Microsoft support site for more information.
- Change the registry setting for the timeout period. Increase the timeout from 30 (the default setting) to 90:
- On some systems, SCCM crashes when updating an image. This scenario occurs when updates are made to the base image, then applied, which results in failure of the SCCM client.
To resolve this issue, install the SCCM client instance in the base image first.
- After updating an image, some applications may fail to work properly due to an ability to verify previously installed licenses. For example, after an image upgrade, launching Microsoft Office may display an error message similar to:
“Microsoft Office Professional Plus 2010 cannot verify the license for this application. A repair attempt failed or was canceled by the user, the application will not shut down.”
To resolve this issue, uninstall Microsoft Office and install the new version on the base image.
- In some cases, downloading Metro apps from the Windows Store to a published virtual machine fails after an extraneous amount of time.
- An application installed on the AppDisk may fail to appear in the Windows Start menu after it is assigned to a Delivery Group and assigned a user's virtual machine.
- When using MCS (Create Catalog wizard) to create static desktops with user changes saved on a personal vDisk: On the Virtual Machines page, if you specify the number of VMs to create and then change the PvD drive letter from its default, the Summary page indicates only one machine will be added. If you proceed, only one VM is created.
Workarounds: Either (1) Create the catalog with one VM and then use the Add Machines action to create more VMs, or (2) On the Virtual Machines page in the wizard, change the PvD drive letter before specifying the number of VMs.
- During logon or logoff on a Windows 10 or Windows Server 2016 machine, the operation may pause and appear to be hung. Click in the session window to resume the operation.
- When using Local App Access with Windows 7 or Windows Server 2012R2 in a multimonitor environment, with desktops configured to launch in full-screen mode (by changing the default.ica file to "DesktopViewer -ForceFullScreenStartup=ON"), the VDA on some monitors may occupy only a partial screen. Some monitors might turn grey, and some might cntain only the CDViewer of the VDA. As a workaround if you have two monitors: Drag the VDA to one corner of the primary monitor until it maximizes and extends over both monitors.
- When Local Host Cache is enabled, users with desktop connections might be unable to reconnect to the desktop during an outage. If this occurs, restart the Citrix High Availability Service.
- After configuring the Site, if you install Studio and add it through the MMC as a snap-in on a remote machine, and then later attempt to remove that snap-in, the MMC might stop responding. As a workaround, restart the MMC.
- Published content will not start successfully when initiated from Citrix Receiver. Content launched through the StoreFront web client (or Web Interface) launches as expected.
Components available separately on the XenApp and XenDesktop download pages have the following known issues.
- Reinstallation of Administrator Logging by a user having securityadmin and dbcreator permissions on the SQL server might fail if Administrator Logging was previously installed by another user who has the same or higher SQL server permissions. Workaround: Reinstall Administrator Logging with a user who has sysadmin permission on the SQL server.
- The installation of the Session Recording Server components fails with error codes 2503 and 2502. Resolution: Check the access control list (ACL) of folder C:\windows\Temp to ensure the Local Users and Groups > Groups > Users has write permission for this folder. If not, manually add write permission.
- Because Session Recording does not support Framehawk display mode, sessions in Framehawk display mode cannot be recorded and played back correctly. Sessions recorded in that mode might not contain the sessions' activities.
- You cannot record the Windows 7 desktop sessions correctly when Legacy Graphics Mode is enabled by XenDesktop site policy and Disk-based Caching is enabled by Citrix Receiver for Windows policy. Those recordings show a black screen. Workaround: Disable Disk-based Caching by deploying with GPO to the machines on which you installed Citrix Receiver for Windows. For more information about disabling Disk-based Caching, see http://support.citrix.com/article/CTX123169 and http://docs.citrix.com/en-us/receiver/windows/4-4/ica-overview-receiver-config/ica-import-icaclient-template-v2.html.
- The rollover setting does not apply to VDI desktop sessions for XenDesktop 7.8, XenDesktop 7.9, and Session Recording Agent. In those cases, each recording file has a maximum size limit of 1GB and activities are not recorded after that limit is reached. The rollover setting DOES apply to XenDesktop 7.11.
- When Machine Creation Services (MCS) or Provisioning Services creates multiple VDAs with configured master image and Microsoft Message Queuing (MSMQ) installed, those VDAs might have the same QMId in certain conditions. This might cause various issues, such as:
- Sessions mighty not be recorded even if the recording agreement is accepted.
- The session logoff signal might not be received by the Session Recording server, which leads to the session always in Live status.
The workaround to create a unique QMId for each VDA differs depending on the deploy methods.
No extra actions are required if Desktop OS VDAs with the Session Recording agent installed will be created with PVS 7.7 or newer and MCS 7.9 or newer in static desktop mode; for example, configured to make all changes persistent with a separate Personal vDisk or local disk of the VDA.
For Server OS VDAs created by MCS or PVS or Desktop OS VDAs and configured to discard all changes when user logs off, use a script (GenRandomQMID.ps1) to modify the QMId at system startup. Modify power management strategy to ensure that enough VDAs are running before users' login attempts.
To use the script, do the following:
1. Make sure the execution policy is set to RemoteSigned or Unrestricted, in PowerShell.
2. Create a scheduled task and set the trigger as at system startup and run with SYSTEM account on the Provisioning Services or MCS master image machine.
3. Add the command as a startup task.
powershell .exe -file C:\GenRandomQMID.ps1
Summary of the GenRandomQMID.ps1:
- Remove the current QMId from the registry.
- Add SysPrep = 1 in HKLM\Software\Microsoft\MSMQ\Parameters.
- Stop related services, including CitrixSmAudAgent and MSMQ.
- To generate a random QMId, start services that stopped previously.
When you install XenApp or XenDesktop and the License Server on the same server and use an installation path containing Unicode characters, the License Server installation fails.
Workarounds - one of the following:
- Install on a path that doesn’t contain Unicode characters.
- Install the License Server on a remote system using a non-Unicode path. During the XenApp or XenDesktop installation point to that License Server.
For the Citrix Licensing 11.14 known issues and fixed issues, see the Citrix Licensing 11.14 known and fixed issues.