• 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 for Desktops Training & Support Archives

ControlUp for Desktops (Edge-DX) training and support-related archives from inside the ControlUp Community on Slack.


Understanding and Aggregating ControlUp process_stops Data for Application Usage Dashboards

Posted on November 9, 2026

The discussion centers on building an Application Usage dashboard leveraging the ControlUp `process_stops` index and addresses several technical questions related to data collection, metric definitions, and field completeness. Data from clients are collected per process exit event, with each process stop generating a record. However, data upload to the backend is batched rather than immediate, using cache files that upload roughly every 10 minutes. This means a slight delay exists between the process exit and when the data becomes available in the index. For aggregation, timestamps such as `stoptime` or `starttime` should be used as the event time, not the record creation time. Regarding the definitions and units of key metrics like `averageworkingset_long`, `totalcputime`, or `average_user_input_delay`, no official public documentation explicitly details these metrics at field level. Users are encouraged to utilize the ControlUp AI Assistant to obtain clarifications. General ControlUp documentation may offer broader context, but precise field definitions are typically obtained through these support channels. The `publisher_name` field may be inconsistently populated for the same process version, such as `mspaint.exe 11.2609`. This is because `publisher_name` is derived from executable file metadata or Authenticode signatures at the time the stop record is finalized. If the process terminates too quickly or the file metadata cannot be accessed—common in WindowsApps or MSIX environments—this field can be blank. Filtering results with `ispartial = false` helps ensure higher-quality data where `publisher_name` is meaningful, though blanks can be coalesced to "Unknown" or reports can group by additional identifiers like process path or file version. The `ispartial` flag indicates completeness of core stop/performance data but does not guarantee all enrichment fields like `publisher_name` or `upn` are filled. The `upn` (User Principal Name) field, representing the user context, is also sometimes missing. This occurs when the process runs under system or service accounts, when only a username or SID is available without a UPN, or when no meaningful interactive user is associated with the process ID. This variability is expected in diverse Windows session or security contexts. For aggregation and analysis, it is advised to use `stoptime` or `starttime` as the primary timestamps and group data by friendly process names or combinations of process name and version/path as needed. Nullable metrics such as input delay or network fields should be explicitly filtered or appropriately handled when aggregating. Multiple rows often represent distinct instances or sessions rather than duplicates. An alternative data source, the `app_focus` index, provides per-minute records of an application's focus time and typically offers richer user identity and application name details. However, `app_focus` does not track discrete process launches as accurately as `process_stops`. Use cases focused on launch frequency benefit from the `process_stops` data, whereas `app_focus` better reflects actual user engagement duration with an application window. Finally, a notable resolution mentioned was that the `upn` omission was fixed by updating the domain list in Employee settings, which contained only a single domain. Also, `publisher_name` is updated only once per day per process, which can affect its consistency across records. If persistent issues arise, it is advisable to open a support ticket for deeper investigation and to provide sample data for analysis. For more details on ControlUp metrics and indexing, users can refer to the ControlUp documentation at https://docs.controlup.com and explore interactive help via the ControlUp AI Assistant. Contact ControlUp support at support@controlup.com for unresolved cases or to report suspected data enrichment issues. Read the entire article here...

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

Troubleshooting ControlUp Endpoint Installation Issues: Logs, Version Control, and Deployment Guidance

Posted on October 9, 2026

When troubleshooting issues with ControlUp endpoint installations where the Agent Manager installs correctly but additional components like SIP, EdgeDX, or Remote DX do not, the primary locations for diagnostic information include the Windows Event Viewer (Application logs) and the folder at C:\ProgramData\ControlUp\Logs. However, users have reported that this logs folder might sometimes exist but be empty, making Event Viewer logs the primary source for troubleshooting. One potential root cause identified is related to the Version Control settings in the ControlUp portal. These settings can delay or prevent the deployment of additional components beyond the Agent Manager. Verifying and adjusting the Version Control configuration is recommended to ensure it is not interfering with installation timing. Besides configuration settings, antivirus or endpoint security solutions frequently interfere with ControlUp installations. It is important to check that all ControlUp-related folders and files are excluded from real-time scanning and quarantine, as security software blocking these files can halt installation progress without clear error messages. Another consideration is the deployment method used for Remote DX, which differs from the Agent Manager and may require separate deployment steps or tools. This factor should be verified, especially in complex or staged deployments. While there is an MSI installer log that could provide more detailed insights and may reside under the ControlUp program data path, its location and availability may vary based on setup. Users are advised to consult the ControlUp documentation on Version Control and agent deployment for the latest guidance. If further help is needed, providing Event Viewer logs, any available installation logs, and screenshots of Version Control settings to ControlUp support will facilitate resolution. For more details on controlling agent versions and deployment, see the official ControlUp documentation at https://support.controlup.com/docs/agent-version-control. Read the entire article here...

