Skip to main content

January 7, 2026

Troubleshoot Working with Horizon

Using the Environment Variable condition, Registry Key, or the Registry Value condition to check whether a specified Omnissa Horizon client property matches a criterion fails.

Problem

Using the Environment Variable, Registry Key, or Registry Value conditions to check whether a specified Horizon property matches a criterion fails.

Cause

Because Horizon starts after Dynamic Environment Manager, the Horizon registry information and environment variables are not created or set at the time that Dynamic Environment Manager checks for them, which causes the checks to fail.

Solution

Instead, use the Horizon Client Property condition. This is a special condition designed to allow Dynamic Environment Manager to check for the properties of the Horizon session. For information on configuring the Horizon Client Property condition, see Managing Conditions.

Was this page helpful?

Provide feedback for this topic

Was this topic helpful?

Please do not include any personal or confidential information.

Generating link…