A community member inquired about automating device group assignment in ControlUp based on a specific registry key value. The initial approach discussed involved writing a PowerShell script to read the registry key and create a custom index in ControlUp, which could then feed into a workflow for moving devices to the appropriate device group. This method also opened possibilities for using the data in dashboards, creating alerts for registry changes, and triggering remediation workflows.
A practical PowerShell script example was shared to demonstrate how to write, read, and output a registry key value under the current user (HKCU). This script was integrated with ControlUp’s Device Events by printing the output between defined event markers. Subsequently, a more detailed script was contributed, which collects registry information along with system and timestamp metadata, outputs it as a compressed JSON object, and supports error handling if the registry key access fails. This script is intended to run periodically to populate ControlUp’s data index, providing the basis for alerting and workflow triggers.
The recommended implementation steps include adding the script to the environment to gather registry data regularly, setting up alerts to trigger on specific registry values, and using ControlUp workflows with webhooks to move devices to the correct device groups based on the registry data. While alerts were initially used for this purpose, the community acknowledged the drawback of proliferation—needing many alerts for multiple groups—and expressed a preference to rely more on workflows for automation, preserving alerts for genuine issues.
To advance beyond alerts, the suggestion was made to leverage ControlUp’s API to retrieve custom data directly, enabling workflows to act on this real-time data without spawning numerous alerts. This approach supports scalable device management workflows, automating group assignments effectively. A recommendation was offered to engage ControlUp Customer Success Management (CSM) or Professional Services for further assistance with complex workflow setups integrating API data extraction. The discussion underscores the evolving use of ControlUp’s scripting, alerting, and workflow capabilities to streamline device group management based on registry key states.
For further reference, ControlUp’s official documentation on custom data scripting, workflows, and alerts can be found at https://docs.controlup.com, and detailed learning modules are available via ControlUp Academy at https://cuacademy.controlup.com.
Read the entire article here...
Printing Related Training & Support Archives
Printing training and support-related archives from inside the ControlUp Community on Slack.
Does the Bandwidth Limit metric come from the Citrix EDT logic?
A question was asked about the Bandwidth Limit metric from the Citrix EDT logic - this is estimated by sending two packets of known size and measuring the time it takes to transmit them. The metric is measured in Mbps and it should not be lower than 1 or 2 Mbps as Citrix is nimble in its bandwidth consumption. Thanks to @member for clarifying.
Read the entire article here...
Read the entire article here...
How to Sign ControlUp Scripts
A user asked how to best sign ControlUp scripts - either through buying a code-signing certificate or using KB guidance. It was suggested that scripts be imported into the SBA using the import button, as they can be too big for copy/paste, and a GitHub link was shared for a script which could be used to sign PowerShell scripts using a code-signing certificate.
Read the entire article here...
Read the entire article here...