How to Query Wi-Fi Adapter Driver Versions Using Custom PowerShell Scripts and Data Indexes in ControlUp

Posted on October 9, 2026

A first-time ControlUp user sought help generating a report or dashboard to query Wi-Fi adapter drivers across devices. They had PowerShell scripts producing the desired output but struggled to implement these within ControlUp. The root challenge involved correctly transforming and sending the script output to ControlUp’s custom data index for dashboard visualization. The recommended approach required modifying the PowerShell script to wrap the output in specific markers—`### SIP DATA BEGINS ###` and `### SIP DATA ENDS ###`—and present the data as a JSON array. This enables the ControlUp agent to parse and ingest the data into a custom data index, which can then be queried in dashboards. A sample script was provided illustrating how to query Wi-Fi drivers using `Get-CimInstance` filtered by device name and manufacturer, then constructing a JSON array with device name, manufacturer, driver version, and driver date properties. This script output was wrapped in the SIP markers for ControlUp Data (CU4D) to capture the information. Configuration instructions detailed how to add this script inside ControlUp for Desktops by navigating to Configuration > Scripts and creating a new script entry. Important options included setting the platform to Windows, language to PowerShell, enabling data sending to a specifically named custom data index (e.g., `wifi_adapter_drivers`), and choosing a trigger such as "Once Per Day" to optimize resource use since Wi-Fi driver info changes infrequently. They also noted enabling "Overwrite Existing Data" to maintain the current driver state without historical data buildup. After running the script on targeted devices, users could verify data ingestion under Configuration > Data and use or import JSON to visualize in dashboards. During deployment, an error involving a positional parameter indicated character encoding issues with the script on some devices, despite the command working via remote shell. This highlighted the importance of script formatting and encoding handled within ControlUp’s execution environment. Further enhancements included correcting the PowerShell property name for the device name field (switching from `device_name` to `devicename`) due to how the data was read, ensuring accurate output reflecting the adapter’s actual name rather than the computer name. A community member also shared a ready-made script and dashboard JSON import, tested on their ControlUp fleet, to streamline adoption. This example underscored ControlUp’s flexibility in integrating custom scripted data sources for tailored visibility into hardware driver versions via dashboards. This case demonstrates how ControlUp’s scripting and custom data indexing framework can extend monitoring and reporting capabilities beyond built-in metrics, supporting complex, field-specific queries through simple PowerShell integration and well-structured JSON output. Users should ensure proper script structure with SIP markers, configure triggers and data indexes thoughtfully, and validate script encoding to avoid runtime errors. Detailed guidance is available in ControlUp’s scripting guide at https://support.controlup.com/docs/scripting-guide and broader dashboard how-to resources in their knowledge base. Read the entire article here...

How to Refresh Service and Application Data On-Demand in ControlUp

Posted on October 6, 2026

