ControlUp Community

Connect, Learn, and Grow

ControlUp Scripts & Triggers Training & Support Archives

ControlUp Script and Trigger training and support-related archives from inside the ControlUp Community on Slack.

Understanding Logon Duration Metrics in ControlUp: Differences Between Console and Analyze Logon Duration Script

Posted on

A discrepancy was observed between the "Logon Duration" metric displayed in the ControlUp console and the results produced by the "Analyze Logon Duration" (ALD) script, with the two values differing significantly. This raised questions about where to begin troubleshooting and how these two measurements relate. It was clarified that the ALD script and the "Logon Duration" metric in ControlUp use different measurement points, meaning their values are not directly comparable. The ALD script requires specific prerequisite audit policies to be enabled on target systems to function correctly, as detailed in ControlUp’s support documentation at https://support.controlup.com/docs/enable-auditing-for-analyze-logon-duration-script. If these audit policies are disabled or misconfigured, the ALD script’s accuracy will be compromised. In this particular case, the use of ControlUp's Disk Monitor revealed excessive disk writes related to enabled audit policies, which led to those audit policies being disabled to reduce disk IO. Disabling the audit policies impacted the ALD script’s ability to provide accurate logon duration measurements. This highlights the dependency of the ALD script on proper audit policy configuration for precise tracking. Regarding which method to use, it is recommended to use the Digital Employee Experience (DEX) console metric for initial logon duration screening. For more detailed and in-depth analysis, the ALD script should be employed, provided the prerequisite audit configurations are correctly set up. This distinction ensures users leverage each tool according to its strengths: quick overview versus detailed investigation. Read the entire article here...

Handling Alert Storms and Outages in ControlUp Scoutbees: Current Best Practices and Upcoming Features

Posted on

During an internet connectivity outage in Italy, a large volume of Scoutbees alerts was triggered due to multiple login request failures, resulting in an alert storm. This situation prompted a request for a dependency model that would suppress downstream alerts when a critical component like a gateway is detected as unavailable. Alternatively, the user inquired about automatically triggering a maintenance window to temporarily disable alerts for affected scouts during such outages. To address this, the current recommended approach involves tuning alert settings to reduce noise while preserving important signals. Key adjustments include configuring alerts to notify only when test results return to normal, thereby limiting notifications to one alert at the start of an issue and one upon resolution. Additionally, increasing the threshold for consecutive failed tests before sending an alert helps ignore brief transient failures but still catches sustained outages. These simple changes significantly reduce alert volume during connectivity issues without missing critical events. Looking ahead, the ControlUp team is actively developing a feature to enable maintenance windows by tag. This will allow users to silence all scouts associated with a specific tag—such as “italy”—with a single action during known problems or outages. This functionality aims to streamline manual alert silencing in complex environments without risking important signals being suppressed automatically. Automatic suppression of downstream alerts in the event of gateway failure is discouraged since synthetic monitoring is designed to reflect real user experience, and connectivity failures are essential to surface. Until the tag-based maintenance feature becomes available, the user opted to implement manual maintenance windows that disable alerts during outages to avoid missing issues outside planned maintenance periods. The approach balances the need to reduce alert fatigue while ensuring critical incidents are not overlooked. The ControlUp team remains open to direct conversations with users to refine upcoming features for scenarios such as this. For further detail on tuning Scoutbees alerts and maintenance windows, see the ControlUp documentation at https://docs.controlup.com. The upcoming maintenance-by-tag feature will enhance flexibility in managing alert noise during large-scale or regional disruptions. Read the entire article here...

Handling Duplicate Entries in ControlUp Custom Dashboards with Time-Series Data Aggregation

Posted on

