A user encountered difficulties querying connection failure data within a specified time range using the ControlUp AI assistant. Despite attempting a straightforward query to count connection failures during a certain period, the AI repeatedly generated errors instead of delivering the requested information. This issue highlighted limitations or temporary glitches in the AI interface for composing complex filter criteria involving time intervals.
Upon reporting the problem to the ControlUp support team, it was acknowledged as potentially related to recent network issues, which may have contributed to the AI malfunction on the previous day. The team requested formal feedback submission to investigate the problem further and verify if it could be reliably reproduced under similar conditions.
In the meantime, a practical alternative was suggested from within the community: a pre-built Citrix connection failures dashboard created by a peer user. This dashboard presents connection failure metrics in an organized and visually accessible format, allowing administrators to monitor relevant data without relying solely on raw AI-driven queries. Such dashboards provide easier insights into connection issues and can be a more reliable solution for identifying failure trends over time.
For users experiencing similar problems with AI query errors related to connection failure data, exploring the ControlUp dashboard options is recommended as an effective workaround. Additionally, reporting such AI issues to ControlUp support ensures ongoing improvement of AI capabilities for querying monitoring data. More information on creating and customizing monitoring dashboards can be found in the ControlUp Knowledge Base at https://docs.controlup.com and tutorials at the ControlUp Academy https://cuacademy.controlup.com.
Read the entire article here...
ControlUp Community Training & Support Archives
All training and support-related archives from inside the ControlUp Community on Slack.
Managing Disk Usage on Laptops with ControlUp SIP Agent
ControlUp provides a scripting engine within ControlUp for Desktops, enabling IT administrators to distribute and execute scripts across devices in their environment. This functionality allows for tasks such as IT administration and data collection. ([support.controlup.com](https://support.controlup.com/docs/scripting-guide?utm_source=openai))
To utilize this feature, navigate to ControlUp for Desktops > Configuration > Scripts to view and manage your scripts. The Scripting Guide offers comprehensive instructions on running scripts in ControlUp for Desktops. ([support.controlup.com](https://support.controlup.com/docs/scripting-guide?utm_source=openai))
For managing disk usage on laptops equipped with the SIP agent, you can adapt existing scripts designed for VDI environments. The Scripting Guide provides detailed information on creating and managing scripts, which can be tailored for laptops. ([support.controlup.com](https://support.controlup.com/docs/scripting-guide?utm_source=openai))
Additionally, the ControlUp Script Library offers a collection of useful scripts compiled by ControlUp, which can be imported and customized for your specific needs. ([controlup.com](https://www.controlup.com/scripts/?utm_source=openai))
By leveraging these resources, you can effectively monitor and manage disk usage on laptops using the SIP agent, similar to the capabilities available for VDIs.
Read the entire article here...
Read the entire article here...
How to Deploy ControlUp Agent via GPO in VDI Environments with MSI Silent Install and PowerShell Automation
Deploying the ControlUp Agent for VDI environments via Group Policy Object (GPO) does not have a dedicated official knowledge-base article, as the installation approach aligns with generic MSI silent installs used in other deployment methods like SCCM or PDQ. The official ControlUp documentation regarding local machine connection and agent communication is the primary reference for deployment: https://support.controlup.com/docs/connect-to-your-machines-locally and https://support.controlup.com/docs/agent-outbound-communication.
For non-persistent VDI setups that use a gold master image, the recommended method is to install the ControlUp agent MSI directly on the master image with specific MSI properties: `MASTER_IMAGE=true`, along with the `AUTHKEY` and `RegistrationKey`. This avoids the need for repeated installations on cloned machines via GPO. For persistent, domain-joined virtual machines, using a GPO Computer Startup Script to run an msiexec command is preferred over GPO Software Installation because it allows passing required MSI properties. An example command line looks like this:
`msiexec /i \\share\ControlUpAgent-xxxx.msi /qn AUTHKEY="" RegistrationKey="" MASTER_IMAGE=true`
The authentication keys are retrieved from the Real-Time Console under Settings → Agent. The Registration Key is mandatory starting from version 9.0. Machines must be manually added to the organization tree unless the agent version is 9.0.5 or higher, which supports self-registration.
When GPO deployment is not optimal, if remote RPC or WMI connectivity is available, deploying the agent remotely via the ControlUp console or Monitor is simpler. For cloud-managed endpoints, Microsoft Intune is the officially documented deployment method.
A practical example was shared demonstrating a PowerShell script to deploy the ControlUp Agent MSI for VDI within a Nerdio scripted action context. The script copies the MSI from a UNC file share to a local temporary path, validates that the MSI file is correctly copied (including a check on the MSI magic bytes), and then executes the msiexec command with silent installation flags, the authentication keys, and logging enabled. It captures and reports installation exit codes and prompts when a reboot is required. The script also includes a post-installation check to list ControlUp-related services to confirm the agent installed and started as expected.
This approach encapsulates the best practice for deploying ControlUp agents in VDI environments using GPO, balancing MSI property requirements, version-specific authentication mechanisms, and practical scripting for automation. For detailed agent deployment contexts and command-line references, the ControlUp official documentation remains the authoritative source: https://support.controlup.com/docs/connect-to-your-machines-locally and https://support.controlup.com/docs/agent-outbound-communication.
Read the entire article here...
Read the entire article here...
How to Configure Low Disk Space Alerts by Percentage in ControlUp for Devices
In ControlUp for Devices (CU4D), setting up an alert to notify an administrator when any device's OS disk free space drops below a certain threshold can be configured through the Events > Alert Rules section. To create an alert for low disk space, a user needs to define the appropriate category, metric, condition, and value that represent the target threshold.
The recommended approach is to use an alert rule that monitors the free space on the OS disk. While the initial example provided in the community discussion suggested a value-based threshold (e.g., a specific number of gigabytes free), it is also possible to configure an alert based on a percentage of free disk space. This is important for flexibility as percentages provide a more relative and scalable measure across devices with different disk sizes.
To implement this, the alert should be defined in the category related to storage or disk metrics. The metric to monitor would be the percentage of free space available on the OS disk. The condition would then be set to trigger when this percentage falls below a certain value (such as 10%). Once the alert triggers, it can be configured to send an email notification to administrators. Furthermore, ControlUp’s integration with script actions can automate responses to these alerts, such as running a system disk cleanup or presenting a user prompt to clean up space.
For detailed steps and additional options, users are encouraged to refer to the official ControlUp documentation on alert rules and script actions, as well as the ControlUp Knowledge Base and Academy resources at https://docs.controlup.com and https://cuacademy.controlup.com. These resources provide comprehensive guidance on setting conditions, selecting metrics, and automating remediation workflows based on alerts.
Read the entire article here...
Read the entire article here...
How IP Restrictions Affect REST API Access and How to Configure the IP Allow List in ControlUp
When IP Restrictions are enabled in a ControlUp organization, they apply not only to user sign-in at app.controlup.com but also to REST API calls that use API keys or tokens for authentication. Initially, there was confusion about this behavior, with one party assuming that IP Restrictions only affected user sign-ins via the web application and would not restrict API calls. However, further investigation clarified that IP Restrictions do indeed apply to API requests.
The key issue encountered was that reporting workflows that fetch machine statistics via the REST API started returning "Unauthorized" errors after IP Restrictions were enabled. Although the API tokens used for authentication were verified as valid and not expired, the requests failed due to the IP restriction settings.
The resolution involves adding the public egress IP addresses of the systems making the API calls (such as those running the reporting workflows) to the organization's IP Allow List in ControlUp. This setting is accessible under Settings → Security → IP Allow List in the ControlUp management console. Once the calling system’s IP addresses are added to the allow list, API calls from those IPs will be authorized, provided a valid API token is also used.
For more detailed guidance, official ControlUp documentation and references include the API endpoint for managing IP allow lists (https://api.controlup.io/reference/orgipallowlistpubliccontroller_create) and the knowledge base article on IP Allow Lists (https://support.controlup.com/docs/ip-allow-list). These resources offer comprehensive instructions for configuring the IP Allow List to control API access securely.
Read the entire article here...
Read the entire article here...
NEW ControlUp Disk cleanup script that actually asks the user what to delete
Chris Twiest demos a new interactive disk cleanup utility built by Sebastien Perusat and now baked into the product. Instead of silently cleaning from the system context, it prompts the end user with what can be reclaimed and lets them choose — recycle bin, temp files, browser cache. Works on Windows and macOS, can be triggered manually or from an alert, writes results to a data index and a device event, and is fully editable. Available in the script library now.
Read the entire article here...
Read the entire article here...
How to Preserve Static Filters When Copying ControlUp Dashboards
In ControlUp dashboards, users may desire to create copies of a dashboard with pre-set filters that remain consistent and "locked" across multiple instances or devices. However, a limitation exists in that filters on copied dashboards reset to default values rather than preserving the original filter settings. This is because filter states are saved within the URL, allowing users to copy or bookmark filtered views.
At the time of the inquiry, a reported bug prevented these filters from automatically restoring when a dashboard was copied or opened from a saved URL. This issue affected workflows where multiple dashboard copies were needed with static filter criteria for consistent monitoring or reporting. ControlUp acknowledged the bug and targeted a resolution by mid-August.
The issue has since been resolved, enabling filters to properly restore from the URL when duplicating or accessing dashboards. While users can facilitate quick filter selection with variables, the fix now ensures filter states remain persistent as intended when copying dashboards, thus supporting more effective and static customized dashboard scenarios.
For further details on dashboard filter functionality and managing variables, users can refer to the ControlUp Knowledge Base and related documentation available at https://docs.controlup.com. The ability to save and restore filter states enhances dashboard usability, particularly in environments requiring consistent monitoring views across multiple devices or team members.
Read the entire article here...
Read the entire article here...
How to Auto Log Off Idle Users in Azure Virtual Desktop Using ControlUp Triggers and Scripts
Several ControlUp community members discussed how to configure a trigger to automatically log off idle users from Azure Virtual Desktop (AVD) hosts using the ControlUp Agent for Virtual Desktop Infrastructure (VDI). One common solution is to leverage existing trigger packs within ControlUp, which include triggers designed to log off a user session after a specified period of inactivity. These triggers can be customized based on time thresholds that fit the organization’s session management policies.
An example script and detailed guidance were shared from ControlUp’s official script library, which provides automation for disconnecting or logging off idle sessions. This script can be adapted and deployed within ControlUp's automation policies to monitor session activity and log off users automatically when idle thresholds are met. The relevant resource is available at https://www.controlup.com/script-library-posts/disconnect-or-log-off-idle-sessions/.
Additional insights were shared from a ControlUp blog post that focuses on session resource optimization through automation. This post outlines best practices and practical examples of using ControlUp automation to manage session states efficiently, including auto-logout for idle sessions. The blog can be found here: https://www.controlup.com/blog/controlup-automation-session-resource-optimization/.
While native solutions like DaaS IQ might offer built-in functionality for auto-logging off idle users, many organizations have adopted ControlUp triggers as a practical workaround until formal approval or integration of native options is completed. The combination of ControlUp’s flexible triggers and scripting capabilities allows administrators to enforce session timeout policies effectively within AVD environments, optimizing resource utilization and enhancing security.
Read the entire article here...
Read the entire article here...
How to Use the New Markdown Export Feature in ControlUp Documentation for Large Language Model Integration
ControlUp's documentation site has introduced a new feature that allows users to copy any documentation page in markdown format. This enhancement is particularly useful for users who want to upload ControlUp content directly into large language models (LLMs), facilitating better and more precise script crafting or automation related to ControlUp products. For example, users can now easily convert the "Scripting Guide" page into markdown and input it into their LLM environment, ensuring that the model has detailed, structured data to work from.
This markdown export capability streamlines the process of creating LLM-friendly documentation inputs, addressing a common challenge when working with extensive or complex technical materials. By providing content in markdown, the documentation is preserved in a clean, readable, and semantically rich format that LLMs can parse more effectively than raw HTML or PDF files.
While it is not explicitly confirmed whether this feature was developed directly by the ControlUp team or if it stems from an update to the documentation platform itself, it represents a valuable improvement for the community. It supports advanced use cases such as automated script generation, query assistance, and customized training data preparation for ControlUp’s digital employee experience (DEX) and IT performance monitoring tools. The feature has been recognized positively by users for simplifying integration of official ControlUp documentation into AI-driven workflows.
For more details on ControlUp’s scripting options and how to utilize documentation effectively, users are encouraged to visit the official documentation site at https://docs.controlup.com, where this new markdown export option is available.
Read the entire article here...
Read the entire article here...
Troubleshooting “Detect Workspace” Stuck Prompt for Citrix Cloud Synthetic Monitors on Public Hives
Some users running synthetic monitors to test Citrix Cloud connections from public hives reported that a few monitors become stuck at the "Detect Workspace" prompt. This behavior was inconsistent, with some monitors seemingly configured the same way functioning normally while others encountered this issue.
The root cause was identified as related to the Citrix Workspace store’s launch method settings. The "Detect Workspace" screen corresponds to the Citrix client detection page, which is controlled on the store side rather than by Scoutbees or the synthetic monitors themselves. Specifically, when the store is configured with the "Launch virtual apps and desktops" setting set to either "Open in Citrix Workspace app" or "Let the user choose," this page appears. On public hives, where the browser environment is fresh and does not retain prior user choices, the prompt recurs on every run, causing the monitors to stall at this screen.
To resolve this, it is necessary to verify and compare the launch settings in Citrix Cloud under Workspace Configuration (or the targeted StoreFront store). Monitors stuck on the detection prompt typically point to stores configured with "Open in CWA" or "Let the user choose," while those that bypass the prompt are connected to stores set to "Use web browser to access apps and desktops." Changing the store’s launch setting to "Use web browser" bypasses the native Citrix Workspace app detection page, allowing the synthetic monitors on public hives to proceed without interruption.
Before making any changes, administrators should confirm these settings by comparing the store configurations between monitors that are stuck and those that are working. This ensures an accurate diagnosis and prevents unintended side effects from changing the launch mode. Since this is a store-level configuration, it requires adjustments within the Citrix Cloud management console, specifically under Workspace Configuration. If the issue persists or if the public hive environments themselves seem problematic, submitting a support ticket for those specific hives is recommended.
For additional guidance on managing Citrix Cloud Workspace configurations and optimizing monitor setups, see the ControlUp Knowledge Base and Citrix documentation on Workspace Configuration: https://docs.controlup.com and https://docs.citrix.com/en-us/citrix-cloud/workspace-configuration.html.
Read the entire article here...
Read the entire article here...