A common challenge faced by ControlUp users involves timely updating of endpoint data, especially when tracking specific services or applications. In one case, a user wanted to confirm the removal of a service on endpoints but found that ControlUp still reported the service as running despite manual removal. This discrepancy occurs because the ControlUp agent updates different types of metrics at varied intervals. Core system metrics typically refresh every 60 seconds, but certain metrics such as service status and installed applications are updated less frequently—services refresh hourly (and shortly after a system reboot), while installed applications update only once per day. This update schedule means that relying solely on on-demand refresh within ControlUp for some metrics is limited, as there is no built-in immediate refresh capability for services or installed apps. To overcome this, users can create a Custom Action script to gather the needed data on-demand. By scripting, users can query the current service status or application state directly from the endpoints and write the results to a custom data index in ControlUp. This approach provides a precise and immediate reflection of endpoint conditions without waiting for the default agent update cycle. ControlUp’s scripting capabilities are documented in detail in the official scripting guide, available at https://support.controlup.com/docs/scripting-guide. This guide helps users build custom scripts that integrate into ControlUp workflows, enabling on-demand data collection tailored to specific monitoring or troubleshooting needs. As of now, no direct feature exists within ControlUp to force an on-demand refresh of hourly or daily metrics such as service and installed app status, but leveraging Custom Action scripts offers an effective workaround. Users looking to improve real-time monitoring of endpoint services should consider implementing these custom scripted solutions until such features potentially appear on future ControlUp development roadmaps. Read the entire article here...

Compatibility and Installation Improvements in ControlUp Mac Agent Manager 2.18 for macOS 26 and 27

Posted on October 6, 2026

ControlUp recently released an update to the Mac Agent Manager with version 2.18.4.4107, officially supporting macOS 27. This release introduces the Mac Agent version 2.18, which addresses installation issues specific to macOS 27. One notable change is the distribution format of the Mac Agent Manager installer; it has shifted from a.dmg file to a.pkg file. This update resolves a problem where the tenant information step failed to appear during manual fresh installations on macOS 27. A common question during this update rollout was whether the new.pkg installer is compatible exclusively with macOS 27 or if it also supports earlier versions, such as macOS 26.x.x and below. The confirmation from the ControlUp team clarified that the new.pkg installer works with macOS 26 as well, ensuring backward compatibility with previous macOS versions. This means that organizations using macOS 26 or earlier can upgrade their ControlUp Mac Agent to leverage the improvements without needing to alter their operating system environment. For users managing ControlUp deployments in mixed macOS environments, this installer update simplifies the installation process by standardizing on the.pkg format while maintaining support for multiple macOS versions. It also enhances installation reliability on macOS 27, which may have encountered issues with the previous.dmg-based installer. For detailed instructions and additional deployment considerations, refer to the official ControlUp documentation and resources at https://docs.controlup.com and the ControlUp Academy at https://cuacademy.controlup.com. Read the entire article here...

Resolving Data Conversion and Rounding Errors in ControlUp Out-of-the-Box Dashboards

Posted on October 5, 2026

A community discussion surfaced an issue regarding inaccurate data conversions and rounding errors observed in ControlUp's out-of-the-box (OOB) dashboards, particularly noticeable on a large screen dashboard but also present in other OOB dashboards such as the Employee Activity dashboard. The discrepancies appeared to be related to the way time values were displayed, potentially involving milliseconds that might require additional conversion or division to display correctly. Upon investigation, this behavior was suspected to be isolated to a specific tenant, prompting others in the community to verify and confirm whether they were experiencing similar issues. The problem was quickly identified as a bug affecting these dashboards' data presentation. The ControlUp support and development team acknowledged the bug and promptly worked to resolve it. Following their intervention, the dashboards were updated and fixed so that the data conversions and rounding errors no longer occurred. This incident highlights the responsiveness of the ControlUp team in addressing data accuracy issues in real-time monitoring dashboards. Users encountering similar symptoms in OOB dashboards displaying time-related metrics should ensure their software is updated to the latest version where this bug fix is included. For additional troubleshooting or updates, consulting ControlUp’s official documentation at https://docs.controlup.com and the ControlUp community forums is recommended. Read the entire article here...

How to Release Remote Control Session Guard in ControlUp During Network Issues

Posted on September 23, 2026

