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


Using ControlUp for Application Patching in Windows Defender Application Control (WDAC) Environments

Posted on November 16, 2026

When deploying ControlUp in environments with strict Windows Defender Application Control (WDAC) policies, particularly where application patching is involved, certain considerations are necessary to ensure compatibility and avoid operational disruptions. WDAC enforces rules that restrict what code or binaries can run on devices, so any update or patch introducing new files potentially outside existing WDAC policies could result in those updates being blocked. A key point is that ControlUp itself must be excluded from WDAC policies to operate correctly. This is a basic prerequisite since ControlUp performs monitoring and remediation functions on endpoints. Beyond this, the use of ControlUp for compliance and patching raises the question of how new application binaries introduced by patching are handled under WDAC. One recommended approach involves leveraging the “Managed Installer” policy feature within WDAC. This policy allows software deployed through managed platforms—such as Microsoft Intune—to be automatically trusted and permitted to run, even if their binaries are new and not explicitly covered by previous WDAC rules. By integrating ControlUp for Compliance with Intune to handle patch deployment, organizations can benefit from this policy to reduce the likelihood of patching failures due to WDAC enforcement. This means that any new binaries pushed via Intune by ControlUp's remediation process should be allowed by default under the Managed Installer policy, avoiding blocks. Testing in Audit mode within WDAC is advised as a next step to validate the setup without enforcing strict blocking, allowing administrators to identify what would be blocked and adjust policies accordingly before moving to full enforcement mode. This phased approach helps mitigate risks associated with new or changed applications following patching. In summary, effective use of ControlUp in WDAC-controlled environments for application patching hinges on excluding ControlUp from WDAC, employing WDAC’s Managed Installer policy to automatically trust Intune-deployed binaries, and performing thorough testing in Audit mode to ensure seamless operation. This approach supports secure application control while enabling dynamic management and patching workflows with ControlUp. For further reference, consult the official Microsoft documentation on WDAC and Managed Installer policies, as well as ControlUp’s integration capabilities with Intune for compliance and remediation at https://docs.controlup.com. Read the entire article here...

Understanding Application Visibility and Template Use in ControlUp’s Compliance Module for Patching

Posted on November 13, 2026

ControlUp’s Compliance Module provides app patching capabilities through a template-based system that defines which applications are scanned and managed for vulnerabilities. Currently, the accessible and comprehensive list of all applications available for patching is embedded within the templates section of the product. This means that users can view all the apps included in the scanning process only by reviewing the template library, as there is no separate, standalone database publicly exposed for all patchable apps. Within the Compliance Module interface, users can also see information about specific applications on the per-device basis, including which devices did not scan a particular app. The apps page and issue page offer visibility into app scan status and vulnerability findings. However, the interface typically defaults to showing only applications with detected vulnerabilities or issues. For example, if an organization has no vulnerabilities reported for Google Chrome, that app will not be visible by default on the app page. This design can make it challenging to review the complete set of applications that can potentially be patched if no issues currently exist. Recognizing this limitation, the ControlUp team is developing a new feature aimed at broader visibility, which will enable users to see all issues and applications regardless of current vulnerability status. This enhancement will also provide detailed insights into the number of devices that have scanned each app and flag those that have not been scanned, offering more comprehensive monitoring and management of application patch compliance. For organizations intending to proactively configure and patch applications before any security vulnerabilities (CVEs) are detected, the current approach is to leverage templates that cover all common or commodity applications. Operators may consult the templates to ensure coverage and discuss with stakeholders about the included applications. Until the new feature is released, users interested in a full, easily accessible list of all potential patchable applications will need to rely on the template definitions and usage in their environments. For the most up-to-date information about the Compliance Module templates and app patching, users can refer to ControlUp’s official documentation at https://docs.controlup.com and keep an eye on announcements for new features that expand app visibility and management. Read the entire article here...

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

Posted on November 11, 2026

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

How to Build a Cross-Platform OS Patch Compliance Dashboard in ControlUp

Posted on November 11, 2026

Building a patch compliance dashboard within ControlUp can be approached in different ways depending on the source of your patch data and the scope of your device environment. For users who leverage ControlUp for Compliance, the platform already offers built-in Compliance dashboards and template reports that provide extensive coverage on patch remediation status, remediation trends over time, and per-device columns such as Patchable and Restart required. These built-in resources can often meet patch compliance reporting needs without requiring custom dashboards. More details can be found in the official documentation on viewing template statuses and results at https://support.controlup.com/docs/view-template-status-and-results. For those aiming to create custom dashboards focused on OS patch levels, the Device Inventory dashboard available in ControlUp’s Dashboard Gallery serves as a useful starting point. It includes widgets that group devices by OS patch level, which can be adapted through the Widget Builder to filter by specific device groups or tags. However, there is a caveat: the Widget Builder currently supports data sources such as Desktops, VDI, Apps, DaaS IQ, and Audit Log but may not pull patch data directly from ControlUp for Compliance. Documentation related to custom dashboards and the widget builder can be accessed at https://support.controlup.com/docs/custom-dashboard-overview and https://support.controlup.com/docs/dashboard-builder. When building a compliance dashboard covering Windows, macOS, and Linux OS patch levels centrally, it is important to understand the differences between OS Patch and OS Version fields, particularly for Windows devices. The OS Patch field on Windows represents feature releases (e.g., 23H2, 24H2), while the OS Version field contains the full build number including update revisions (e.g., 10.0.26100.xxxx), which reflects the monthly cumulative updates and is a more precise indicator for patch compliance. The Device Inventory dashboard groups devices by OS Patch, showing release levels rather than patch levels. Users are encouraged to build widgets grouping devices by OS Name and OS Version, combined with platform filters and group/tag filters, to display Windows, macOS, and Linux in one unified dashboard. It is recommended to inspect the raw data behind widgets to verify version string formats for macOS and Linux, as this may vary. Additionally, exploring the Missing Patches data set is beneficial since it provides a compliance-centric view by showing missing patches per device for both Windows and macOS (Linux is currently excluded). However, availability of this data in the Widget Builder should be confirmed as it may not yet appear in all environments. For comprehensive platform feature support details, ControlUp’s documentation at https://support.controlup.com/docs/comparison-of-supported-features-across-os-platforms offers guidance, making it a valuable resource during dashboard creation. Read the entire article here...

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

Posted on November 11, 2026

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

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

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

Posted on November 3, 2026

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

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 Use ControlUp AI Decision Nodes to Trigger Conditional Script Execution in Automated Workflows

Posted on November 3, 2026

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 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...
  • Page 1
  • Page 2
  • Page 3
  • 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..