Monitoring and Troubleshooting in Horizon Console

You can use a variety of procedures for monitoring, diagnosing, and fixing problems that you might encounter when using Horizon 8. You can use Horizon Help Desk Tool for monitoring and troubleshooting, use other troubleshooting procedures to investigate and correct problems, or obtain assistance Technical Support.

For information about troubleshooting desktops and desktop pools, see the Desktops and Applications in Horizon 8 document.

Monitor Security Advisories in Horizon Console

Horizon Console displays security advisory notifications for supported Horizon 8 products deployed in your environment. These notifications help administrators identify security advisories that may affect their deployed product versions and access the relevant Omnissa security response information.

Connection Server periodically checks the Omnissa Connect (CXP) advisory endpoint using the product codes and versions of the deployed products. When applicable advisories are found, Horizon Console displays a notification banner and provides the advisory details for review.

This feature covers the following products:

• Unified Access Gateway (UAG)
• Horizon Agent
• Enterprise Connection Server

Prerequisites

Before using the security advisory feature, verify the following requirements.

Administrator privileges

You must sign in to Horizon Console with full administrator privileges to access the Security advisories page and view the advisory banner.

Network connectivity

The required components must be able to reach connect.omnissa.com to retrieve security advisory information. If your environment restricts outbound network access, configure the necessary firewall rules or allowlist entries.

Verify whether your deployment requires access from Connection Server, the browser running Horizon Console, or both.

Air-gapped environments

The feature requires access to the external advisory service. If the required connection is unavailable, Horizon Console cannot retrieve current advisory information through this feature. See Security Advisories in Air-Gapped Environments for more information.

How Security Advisory Polling Works

Connection Server checks the CXP advisory endpoint every four hours. Each request includes the product codes and versions of the deployed products so that the endpoint can return relevant security advisory information.

Polling runs automatically in the background. You do not need to initiate a check manually.

The CXP endpoint is an unauthenticated API that returns security advisory metadata. The request includes product codes and version information, rather than sensitive environment data.

After each check, Horizon Console displays the resulting advisory status. If the endpoint returns applicable advisories, the console displays a notification banner and the associated details. If no applicable advisories are returned, the console displays a status indicating that no advisories were found. If the check fails, the console displays an error status.

View Security Advisories in Horizon Console

Follow these steps to review security advisories.

1. Sign in to Horizon Console with full administrator privileges.
2. Check whether a security advisory banner appears.
3. If the banner appears, click it to open the Security Advisory section.
4. You can also navigate directly to the Security Advisory section in Horizon Console.
5. Review the advisory status and the available details.
6. Click the link associated with an advisory to open the corresponding Omnissa security response page.
7. Review the affected product versions and remediation guidance to determine the appropriate action for your environment.

Understand Security Advisory Statuses

Horizon Console displays one of the following states after an advisory check.

Review Advisory Details

When advisories are available, Horizon Console displays the information returned by the CXP endpoint. The available details include

• Product name: The product associated with the advisory.
• Version: The product version identified in the advisory.
• Severity: The severity assigned to the advisory.
• Published date: The date the advisory was published.
• Description: A summary of the security issue.
• CVE identifier: The associated Common Vulnerabilities and Exposures (CVE) identifier, if available.
• CVSS score: The Common Vulnerability Scoring System score, if available.
• OMSA identifier: The associated OMSA identifier, if available.

The information displayed may vary depending on the advisory.

To determine whether an advisory affects your environment, compare the affected product versions with the versions deployed in your environment. Then open the associated Omnissa security response page to review the impact and recommended remediation.

Note: Do not rely on the severity alone to determine whether a product is affected. Always review the affected versions and remediation instructions in the security response.

Security Advisories in Air-Gapped Environments

Horizon Console requires access to the CXP advisory endpoint to retrieve current security advisory information. If the required network connection is unavailable, the console cannot retrieve the latest advisories.

In this situation, Horizon Console may display a message indicating that the advisory server is unreachable. The advisory grid may also appear empty.

An empty grid in this state does not mean that no security advisories apply to your environment. It means that the advisory information could not be retrieved.

If you are working in an air-gapped environment, follow these steps:

1. Verify whether the environment is intentionally isolated from external networks.
2. If connectivity is expected, check the required network access and firewall rules for connect.omnissa.com.
3. Review any available error information to identify the cause of the connection failure.
4. If the environment must remain air-gapped, obtain the relevant Omnissa security response information through an approved system with external access.
5. Follow your organization's security procedures to assess the advisories and apply the recommended remediation.

After connectivity is restored, subsequent automatic checks can retrieve advisory information, subject to the polling schedule and endpoint availability.

Troubleshooting

Best Practices

• Review security advisories when they become available.
• Check whether the affected product versions match your deployment.
• Follow the remediation guidance in the linked Omnissa security response pages.
• Investigate failed advisory checks rather than assuming that no vulnerabilities exist.
• Establish a separate process for obtaining and reviewing security advisories in air-gapped environments.
• Continue following your organization's vulnerability management and patch management procedures.

Horizon Console helps administrators identify relevant security advisories for supported Horizon 8 products. Reviewing the advisory details and following the associated Omnissa security response guidance helps administrators determine the appropriate remediation for their environments.