A common issue encountered by Support Teams when using ControlUp for remote session management is the challenge of releasing the session control guard when a user's device experiences network issues. In such scenarios, the support agent is often disconnected and attempts to reconnect to the remote session can fail or be significantly delayed, especially during active phone support sessions. This delay can hinder timely assistance and prolong user downtime. The root cause stems from the remote control session remaining locked or guarded by the ControlUp client process, preventing immediate reconnection or takeover of the session. To resolve this, a practical workaround involves terminating the ControlUp Remote Control process associated with the session on the support agent's device. Specifically, killing the process named CU_RC.exe frees the control of the remote session, allowing the agent to reconnect without the usual delays caused by the locked session state. This method has been verified by multiple users within the community as an effective way to release the session control guard promptly. It is recommended as a quick and straightforward action in cases where network instability disrupts remote control continuity. Teams are advised to share this approach as a standard troubleshooting step to minimize downtime during remote support sessions. It should be noted that forcibly terminating the CU_RC process might interrupt an ongoing session and should be performed with clear communication to the end-user. Additionally, this technique is applicable in environments using current versions of the ControlUp Remote Control feature and may need adaptation if underlying product updates change process names or behaviors. For more detailed information on managing remote control sessions in ControlUp and handling connectivity issues, users can refer to ControlUp’s official documentation and knowledge base at https://docs.controlup.com or explore training resources at https://cuacademy.controlup.com. Read the entire article here...

Resolving macOS Network Extension Approval Prompts During ControlUp Agent Deployment

Posted on September 21, 2026

When deploying the ControlUp macOS agent via ControlUp for Digital Experience (CU4D), users may encounter a system prompt asking for approval related to a Network Content Filter extension. This prompt is legitimate and a standard security feature of macOS. Apple requires explicit user or Mobile Device Management (MDM) approval for network extensions because they run in the background and have the capability to inspect network traffic. The specific prompt appears due to the agent’s use of a network extension to facilitate Unified Communications and Collaboration (UC&C) live monitoring. While the agent itself continues functioning without this approval, enabling the extension is necessary to capture and provide real-time UC&C data, which is vital for comprehensive digital employee experience monitoring focused on communication tools and services. Deployment of the ControlUp macOS agent often involves using remote control utilities like ScreenConnect, and configuration of these network extension approvals can be managed through MDM solutions such as Jamf or Microsoft Intune. By applying configuration profiles through MDM, administrators can reduce or prevent these approval prompts from appearing to end users, streamlining the deployment process and improving user experience. For further details and step-by-step instructions on deploying the macOS agent and handling configuration profiles in MDM environments, refer to ControlUp’s official documentation at https://support.controlup.com/docs/configuration-profiles-for-mdm-deployment. This article has been validated with recent versions of Jamf and Intune, ensuring compatibility and applicability in modern macOS management setups. Read the entire article here...

Troubleshooting macOS Agent Crashes with ControlUp 2.18 Release Candidate

Posted on September 10, 2026

ControlUp community members raised a question about the availability of a reference for macOS agent errors and resources for troubleshooting or triaging these errors. This inquiry specifically concerned a crash issue observed with the macOS agent in ControlUp environments. The discussion revealed that the reported crashes were linked to a beta or release candidate version of the macOS agent, specifically version 2.18. ControlUp experts confirmed that the issue causing these agent crashes had been identified and a fix was underway. Although quality assurance (QA) testing was still in progress, a new release candidate (RC9) of the macOS agent 2.18, which addressed the crash problem, was available. Customers experiencing these issues were offered access to this updated version to prevent further crashes on their tenants. To facilitate resolution, users were encouraged to share their organization name privately with ControlUp support or directly email support@controlup.com to have the macOS 2.18 RC9 agent enabled on their tenant. This direct support channel ensures that affected customers can quickly obtain the fixed version before a full official release. User feedback in the community was acknowledged as valuable input that helps ControlUp improve the quality and stability of their product. For ongoing or future macOS agent error triage, users should monitor official ControlUp support channels and documentation, and reach out to support for prompt assistance. ControlUp’s knowledge base and ControlUp Academy (https://cuacademy.controlup.com) are recommended resources for learning about agent troubleshooting best practices. Additionally, emailing support@controlup.com remains the primary route to address specific macOS agent issues, especially during pre-release or fixed-release candidate phases. Read the entire article here...
  • Page 1
  • Page 2
  • Page 3
  • Interim pages omitted …
  • Page 52
  • 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..