Horizon DaaS 9.1.x | 13 OCT 2022

See Revision History below for additions and updates to these release notes.

Links to release notes for other versions: 8.0.0 | 8.0.1 | 9.0.x

What's in the Release Notes

The release notes cover the following topics:

Links to Other Resources
NEW - Horizon DaaS 9.1.4 - Released October 2022
Horizon DaaS 9.1.3 - Released August 2022
Horizon DaaS 9.1.2 - Released March 2022
Security Hotfixes - Released December 2021
Horizon DaaS 9.1.1 - Released September 2021
Software Versions Required for Upgrade
Note Regarding Appliance Restore After Upgrade
New Features
Best Practices
Supported GPU Cards
Known Limitations
Resolved Issues
Known Issues

Links to Other Resources

Product Documentation

All product documentation for Horizon DaaS is located on the VMware Horizon DaaS documentation landing page.

Note: The documentation linked from the Service Center and Administration Console interfaces is shared between the two products and is labelled with the Horizon Cloud Service product name. These documents, the Service Provider Administration and Tenant Administration guides respectively, are identical in content to the same documents that you access on the VMware Horizon DaaS documentation landing page.

Compatibility Information

For the most recent information about compatibility between this product and other VMware products, see the VMware Product Interoperability Matrices.

NEW - Horizon DaaS 9.1.4 - Released October 2022

Horizon DaaS 9.1.4 is now available on My VMware for download and manual install.

Horizon DaaS 9.1.4 includes fixes for the issues listed below.

Issue	Resolution
In Horizon DaaS 9.1.3 deployments, dbmonitor.log displays the error: *“Caused by: java.net.UnknownHostException: THIS_DB_IP”*.	For new Horizon DaaS 9.1.4 installations, this issue has been resolved. If you are upgrading from Horizon DaaS 9.1.3, you must first perform the remediation steps described in VMware Knowledge Base (KB) article 89737 before installing Horizon DaaS 9.1.4.

Horizon DaaS 9.1.3 - Released August 2022

Horizon DaaS 9.1.3 is now available on My VMware for download and manual install.

Horizon DaaS 9.1.3 includes fixes for the issues listed below.

Issue	Resolution
Spring Framework update	Spring Framework has been updated to 5.3.12+ and 5.2.18+
In Horizon DaaS 9.0.2, the launch console shows a black screen with loading indication.	This issue has been resolved so that the screen appears as expected. Note: If you are using vCenter 7.0 with ESXi 6.7 you must configure vCenter with the `config.mksdevproxy.enable` parameter for this fix to work.
Users were able to create a Virtual Machine even though no capacity was available.	This issue has been resolved so that this is no longer possible.
Users need support for additional GPU cards.	New GPU cards have been added to Supported GPU Cards section below.
The hot plug setting on an existing assignment would change from No to Yes unexpectedly after Blue/Green upgrade from Horizon DaaS 8.0.	This issue has been resolved so that the setting no longer changes after upgrade.
After upgrading to Horizon 20.2.0, users observed warning regarding PG auth on all three databases.	This issue has been resolved so that the warnings no longer occur.
Virtual Machine Name on User Activity Event was disappearing after a VDI was rebuilt.	This issue has been resolved so that the Virtual Machine Name continues to appear as expected.
"Technical Contact info" email address cannot be set to an address that contains two dots in the domain name.	This issue has been resolved so that the system accepts email addresses containing two dots.
Running apsetup.sh resulted in TLS v1.1 being enabled.	This issue has been resolved so that TLS v1.1 is no longer enabled when you run apsetup.sh.

Horizon DaaS 9.1.2 - Released March 2022

Horizon DaaS 9.1.2 is now available on My VMware for download and manual install.

This release includes the following new features.

Support for Four Client-Side Monitors
Horizon DaaS now supports up to four monitors with less than 4K resolution, or three 4K monitors. This functionality requires that Soft3D is not enabled.
2 Factor Authentication Using Unified Access Gateway
The system now supports RSA SecurID and Radius authentication for internal users via Unified Access Gateway (UAG). For information on setting up 2 Factor Authentication, see 2 Factor Authentication in Horizon DaaS 9.1.0 Tenant Administration.

