Limited Availability
Horizon 8 offers Horizon Delegate with limited availability.
Horizon Delegate is now production-ready and available through a Limited Availability (LA) program for Horizon 8.
To request access to the Limited Availability program, contact horizon-delegate-request@omnissa.com, Omnissa sales representative, or Omnissa partner.
Horizon Delegate releases resources when they are not in use, without losing conversations or interrupting work in progress. Conversation history is kept until the user deletes the conversation.
- Horizon Delegate starts when the user logs in to the remote desktop, but it stays dormant until the user opens the Horizon Delegate panel.
- After the user disconnects, Horizon Delegate waits for an idle period before it releases its resources. If the user reconnects within that period, the session continues. While a request is still running, including a request that is waiting for an approval, Horizon Delegate keeps its resources.
- After a conversation is idle for a period, Horizon Delegate releases the resources for that conversation and keeps the conversation history. The next request in the conversation resumes it.
- If a request makes no progress for a period, Horizon Delegate stops it. Time that the user spends deciding on an approval request does not count toward this period.
You can change these periods with the following group policy settings. For the full policy reference, see Horizon Delegate Group Policy Settings.
| Group Policy Setting | Default | Description |
|---|---|---|
| Idle runtime keep-alive (milliseconds) | 300000 (5 minutes) | How long Horizon Delegate keeps its resources ready after the user disconnects and any running request finishes. When this time expires, Horizon Delegate stops its background processes and returns CPU and memory to the remote desktop. |
| Enable runtime session management | Enabled | Keeps an idle conversation ready for reuse and releases it after the keep-alive time. |
| Runtime session keep-alive after turn (milliseconds) | 900000 (15 minutes) | How long an idle conversation and its MCP processes stay ready after the last request finishes. A follow-up request within this time responds faster. |
| Turn inactivity timeout (milliseconds) | 600000 (10 minutes) | The longest time a request can run without making progress before Horizon Delegate stops it. Any progress resets this time. |
| Turn abort grace period (milliseconds) | 15000 (15 seconds) | After a request is stopped, how long Horizon Delegate waits for it to end cleanly before it forces the request to end. |
Was this page helpful?