When transitioning from VMware ESX to a Hyper-V environment for Citrix, monitoring Hyper-V hosts through the ControlUp Management Console requires a different setup than for ESX hosts. Unlike ESX, which can be monitored directly once properly connected, Hyper-V monitoring in ControlUp necessitates deploying the ControlUp agent on each Hyper-V host. This agent installation allows ControlUp to gather detailed performance and health data from the Hyper-V hypervisors.
A common issue encountered during this transition is that ControlUp might mistakenly identify a few virtual machines as Hyper-V hosts instead of the actual hypervisor servers. This usually happens if the agents are not installed on the Hyper-V hosts themselves, or if the connection configuration is not correctly set up for Hyper-V clusters. Therefore, simply having the hypervisor hosts visible in the environment without the agent does not provide full monitoring capabilities.
To properly monitor Hyper-V clusters with ControlUp, administrators should follow the official guidance for connecting to Hyper-V hypervisors. The key step is to deploy the ControlUp agent on every Hyper-V host within the clusters. This enables comprehensive visibility into the hypervisor layer similar to what was available for ESX hosts. Detailed instructions and best practices for this process can be found in the ControlUp documentation at https://support.controlup.com/docs/connect-to-your-hypervisors#connect-a-hyperv-hypervisor.
In summary, migrating from ESX to Hyper-V environments requires deploying the ControlUp agent on Hyper-V hosts to achieve effective hypervisor monitoring. Proper identification of Hyper-V hosts and cluster setup within ControlUp hinges on this agent deployment, ensuring accurate and actionable insights for Citrix environments running on Hyper-V.
Read the entire article here...
VMware Related Training & Support Archives
VMware training and support-related archives from inside the ControlUp Community on Slack.
How to Report Horizon Client Versions Across User Sessions Using ControlUp
A common requirement for managing VMware Horizon environments is the ability to report on the endpoint client versions—referred to as "HZ Client Version"—used by users to connect to the Horizon infrastructure. This need becomes particularly important in hybrid environments where users connect from both managed internal devices and unmanaged BYOD (Bring Your Own Device) endpoints. Tracking client versions helps administrators identify devices running outdated Horizon clients that require upgrades to ensure security, compatibility, and optimal performance.
Within ControlUp, the Horizon client version information can be accessed via several mechanisms. The VDI - Details view in the ControlUp console displays the HZ Client Version associated with each session, providing a straightforward way to see the current client version used. For programmatic or historical data extraction needs, ControlUp also offers a real-time data API (https://api.controlup.io/reference/gettables) which can retrieve live session details including client versions. Additionally, the "initial HZ client version" field recorded in the Session Activity report captures the client version that was used to start the session. This field, although labeled as "initial," effectively serves as a snapshot of the client version at session start.
However, because users in hybrid scenarios may connect multiple times throughout the week from different devices or update their Horizon client between sessions (for example, by disconnecting, updating, and reconnecting), it is important to consider that the client version can vary across sessions. The "initial HZ client version" is tied to each individual session start, so accumulating this information over a period allows administrators to identify all versions in use and target users on outdated clients. Pulling session activity reports over time and correlating the client versions used enables identification of BYOD devices needing updates even if the same user connects from multiple endpoints.
In summary, the "initial HZ client version" contained in ControlUp’s Session Activity reports is the key field for tracking Horizon client versions across user sessions. The ControlUp real-time data API further facilitates custom querying and automation for this reporting. For detailed exploration of session data, the VDI - Details view complements these options with an at-a-glance interface. Using these tools, administrators in hybrid environments are able to efficiently monitor and manage Horizon client versions on both managed and BYOD devices, ensuring compliance and performance consistency.
Read the entire article here...
Read the entire article here...
Troubleshooting Missing Unified Access Gateway Metrics in ControlUp Due to Horizon API Version Limitations
When configuring the connection to VMware Unified Access Gateway (UAG) in ControlUp version 9.2.5.634, a common issue arises where the UAG appears connected but does not show any metrics or visibility under the EUC Environment or the DEX Connection Servers section. Although the initial connection test succeeds, UAG metrics are missing from the interfaces, leading to confusion about what might be incorrectly configured.
One critical root cause identified is related to the Horizon REST API version supported by the UAG and Connection Servers. ControlUp relies on Horizon’s Monitor Gateways API version 5 to retrieve UAG data, but many Horizon environments running version 2412 or earlier only support versions 3 or 4 of this API. This incompatibility prevents ControlUp from properly monitoring the UAG, resulting in the absence of UAG metrics despite a seemingly successful connection configuration. This limitation is not explicitly detailed in ControlUp’s documentation, making it an easy pitfall for users in older Horizon environments.
Users who upgraded their Horizon Connection Servers to version 2603 reported that after refreshing the UAG settings in ControlUp, UAG metrics became visible and functional, confirming that full UAG monitoring support requires Horizon environments with API version 5 or newer. For those in unsupported environments, the UAG section will fail to sync correctly, although some other synchronization data like "NIC" sync may still appear. This partial failure causes issues with automatic EUC syncs, which will fail on an hourly schedule unless UAG syncs are disabled. Manual syncs from the ControlUp Console, however, still function as a workaround until an official fix or workaround is provided by support.
In light of these findings, users experiencing missing UAG metrics should verify the Horizon API version compatibility and consider upgrading their Horizon environment if UAG monitoring is required. It is also advisable to coordinate with ControlUp support to analyze logs and explore potential short-term solutions. Additional monitoring configuration details can be found in ControlUp’s official documentation on monitoring OmniSaaS and UAG here: https://support.controlup.com/docs/monitor-omnissa-unified-access-gateway. This document clarifies the expected behaviors and limitations with UAG monitoring in various Horizon versions.
Read the entire article here...
Read the entire article here...
ControlUp Community Meetup 15: How to: Connecting MCP AI to your Real-Time Data
Learn how to connect AI to live enterprise data using the ControlUp MCP Server. In this session, Chris Twiest explains the fundamentals of Model Context Protocol (MCP), including LLMs, prompts, system prompts, tool calling, and retrieval, before demonstrating how to connect Claude Desktop to ControlUp. Watch a live walkthrough of configuring the MCP Server, querying real-time endpoint data, visualizing application crashes, comparing results against historical baselines, and using system prompts to dramatically improve AI accuracy. The session also explores practical use cases, including upgrade planning, combining multiple MCP servers, building custom AI interfaces, and the future of autonomous endpoint management.
Read the entire article here...
Read the entire article here...
How to Diagnose Microsoft Teams SlimCore Optimization in Citrix and Other VDI Environments Using PowerShell Scripts
This discussion highlights two PowerShell scripts developed to aid tracking and diagnosing Microsoft Teams SlimCore Optimization specifically within Citrix environments, with potential applicability to Azure Virtual Desktop (AVD), Windows 365 (W365), and VMware Horizon sessions. SlimCore is an optimized media stack used in virtual desktop infrastructure (VDI) scenarios to enhance Teams call performance by offloading audio and video processing to the client side.
Read the entire article here...
Read the entire article here...
ControlUp Synthetic Monitoring Workflows and Workarounds
A user named Alexander asked Nathan about a known limitation with ControlUp Synthetic Monitoring - specifically, that the server_name is often empty for NetScaler Gateway scouts. Nathan recommended a few different workarounds for auto-restart and suggested adding more fields to the webhook payload for debugging. The suggested workflow was to use resource and query ControlUp Real-Time DX / CVAD for machines or sessions matching the published resource.
Read the entire article here...
Read the entire article here...
Troubleshooting Black Screen Issues on Omnissa Horizon
Users on Omnissa Horizon are experiencing black screen issues when reconnecting to a session. The issue occurs 4-5 times a day and the only workaround is to force a logoff, leading to lost work. The setup and environment are described in detail, along with past troubleshooting attempts. A fellow ControlUp member suggests looking at Horizon Agent logs and utilizing Horizon's API to lock a VM for further investigation.
Read the entire article here...
Read the entire article here...
Episode #20 – Conversation with Ryan Mangan, Founder of EfficientEther
Tune in to Episode #20 of ControlUp Community Radio, where host Douglas Brown welcomes Ryan Mangan, founder of EfficientEther, a cutting-edge platform dedicated to optimizing cloud costs through AI technology. With nearly 20 years of expertise in user computing, Ryan brings deep insights from his extensive work with RDS, VMware, and Azure Virtual Desktop.
Ryan shares his journey and the motivation behind launching EfficientEther, highlighting how organizations face increasing complexities and waste in managing cloud expenditures due to subscription-based models.…
Read the entire article here...
Read the entire article here...
Setting Up a Trigger for Identifying Unused VMs in ControlUp Focus Discussion.
Several users discussed how to set up a trigger for identifying unused VMs older than 45 days, specifically in relation to the ControlUp environment. Suggestions were given about using the built-in Session Activity report or APIs to identify machines with no recent logins. Some users mentioned testing and recoding scripts for different hypervisors. One user also brought up the issue that not all VMs have a Horizon agent.
Read the entire article here...
Read the entire article here...
Troubleshooting the Latest Version of the Omnissa Horizon Agent with ControlUp
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 article here...
Read the entire article here...