Instant Clone Clean-up Tool

The Instant Clone Clean-Up Tool is included in the ngvcUtil.sh utility script and is used to clean up the remaining instant clone cp-\* VMs (cp-template, cp-replica, cp-parent) after a published image is unassigned on a datastore.

WARNING: Do not use the Instant Clone Clean-Up Tool when an image publish task (converting a VM to an image or creating a new image) is in progress.

To run the Instant Clone Clean-Up Tool:

Connect to the SP appliance using PuTTY.
Navigate to the script directory:
>/usr/local/desktone/scripts
Run the script:
>sudo ./ngvcUtil.sh

The system shows the following prompt:

What would you like to do? Enter M for ESX maintenance or U for unprotect Instant Clone internal VMs or C for Instant Clone internal VMs cleanup
Enter C.
When prompted, enter vCenter host name or IP address and vCenter User Name.
Available options appear: list, unprotect, delete, exit.

Note the following:
- For the list command, if no option is specified all internal VM groups are listed (same as using the -all option).
- The unprotect and delete commands are sub-commands that can only be used after executing the list command. If you attempt to execute either of these from the main menu (i.e. without first executing the list command), the system will show a warning that you cannot run that sub-command on all internal VM groups.
- For the unprotect command, if you want to unprotect all internal VMs specify the -all option.
- For the delete command, if you want to delete all the listed internal VMs specify the -all option.
  Note: If you execute the list -D command after all defective VMs have been deleted, no VMs are displayed.

Horizon DaaS 9.1.2 also contains a fix for the following issue.

Issue	Resolution
When adding custom applications or changing the default icon for an application, the icon does not display in HTML Access or App Blast Portal.	This issue has been resolved so that the user is able to see the custom icon of any size in HTML Access or App Blast Portal.

For known issues in Horizon DaaS 9.1.2, see Known Issues below.

Security Hotfixes - Released December 2021

Hotfixes to address a critical vulnerability in Apache Log4j identified by CVE-2021-44228 and CVE-2021-45046 are now available My VMware for download and manual install. Review VMSA-2021-0028 for more details.

Horizon DaaS 9.1.1 - Released September 2021

Horizon DaaS 9.1.1 is now available on My VMware for download and manual install. This release supports the use of VMware NSX-T™ Data Center.

Note: Use of NSX-T Data Center is supported for new Horizon DaaS 9.1.1 installations only.

Horizon DaaS 9.1.1 also contains fixes for the following issues.

