A user reported an issue with the latest version of Omnissa Horizon Agent, causing problems with fields not populating correctly and rebranded directories. The issue has not been resolved in the latest ControlUp beta, but support is available by opening a ticket.
Read the entire ‘Troubleshooting the Latest Version of the Omnissa Horizon Agent with ControlUp’ thread below:
With the latest Omnissa Horizon Agent version 2412 I noticed that some fields that pull from Horizon don’t seem to be populating correctly. See the attached screenshot. The top machine is running the older version of the agent and the bottom two have the rebranded 2412 agent.
It’s worth noting that this upgrade on the Horizon side has caused a number of issues for us for any application’s that integrate with Horizon due to the rebranding & changing of paths from "VMware" directories to "Omnissa" directories.
Any chance that this is resolved in the latest CU beta? I didn’t see any mention of it on the release notes but thought it would be worth an ask.
no it’s not resolved yet in the latest beta and we’re working with Omnissa to get upgraded license keys to install 2412 ourselves. It is something we are aware of though that could happen
regardless that can you please open a ticket and feel free to mention me for escalation
Will do. Thank you for the info!
Continue reading and comment on the thread ‘Troubleshooting the Latest Version of the Omnissa Horizon Agent with ControlUp’. Not a member? Join Here!
Categories: All Archives, ControlUp for VDI