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...
ControlUp Dashboards
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 Calculate Time Saved from Automation Runs in ControlUp Dashboards Using Calculated Metrics
A user sought to create insights on time saved through automations by modifying the existing scripting and automation dashboard in ControlUp. Their goal was to add a calculated column that multiplies the number of successful script runs by a fixed value (such as 5 or 10) to estimate the total minutes saved. The user attempted to apply a mathematical transformation—specifically multiplying the "success-runs" metric by 10—via the dashboard's JSON transformation editor. However, they encountered difficulties as the table widget was built using the advanced JSON builder, which does not support switching to the basic editor mode where simple calculated columns can be added or modified directly.
ControlUp's community and support experts explained that the particular widget in question is created through the advanced JSON editor and does not support adding custom calculated columns directly on individual tables. The system currently does not allow adding a calculated column that multiplies existing columns in the advanced editor since it applies transformations to each column rather than enabling column-to-column calculations.
A recommended workaround is to use the associated "stat" widget found elsewhere on the same dashboard. This widget provides basic aggregated metrics and allows users to add simple calculations, such as multiplying the total number of successful script runs by a fixed number to calculate total time saved. By performing the multiplication in the stat widget rather than modifying the complex JSON table, users can achieve their insight goal effectively.
This limitation highlights that for advanced dashboards created via JSON editing in ControlUp, calculated columns that depend on arithmetic of existing columns must be created through simpler widgets or by recalculating the data outside the table visualization. Users aiming to customize time-saving metrics based on script run counts should consider leveraging stat widgets or other summary-level visualizations that support straightforward calculated metrics. For further guidance, ControlUp's official documentation on the dashboard widgets and calculations can provide additional instructions: https://docs.controlup.com/display/DOCS/Dashboards and https://docs.controlup.com/display/DOCS/Data+Transforms.
Read the entire article here...
Read the entire article here...
How to Implement Native macOS and Windows Self-Service Disk Cleanup via ControlUp Edge DX Without External Tools
A ControlUp community member developed a native self-service disk cleanup solution for macOS and Windows users, designed to be triggered via ControlUp Edge DX without requiring IT intervention or external tools. The goal was to allow users to safely free disk space through a simple, native dialog that displays current disk usage and offers a checklist of safe-to-clean areas such as Trash, application caches, container caches, logs, Xcode build cache, and old temporary files. Each item is described in plain language and sorted by the space it occupies, allowing users to select and confirm the cleanup themselves.
On macOS, the dialog is implemented using only built-in osascript capabilities—no additional tools like swiftDialog or extra installations are necessary. For both macOS and Windows, the solution emphasizes safety by running a dry-run by default, excluding critical system folders and personal directories such as Documents, Downloads, Keychains, and SSH keys from cleanup. The cleanup operates within the context of the logged-in user, not root, ensuring user-specific data protection. After cleanup, the system verifies the amount of space reclaimed against the actual free volume.
Triggering this cleanup from an Edge DX alert, either automatically due to disk usage thresholds or on-demand, enables a small dashboard that reports on reclaimable and freed disk space, all without requiring elevated permissions, Intune writes, or admin consent. One of the more challenging technical aspects was delivering the cleanup dialog from a root-level agent into the user’s session, given the restrictions of macOS and Windows environments.
The community member shared that while the script could likely be optimized or shortened by more experienced developers, this version works reliably and safely. Detailed setup documentation is available by request. Additionally, to complement the cleanup tool, the developer created an analytics dashboard to track the cumulative space saved by the script. This solution offers a practical way for organizations using ControlUp Edge DX to empower their end users with safe, controlled disk cleanup capabilities, minimizing helpdesk workload without compromising disk security or user privacy.
For more on creating and managing custom alerts and actions within ControlUp Edge DX, consult the official documentation at https://docs.controlup.com/edge and explore ControlUp Academy at https://cuacademy.controlup.com for training on extending ControlUp functionality.
Read the entire article here...
Read the entire article here...
Analyzing Windows Client Boot Time Delays: Using External Scripts to Generate Boot Performance Reports in ControlUp Environments
A community discussion sought an effective method to analyze Windows client boot times with detailed insights into the causes of any delays. The original inquiry focused on whether there was an existing script or dashboard capable of breaking down boot delays, as the environment faced issues with slow client startups. Such diagnostics would provide valuable information to address client performance problems.
In response, a community member shared a beta script designed as a boot analyzer, which generates an HTML report summarizing boot performance. This script creates an output that visually breaks down boot times, helping identify the components or processes causing delays. However, the script does not currently save boot information within the ControlUp platform because the ControlUp agent is not active during the Windows boot phase, preventing direct integration of boot data into ControlUp's indexes.
While the script is substantial and complex, it offers a practical starting point for environments needing detailed boot-time diagnostics. The contributor noted the lack of time to fully test writing the boot data to the ControlUp index but confirmed the HTML report format is functional and aesthetically clear. The shared approach highlights the current workaround for boot analysis within ControlUp environments: external data collection and report generation rather than native ControlUp indexing, due to agent limitations during system startup.
For users seeking to monitor boot performance in Windows clients using ControlUp, this solution involves running external scripts to analyze boot metrics and then reviewing detailed offline reports. Until ControlUp supports native boot-time data collection via its agent during the startup phase, such scripts provide the most direct method to diagnose and troubleshoot boot delays.
Read the entire article here...
Read the entire article here...
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...
Applying Permanent Filters to ControlUp Dashboards Based on Device Tags
In ControlUp, applying a permanent filter to a dashboard that restricts data to devices tagged with a specific label, such as "Eugene," is not natively supported. While global filters can be set to apply across all dashboards, they cannot be configured to be permanent for a single dashboard or to restrict data to devices with a specific tag.
A workaround involves bookmarking the URL of the dashboard after applying the desired filter. This method ensures that the dashboard opens with the filter applied, displaying only devices tagged with "Eugene." However, this approach has limitations:
- **Manual Application**: The filter must be manually applied each time the dashboard is accessed, as the URL does not retain the filter settings permanently.
- **URL Filter Bug**: There is a known issue with URL filters that is currently being addressed. This bug may affect the functionality of the URL-based filtering method.
For more detailed information on filtering devices by tags and creating customized views, refer to the ControlUp documentation on viewing your list of devices. ([support.controlup.com](https://support.controlup.com/docs/device-dashboard-overview?utm_source=openai))
As of now, there is no built-in feature in ControlUp that allows for the permanent application of a filter to a specific dashboard based on device tags. Users are advised to monitor updates from ControlUp for potential enhancements in this area.
For further assistance or to stay informed about updates, consider reaching out to ControlUp support or visiting the ControlUp Community forums.
([help.controlup.com](https://help.controlup.com/hc/en-us?utm_source=openai))
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...
How to Calculate and Display Compliance Percentage Using ControlUp JSON Query and Transformations
This discussion addresses how to display a compliance percentage in a ControlUp dashboard card based on two widget values: total devices and compliant devices. The goal is to calculate and show a compliance rate as a percentage, for example, showing 5% if 10 out of 200 devices are compliant. The solution involves using the ControlUp JSON builder with a custom query and transformation setup.
To achieve this, the key is to use the "CombineMetrics" plugin in the JSON configuration. This plugin allows the calculation of a ratio (a percentage) by specifying the compliant devices count as the numerator and the total devices count as the denominator. Participants shared examples modeled after an AI dashboard where a similar percentage metric—percentage of users accessing AI-related websites—is calculated by summing durations and using filters.
One example query includes the use of "cardinality" aggregation on device IDs, filtering by device groups and OS details to separately count total devices and compliant ones. This data is then fed into a transformation block that scales the ratio by 100 and applies precision to display the percentage nicely. The JSON snippet demonstrates how the numeratorNodeIds and denominatorNodeIds correspond to the compliant and total device counts, respectively, providing a ready-to-adapt template.
Additionally, the conversation touched on the potential for applying conditional palette colors to the percentage display, similar to gauges, to visually represent thresholds (e.g., red for 0%, orange at 50%, green at 100%). Though not yet implemented, this idea is being considered as part of ongoing UI improvements.
For further implementation guidance, ControlUp documentation on custom widgets and the JSON query builder is a useful resource at https://docs.controlup.com. The approach described can support not only two values but can be extended to combine multiple metrics as needed, providing flexible compliance and performance monitoring visualizations in ControlUp dashboards.
Read the entire article here...
Read the entire article here...
How to Use ControlUp Live View to Identify Processes Causing CPU Spikes in VDI Environments
When attempting to diagnose CPU spikes and identify the specific processes responsible using ControlUp, the most effective approach is to utilize the Live view, also known as the VDI page in the ControlUp Web UI. This view provides real-time, granular insights into process-level CPU consumption across virtual desktop infrastructure (VDI) environments. Unlike historical reports, which show aggregated past data such as CPU Utilization Max but lack immediacy, the Live view updates metrics approximately every three seconds, enabling administrators to track CPU spikes as they happen and correlate them with individual processes.
Accessing this Live view requires either appropriate licensing or configuration that may prompt for a user principal name (UPN) login depending on how ControlUp is set up in the organization. When correctly logged in, administrators can drill down into specific machines experiencing CPU spikes and see a detailed, sortable list of CPU-intensive processes. This functionality helps pinpoint the exact processes causing resource bottlenecks, which is critical since the total CPU utilization of a machine does not always equal the sum of all visible processes. This discrepancy arises because kernel interrupts and other system-level operations that consume CPU are not attributed to individual user processes.
Users noted that if access to the Live view is initially unavailable or the relevant VDI tab not visible, it may be due to missing licenses or particular configuration settings controlled by the ControlUp administrator in the environment. In such cases, reaching out to the administrator and providing the UPN for authentication often resolves access issues. Without this, troubleshooting CPU spikes becomes difficult, and users may resort to external scripting solutions like PowerShell, which can be less reliable and less integrated.
Once logged into the Live view, operators can monitor real-time CPU usage per user and process, identify the top five consumers, and respond quickly to performance incidents causing a slowdown in the VDI environment. While the Live view is potent for immediate troubleshooting, storing long-term granular process data in a live manner is impractical due to data volume and cost, so ControlUp uses historical reports for trend analysis. Overall, the Live view is regarded as an essential and powerful feature in ControlUp’s suite for understanding and resolving CPU utilization spikes in virtualized desktop environments.
For further information on configuring and accessing the Live view in ControlUp, administrators can consult the official ControlUp documentation at https://docs.controlup.com and the ControlUp Academy at https://cuacademy.controlup.com. These resources cover licensing requirements, configuration steps, and best practices for effectively using real-time monitoring to maintain optimal VDI performance.
Read the entire article here...
Read the entire article here...