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...
Storage Related Training & Support Archives
Storage training and support-related archives from inside the ControlUp Community on Slack.
How to Alert on Added Storage Devices by Drive Letter in ControlUp Using os_disk_configuration Filters
A community member sought assistance with creating a ControlUp trigger or alert to detect when storage devices are added to a physical endpoint and assigned a drive letter or mounted. The data relevant to this event is visible in the ControlUp 4D (CU4D) Performance tab under the Operating System location and stored in the *_devices* index. Specifically, the data is found in the os_disk_configuration field, which contains a JSON array showing details about mounted drives, including drive letters. The user’s challenge was to configure an alert that could detect any newly mounted drive except the system drive C:\ without having to set multiple alerts for every potential drive letter (e.g., D:\, E:\, etc.). They noted the lack of regex support in the filter queries limited their options.
The issue arises because the os_disk_configuration field holds a JSON array with multiple drive entries, and filtering out drive_letter "C:\" naively removes all entries due to the structure of the array. Attempts to use a “does not contain” filter eliminated all Windows devices, only showing macOS devices, complicating detection on Windows endpoints. The user also tried to narrow the focus to removable media but learned that their security team's use case requires alerting on any disk, mounted by drive letter, which remains the best indicator available.
Advice provided during the discussion included adding filters for platform or OS to ensure the alert targets only Windows devices (e.g., platform set to 1 or OS equals Windows). This helped reduce irrelevant results but did not completely solve the filtering problem. Suggestions included playing with additional filters such as combining conditions to exclude drive_letter "C:\" while explicitly including removable devices, though this required trial and error. A recommendation was to test filter configurations in the CU4D index view, including setting the platform to 1 to target Windows devices specifically.
Ultimately, the thread highlights the challenge in using ControlUp’s current filtering capabilities on complex JSON arrays like os_disk_configuration for dynamic drive letters without regex support. The workaround involves narrowing the scope by platform/OS filters and experimenting with composite negation filters, although a straightforward out-of-the-box solution for this specific alert scenario is limited. Users needing comprehensive coverage for any drive letter other than C:\ must create a series of alerts or await enhanced filter features. For now, leveraging the detailed disk configuration data in the *_devices* index with strategic filter layering is the best approach.
For further reading on creating and troubleshooting alerts and filters in ControlUp, users can consult official documentation at https://docs.controlup.com and explore ControlUp Academy resources at https://cuacademy.controlup.com.
Read the entire article here...
Read the entire article here...
Resolving UI and Remote Control Discrepancies When Accessing Devices via Global Search in ControlUp 4 Desktop
When using ControlUp 4 Desktop (CU4D), users have observed a discrepancy in the user interface and remote control experience depending on how they access device details. Specifically, accessing a device via the global search feature directs users to a different-looking interface than when navigating through the Devices > Details path. The interface reached through global search appears to be the older Angular-based UI, characterized by a red-themed layout and missing certain functional tabs such as RMM (Remote Monitoring and Management), Internet Explorer management, network, and storage tabs that are present in the modern white-themed interface accessed via the sidebar device menu.
This difference is not just cosmetic; the remote desktop experience also varies between these two paths. The remote control window initiated from the global search interface does not match the one available through the Devices > Details route, indicating that two different backend platforms or UI frameworks are in use. The sidebar route leverages the integrated DEX (Digital Employee Experience) platform embedded in the main ControlUp site, while the global search currently directs users to the legacy environment.
This issue has been acknowledged by the ControlUp team as a known problem. A fix is planned to unify the experience so that both access methods will lead to the modern UI and consistent functionality, including the proper remote control interface and management tabs. The resolution was expected to be rolled out within a few weeks from the time the issue was reported.
Until this fix is deployed, users should expect the global search function to open the older interface with limited features, while the Devices > Details navigation provides the full, up-to-date DEX platform experience. For the latest updates on this issue and other CU4D features, users can refer to the official ControlUp documentation and community resources.
Read the entire article here...
Read the entire article here...
Proactively Managing Thin-Client SSD Wear: A New Endpoint Script from ControlUp Community Members
A user shared an endpoint script (zzSP_Prod_IGEL_Thinclient_SmartStatus) that can be used in IGEL or thin-client environments to gather information about SSD and storage wear. The script shows important details such as wear level, TB written, and pre-EOL state and can be helpful in proactive hardware-lifecycle management. The dashboard and script are available for use.
Read the entire article here...
Read the entire article here...
Storage Tab Not Showing Reliably in ControlUp Desktop Agent
A user reports that the Storage tab is not showing reliably in the recently installed newer Desktop Agent for a large VDI pool with around 1000 non-persistent machines. They haven't seen any reports of this issue and suggest opening a support case for further investigation. Another user adds that kernel ETW messages may be used for this feature and advises the user to provide more details on how the data is collected for troubleshooting. The affected machines are single-session and a new image is being rolled out, so the user will check if the issue persists and create a case if needed.
Read the entire article here...
Read the entire article here...
Troubleshooting Login Slowdowns: How ControlUp Can Help
A user asked for help with login slowdowns and received suggestions to use CU4VDI trigger to run the ALD script, deploy ControlUp Disk Monitor, and run API queries to gather data. The AI Assistant or Claude/Gemini/ChatGPT can be used to correlate the data and determine the root cause of the issue. The ControlUp PS team is also available for assistance.
Read the entire article here...
Read the entire article here...
Live Remote Management: Troubleshooting Without Taking Over the User
See how Live Remote Management in ControlUp for Desktops enables real-time troubleshooting and remediation without disrupting the end user or taking over their session.
Read the entire article here...
Read the entire article here...
Troubleshooting the Management Option for File and Registry Browsing on ControlUp Live Features
A user encountered an issue with the new live features on ControlUp, specifically with the management option for file and registry browsing. After troubleshooting, it appears to be a permissions issue and potentially a global feature flag. The user was advised to log with support for further assistance.
Read the entire article here...
Read the entire article here...
Upcoming Feature: Remote Management in ControlUp
A user asked about the options under 'Remote Management' in ControlUp's roles and permissions. It was noted that these options are currently unavailable and are part of a new feature that is in Internal Beta. There is no ETA for general release at this time. The user is looking forward to this new feature.
Read the entire article here...
Read the entire article here...
Setting Up Biometric Usage Logging in ControlUp
Instructions for setting up a system to log biometric usage on endpoints were asked about in a Slack conversation with employees from ControlUp. The goal is to have a storage period of 7 years. Different suggestions were made, including using an API and PowerBI, as well as involving an account manager in the process. The data is associated with the user identity and compliance standards vary by country.
Read the entire article here...
Read the entire article here...

