• 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

Microsoft Related Training & Support Archives

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


ControlUp Community Meetup #18 — ControlUp Workflows in Action | Live Demos & Community Q&A

Posted on November 12, 2026

In this ControlUp Community Meetup, we walk through the drag-and-drop workflow builder and demonstrate how triggers, actions, and logic work together—from responding to an alert to managing a password-expiry process. Read the entire article here...

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

Automating Windows 365 Cloud PC Rightsizing with AI Canvas: Cost and Performance Optimization

Posted on November 3, 2026

A new AI prompt has been developed for ControlUp's AI Canvas to automate the rightsizing evaluation of Windows 365 Cloud PCs within an organization. The prompt identifies every Windows 365 Cloud PC, determines its current plan based on CPU, RAM, and storage configuration, and analyzes recent performance metrics to assess whether the plan suits the workload. It estimates the potential savings or costs associated with resizing each Cloud PC and presents the results along with actionable recommendations. The process begins by querying all Cloud PCs configured with the Microsoft Cloud PC provider. Devices not reporting back within the last 14 days are excluded from sizing recommendations but flagged separately since they may still incur licensing costs despite inactivity. The prompt calculates usage metrics over a recent 7-day window, focusing on CPU load (p95) and memory utilization (p95), plus storage consumption on the system disk. Oversizing is flagged when CPU and memory usage consistently remain low (under specified thresholds), prompting recommendations to downgrade one step in the plan ladder if the workload still fits comfortably within the smaller configuration. Conversely, oversizing occurs if resource usage exceeds defined upper limits, triggering an upgrade suggestion. Storage sizing is handled separately, moving devices to plans with appropriately sized storage tiers based on usage, with thresholds designed to avoid undersized or oversized drives. Pricing uses Microsoft’s public Windows 365 Enterprise list prices as of November 2026, converted into cost differences reflecting the proposed resizing changes. The prompt outputs a comprehensive dashboard including a net monthly savings stat, a donut chart categorizing Cloud PCs by sizing verdict (right-sized, oversized, undersized, storage too small/large, not reporting, or unmatched), and a detailed table for all devices showing current and recommended plans, verdicts, pricing impact, VM size, region, and storage type. An AI-generated summary provides holistic findings, including potential savings, constraints on high-demand users, and caveats such as volume licensing discounts and workload peaks outside the measurement window. Testing in lab environments indicates the prompt works reliably, producing clear and actionable results within acceptable execution times. Feedback suggested that the visual emphasis on total savings paired with detailed explanations improved usability. The solution currently covers Enterprise licenses only, with Business and Frontline licenses excluded from analysis, and the pricing reflects list prices that may differ from negotiated agreements. This prompt is intended to run as a single AI Canvas operation with efficient batch querying to stay within API limits, making it scalable for real-world tenant environments. This AI prompt for Windows 365 rightsizing represents a powerful tool to optimize Cloud PC deployment costs and performance by providing IT teams with data-driven resizing recommendations and potential financial impact upfront. Further refinements may include extending support for additional license types and adjusting resource thresholds as usage patterns evolve. For more information about Windows 365 Cloud PCs and rightsizing, see the official Microsoft documentation: https://docs.microsoft.com/en-us/windows-365/right-sizing-cloud-pc and ControlUp resources at https://docs.controlup.com. Read the entire article here...

How to Set Up Workflow Failure Notifications in ControlUp

Posted on November 2, 2026

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

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

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

Maximizing Employee Experience Insights with ControlUp: Key Features, Metrics, and Best Practices

Posted on October 20, 2026

