This section provides details of the known issues in Horizon Management Pack.

Date format for Horizon Availability → Connection Servers → certificate expiry coulmns in VMware Horizon versions 8.7 and 8.8 are not consistent.

The API Response for VMware Horizon versions 8.7 and 8.8 have a different date format and this causes date format inconsistencies in the UI.

Horizon adapter collection might stop if configured Horizon Server undergoes upgradation.

Impacted versions:
  • Horizon Server 7.13 upgraded to Horizon Server 7.13.1 or 7.13.2
  • Horizon Server 7.13 upgraded to any Horizon Servers 8.x
  • Horizon Servers 8.x upgraded to Horizon Servers 8.3 or higher
  • Horizon Server 8.3 upgraded to Horizon Servers 8.7 or higher

Workaround

Restart the Horizon adapter to continue collection.

VDI Pools capacity widget of the Horizon Day to Day Operations dashboard show incorrect data, pointing to session remaining.

Workaround

This widget can be edited to select VDI Pool / Capacity list instead of Capacity / RDS Farm distribution.

Number of sessions at Horizon Connection Server level shows incorrect value.

Issue originated from Horizon.

Logon Duration is shown negative.

The issue is originating from Horizon.

Helpdesk API fails to fetch the protocol metrics for sessions.

The issue is originating from Horizon.

Logon metrics will be missing post upgrade of management pack for Connected Sessions.

Events are not retriggered for connected sessions hence logon metrics goes missing. The metrics are displayed once the session is reconnected. New sessions will not have any issues in fetching the logon segments.

Note: This issue is valid only for the VMware Horizon versions 7.13.1 and 7.13.

Logon Metrics is missing if there is time sync issue in Event DB, Horizon Desktop & Connection Servers.

To check whether there is time sync issue or not, follow these steps:
  1. On the Connection Server, Navigate to Monitor > Session.
  2. Identify the user who is logging off.
  3. Go to Events tab and note down the Updated timestamp in the right corner of the table.
  4. Log off the same user session, note down the time stamp from the Time column of the table with Agent Module & Message User xxx has disconnected from machine yyy.

    If the timestamps are not matching then there is time sync issue between Event DB, Horizon Desktop & Connection Servers

    Workaround: Fix the time sync issue to resolve the missing logon metrics.

Data Missing in RDS Performance Dashboard.

To populate the data for the RDS Performance Dashboard, follow the steps given below:
  1. Click Edit Widget in Profile Performance widget.
  2. Under configuration, select Box columns value as 4 (from 2).
  3. Under Output Data, select the existing two metrics and click Remove selected metrics.
  4. Click Add New Metrics and search for Horizon RDS Desktop Session and select it.
  5. Select the metrics Session|Time taken to load Profile and Session|Time taken to Logon and click OK.
  6. Repeat 4 and 5 steps for Horizon RDS Application Session.
  7. Click SAVE.

Performance KPI metrics are not populated.

Performance KPI metrics are not populated in the Horizon Management Pack if::
  • The underlying vCenter infrastructure is hosted on AVS or GCVE
  • The ESXi version is less than 6.7u1
  • The VMware tool version is less than 10.3.5
  • The metrics are not enabled in the default policy of the vCenter adapter
Workaround:

Use VM Tools 10.3.0 on ESXi 6.7u1 and later.

Duplicated Objects and Relations found in the Traversal spec when a vCenter is mapped to 2 different Horizon Pods.

If a vCenter server is shared across multiple Horizon Pods:
  • The adapter does not support the configuration
  • The computed metrics are wrongly calculated due to shared relations
  • Related Objects are duplicated under both pods
  • Traversal spec duplicates child objects under both pods

Some of the sessions are having start time as NULL causing the incorrect number of sessions/users.

The issue is originating from Horizon.