Limited Availability: Troubleshooting Horizon Delegate

You can use Horizon Delegate log files and common checks to troubleshoot problems.

Log files

By default, Horizon Delegate stores log files on the remote desktop in the following location:

%TEMP%\omnissa-<username>\horizon-delegate-<sessionId>-<processId>.log

Log files rotate based on size. Each file can be up to 10 MB, and up to 10 files are kept. Older files are deleted.

Change the logging configuration

The default log level is 2 (info). Horizon Delegate reads the logging settings from the following registry keys, in this order: per-user policy, per-machine policy, and installation default.

• HKCU\SOFTWARE\Policies\Omnissa\Horizon\HorizonDelegate\Logging
• HKLM\SOFTWARE\Policies\Omnissa\Horizon\HorizonDelegate\Logging
• HKLM\SOFTWARE\Omnissa\Horizon\HorizonDelegate\Logging

Restart Horizon Delegate after you change a logging setting.

Common problems

• The Horizon Delegate panel does not appear in the Horizon Web Client - Verify that Horizon Delegate is enabled for the desktop pool and that the machines in the pool have Horizon Agent installed with the Horizon Delegate feature. Verify that the user is connecting with a supported Horizon Web Client. See System Requirements for Horizon Delegate. If the Enable Horizon Delegate setting does not appear in Horizon Console, Horizon Delegate is not enabled at the server level. Contact Omnissa to get the configuration details.
• An MCP server does not appear in the Connectors panel - Verify that the server is allowed by the Horizon Delegate group policy settings and by the GitHub Copilot allow and block lists. See Deploying Enterprise MCP Servers for Horizon Delegate.
• A local MCP server does not start - Verify that the runtime that the server needs, such as Node.js, is installed on the remote desktop.
• The screen capture or voice input action is not available - Verify the GrabScreenshotPolicy and AudioInputMethod settings. See Horizon Delegate Group Policy Settings.