Updated on 12 FEB 2019
VMware vRealize Operations for Horizon 6.6 | 20 SEP 2018
Check for additions and updates to these release notes.
What's in the Release NotesThe release notes cover the following topics:
- About VMware vRealize Operations for Horizon
- What's New
- Upgrading to Version 6.6
- Known Issues
VMware vRealize Operations for Horizon extends the functionality of VMware vRealize Operations Manager to monitor and manage VMware Horizon environments. vRealize Operations for Horizon collects data about your resources and presents that data in preconfigured dashboards for both real-time and predictive analysis.
- vRealize Operations Manager 6.7 and 7.0 support: You can now use vRealize Operations for Horizon with versions 6.7 and 7.0 of vRealize Operations Manager.
Important: vRealize Operations for Horizon 6.6 is only compatible with vRealize Operations Manager 7.0 with the security patch installed. See KB 59651 for more information.
- Horizon 7.6 support: vRealize Operations for Horizon now supports Horizon versions 7.3 to 7.6.
- App Volumes 2.14 support: vRealize Operations for Horizon now supports App Volumes 2.14.0 and 2.14.2.
vRealize Operations Manager for Horizon 6.6 requires the following VMware products:
- VMware Horizon 7.3 to 7.6 (requires Microsoft .NET Framework 4.6.2 or higher)
- VMware vRealize Operations Manager 6.7 or 7.0
vRealize Operations Manager for Horizon is also compatible with the following products:
- VMware App Volumes 2.14.x
- VMware Unified Access Gateway 3.2 and later
For the most current information about supported versions, see the VMware Product Interoperability Matrices.
This section contains notes about the upgrade process. For complete upgrade instructions, see Upgrading vRealize Operations for Horizon.
- Important: Microsoft .NET Framework 4.6.2 or later is required on the host where the broker agent is installed.
- Important: To ensure proper functionality, you must install the vRealize Operations for Horizon 6.6 desktop agent separately even if you chose to install it with Horizon 7.6.
- You can upgrade from vRealize Operations for Horizon 6.1 or later to vRealize Operations for Horizon 6.6. If you have vRealize Operations for Horizon 6.0 or earlier, you must first upgrade to vRealize Operations for Horizon 6.1 and then to vRealize Operations for Horizon 6.6.
- You must upgrade all vRealize Operations for Horizon agents in your environment to version 6.6. Environments containing older versions of vRealize Operations for Horizon are not supported with version 6.6.
- Dashboards, views, and reports from older versions are retained during the upgrade process. These legacy items are prefixed with the word View and can be removed safely.
- Due to an existing limitation, you must restart the vRealize Operations Manager cluster after the upgrade for the process to complete.
- Sessions that are active during the upgrade might not report data after the upgrade is complete. Restart the desktop agent for any active sessions that are not reporting.
- After you upgrade the broker agent, you must pair it with the Horizon Adapter instance again. All other broker agent configuration data is retained.
The vRealize Operations for Horizon user interface and documentation are available in English, French, German, Spanish, Japanese, Korean, Simplified Chinese, and Traditional Chinese.
vRealize Operations for Horizon has the following limitations.
- Physical desktops in a pool are not monitored.
Physical desktops included in a desktop pool are not monitored or shown in the user interface. However, physical RDS hosts are monitored and shown in the user interface.
- High availability (HA) failover can result in the Horizon Adapter not collecting data.
For more information, see KB 2092874: Best practices for configuring vRealize Operations for Horizon when HA is enabled.
- Environments containing older versions of vRealize Operations for Horizon are not supported with version 6.6.
To ensure that the product can operate normally, you must upgrade all vRealize Operations for Horizon agents in your environment to version 6.6.
- Using separate network cards for different subnetworks in vRealize Operations Manager is not supported. This can cause the Horizon Adapter instance to bind to an incorrect IP address.
- The adapter configuration files
/usr/lib/vmware-vcops/user/plugins/inbound/V4V_adapter3/work/msgserver.propertiesmust be updated at the same time.
- Existing adapter instance configuration files are not removed during the upgrade process. If the TLS configuration has been modified on the adapter side, the broker and desktop agent might fail to connect. Ensure that the adapter instance and agents use the same TLS configuration.
- For sizing and scaling guidelines, see KB 2098051: vRealize Operations for Horizon sizing guidelines.
- Computer-based AppStacks are not supported. Metrics can be displayed for user-assigned AppStacks only.
- The VM Metrics widget on the Horizon Help Desk dashboard cannot display information for a connected session.
When you select a session in the Horizon Connected Sessions widget, the VM Metrics widget does not display relevant information, and the topology in the Selected Session Related Objects widget is incorrect. This is because the vCenter Server configuration in Horizon Administrator is different from the configuration on the vCenter Adapter, which prevents the Horizon Adapter from resolving the FQDN of the vCenter Server successfully.
Workaround: Ensure that the vCenter Server configuration in Horizon Administrator is consistent with the configuration on the vCenter Adapter. Specify the vCenter Server by FQDN in both configurations or by IP address in both configurations.
- The broker agent configuration utility fails to open and displays an error.
When you attempt to open the broker agent configuration utility, a Microsoft .NET Framework error is displayed indicating that an "Unhandled exception has occurred in your application."
Workaround: Install Microsoft .NET Framework version 4.6.2 or higher on the host where you have installed the broker agent.
- The Blast protocol metric is not available on the Horizon RDS Pools dashboard.
Blast protocol data for RDS pools is not displayed.
Workaround: Create a super metric to calculate Blast data with the pool object.
- Unified Access Gateway appliances and sessions for different Horizon pods are displayed.
You can test and add Unified Access Gateway appliances that are configured for a different Horizon pod in your environment. Sessions launched through that Unified Access Gateway can also be seen in the dashboard for the current Horizon pod.
- Duplicate App Volumes Manager installations can be added in the broker agent.
In the vRealize Operations for Horizon broker agent configuration utility, you can add App Volumes Manager installations by IP address or by FQDN. It is possible to add an IP address and an FQDN that refer to the same App Volumes Manager installation.
Workaround: In the broker agent configuration utility, delete one of the references manually and restart the broker agent service.
- Deleted objects might be displayed in the Unified Access Gateway widget.
The Unified Access Gateway widget might continue to display objects that you deleted by using the broker agent.
Workaround: Stop the adapter instance and remove the affected objects from the inventory tree. Then start the adapter instance again.
- Pod names are not displayed in the Horizon Connected Sessions widget within the expected time of 15 minutes.
On the Horizon Help Desk dashboard, the Pod Name column in the Horizon Connected Sessions widget is not populated within 15 minutes even though data is displayed in all other columns.
Workaround: None. Pod names should be displayed within 60 minutes after session launch.
- The desktop agent does not operate properly on a machine with an account that has an AppStack assignment.
When you install the desktop agent on an account with an AppStack assignment in App Volumes, the agent might be installed on the mounted AppStack instead of local storage. In this case, after you restart the virtual machine or log in as another user, the agent will no longer operate properly.
Workaround: Do not install the desktop agent on an account that has an AppStack assignment. You can install it on the base template of the desktop machine or on another account.
- Horizon pods continue to appear on Horizon dashboards even after they are no longer monitored.
You choose to stop monitoring a Horizon pod, but information about that pod still appears on dashboards.
Workaround: Restart the service by running
service vmware-vcops --full-restart. Alternatively, in the vRealize Operations Manager user interface, manually delete the target Horizon pod resource and all Horizon Connection Server, security server, and pool resources related to it.
- Incorrect data is displayed for some entries in the Horizon Connected Sessions widget on the Horizon Help Desk dashboard.
Incorrect data might be displayed for reconnected sessions.
Workaround: Click the Edit icon on the widget and select All Active Sessions.
- After vRealize Operations for Horizon is upgraded, logon-related metrics for existing sessions are not retained.
The following metrics are affected:
- Logon time
- Average logon time
- Maximum logon time
- After the name of a Horizon Adapter instance is changed, related data cannot be displayed on the Horizon Adapter Self Health dashboard.
The Horizon Adapter collector resource does not automatically update to reflect changes to the name of the Horizon Adapter instance.
Workaround: Do not change the name of a Horizon Adapter instance after its creation. Revert any affected instances to their original names.
- Certain network alerts are not generated for user sessions that were established before the Horizon Adapter was configured.
The following alerts are not generated:
- PCoIP|Round Trip Latency (ms)
- PCoIP|Packet Loss Percent
Workaround: None. Alerts will be generated normally after the sessions are disconnected and re-established.
- User names that include multibyte characters might not be displayed correctly.
In the vRealize Operations Manager user interface, user names that include multibyte characters (such as Chinese) might not be displayed correctly.
Workaround: None. Avoid using such characters if possible.