• Skip to primary navigation
  • Skip to main content
  • Skip to primary sidebar
  • Skip to footer
ControlUp Community

ControlUp Community

Connect, Learn, and Grow

  • Blog
  • Archives
  • Findings
  • Meetups
  • Videos
  • Events
  • Categories
    • ControlUp One Platform
    • ControlUp for Apps
    • ControlUp for Compliance
    • ControlUp Dashboards
    • ControlUp for Desktops
    • ControlUp for VDI
    • ControlUp Scripts & Triggers
    • ControlUp Synthetic Monitoring
    • ControlUp Workflows
  • Topics
    • Logos & Wallpaper
    • ControlUp.com
  • Join

ControlUp Community Training & Support Archives

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


Configuring ControlUp Employee Identification on macOS Devices Managed by Jamf

Posted on November 2, 2026

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 Aggregate Boolean Agent Status Metrics in ControlUp Dashboard Widgets by Restructuring Data and Using Multi-Widget Workarounds

Posted on October 31, 2026

A community member sought to create a ControlUp dashboard widget using a custom data source where each device has multiple Boolean metrics reflecting the status of installed management agents. The initial data structure was wide, with separate columns for each agent’s status per device. The user wanted to transform this into a long-format table that aggregates and counts the number of devices reporting `false` for each agent, effectively turning columns into rows and summarizing devices per negative status. The question was whether ControlUp’s widget capabilities, including `queryConfigs`, aggregations, or transformations, could natively support this pivot-and-count operation within a single widget. The response clarified that although ControlUp supports aggregations such as counting unique devices and allows multiple aggregations in a table widget (via the advanced "+extra metric" option), it does not currently allow multiple filters to produce multiple outputs combined into a single aggregated view with different filtered counts in one widget. The suggested workaround involved creating separate widgets for each agent status count, filtering each widget on true/false values individually. The community also highlighted that the ControlUp Grid viewer can display the raw record data per device, which is useful for detailed inspection but does not perform the desired pivot aggregation. A more structural solution proposed was to redesign the data model itself. Instead of a wide layout with one column per agent, organize the data in a long format, where each record contains a device ID, the agent name, and its installed status as a Boolean value. This normalized design permits grouping by both device and agent within a single widget, facilitating aggregation and counting where the agent’s status is `false`. This approach aligns better with ControlUp’s current analytical model and dashboard features. For now, native support for multi-query aggregation and output combination, similar to query builders in Grafana, does not exist in ControlUp dashboards but might be considered in future enhancements. Users seeking advanced cross-agent aggregation must either rely on multiple widgets, external data transformation before ingestion, or data model restructuring to achieve their goals. For more information on ControlUp dashboard widgets, custom data sources, and advanced JSON configurations, users can consult the official ControlUp documentation at https://docs.controlup.com, or explore the ControlUp Academy at https://cuacademy.controlup.com. Read the entire article here...

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

Posted on October 30, 2026

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 October 29, 2026

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 October 29, 2026

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...

Resolving RemoteDX Plugin Incompatibility During ControlUp Windows Agent 64-bit Upgrade

Posted on October 27, 2026

When upgrading the ControlUp Windows Agent (CWA) from a 32-bit to a 64-bit version, users may encounter an installation error related to the RemoteDX plugin, specifically involving the cuepux library. The log shows a warning indicating that third-party add-ons, including cuepux, are incompatible with the 64-bit application. The message references a saved JSON file listing the incompatible plugins and halts the installation process accordingly. The root cause is that the installed RemoteDX plugin version 2.4.2.136, although appearing to be 64-bit, is not compatible with the new 64-bit CWA. To resolve this, it is necessary to update the RemoteDX plugin to a more recent version that supports the 64-bit agent. ControlUp recently released updates to the RemoteDX/Remote Client plugin and the RemoteDX plugin installer for Citrix environments. The latest recommended installer versions are 1.0.8 or 1.0.9. These versions address compatibility issues that prevent the older plugin from functioning with the 64-bit CWA. Deployment methods vary depending on the environment. For organizations leveraging Citrix Cloud, the RemoteDX plugin can be updated through Citrix Client app management (formerly Global App Configuration service) under the Updates and Plug-ins section. However, if this service is not in use—such as in cases where organizations perform manual deployment—the update must be handled via existing software deployment systems like SCCM. It is important to note that the ControlUp Agent Manager automates only the agent updates and does not manage RemoteDX plugin deployment, requiring separate handling. Direct download links for the updated RemoteDX plugin installers are provided by ControlUp to facilitate straightforward manual deployment: - Version 1.0.9: https://downloads.controlup.com/RemoteDX/plugin-installer/RemoteDXPluginInstaller_1.0.9.msi - Version 1.0.8: https://downloads.controlup.com/RemoteDX/plugin-installer/RemoteDXPluginInstaller_1.0.8.msi Updating the RemoteDX plugin to one of these versions resolves the incompatibility issue and allows the successful installation of the 64-bit ControlUp Windows Agent. Users experiencing this error should ensure the latest compatible RemoteDX plugin is deployed in their environment according to their deployment capabilities. Read the entire article here...