ControlUp users focusing on digital employee experience (DEX) and user experience monitoring have found several features and best practices especially valuable for measuring adoption, engagement, and satisfaction across their environments. Key recommendations center around combining telemetry data with direct user feedback such as surveys to obtain richer insights. Surveys are most effective when paired with quantitative telemetry metrics, as this correlation reveals gaps and areas for improvement that neither approach alone can fully expose. A primary metric endorsed by the community is the DEX Score, which aggregates user experience data into a single score per user, and can be rolled up by department, location, or persona. Trending DEX Scores over time provides a clear adoption and satisfaction narrative. In addition, monitoring logon duration per group is critical because delays here are a common source of user frustration and complaints. For user experience visibility, the Employee View dashboard enables IT teams to quickly identify issues impacting end users. Other frequently cited dashboards include those focusing on Windows application crashes, app stability and performance, AI-driven apps and sites usage, and Teams/Unified Communications call quality—particularly important for organizations heavily reliant on Microsoft Teams. Anomaly detection using AI (Pulse AI) is recommended over static threshold alerts, as it can find unusual patterns proactively and even suggest or enact fixes via workflows. Custom dashboards should be tailored to different stakeholders—executive views showing aggregated DEX by business units, operational views tracking logon times and resource usage, and user experience views combining app performance and user sentiment. In addition, creative use of automation workflows can significantly enhance support responsiveness. For example, a self-healing workflow can collect diagnostic data on machine issues, generate AI-driven recommendations, automatically open service tickets (e.g., in ServiceNow), and notify users with remedial steps before they contact helpdesk. Integrations such as with ServiceNow enable automated ticket creation and remediation workflows that improve IT support efficiency and end-user communication. ControlUp roles can be customized to give access across teams (security, network, telephony) beyond just helpdesk functions, helping different groups leverage relevant telemetry. New users of ControlUp are advised to start with free courses available at ControlUp Academy, followed by hands-on evaluation of dashboards in the Dashboard Gallery to understand available data and refine dashboards per organizational needs. Building out use cases and dashboards incrementally—starting with a few key metrics and expanding gradually—helps organizations avoid measurement overload and focus on actionable insights. Finally, community insights emphasize ongoing management of user personas underpinning DEX Score segmentation, with approaches varying from manual updates to bulk imports depending on organizational scale. Overall, a combined strategy using ControlUp’s telemetry, custom dashboards, integrations, AI-powered anomaly detection, and employee survey data provides a powerful framework for measuring and improving employee experience in IT environments. Relevant resources include: ControlUp Academy: https://cuacademy.controlup.com ControlUp official documentation: https://docs.controlup.com ControlUp Community: https://community.controlup.com Dashboard Gallery (within ControlUp platform) Read the entire article here...

Why ControlUp Uses LDAP (Port 389) Instead of LDAPS for Active Directory Queries and Firewall Configuration Guidance

Posted on October 13, 2026

ControlUp’s Realtime DX Console and Monitor components currently use LDAP (Lightweight Directory Access Protocol) on port 389 to communicate with Active Directory for essential functions such as reading the domain’s organizational structure, discovering computers, and retrieving user and group information. This communication method is explicitly documented in ControlUp’s support materials. While security teams often prefer LDAPS (LDAP over SSL/TLS) on port 636 to secure directory queries, ControlUp’s product does not automatically fall back from LDAP to LDAPS if port 389 is closed or blocked. The reliance on LDAP instead of LDAPS is outlined in ControlUp’s official documentation, including the Communication Ports for VDI environments, particularly for the EU region. These documents confirm the use of LDAP on port 389 as a mandatory communication channel for the Console and Monitor to function correctly. Attempting to restrict access by only allowing LDAPS traffic on port 636 without open access on port 389 will disrupt domain querying operations and break functionality. There is currently no straightforward option within ControlUp to switch these queries from LDAP to LDAPS. The documentation and community experts note that closing port 389 and permitting only port 636 is not supported and will result in operational issues. This limitation is important for network and firewall teams to understand when reviewing and tightening rules related to ControlUp’s network communication. For detailed information on required ports and communication flows, ControlUp provides a dedicated documentation page at https://support.controlup.com/docs/communication-ports-used-by-controlup-hybrid-cloud-eu-customers, which includes tables and descriptions of mandatory ports for the Console and Monitor roles. Users seeking secure directory communication should be aware of this existing protocol limitation and plan network configurations accordingly to avoid disruptions. 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...
  • Page 1
  • Page 2
  • Page 3
  • Interim pages omitted …
  • Page 39
  • 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..