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...
ControlUp Community Training & Support Archives
All training and support-related archives from inside the ControlUp Community on Slack.
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...
How to Create CPU Usage Alerts in ControlUp That Exclude Restart and Boot Spikes
A common challenge in monitoring CPU usage is avoiding false alerts during system restarts or boot periods, when CPU spikes are normal but typically short-lived. One effective method to address this in ControlUp is to configure an alert rule targeting the device_status data index with specific conditions to filter out these transient spikes.
To create a CPU alert that excludes restart or boot-phase spikes, set up a static threshold alert on Devices with a condition such as cpuload > 80 (adjust the threshold based on your environment). The key element is applying a time window and hit count that accommodates short bursts without triggering alerts. For example, use a time window of 600 seconds (10 minutes) and require 5 hits within that period before the alert fires. Additionally, a retrigger delay of 3600 seconds (1 hour) helps reduce repeated alerts for sustained high CPU usage.
This configuration works because CPU usage during boot or restart typically spikes briefly and does not persist long enough to meet the hit criteria within the time window, thereby filtering out most false positives without complex logic. For situations where CPU remains elevated for longer periods during boot—due to updates, login scripts, or heavy startup applications—it is recommended to implement an uptime check or guard. This further refines alerting by ensuring the system has been running beyond a certain uptime threshold before alerts activate.
These steps provide a practical approach to balancing sensitivity and noise in CPU alerting, improving monitoring accuracy in environments where restarts cause predictable, short-term CPU spikes. For more detailed guidance on creating and tuning alert rules, consult the ControlUp documentation at https://docs.controlup.com/alert-rules and consider exploring uptime monitoring techniques available in ControlUp's device health metrics.
Read the entire article here...
Read the entire article here...
Troubleshooting Access Denied Errors When Upgrading ControlUp Monitor Servers Using PowerShell
When upgrading a ControlUp monitor server from version 9.0.0.1680 to 9.2.0.733 using the PowerShell commandlet Invoke-CUMonitorUpdate, the process may fail with an "Access is denied" error. This failure occurs after the installation steps "Install Verify Service already installed" and "Install Copy Files" complete successfully, specifically at the step involving stopping the `cuMonitor` service. The error indicates that Windows denied access during the attempt to stop or control this service, despite running PowerShell as an administrator and having folder-level access to the monitor installation directory.
The root cause is typically related to security settings or interference by antivirus (AV) or endpoint detection and response (EDR) software, which can block the service from stopping. Alternatively, a restrictive service Access Control List (ACL) can prevent the upgrade from proceeding. When attempting to upgrade through the ControlUp Console, a similar failure occurs silently because the console relies on remote commands (via admin share or WMI) that suffer the same permissions restrictions.
To resolve this issue, manually stopping the `cuMonitor` service with elevated privileges is required. Running `sc.exe stop cuMonitor` on the monitor host as an administrator can successfully stop the service. If this command fails, it is necessary to configure AV/EDR exclusions for the ControlUp monitor executable and folder (`C:\Program Files\Smart-X\ControlUpMonitor\` and `cuMonitor.exe`) or adjust the service's ACL using `sc.exe sdshow cuMonitor` to inspect and modify permissions. Once the service is stopped, re-running the Invoke-CUMonitorUpdate commandlet completes the upgrade successfully.
When upgrading through the ControlUp Console, ensure the account used has local administrator rights on the monitor host; otherwise, upgrade via the PowerShell commandlet locally on the machine is recommended for reliability. This approach has been verified to resolve the access denied error and enable the upgrade to proceed without interruption.
For more details on managing ControlUp monitor services and upgrade procedures, refer to the official ControlUp documentation at https://docs.controlup.com or consult ControlUp support resources.
Read the entire article here...
Read the entire article here...
How to Use ControlUp’s Beta Features for Desktops: Deployment, Benefits, and Best Practices
ControlUp has introduced new beta features for its ControlUp for Desktops agent, offering users early access to the latest enhancements and improvements. This beta version is designed to allow IT administrators and users to test new functionalities before they are released for general availability. To participate in the beta, users can configure their agent version control settings to deploy the beta version selectively across specific devices. This targeted deployment helps organizations evaluate the beta features in a controlled environment without impacting their entire infrastructure.
The update has been well-received by the community, highlighting the significant value and innovation brought by the new capabilities. The positive feedback underscores the quality and effort invested by the development team in enhancing the user experience and functionality of the ControlUp agent. Although detailed specifics of the beta features were not outlined in the initial announcement, users are encouraged to review the beta release notes and experiment with the new version in their test environments to understand the full scope of improvements.
As this version is a beta, it is important to note that it may contain experimental features or potential issues not present in stable releases. Organizations should exercise caution by limiting beta deployment to non-critical systems or test groups, monitoring performance, and providing feedback to ControlUp to assist in refining the final release. Users can manage agent versions and access version control documentation at https://support.controlup.com/v1/docs/agent-version-control to ensure proper deployment and rollback options are understood.
For further information on ControlUp agent management, deployment best practices, and how to leverage new updates effectively, consulting the official ControlUp documentation at https://docs.controlup.com and the ControlUp Academy at https://cuacademy.controlup.com is recommended. These resources offer comprehensive guidance on everything from installation to advanced feature configuration, ensuring IT teams maximize the benefits of ControlUp across their digital workplaces.
Read the entire article here...
Read the entire article here...