ControlUp v9.2.5.776 REST API Bug Affects Horizon 2406 and 2412 Integration; Workaround and Fix Pending

In ControlUp version 9.2.5.776, a significant issue was identified impacting Omnissa Horizon environments running versions 2412 and 2406. This release introduced a bug affecting the REST API integration used by these Horizon versions, causing disruptions in built-in SYNC functionality and monitoring, including problems with the new Unified Access Gateway (UAG) agentless monitor. The root cause lies in the incompatibility or improper support of REST API versions 3 and 4 by this ControlUp release. Horizon environments 2503 and above, which utilize REST API version 5, were not affected and continued to function correctly.

As a temporary workaround, users in affected Horizon 2412 and 2406 environments can revert their Collectors to use the older SOAP-based method by setting a new registry entry (Use Soap = 1). This older SOAP method, while more resource-intensive and anticipated to be phased out eventually, restores functionality until the bug is fixed. ControlUp has clarified that this is a bug rather than a planned deprecation of REST API support for these Horizon versions, and a fix is actively being developed and will be released promptly.

The issue was initially not reflected in the release notes or documentation, which generally specify Horizon version requirements starting at 2406 or higher for Omnissa Horizon integration. Users should be aware that Omnissa Horizon 8.2412 remains supported until January 28, 2028, underlining the importance of maintaining compatibility. ControlUp’s development team is replicating the problem using different 2412 builds to understand the issue fully, noting that the bug seems reproducible with specific builds like 8.14.0 (build 14371628935).

Caution is encouraged for organizations running Horizon 2412 or 2406 environments on this ControlUp version to avoid unanticipated monitoring data loss, as was experienced in some community reports with prolonged missing metrics. ControlUp’s documentation team is preparing to add this issue as a known bug in the current release notes to inform users more effectively until a correction is deployed. For the most accurate and updated guidance, users should consult ControlUp’s official resources at https://docs.controlup.com and seek support if needed.

Read the entire ‘ControlUp v9.2.5.776 REST API Bug Affects Horizon 2406 and 2412 Integration; Workaround and Fix Pending’ thread below:

Warning for Omnissa Horizon Customers:

I recently upgraded to v9.2.5.776, and it completely broke the built-in SYNC for our Horizon 2412 environment.
ControlUP v9.2.5.776 ~drops support~ has a BUG for REST API version 3 and 4. These versions 3 & 4 REST API are used in Horizon 2412 and under.
Horizon 2503 and above use REST API version 5, which works fine. (_same issue with the new UAG agentless monitor_)
The workaround is to downgrade your Collectors to use the older SOAP method, which uses wore resources and will (i assume) eventually be dropped from support. This is switched via a new registry entry – (Use Soap =1).

There is nothing in the Release Notes about version requirements. VDI (Real-Time DX): support.controlup.com/docs/real-time-dx-versions-1
There is a mention of Horizon limitations here, but it states Horizon 2406 or higher.: Set Up Omnissa Horizon Integration. support.controlup.com/docs/add-horizon-integration

Hopefully this post will help anyone running “older”, but still supported versions of Horizon.
Omnissa Horizon 8.2412’s End of Support (EOS) is scheduled for January 28, 2028.

partially correct, for 2406 and 2412 the dev team overlooked that the uag integration wasn’t going to work with rest because they use a too new api call for it. We fixed this in this version but for reasons we are now looking at this also broke other parts in the integration. The horizon api versions are not v4 for horizon x and v5 for horizon y. These versions are updated if Omnissa has to change something in the api endpoint.

We are not dropping rest support for horizon 2406 or 2412 this is clearly a bug that we currently are looking at

anything to add?

Thank you Wouter, I’ve edited my comments above so I do not mislead anyone. Hopefully the older REST APIs are added back in the next release.

thank you! fyi: usually we test with the 2 latest current releases and 2 latest ESB’s but for this I am currently building a small 2412 environment to see what is happening. We tried to reproduce by forcing the older api call with a newer horizon version but that worked as well.

to be clear with the current version I have no problems talking to 2503 or newer and the bug only seems to apply for 2406 and 2412

nothing to add here, couldn’t have said it better

just so it’s absolutely clear. We’re not planning on dropping support on this. I’ll ensure this gets fixed and back out there in a new release asap.

Got it. I appreciate the clarity and transparency that this ControlUP Community provides. It it very helpful for sure. But I at least wanted to throw out a warning for others in the community so that they do not have 6 hours of missing metrics like I do. It’s a pretty serious bug, and I’m sure it will generate a few more support tickets.

Makes sense, I appreciate it! I’ve already asked our documentation team to add a known issue for this release.

for my info: can you share the exact 2412 build you are on? I know they had several issues with the first one and published 2412.1 pretty quickly after it

(we had that recently in a demo environment that was on the first 2412 and it just stopped being able to create desktop pools…..)

8.14.0 build – 14371628935
version 2412

interesting, thats not the version that we can currently download but I have at least 2412 and setting it up right now. Will continue reproducing tomorrow

Continue reading and comment on the thread ‘ControlUp v9.2.5.776 REST API Bug Affects Horizon 2406 and 2412 Integration; Workaround and Fix Pending’.  Not a member? Join Here!