In a ControlUp Community discussion, a user presented a scenario involving a custom data index used to track daily speed test results—upload speed, download speed, and latency—recorded per computer. The data is accumulated over time without overwriting previous entries, enabling the calculation of 30-day averages and trend analysis. However, when visualizing this data on custom dashboards with multiple panels like gauges, tables, and grids, the user encountered the problem of duplicate entries for the same computer appearing multiple times within the selected date range (e.g., last 10 days). The challenge was to display only the most recent entry for each computer while preserving all historical data in the index. The core insight shared by community members was that raw data views such as grids inherently show all individual records, which results in duplicates when multiple entries per device exist over the date range. To resolve this, it is recommended to use aggregation functions that summarize data at the device level rather than displaying raw records. Aggregates can consolidate multiple entries for the same device, ensuring that each device appears only once, typically reflecting a calculation like the most recent value or an average over the period. A practical suggestion was to avoid the raw grid view for this purpose and instead configure the dashboard panels to aggregate results based on a unique device identifier, such as device_id, rather than the device name. Aggregating on device_id ensures that all entries related to the same device are grouped properly. This method allows viewers to see one summarized record per device that represents the latest or otherwise relevant aggregated values. Without access to the user’s custom index or dashboard JSON configuration, the community could not provide a definitive tweak but highlighted the importance of aggregation and key field selection. This approach maintains the historical dataset intact, supporting trend analysis while enabling concise visualization devoid of duplicate device entries. Users working with ControlUp custom indexes and dashboards that store multiple time-series records per device should leverage aggregation functions on unique device identifiers within their panels to effectively manage display deduplication over time. For further guidance on using ControlUp dashboards, filters, and aggregation functions, see the ControlUp documentation at https://docs.controlup.com and ControlUp Academy tutorials at https://cuacademy.controlup.com. Read the entire article here...

How to Use ControlUp AI Decision Nodes to Trigger Conditional Script Execution in Automated Workflows

Posted on

A user sought advice on creating an automated workflow in ControlUp that uses the AI node to diagnose issues and then runs specific scripts based on the AI’s suggested solutions. The user wanted the flow to dynamically execute one or two scripts out of a set of five, depending on whether the AI recommended actions such as a repair or a driver update. The solution involved leveraging an AI decision node within ControlUp’s automation workflow. This AI decision node allows the configuration of custom questions and multiple outputs based on the AI’s analysis. By setting conditions within this node to evaluate the AI’s recommended solution, the workflow can branch and trigger particular script nodes accordingly. Using the AI decision node to branch the workflow, users can effectively map various AI-generated solutions to corresponding remediation scripts. For example, if the AI suggests a system repair or a driver update, the flow can be directed to execute the relevant script via a run script node. This approach supports flexible and conditional automation based on AI diagnostics within ControlUp’s process automation environment. Overall, integrating the AI decision node with conditional outputs enables sophisticated, solution-driven scripting workflows. Users can build customized automation flows that respond dynamically to AI findings, improving IT issue resolution efficiency. For more detailed instructions on AI node configuration and automation flows, users should reference ControlUp’s official documentation and resources such as https://docs.controlup.com. Read the entire article here...

How to Set Up Workflow Failure Notifications in ControlUp

Posted on

ControlUp has introduced a new feature to address the need for workflow failure alerts. Previously, users had to rely on external monitoring tools to detect when a workflow failed to run or encountered an outage or degradation. Recognizing this gap, ControlUp released a built-in notification system that notifies users directly when a workflow fails. This notification functionality is integrated into the "Start" node of ControlUp’s workflow designer. Within this node, there is a "Notification" section that allows users to configure alerts for different events, including both failed and successful workflow runs. Currently, the notifications can be sent via email, Slack, and Microsoft Teams, covering the most common communication platforms used in IT environments. This feature is designed to provide immediate visibility of workflow execution status directly within ControlUp, eliminating the need to rely solely on external monitoring solutions for this purpose. Users can set up their preferred notification channels and receive timely alerts to promptly respond to workflow issues, improving operational efficiency and reducing downtime. ControlUp welcomes feedback from users to enhance this notification capability further. Those interested in configuring or testing the new workflow failure notifications should look for the "Notification" section in the Start node of their workflow setups. For additional information or updates on ControlUp workflows and notifications, users can refer to official documentation on the ControlUp Knowledge Base at https://docs.controlup.com or explore related courses on the ControlUp Academy at https://cuacademy.controlup.com. Read the entire article here...

Configuring ControlUp Employee Identification on macOS Devices Managed by Jamf