Issue	Resolution
Horizon Version Manager (HVM) pre-upgrade checks should include 1-1 mapping of RM to host manager.	Added HVM pre-upgrade checks to include 1-1 mapping of RM to host manager.
Horizon Air Link (HAL) needs to accommodate NSX-T based greenfield installation.	Updates to improve networking processes.
Expanding compute resources in SP taking a long time to display vCenter information.	With this fix expanding compute resources in SP no longer takes an extended period of time.
Need to support equals (=) and hashcode (#) characters while comparing GM agent version composite code.	Added fixed to support equals and hashcode characters while comparing GM agent version composite code.
In the Administration Console, Inventory > Capacity lists all datastores in cluster and not just the tenant's configured datastores.	Added fix to list only the tenant's configured datastores.
No option to reboot the appliance after applying the hotfix in HVM.	Added option to reboot the appliance after applying the hotfix.
RM AppSvrStats wbemcli Heap usage rate is high in DaaS 9.0.1 environment.	Added fix to correct wbemcli heap usage rate.
Resync task failed because NGVC requestID was not created.	Changes implemented to eliminate this failure.
Swap is disabled on service provider and resource manager.	Made changes to enable swap on SP and RM.
Task Status was stuck as SubmittedtoElement when publishing an image.	Addressed the intermittent issue where the task_id was overwritten with a null value in quartz job.
Desktop Models hard drive value is restricted to 2 digits.	Removed UI restriction of 2 digits for Desktop Models hard drive value.
Need to add profile for nVidia Card RTX8000.	Added Profile for nVidia Card RTX8000 with profile name grid_rtx8000-2q.

Software Versions Required for Upgrade

Before upgrading to Horizon DaaS 9.1.0, confirm that the service provider and tenant appliances in your environment are running Horizon DaaS 9.0.0, 9.0.1, or 9.0.2. These are the versions required for upgrade.

Note Regarding Appliance Restore After Upgrade

Restoring Horizon DaaS platform appliances to previous versions after upgrading to the 21.1.0/9.1.0 release is supported.

To ensure that the platform setup can support anticipated/unexpected restores of any appliances of version 20.2.0/9.0.0/9.0.1/9.0.2, before performing the Restore you must copy the entire directory (/opt/vmware/horizon/link/transfer/20.2.0.4133.0) from the 20.2.0/9.0.0/9.0.1/9.0.2 Horizon Air Link appliance to the new 21.1.0/9.1.0 Horizon Air Link appliance at the same path (/opt/vmware/horizon/link/transfer/). This can be done at any point in time after installing the 21.1.0/9.1.0 Horizon Air Link appliance, including after upgrading the platform Management appliances (SPs and RMs).

New Features

Service Provider Administration

With this release, security enhancements have been made to harden the management appliances and Horizon DaaS platform services.
With this release, the Service Provider, Resource Manager, and Tenant Appliances will be upgraded to Ubuntu 18.04 LTS as part of the Blue/Green upgrade process.

Tenant Administration

Tenant Auto Agent Update (AAU) has been enhanced to upgrade persistent desktop assignments and golden images using different Horizon Agent Installer (HAI) versions, based on OS type and version.
Tenant Auto Agent Update (AAU) has undergone several enhancements for stability and functionality, including the ability to roll back the agent update for a desktop if that was enabled beforehand.
Support for VMware Instant Clone Smart Provisioning, where the provisioning mode (A or B) depends on environmental factors like pool size and image size. has been added. For more information, see https://techzone.vmware.com/?share=video2745.

Top of Page

Best Practices

Knowledge of the following facts is useful before using Horizon DaaS.

Agent Update for Assignment with 1 VM

If you are performing Agent Update for an assignment with only 1 VM, you must set Available VMs to Users to 0.

Moving VMs in vCenter

Moving appliance VMs to other folders in vCenter is not recommended because there are checks performed during resync and upgrades that fail if the appliance VM is not in the folder in which it was created.

Replacing Platform Files Before Upgrade

The platform files on the Customer Connect site are sometimes updated for bug fixes and improvements. When this happens, you should replace the files on HVM with the new ones so you can avoid known issues during upgrade.

Confirm that the files on HVM are the same as those on Customer Connect site by the comparing hash values on each file before upgrading Service Provider, Resource Manager, and Tenant.
If the hash value do not match download the new files from the Customer Connect site and put them into HVM.

Deploying Horizon DaaS at Scale

The following are best practices for building and scaling a Horizon DaaS production deployment:

Each Tenant Resource Manager (RM) supports a maximum of 18 tenants (with 12 tenants as the recommended maximum).
Each Tenant RM manages a single vCenter Server instance.
- The vCenter Server instance manages a maximum of 10,000 VMs, across multiple clusters.
When a tenant requires multiple Desktop Managers (the Tenant Appliance being also a Desktop Manager), each DM must be assigned to a separate vCenter cluster but can be assigned to the same vCenter. As such for large tenants with two DMs, they must be assigned to two separate vCenter clusters, but those can be managed by the same Tenant RM that is managing the vCenter Server instance for both clusters. Please do keep in mind the best practices for vCenter Server scalability (including recommendations when using VMware App Volumes for application lifecycle management).

Example: A Horizon DaaS production deployment with 60 tenants each needing only the Tenant Appliances, with a single capacity collection assigned to the Tenant, and each Tenant running fewer than 2,000 VMs.

For this environment the recommended setup would be:

Datacenter Service Provider appliances pair.
- The Service Provider connects to a vCenter Server for the management appliances.
- Although this vCenter is only for the platform management function, it doesn't need to be dedicated to that task and can be used for other management functions.
- The Service Provider does not connect directly to vCenter but uses the HAL appliance for the any operations towards vCenter.
Five Tenant RMs, each managing 12 tenants.
To support the tenant desktop workloads, five (5) vCenter Servers with clusters, and the number of clusters depending on whether dedicated or partitioned clusters are used.
- Recommended maximum of 10,000 VMs per vCenter Server.
- Each Tenant Appliance or Desktop Manager manages a maximum of 2,000 desktops or sessions.
- For large tenants, it is recommended to dedicate the vCenter Server cluster.
60 Tenant Appliance pairs (and most likely 60 Unified Access Gateway pairs as well).
If some of those tenants need another DM, then those DMs can be assigned to an existing Tenant RM, but not to the vCenter cluster that is assigned to the Tenant Appliance of the same tenant.
- Keep in mind the recommended maximum of 12 tenants supported per Tenant RM.

Compatibility with other VMware Products

For the most recent information about compatibility between this product and other VMware products, see the VMware Product Interoperability Matrices.

Browser Experience

The Administration Console is compatible with recent versions of Google Chrome, Mozilla Firefox, Microsoft Internet Explorer, and Microsoft Edge. Even though you can try using Apple Safari, use of the Administration Console in Apple Safari is not supported in this release.

Creating a Template Desktop VM

When you are creating a template VM, after you have finished configuring it run the following command in Windows PowerShell:

Get-AppxPackage|Remove-AppxPackage

This prevents a possible sysprep issue that leads to image publish failure.

Refreshing Desktop Capacity Information on Tenant Quotas Tab

When editing a tenant, if the Desktop Capacity information on the Quotas tab is not correct, then refresh the page to correct this. In particular, the In Use value for Std Capacity may sometimes display incorrectly and need to be refreshed.

Supported GPU Cards

This new section of the release notes lists the GPU cards supported by Horizon DaaS. The list will be updated as new cards are verified.

Note: If you want to use a card that is not currently listed, create a ticket with VMware Global Support Services.

Device

NVIDIAGRID K1

NVIDIATesla M60

NVIDIATesla M10

NVIDIATesla M6

NVIDIATesla P100C

NVIDIATesla P100

NVIDIATesla P100X

NVIDIATesla P40

NVIDIATesla P6

NVIDIATesla P4

NVIDIATesla T4

NVIDIATesla V100X

NVIDIATesla V100DX

NVIDIATesla V100

NVIDIATesla V100S

NVIDIATesla V100L

NVIDIATesla V100-PCIE-32GB

NVIDIAQuadro RTX 8000

NVIDIA A16

NVIDIA A40

NVIDIA RTX A2

NVIDIA RTX A10

NVIDIA RTX A6000

NVIDIA Quadro RTX 6000

NVIDIA Quadro RTX 8000

Known Limitations

Customer Appliance Configuration Changes Do Not Persist After Upgrade

After you upgrade your environment, custom configuration settings that you made (for example, modifying disk timeout) do not persist and need to be re-applied manually when the upgrade is complete.

User Activity License Report - Data Does Not Persist After Upgrade

After you upgrade your environment, data for User Activity License Reports (formerly known as Concurrent Users License Reports) run before the upgrade is no longer available. To avoid this issue, it is recommended that you save any data you want to keep before performing the upgrade.

Horizon Version Manager - Connection to vCenter Server Using FQDN

If your Active Directory and DNS Server are running on the same machine, you may find that Horizon Version Manager cannot reach the vCenter Server by its Fully-Qualified Domain Name (FQDN) while still being able to connect using its IP address. The workaround for this is to add host entries to the /etc/hosts file for the FQDN. For example: vc1dc1.newdaas.local xx.xxx.xx.xx

After Failed Deployment - Manual Clean-Up Required

For security reasons, after a failed Horizon DaaS deployment you are required to perform a manual clean-up of the primary service provider appliance (SP1). During deployment, Horizon Air Link establishes temporary SSH trust between the installing node and SP1 by copying the node's SSH public key to the SP authorized keys list. In a successful deployment these keys are removed automatically after the deployment is complete. But when there is an unexpected deployment failure, you need to remove these keys manually.

Migrating Between Clusters in Multi-DM Environment

In a multi-DM environment with two clusters assigned to different (but linked) vCenters, if you migrate a VM from one cluster to the other, the migrated VM is marked as deleted in the tenant FDB and is not available for use. The workaround for this is to wait for the system to perform a full inventory update. This can take up to 12 hours. [2187188]

Connecting to Administration Console Using Mozilla Firefox

Attempting to connect to the Administration Console via Mozilla Firefox can fail with a connection timeout due to a bug in Firefox. The workaround for this is to change the name of certificate file, which is located in the C:\Users\‹username›\AppData\Roaming\Mozilla\Firefox\Profiles\‹filename›.default directory and has a name similar to cert1.db, and then restart the browser.
Attempting to connect to the Administration Console via Mozilla Firefox fails when you are using a self-signed certificate (normally in a development environment). You can avoid this issue by using another browser.

DNS Server IP Edits for Domain Join Require Support Ticket

When editing an existing Active Directory Domain, you can no longer directly edit DNS Server IPs in the Administration Console. To change DNS Server IPs, file a ticket with VMware support.

Default Limit of 2,000 Desktops Per Pod

There is now a default limit of 2,000 VMs per pod, both in desktop assignments and in farms. This includes VMs created in earlier versions of the product but does not include Utility or Imported desktops. When you are creating or editing an assignment or farm and the remaining capacity displayed appears to be too low, it may be because this limit has been reached. The default limit of 2,000 can be adjusted on request. For more information, contact your VMware representative.
Note to Service Providers: When registering or editing a tenant, you can change this setting by modifying the value in the new Max Desktop Count Per DM field on the General tab.

Agent Upgrade to HAI 18.4 Requires Use of BAT File

When you upgrade from an older agent build to the HAI 18.4 using the HAI user interface, the installer creates the HAI-upgrade.bat file and then interrupts the upgrade, prompting you to close the user interface and complete the upgrade using the BAT file.

When the upgrade is complete, the VM will be rebooted automatically. You can prevent this reboot by doing either of the following:

Update the command-line options in the HAI user interface before the BAT file is generated, adding /norestart at the end of the command.
Manually update the generated HAI-upgrade.bat file, adding /norestart at the end of the command.

Note: The VM must be rebooted sometime after the upgrade in order for the Agent to be usable.

Updating Images Using Console Access

Performing updates to images (such as updating agents) using console access without taking the image offline and then accessing it via the Helpdesk Console (beta feature) is not supported and can cause issues with the image and subsequent pools spun up using this image. Do not attempt to perform image updates this way. Always duplicate the image from the Admin Console and then update it using the HACA Console.

Copying and Pasting Between Client System and VM With HTML Access

Copying and pasting text between a client system and a VM is supported by default when the user is connected via the Horizon Client. When the user is connected via HTML Access, however, you must configure this feature before the customer can use it. For more information, see the VMware Horizon HTML Access documentation.

Users Still Able to Log into Dedicated Desktops After Being removed From User Group

If a user is in an Active Directory group that is assigned to a dedicated desktop assignment, once the user has logged into a particular desktop they will be able to continue logging into that same desktop until the user is unassigned from that desktop in the Administration Console, unless either the user is removed entirely from the Active Directory or the desktop is deleted.

Wait Time for Generating Admin Activity Report

When you initiate an export on the Admins tab of the Activity page (Monitor > Activity > Admins), there is an interval of time as the system generates the report, during which you are not able to perform other tasks in the Administration Console. Depending on the number of records, this interval can be several minutes long. For the maximum report size (50,000 records), the wait time is approximately 10 minutes.

Data Sorting in Exported User Activity Report

When you export data from the Users tab of the Activity page (Monitor > Activity > Users), the data in the generated .csv file is not sorted by date. There are two options for correcting this:

Open the .csv file in Excel and set the date format for the cells containing dates to mm/dd/yy hh:mm AM/PM (e.g. 3/14/12 1:30 PM).
Create a new blank Excel workbook and then use the data import wizard to import the .csv file.

Converting a Desktop to an Image

If you initiate converting a desktop to an image but cancel before the task finishes, a second attempt to convert the desktop to an image may fail. To avoid this issue, you should power off the desktop and power it on again before attempting to convert it to an image a second time.

Time Interval Before Changes to Settings Take Effect

When you change one of the following settings, it can take up to 5 minutes for the change to take effect.

General Settings page (Settings > General):
- Session Timeout - Client Heartbeat Interval, Client Broker Session, Client Idle User
- HTML Access - Cleanup credentials when tab is closed
- Pool/Farm Options - Enable Client Retry
Identity Management page (Settings > Identity Management):
- Select item and click Configure - Force Remote Users to Identity Manager

Service Provider Information

When you change one of the following tenant policies, it can take up to 5 minutes for the change to take effect.

desktop.connection.corrective.action.required
desktop.connection.retry.count
client.retry.enabled
element.session.logontiming.enabled
jms.agent.allow.mmr
jms.agent.allow.usb

Resolved Issues

The following issues have been resolved in Horizon DaaS 9.1.0. For issues resolved in minor releases (Horizon DaaS 9.1.1, etc.), see the relevant sections above.

When the Active Directory group assigned the Super Administrator role was moved to another OU within Active Directory, Admin users in that group were able to login to the Administration Console but were not able to make changes. This issue has been remedied so that users can make changes as expected. [2554690]
When you removed a configured admin group from Active Directory directly before removing the group in the Administration Console, this caused two issues on the Settings > Roles & Permissions page:
- The deleted group was listed as \unknown\XXXX.
- If you added a new admin group to the existing list, an error occurred and the group details were not saved.
This Active Directory problem has been resolved, so that these issues no longer occur. [2543068]

Known Issues

Service Provider Issues

Issues that are new in this release are in bold.

After deploying Horizon DaaS 9.1.3, dbmonitor.log displays the error: “Caused by: java.net.UnknownHostException: THIS_DB_IP”.

Workaround: Perform the remediation steps described in KB article 89737.
When using a vCenter instance supporting multiple tenants, the recommended maximum number of tenants is 12, and the maximum supported is 18. To support more tenants, you must add another Tenant Resource Manager and add another vCenter instance.

Workaround: None. This capacity will be expanded in future releases.
After upgrade, settings for Unified Access Gateway (UAG) can be lost, preventing users from accessing desktops.

Workaround: Run the apsetup script on each tenant appliance:

sudo /usr/local/desktone/scripts/apsetup.sh

[2551708/2550694]
If you change the name of a tenant in Service Center, the name is not changed in vCenter and upgrading that tenant fails.

Workaround: Change the tenant name in vCenter and retry the upgrade.

[2516006/2502672]
During upgrade, the tenant migration can fail with the following error:

Failed to connect virtual device Ethernet0

Workaround: Follow the instructions in Knowledge Base article 2093588.

[2409011]
If you attempt a rollback to the previous version, you might see a HAL error saying "java.rmi.RemoteException: VI SDK invoke exception:javax.net.ssl.SSLHandshakeException: Remote host closed connection during handshake". This can occur when the size of the /opt/vmware/horizon/link/conf/settings.json configuration file is too large.

Workaround: Clean up any failed/completed jobs along with any unnecessary manifest versions.
If you attempt a rollback to the previous version, you might see a HAL error saying "Given final block not properly padded.javax.crypto.BadPaddingException: Given final block not properly padded". This can occur because of a bug in the Java encryption/decryption module.

Workaround: Remove the jobs manually from the JSON file.

Tenant Administration Issues

Issues that are new in this release are in bold.

The known issues are grouped as follows:

Active Directory
Images, Farms, Assignments
Reports
User Interface
App Volumes
Localization

Active Directory - Known Issues

It takes up to 15 minutes for the Administration Console to reflect a lockout or unlocked state of the primary bind domain account.
The system's connection object to Active Directory is cached for 15 minutes. As a result, it might take 15 minutes from the time point when the primary bind account goes to locked state and the system raises the notification to the administrator. Conversely, after the administrator clears the locked-out condition of the account, it might take up to 15 minutes for the system to stop notifying about the now-cleared account.

Workaround: None. [2009434]
Reusing the same farm name with a different domain in the same Active Directory forest can lead to domain join failures due to duplicate service provider names (SPNs). Due to a new feature for domain controllers in Microsoft Windows Server 2012 R2 and higher, a duplicate SPN check on the domain controller causes domain join failures. See the Microsoft KB article 3070083.

Workarounds:
- Avoid reusing farm names.
- As described in that Microsoft KB article, deactivate duplicate SPN checks in the Active Directory domain.
[1969172]

Images, Farms, Assignments - Known Issues

After upgrading vCenter Server to version 6.7 or 7.0, instant clone deployment fails with the following error in the Activity log of the Administration Console: "SERVER_FAULT_FATAL - Runtime error: No full links for internal VMs found."

For more information, see the following KB: https://kb.vmware.com/s/article/89679.
[3063545]
In Floating Traditional Clone assignments, auto-login to the VDI machines is failing post-customization. This is happening because the clean up script is not being run after the customization of the VDI machine. [2821801]
In large deployments, it is possible for a small number of VMs in a floating desktop assignment to go into an Unknown state because some Windows Services, like the Blast Service on the agent, do not start and the agent heartbeat reports AGENT_ERR_PROTOCOL. In this case, hovering over the Agent Status value for the VM displays a tool tip indicating an agent error.

Workaround: Restart the VM from the Assignment page or log into the VM via RDP and restart the VMware Blast service from Windows Services. [2406279]
When you attempt to update the agent on an image, the convert-to-image task may fail on the cloned VM.

Workaround: Delete the clone VM (not the original image) and retry. The clone VM will appear in Utility VMs. If the retry is unsuccessful, save the clone VM, perform the steps below to get the DCT logs, and then contact your VMware representative.
1. On the clone VM, browse to C:\Program Files\VMware\VMware View\Agent\DCT and open the file 'support.bat'.
  A cmd prompt window opens and prints several messages stating which logs are currently being gathered. This process may take a few minutes to complete.
2. When prompted to collect dump files enter 'n' unless VMware has requested that you gather dump files.
  A zip file is placed on the desktop containing collected logs.
For more information on obtaining logs, see the following KB: https://kb.vmware.com/s/article/1017939.

[2202387]
When you use the Update Agent feature from an agent version earlier than 18.2.2, the update process can hang on desktops that have a 'run once' pending.

Workaround: Perform the agent update, adding the following command line argument on the Command Line tab of the Agent Update wizard:
VDM_SUPPRESS_RUNONCE_CHECK=1

[2191312]
When you have two dedicated desktop assignments associated with the same group of users, the following issue can occur. If a user opens a desktop from one of the assignments using the Horizon Client and then a user attempts to open a desktop from the other assignment with the Horizon Client, the second attempt fails with an error indicating the user is not entitled to the desktop.

Workaround: Open the desktop in the second assignment using the browser instead of Horizon Client. [2201599/1813881]
When you push updates for a traditional clone assignment, a small number of VMs may enter a PXE boot error state. For example:
- PXE-E53 : No boot filename received
- PXE-MOF: Operating System not Found.
Workaround: This is a NetApp issue, so there is no workaround in Horizon DaaS. [1969642]
When a user is entitled to a dedicated desktop assignment, that assignment appears under Assignments in the user detail information shown when you click on the user's name in the Administration console. However, after the user launches a desktop from the assignment, it no longer appears in the user detail information.

Workaround: None. [1958046]
Shrinking an Instant Clone assignment can sometimes fail to delete one of the VMs, which then goes to a powered off state.

Workaround: Power on the VM. When it is powered on and visible in the assignment, shrink the assignment again. [2027097]
If you attempt to create a farm using a Windows Server 2016 image, the VMs may hang at the customization stage.

Workaround: Deactivate the tiledatamodelsvc service on the Windows Server 2016 image and then create the farm. [2010914]

Reports - Known Issues

When CPU usage on a desktop is very high--for example, when an application is using 100%--the Desktop Health alert notification does not display on the Desktop Health tab of the Reports page.

Workaround: None. [2015486]
When IPv6 is enabled on an image, the abnormal IP notification may not display on the Desktop Health tab of the Reports page.

Workaround: Deactivate IPv6 for the image. [2017500]

User Interface - Known Issues

New created or cloned VM is not listed in Imported VMs due to duplicate key value violating the unique constraint "t_general_machine_mac_address_key".

Workaround : None. This issue will be resolved in future releases.

[2887657]
The administration console is slow when you attempt to display the Desktops tab for a specific assignment. [2820840]
The memory usage percentages reported for desktop health reports and used for the desktop health alerts are based on percentage of committed memory, which equals physical memory plus pagefile size, and not on percentage of only physical memory.
Committed memory for a desktop VM is calculated as physical memory plus pagefile size. When calculating the percentage of memory usage in a desktop, the system takes the percentage used of that total (physical memory plus pagefile size). Both the desktop health alerts and the memory usage report in the desktop health reports use that percentage calculation. However, when you log into a desktop VM and open the Windows Task Manager to view the memory usage in the desktop's Windows operating system, the Windows Task Manager displays percentage based on physical memory only. As a result, the memory usage percentage that the desktop's Windows Task Manager displays does not match the memory usage percentage displayed in the Desktop Health reports or in the desktop health alert.

Workaround: Keep in mind this difference if you decide to make a comparison between the memory usage percentage reported by a desktop's Windows Task Manager and the memory usage percentage reported in the Administration Console's Desktop Health report and desktop health alerts for that desktop. [2015772]
Some pages in the Administration Console do not display correctly in the Safari browser.

Workaround: Use a different browser to access the Administration Console. [1956356/1956348 ]

App Volumes - Known Issues [these are in SP Release Notes only]

After the App Volumes agent is installed on an image VM, the App Volumes agent is not able to communicate with the App Volumes Manager until the DaaS agent pairing process is completed. The following error message is displayed: "Connection Error, Unable to contact App Volumes Manager. Virtualization is disabled".

Workaround:
1. Prior to installing App Volumes agent, ensure that the DaaS agent pairing process is completed.
2. If DaaS Agent pairing occurs after the App Volumes agent is installed, ignore the connection error and click OK. If the DaaS agent is paired later, the connection is set up automatically.
[2036603]

Localization - Known Issues

When non-ASCII or high-ASCII characters are used in the True SSO template name, retrieving the template fails and True SSO cannot be configured successfully.

Workaround: Use only ASCII characters in the names of your True SSO templates. [1957829]
Some text on the Desktop Health tab of the Reports page is not being localized.

Workaround: None [2019363]

Revision History

Date	Description
07 JAN 2021	Initial release
23 MAR 2021	Added Required Versions - 2733701
23 Sept 2021	Added 9.1.1
08 DEC 2021	Added best practice - Replacing Platform Files Before Upgrade - 2886062
30 MAR 2022	Added 9.1.2
29 JUN 2022	Known Issue 2887657