ControlUp Community

Connect, Learn, and Grow

ControlUp for VDI (Real-Time DX) Training & Support Archives

ControlUp for VDI (Real-Time DX) training and support-related archives from inside the ControlUp Community on Slack.

Comprehensive User-Created Training and Operating Manual for ControlUp Real-Time DX Console

Posted on

A ControlUp community member has created a comprehensive Training and Operating Manual for the ControlUp Real-Time Digital Experience (DX) Console, originally developed as internal training material but now shared publicly to benefit the wider user community. The manual spans roughly 22 pages and includes detailed explanations, diagrams, and knowledge base references, aiming to deepen understanding of ControlUp’s architecture, setup, operations, and troubleshooting. The manual covers multiple critical areas for both new and experienced users. It begins with an overview of the console architecture and the data collector pattern, supported by detailed diagrams to visualize the system’s workings. Installation topics include the sequence of setup steps, pitfalls like the “shared-credentials trap,” mechanisms for Multi-Site Association, and agent auto-deployment processes. For everyday operations, the manual highlights powerful console features such as column grouping, Branch Mapping, and registry comparison. It also clarifies common confusions around event logs, particularly the differences between LogName and event ID. Troubleshooting guidance is a key focus, addressing connectivity challenges including those posed by corporate proxy environments, with practical PowerShell snippets included to assist in resolution. Advanced topics such as script actions with argument extraction from column values are also presented. The manual further differentiates ControlUp’s on-premises variants, specifically IOP, COP, and SOP configurations, which is valuable for users managing hybrid or fully on-premises deployments. This document is an independent user-created resource and is explicitly noted as unofficial; it does not carry warranty, support, or official endorsement from ControlUp. Users are encouraged to use it as a supplement to official resources and to consult ControlUp’s Knowledge Base and ControlUp Academy for formal guidance. The author invites feedback and corrections from the community to improve the manual’s accuracy and usefulness over time. This shared resource represents a valuable starting point and practical reference for ControlUp console users wishing to deepen their operational knowledge and troubleshooting skills. For official documentation and further training, users can visit the ControlUp Knowledge Base at https://docs.controlup.com and the ControlUp Academy at https://cuacademy.controlup.com.

Read the entire article here...

How to Initiate Remote Assist for VDI Sessions in ControlUp and Upcoming Improvements to Global Search and Enrich Plugin

Posted on

In ControlUp, currently the primary method to start a remote assist session for a VDI user involves navigating through the interface by selecting VDI > Details > drilling down to the specific pool, or by using the search grid to find a user, then right-clicking their session, choosing Session Management, and finally selecting Remote control. This workflow contrasts with some other remote support tools, such as ScreenConnect, which offer a global search feature enabling quick retrieval of any active session—physical or virtual—directly by searching the user's name. The new global search functionality in ControlUp primarily directs users to the session activity reports rather than live session data. This design choice was intentional to focus on long-term historical data rather than real-time session information. However, multiple community members highlighted the benefit of extending the global search to include live VDI sessions, which would allow quicker identification and management of active sessions and streamline remote assist workflows, particularly for VDI. The need for this improvement is tied to efforts by some organizations to consolidate tools, replacing separate remote assist products with ControlUp. The current process for VDI sessions is seen as less efficient compared to physical endpoints, where the user’s device appears directly in the global search, facilitating straightforward remote control initiation. Adding real-time VDI session data to the global search would align ControlUp’s user experience with that of other remote support tools and simplify support staff workflows. Additionally, the community suggested expanding ControlUp’s Enrich plugin—already valued for integrating with ticketing systems and enhancing remote support capabilities—to cover VDI environments. This expansion is confirmed to be on ControlUp’s roadmap and is expected to be developed later in the year, promising to further enhance VDI support operations. For more detailed guidance on starting remote control sessions and using ControlUp’s search features, users can consult the official ControlUp documentation at https://docs.controlup.com and explore the ControlUp Academy resources at https://cuacademy.controlup.com.

Read the entire article here...

Troubleshooting Script Actions in ControlUp Realtime and Web Consoles

Posted on