Posted on

ControlUp's Employee Identification feature supports macOS devices, including those managed by Jamf. However, for accurate employee identification on Macs, it's essential to configure an approved domains list. This list specifies which domains are recognized for employee identification purposes. Without this configuration, macOS users may not be identified correctly. **Configuring Approved Domains on macOS:** 1. Navigate to **Settings** > **Experience Score** > **Privacy** in the ControlUp console. 2. Click **+Approve Domain**, enter the desired domain (e.g., `controlup.com`), and click **Submit**. 3. Repeat the process for each additional domain you wish to include. It's important to note that on macOS, the approved domains list requires exact domain matches. For instance, if `controlup.com` is approved, subdomains like `uk.controlup.com` must also be added separately to ensure proper identification. ([support.controlup.com](https://support.controlup.com/docs/employee-identification?utm_source=openai)) **Integration with Jamf and Entra ID:** In environments where macOS devices are enrolled via Jamf and utilize Entra ID for authentication, the approved domains list becomes particularly crucial. The domain part of the Entra ID User Principal Name (UPN)—the portion after the `@` symbol—must be included in the approved domains list for successful employee identification. For example, if users authenticate with `user@controlup.com`, then `controlup.com` should be added to the approved domains list. This configuration ensures that ControlUp can accurately identify employees based on their Entra ID credentials. ([support.controlup.com](https://support.controlup.com/docs/employee-identification?utm_source=openai)) **Compatibility Matrix:** ControlUp offers a comprehensive monitoring and management solution across various operating systems, including Windows and macOS. While many features are supported on both platforms, there are some differences: - **Endpoint & App Monitoring:** Supported on both Windows and macOS. - **Device Health Scores:** Supported on both Windows and macOS. - **Remediation Actions & Scripts:** Supported on Windows; on macOS, only partial support is available, including actions like reboot, clear user profiles, and factory reset. Scripts are not supported on macOS. - **Automated Optimization:** Supported on Windows; not supported on macOS. - **Remote Assist & Control:** Supported on Windows and macOS, with some limitations on macOS. - **Employee-centric Dashboards & Experience Scoring:** Supported on Windows; not supported on macOS. For a detailed comparison of supported features across operating systems, refer to the [Comparison of Supported Features Across OS Platforms](https://support.controlup.com/docs/comparison-of-supported-features-across-os-platforms). By configuring the approved domains list appropriately and understanding the compatibility matrix, organizations can ensure effective deployment and management of ControlUp's features on macOS devices, leading to enhanced digital employee experience and operational efficiency. Read the entire article here...

How to Change the Device Registration Code for ControlUp Windows Agents Without Reinstalling

Posted on

The Windows Agent Manager for ControlUp stores the Device Registration Code (DEVREGCODE) in the system registry at the location HKEY_LOCAL_MACHINE\SOFTWARE\Avacee\SIP, specifically under the value named DeviceRegistrationCode. This registry entry is critical for device identification and communication with the ControlUp environment. When a machine with an outdated registration key falls out of the monitoring system and then comes back online, it can cause connectivity or recognition issues due to the persistent old registration information. It is possible to change the Device Registration Code without performing a full reinstall of the Windows Agent. This can be done by editing the registry value directly at the specified path. After modifying the DeviceRegistrationCode, it is necessary to restart the ControlUp agent service for the change to take effect. However, simply changing the registry value is not sufficient if the device has previously registered with ControlUp, as cached identity data may cause the agent to continue using the old credentials. To fully re-register the device within ControlUp, it is also required to delete specific cached files that store device tokens. These files are located in the directory C:\ProgramData\Avacee\sip_agent\cachefiles and include uid.txt and DeviceAccessToken.txt. Removing these files forces the agent to discard the old cached tokens and register anew using the updated Device Registration Code. This approach facilitates scripted remediation, making it practical to deploy changes via Group Policy Objects (GPO), Microsoft Intune, or similar device management tools. However, it is strongly advised to test such changes on a limited set of devices first to confirm that the process completes successfully and does not inadvertently disrupt device monitoring. In summary, updating the Device Registration Code on a ControlUp-managed machine without reinstalling is achieved by directly editing the registry, restarting the agent service, and clearing cached device token files to force re-registration. This method is useful when older registration keys cause devices to lose or restore connectivity improperly in ControlUp environments. Read the entire article here...

