A new user of ControlUp sought guidance on building workflows to manage device organization, specifically adding devices to groups and tagging them. The user was attempting to create a workflow starting with a "List Devices" step, filtering devices by an ID pattern containing "HR," followed by a "Set Group" step intended to assign those devices to an "HR" group. However, uncertainty arose over what value to enter in the "Device ID" field within the "Set Group" step.
A key insight provided by community members clarified that the "List Devices" action returns multiple device records, each representing a unique device. Consequently, the "Set Group" step cannot directly accept multiple device IDs at once in a simple field. Instead, it requires isolating each device's ID through iteration. This can be accomplished by using an array to collect the IDs and then looping through the array to apply the group assignment individually to each device. This approach ensures that each device is addressed correctly when setting group membership.
Further advice noted that an alternative and potentially more streamlined approach is to assign the group at the time of agent deployment. According to ControlUp's official documentation on agent installation and distribution (https://support.controlup.com/docs/edge-dx-agent-distribution-and-installation-for-windows#installation-methods), groups can be set during the agent installation process itself, which might simplify workflows where initial grouping is critical.
For complex or specific setup requirements, it is recommended to consult your ControlUp Customer Success Manager (CSM), who can provide tailored support based on your environment and goals. This guidance should help new users effectively automate device grouping and tagging using ControlUp workflows while leveraging best practices outlined in the official resources.
Read the entire article here...
ControlUp for Desktops Training & Support Archives
ControlUp for Desktops (Edge-DX) training and support-related archives from inside the ControlUp Community on Slack.
Understanding and Managing Device Online Status Timeout in ControlUp
In a recent discussion regarding device status indicators within ControlUp, a user inquired about the possibility of customizing the timeout period that determines when a device’s online status changes from a green dot to gray after losing connection. Currently, the system shows a green dot for devices that have been contacted within the last 60 minutes. The user wanted to reduce this timeout to 10 minutes so that devices appear offline sooner after losing connection.
It was clarified by a ControlUp expert that the 60-minute window for displaying a device as online is a platform-level behavior that is hardcoded and currently not adjustable by tenants or administrators. The ControlUp agent operates on a fixed heartbeat cycle, and the online or offline status indicator is calculated server-side based on this fixed threshold. As such, there is no existing setting within the Extended Settings or any other configuration that allows users to shorten this timeout period.
Since this timeout value is not configurable via the UI or Extended Settings, changing it would require a formal feature request to ControlUp’s development team. For now, the 60-minute heartbeat interval remains the standard for determining online device status, and users must expect the green dot to persist for up to one hour after the last successful contact. This behavior is consistent and reliable to avoid fluctuating device statuses due to shorter network interruptions.
For more detailed information on ControlUp agent heartbeat and device status indicators, users can consult the ControlUp documentation and knowledge base at https://docs.controlup.com or explore related training resources on the ControlUp Academy at https://cuacademy.controlup.com.
Read the entire article here...
Read the entire article here...
Status and Options for Ivanti Neurons ITSM Integration with ControlUp
ControlUp currently offers a native, first-party integration exclusively with ServiceNow for IT service management (ITSM) purposes. This integration provides advanced functionality beyond typical ticket creation: it can update an originally created ticket automatically if the same issue recurs, close the ticket when the issue resolves, and reopen it if the problem reappears, based on configurable recurrence and timing settings. Additionally, this ServiceNow integration is embedded directly into the device overview and specific device details user interface within ControlUp, providing seamless operational visibility.
Other ITSM systems are supported primarily through ControlUp Workflows, which offer integration capabilities with several platforms including Jira Service Desk, Freshservice, Zendesk, TOPdesk, and Halo ITSM, using broad REST-based connectivity. ManageEngine ServiceDesk Plus and its on-premises version also have integration options available behind feature flags. While Jira is integrated for workflows, it does not yet have a native ControlUp integration matching ServiceNow’s level of direct functionality.
Regarding Ivanti Neurons ITSM, there is currently no native or first-party integration with ControlUp. No active development plans or timelines have been announced for such an integration. Ivanti Neurons is also not included in the existing set of ITSM connectors available in ControlUp Workflows. However, users interested in integrating Ivanti Neurons can leverage the Workflows platform’s custom integration feature, which allows interaction with Ivanti’s REST API to build tailored solutions fitting organizational needs. Although this requires some configuration effort, it is the recommended alternative until an official integration is developed.
The ControlUp team has acknowledged requests for additional native ITSM integrations beyond ServiceNow, including Ivanti Neurons and Jira, and has indicated these will be considered for future roadmap development. However, no estimated time of arrival (ETA) is provided at this stage. For now, leveraging the robust Workflows engine with available connectors and custom API integrations offers the best path forward for integrating ITSM systems other than ServiceNow.
For detailed guidance on configuring Workflows, custom integrations, and the native ServiceNow integration, users can refer to ControlUp’s official documentation at https://docs.controlup.com and the ControlUp Academy at https://cuacademy.controlup.com.
Read the entire article here...
Read the entire article here...
Automating Detection and Remediation of Stuck BitLocker Encryption on Windows 11 Endpoints with ControlUp Real-Time Automation Engine
When deploying hundreds of Windows 11 endpoints managed by Intune, a common issue with BitLocker encryption is that the process sometimes becomes stuck at a certain percentage completion. While manually pausing and restarting the encryption process resolves the issue within minutes, automating this detection and remediation can save considerable time and ensure consistent endpoint security.
Using ControlUp Real-Time Automation Engine (CU4D), such automation is achievable by leveraging scripted detection and remediation. One approach is to create a single script that both detects the encryption status and initiates a restart of the encryption process if it remains stuck at the same percentage. This script can be deployed across all affected devices and scheduled to run periodically, for example, once per day, to identify any stuck BitLocker jobs and resolve them promptly.
A more modular approach involves creating two separate scripts: a detection script and a remediation script. The detection script would check the current encryption percentage, and if it identifies a stuck state, it writes the status to a custom index attribute within ControlUp. An alert can then be configured based on the value of this custom attribute. When the alert triggers due to a stuck encryption status, the remediation script executes automatically to restart the BitLocker encryption, ensuring a timely resolution without manual intervention.
This method harnesses ControlUp's ability to store custom scripted outputs in custom indices and link those to alert triggers, thus providing a robust, automated way to handle encryption stalls on Intune-managed Windows 11 devices. For further details on configuring custom scripts, custom indices, and alerts in ControlUp, administrators can refer to ControlUp's documentation at https://docs.controlup.com and explore automation capabilities in the ControlUp Academy at https://cuacademy.controlup.com.
Read the entire article here...
Read the entire article here...
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 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 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...
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...
Understanding ALERT RULES Licensing and Usage in ControlUp One EVENTS Tab
Within the ControlUp One platform, the EVENTS tab includes an ALERT RULES section that is specifically designed for ControlUp for Desktops (CU4D). Users who do not have a CU4D license will encounter a license error when accessing the ALERT RULES tab, even though other areas like OVERVIEW and EVENT DETAILS function normally. This is because the ALERT RULES feature is directly tied to CU4D licensing and capabilities.
The ALERT RULES in ControlUp One covers alerting for CU4D, ControlUp for VDI (CU4VDI), and Synthetic Monitoring; however, the creation and management of alert rules within this tab are exclusive to CU4D. For alerting related to ControlUp for VDI and Synthetic Monitoring, users must configure those alerts within their respective products. Once alerts are configured in each solution, they will be aggregated and displayed together in ControlUp One for centralized monitoring.
In summary, the ALERT RULES function in the ControlUp One EVENTS tab is dedicated to CU4D alert creation, and attempting to access this function without the proper CU4D license will trigger a license error. Alert management for CU4VDI and Synthetic Monitoring requires using those individual products’ alerting tools, after which their alerts become visible collectively within the ControlUp One interface. This division maintains clear licensing boundaries and functional segregation across ControlUp’s different monitoring products.
For more information, see ControlUp’s official documentation on alerting and licensing at https://docs.controlup.com and explore the ControlUp Academy for training on alert configuration and best practices at https://cuacademy.controlup.com.
Read the entire article here...
Read the entire article here...
How to Enable File Browsing in ControlUp’s File Browser by Configuring Role Permissions
A common issue encountered with ControlUp's File Browser feature is the inability to see any files within a user's system during a remote session, despite being able to navigate folders. This typically occurs when the appropriate permissions are not enabled for the user role in ControlUp. For example, a user attempting to retrieve log files without interrupting a session might notice that the file list remains empty, even though directories are visible.
The root cause is often related to role permissions. By default, the built-in Admin role in ControlUp does not have the File Browser permission enabled for viewing files. To resolve this, administrators need to create a custom role that explicitly grants this permission. Specifically, under Device Permissions, navigating to Remote Management > Management > File Browser, the administrator must set the scope to allow users assigned this role to view files.
Once the custom role is created with the correct File Browser permissions, it is possible to assign the user both the built-in Admin role and this new custom role simultaneously. ControlUp's role-based access control supports multiple role assignments per user, enabling flexible and granular permission management without removing any existing higher-level roles such as Admin.
In summary, to access files via ControlUp’s File Browser, ensure that the user has a custom role with the "View Files" permission under File Browser enabled. This role can be combined with the default Admin role, allowing complete management capabilities while enabling file browsing. For detailed role creation and permission configuration instructions, refer to ControlUp's official documentation on role management at https://docs.controlup.com.
Read the entire article here...
Read the entire article here...