A user asked how long it takes for a script action to be available in the Web Console after creating it in the Realtime Console, and another user responded that it usually takes a few seconds. If the issue persists, instructions were given for a potential solution and to contact support. The process of updating and running the new version of a script on the Web Console was also discussed. The user found that the new version was not immediately populated, but refreshing the web console and using the Save Configuration feature may help in this process. Support can be contacted at support@controlup.com if necessary.

Read the entire article here...

ControlUp Survey.exe Crashing: AV Exclusions to Blame?

Posted on

Several users experienced high volumes of crashing with the process 'Survey.exe' but found no active surveys running. One member recommended checking the version of the sip agent installed on the VDI's and to review the AV exclusions, which can be found on the updated documentation page at https://support.controlup.com/docs/av-exclusions-for-controlup. A user also reported having a dump file for the issue. Others suggested that this may be a result of the AV exclusions not being applied properly and causing a loop of 'Survey.exe' starting and crashing immediately.

Read the entire article here...

How to Pinpoint CPU-Heavy Processes Across Your VDI Fleet with ControlUp

Posted on

This thread walks through a real customer question: how do you find which processes are eating the most CPU across a large VDI estate (200 servers) over a long period, so you know what to optimize? It starts in ControlUp Dashboards. Using the VDI process data, you can build a widget showing top processes by CPU, then narrow it to the machines you care about using global filters (filter by folder, or switch to query filters with IS / IS NOT). A table beats a bar chart for a top-50 view, and any filters and time frames you set are saved in the URL, so you can bookmark or share the exact view. The built-in Gallery dashboards (notably "Big Screen Dashboard VDI") already include a processes-by-CPU widget out of the box. The harder part is the one the customer really cared about: getting a meaningful picture across all machines rather than a single noisy spike on one box. The data is stored per process per 5-minute timeslot, not pre-aggregated per machine, so the practical approach that emerged was: Filter to the folder containing all target machines. Use CPU usage P95 to strip out short, expected spikes (with a fallback to average CPU, since P95 returned N/A in some environments — a possible bug worth a support ticket). Add metrics under Advanced: computer_name (unique count) to see how many machines run the process, and process_name (count) to see how often it appeared (each record ≈ a 5-minute aggregate). The processes worth optimizing are the ones combining high CPU + high machine count + high record count. Worked example: a process showing ~1,080 records across 197 machines roughly translates to ~90 hours of activity over 7 days, or a few minutes per machine per day. The same method surfaced candidates like CompatTelRunner.exe, WerFault.exe, and WEM-related activity for further investigation. To go deeper, the App Trends and App Statistics reports let you drill into a specific app, and product_name data helps identify what's actually behind generic process names like setup.exe. A few important caveats came up: averages hide spikes (10% average could be one minute at 100%), process counts are per machine, and hypervisor-level CPU (e.g., XenServer) can disagree with in-VM agent data when hosts are over-provisioned — which is also why a Sizing Recommendations report may suggest removing vCPUs even on a machine that looks maxed out. Bottom line: use the dashboard to identify the heavy processes (folder filter + P95/avg CPU + machine count + record count), then use the App Trends report to dig into the details per app.

Read the entire article here...

Upgrading to the Latest ControlUp Version – What to Expect

Posted on

A member asked for known pitfalls when upgrading from ControlUp version 9.2.0622 to 9.2.0711 and mentioned some desired features. A product manager mentioned there as no known pitfalls and 20+customers have already upgraded. The new features were revealed to be Citrix VDA Registration State Monitoring, Windows Process Relationship Monitoring, and Citrix User Connection Failure Monitoring. Another member commented on the benefits of these features.

Read the entire article here...

Troubleshooting Missing Machine Metrics in DEX after Updating ControlUp Agents

Posted on

A user is experiencing issues with machine metrics not showing up in DEX after updating their Horizon Farm to agent 9.2.0.622. Another user suggests that the monitors may not be able to connect to the agents. It is then clarified that agents do not directly connect to DEX and that the issue may be due to a failure in the inbound or outbound connections between monitor and agent. The monitors may still be running.

Read the entire article here...