Understanding ControlUp Compliance Update Latency and Best Practices for Timely Patching

Posted on

When organizations use ControlUp for Compliance to monitor and manage application updates, a common question arises regarding how quickly updates, such as security patches for applications like Google Chrome, become available through the platform’s compliance module. This is particularly important when timely patching is critical to address vulnerabilities identified by CVEs. The update availability process in ControlUp for Compliance involves several stages. First, a new application version must be included in the patch catalog, which is derived from a third-party patch feed. The speed at which a new version appears in this feed varies by application vendor and release and is outside ControlUp’s direct control. For major browsers like Chrome, this step is typically quick but not guaranteed within a specific timeline. Once the patch feed updates, ControlUp scans it every three hours to update the catalog. The tenant then checks for a catalog update approximately every hour, resulting in roughly a four-hour delay on ControlUp’s side before the tenant receives the latest version information. After that, devices report their compliance status based on their scanning schedule, meaning the frequency with which devices scan for updates directly impacts how soon they reflect new versions. The installation or remediation of updates follows according to template settings, including remediation windows and any manual triggers from administrators. For sensitive environments requiring rapid response, such as those impacted by CVEs, recommendations include increasing scan frequency to daily or more, configuring remediation windows to allow timely installations, and leveraging the ControlUp Content Delivery Network (CDN) with the “Allow CDN bypass for self-updating applications” option (available starting with agent version 1.6). This setting enables applications like Chrome to update directly from the vendor, speeding up patch delivery. Additionally, maintaining the application’s native auto-update functionality provides a primary defense layer, with ControlUp Compliance providing oversight to catch devices where auto-update failed. In practice, new Chrome updates have been observed to appear in Compliance the day after a vendor’s release, although this example should not be considered a guaranteed SLA due to variations in vendor feeds and catalog processing times. Windows patching follows a similar cadence, typically aligned with Microsoft’s Patch Tuesday schedule, and similarly may take up to three days to reflect in the catalog after release. Further details on scheduling scans and managing templates in ControlUp for Compliance are available in the official documentation here: https://support.controlup.com/docs/controlup-for-compliance Read the entire article here...

How to Refresh Updated Subflow Input Variables in ControlUp Flows Without Re-adding the Node

Posted on

When working with ControlUp’s flow automation, users may encounter a situation where updating the input variables of a subflow does not immediately reflect those changes in the parent flow’s Run sub flow node. This occurs because the Run sub flow node loads the subflow’s input variables only once per parent flow page load. Consequently, if you modify the subflow inputs but remain on the same browser tab with the parent flow loaded, the Run sub flow node can continue to display the previous set of inputs, giving the appearance that the updates have not applied. This behavior is by design and there is no dedicated “refresh” button to update the inputs dynamically within the same session. However, it is not necessary to remove and re-add the subflow node to refresh the inputs. The recommended procedure to see the updated input variables in the parent flow is to first save the changes made to the subflow, then perform a browser page refresh (such as pressing F5) on the parent flow’s tab. After the page reloads, opening the Run sub flow node will reveal the updated input fields. Existing input values will be preserved through this process, allowing the user to simply add values for any new inputs before saving the parent flow. It is important to note that if any new input variables introduced in the subflow are not filled in within the parent flow’s Run sub flow node, those inputs will have empty values when the subflow executes. Therefore, users should ensure that all necessary new inputs are populated to avoid unintended empty values during runtime. This behavior is consistent across current ControlUp flow environments and is not indicative of an error but rather a reflection of how input variables are cached per browser session for performance reasons. For further details on managing flows and subflows in ControlUp, users can consult the ControlUp documentation at https://docs.controlup.com, which provides comprehensive guidance on flow design and best practices. This approach ensures users can effectively manage input variable updates without unnecessary node removal, streamlining the development and maintenance of complex automated workflows. Read the entire article here...