Understanding OAuth and Application Registration in ControlUp’s Entra ID Integration

Posted on October 27, 2026

When integrating ControlUp with Microsoft Entra ID, two primary authorization methods are available: OAuth and Application Registration. Each method offers distinct functionalities and configurations, catering to different organizational requirements. **OAuth Integration** OAuth enables users to authenticate into ControlUp using their Entra ID credentials. This method requires setting up a Service Principal (Enterprise Application) within the Entra ID tenant. Administrators can manage this Service Principal, including restricting user access or revoking consent, independently of the global App Registration. The necessary permission for OAuth is `User.Read`, which allows ControlUp to read basic user attributes such as name and email address. However, OAuth does not inherently support automatic role assignments based on Entra ID group memberships. To achieve such functionality, an additional App Registration is required. ([support.controlup.com](https://support.controlup.com/docs/how-to-set-up-oauth-with-entra-id?utm_source=openai)) **Application Registration Integration** The Application Registration method involves registering an application within Entra ID and granting it specific permissions to interact with ControlUp. This approach is essential for features like automatic role assignments based on Entra ID group memberships. The required permissions include `User.Read.All`, `Group.Read.All`, `Application.ReadWrite.All` (necessary for automatic SAML setup), and `Policy.ReadWrite.ApplicationConfiguration` (also required for automatic SAML setup). After adding these permissions, administrators must grant admin consent for the application to function correctly. ([support.controlup.com](https://support.controlup.com/v1/docs/microsoft-entra-id-integration?utm_source=openai)) **User Identification in ControlUp** ControlUp identifies users based on their User Principal Name (UPN), which is typically their work email address. On Windows devices, ControlUp uses the account the user signed in with. On macOS, since there's no single sign-in UPN, ControlUp looks for a work email address in accounts signed in on the Mac. If ControlUp cannot identify the employee using a device, the device doesn't appear in any Employees dashboard and doesn't receive an Experience Score, though it still appears in the Devices view. ([support.controlup.com](https://support.controlup.com/docs/employee-identification?utm_source=openai)) **Conclusion** For organizations aiming to utilize OAuth with User Delegation in ControlUp, it's crucial to understand that while OAuth facilitates user authentication, it does not automatically assign roles based on Entra ID group memberships. To achieve this functionality, setting up an Application Registration with the appropriate permissions is necessary. Additionally, ControlUp identifies users based on their UPN, which is typically their work email address. Read the entire article here...

Resolving Condition Input Issues in ControlUp Workflows: Retyping and Node Reconnection Best Practices

Posted on October 27, 2026

A community member reported encountering an issue in ControlUp workflows involving "if/then" conditional statements. The problem occurred when previously accurate conditions appeared not to function correctly until the user cleared the input fields and retyped the values. This behavior suggested that breaking and re-establishing the connection between workflow nodes could affect how input boxes processed or retained their values. Specifically, conditions involving tag lists and byte size comparisons behaved inconsistently unless manually re-entered. The user shared JSON data illustrating the conditions in question, which compared a calculated byte size against a threshold and checked whether a device tag list did not contain a specific tag ("dna_created"). Although the raw conditions were valid and logically sound, the workflow returned unexpected results until the inputs were cleared and retyped. Upon removing and manually reentering the lookup fields, the condition evaluations worked as intended. Further investigation revealed that the issue could not be consistently reproduced and appeared to resolve itself after refreshing or reconnecting the nodes. A follow-up confirmed that the workflow conditions were working correctly in later tests, properly evaluating tag presence and logical operators to produce the expected false result when the tag list included "dna_created." This suggests a transient glitch related to how ControlUp’s workflow editor handles input persistence or data-binding in condition nodes, particularly with dynamic references or lookups. For users experiencing similar issues, a recommended workaround is to manually clear and retype values in the "if/then" condition inputs to force a refresh of the connection state. If the issue persists, recreating or reconnecting the nodes may help restore proper evaluation. Keeping ControlUp updated to the latest version may also mitigate such transient inconsistencies. For more details on workflow conditions and node behavior, refer to ControlUp’s official documentation on workflows and condition nodes at https://docs.controlup.com/solutions/workflows. Read the entire article here...

How to Collect and Visualize Custom Script Data from VDI Sessions in ControlUp Dashboards

Posted on October 23, 2026

A community member inquired about the possibility of collecting custom data extracted from scripts running within Virtual Desktop Infrastructure (VDI) sessions and then using that data to create a ControlUp dashboard. Specifically, the user wanted to determine which users were utilizing Macros in Excel during their VDI sessions, with a simple Yes or No indicator, and then visualize this information on a dashboard. Alternatively, they asked if it was feasible to query session-specific data, such as the history of active URLs accessed during a VDI session, and build a corresponding dashboard to monitor those URLs. A ControlUp expert clarified that while ControlUp does not natively collect or display custom data directly from VDI environments by default, it provides a flexible mechanism to capture and associate additional data via the use of tags and supplemental metadata. These tags can be applied to entities within the ControlUp environment, including sessions or machines, and can be leveraged to filter and create richer dashboards. The expert pointed to the official documentation covering how to add a tags column to the information grid, which facilitates easier tracking and visualization of tagged data ([https://support.controlup.com/docs/add-tags-column-to-information-grid](https://support.controlup.com/docs/add-tags-column-to-information-grid)). The recommended approach involves writing external scripts or monitoring tools that extract the needed data—such as whether Excel macros are in use or the URLs accessed during a session—and then injecting this information as tags or extra columns to the associated VDI sessions in ControlUp. Once this data residence is established via tagging, ControlUp’s advanced dashboarding and reporting features can be used to create custom dashboards displaying the binary Yes/No macro usage status or detailed URL access history across sessions. This method requires integrating ControlUp with custom monitoring or scripting workflows that feed data into the platform through tags. It is not an out-of-the-box feature but leverages ControlUp’s extensibility for environments needing custom telemetry. Users aiming to build such solutions should also consider ControlUp’s APIs and scripting capabilities detailed in the official ControlUp Knowledge Base and Academy resources at https://docs.controlup.com and https://cuacademy.controlup.com for advanced custom data reporting. Read the entire article here...

Managing Manual Software Installs on Developer Laptops Using ControlUp’s Installed Apps Index and Shadow IT Prompt

Posted on October 23, 2026

Several ControlUp community members discussed the challenge of identifying software manually installed by local administrators on developer laptops and other endpoints. This issue often complicates software inventory management and security auditing, as organizations need to distinguish between authorized baseline applications and additional, manually installed programs. The core difficulty arises from the fact that ControlUp’s data collection primarily tracks which applications are installed via its installed_apps index, but does not inherently record the installer’s identity or differentiate between default baseline software and manual admin installs. Without this attribution, it becomes tricky to pinpoint deviations from standard configurations. One suggested approach is to define a list of default or approved baseline applications and then use queries to highlight deviations from that list, effectively flagging manually installed or unauthorized software. A community member also recommended leveraging existing ControlUp content, specifically the Shadow IT prompt found in the prompt library under the security category. This prompt is designed to assist in identifying applications outside the known or approved inventory, which aligns well with the problem of detecting non-baseline, admin-installed software. Experimenting with this prompt, in combination with custom baseline definitions, provides a practical investigation method using the ControlUp platform’s Canvas feature and alerting capabilities. Overall, addressing this use case requires a combination of custom baseline software lists, regular monitoring via the installed_apps index, and making use of security-focused prompts like Shadow IT. While ControlUp does not automatically track the installer identity, these strategies enable administrators to gain better visibility into manual software installations and maintain tighter control over endpoint configurations. Read the entire article here...
  • « Go to Previous Page
  • Page 1
  • Page 2
  • Page 3
  • Page 4
  • Interim pages omitted …
  • Page 180
  • Go to Next Page »

Primary Sidebar

ControlUp Academy

Enroll in ControlUp Academy for expert-led technical training, equipping you with skills to effectively deploy, manage, and grow your ControlUp investment.

Learn here >

Rotating Images

Hidden Gem from our Community on Slack!

ControlUp Betas - What's Coming Next?
NEW ControlUp Features - Stay Up-to-Date!
ControlUp Scripts - Scripting, Zero to Hero
Latest KB Articles - Be the First to Learn

Video Tutorials Library

Visit our technical how-to videos, offering step-by-step tutorials on advanced features, troubleshooting, and best practices.

Watch here >

ControlUp Blog

Check out the ControlUp blog for expert advice and in-depth analysis.

Read here >

ControlUp Script Library

Visit the ControlUp technical script library, which offers a multitude of pre-built scripts and custom actions for your monitoring and troubleshooting requirements.

See here >

ControlUp Support

Visit the ControlUp support home and to delve deeper into ControlUp DEX solutions.

Browse here >

Footer

      

ControlUp Community
Of Techie, By Techie, For Techie!

Terms of Use | Privacy Policy | Security
Dive Deeper, Learn more at ControlUp.com

  • facebook
  • twitter
  • youtube
  • linkedin

© 2023–2026 ControlUp Technologies LTD, All Rights Reserved.

We use cookies to ensure that we give you the best experience on our website. by continuing to use this site you agree to our Cookie policy..