• 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

Browsers Related Training & Support Archives

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


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

Troubleshooting Missing macOS Script Details in ControlUp Event Logs and Resolution via 2.18 RC Agent

Posted on September 9, 2026

Users managing macOS devices within ControlUp reported an issue where script execution events only displayed "script started" and "script completed" messages without showing which script was run or its output. This behavior was a departure from prior functionality, where script details and outputs were visible. Windows devices did not exhibit this problem, and macOS scripts continued to generate output as expected. The concern arose when verifying the actual execution of scripts on macOS devices became necessary, but the ControlUp console failed to surface detailed script information. Further investigation revealed that ControlUp versions 2.17 and 2.18 for macOS, as well as the Windows version, should include script details in raw event data accessible either through developer browser tools or the ControlUp API endpoint at https://api.controlup.io/reference/get-system-events. However, in the normal device view within ControlUp, the description field showing script details was missing or blank, even though the event index properly contained the script output information. This suggested a user interface issue rather than a complete loss of the event data. The root cause appeared to be tied to the macOS 2.18 release state. The 2.18 build available was a special release candidate (RC) version, not yet generally available (GA), and it contained fixes targeting this exact problem. Users running this 2.18 RC version (including builds like 2.18.301.5B9E7EB35 and RC9) reported that the issue was resolved in those builds, with script details properly displayed alongside event logs. ControlUp staff offered to enable this release candidate on affected tenants to restore full visibility of macOS script execution events. In summary, the lack of script detail visibility on macOS devices in ControlUp event views was a recognized bug in releases prior to 2.18. The problem was fixed in the 2.18 RC macOS agent builds, which restored proper logging and display of script names and outputs. Users encountering this should verify their macOS agent version and upgrade to the 2.18 RC or later when it becomes generally available. Meanwhile, script event data can still be queried directly via the ControlUp API or found in event indices, offering a workaround until the UI fully reflects the script details. For more information on monitoring system events and interacting with the ControlUp API, consult the official documentation at https://docs.controlup.com/ and https://api.controlup.io/reference/get-system-events. Read the entire article here...

NEW ControlUp Disk cleanup script that actually asks the user what to delete

Posted on July 28, 2026

Chris Twiest demos a new interactive disk cleanup utility built by Sebastien Perusat and now baked into the product. Instead of silently cleaning from the system context, it prompts the end user with what can be reclaimed and lets them choose — recycle bin, temp files, browser cache. Works on Windows and macOS, can be triggered manually or from an alert, writes results to a data index and a device event, and is fully editable. Available in the script library now. Read the entire article here...

Troubleshooting “Detect Workspace” Stuck Prompt for Citrix Cloud Synthetic Monitors on Public Hives

Posted on July 23, 2026

Some users running synthetic monitors to test Citrix Cloud connections from public hives reported that a few monitors become stuck at the "Detect Workspace" prompt. This behavior was inconsistent, with some monitors seemingly configured the same way functioning normally while others encountered this issue. The root cause was identified as related to the Citrix Workspace store’s launch method settings. The "Detect Workspace" screen corresponds to the Citrix client detection page, which is controlled on the store side rather than by Scoutbees or the synthetic monitors themselves. Specifically, when the store is configured with the "Launch virtual apps and desktops" setting set to either "Open in Citrix Workspace app" or "Let the user choose," this page appears. On public hives, where the browser environment is fresh and does not retain prior user choices, the prompt recurs on every run, causing the monitors to stall at this screen. To resolve this, it is necessary to verify and compare the launch settings in Citrix Cloud under Workspace Configuration (or the targeted StoreFront store). Monitors stuck on the detection prompt typically point to stores configured with "Open in CWA" or "Let the user choose," while those that bypass the prompt are connected to stores set to "Use web browser to access apps and desktops." Changing the store’s launch setting to "Use web browser" bypasses the native Citrix Workspace app detection page, allowing the synthetic monitors on public hives to proceed without interruption. Before making any changes, administrators should confirm these settings by comparing the store configurations between monitors that are stuck and those that are working. This ensures an accurate diagnosis and prevents unintended side effects from changing the launch mode. Since this is a store-level configuration, it requires adjustments within the Citrix Cloud management console, specifically under Workspace Configuration. If the issue persists or if the public hive environments themselves seem problematic, submitting a support ticket for those specific hives is recommended. For additional guidance on managing Citrix Cloud Workspace configurations and optimizing monitor setups, see the ControlUp Knowledge Base and Citrix documentation on Workspace Configuration: https://docs.controlup.com and https://docs.citrix.com/en-us/citrix-cloud/workspace-configuration.html. Read the entire article here...

How to Enable File Browsing in ControlUp’s File Browser by Configuring Role Permissions

Posted on July 17, 2026

A common issue encountered with ControlUp's File Browser feature is the inability to see any files within a user's system during a remote session, despite being able to navigate folders. This typically occurs when the appropriate permissions are not enabled for the user role in ControlUp. For example, a user attempting to retrieve log files without interrupting a session might notice that the file list remains empty, even though directories are visible. The root cause is often related to role permissions. By default, the built-in Admin role in ControlUp does not have the File Browser permission enabled for viewing files. To resolve this, administrators need to create a custom role that explicitly grants this permission. Specifically, under Device Permissions, navigating to Remote Management > Management > File Browser, the administrator must set the scope to allow users assigned this role to view files. Once the custom role is created with the correct File Browser permissions, it is possible to assign the user both the built-in Admin role and this new custom role simultaneously. ControlUp's role-based access control supports multiple role assignments per user, enabling flexible and granular permission management without removing any existing higher-level roles such as Admin. In summary, to access files via ControlUp’s File Browser, ensure that the user has a custom role with the "View Files" permission under File Browser enabled. This role can be combined with the default Admin role, allowing complete management capabilities while enabling file browsing. For detailed role creation and permission configuration instructions, refer to ControlUp's official documentation on role management at https://docs.controlup.com. Read the entire article here...

Troubleshooting a Workflow Scheduling Issue in ControlUp.

Posted on June 10, 2026

Some users reported a workflow issue where a scheduled workflow still appeared as manual, even after changing it to scheduled. Another user suggested that selecting an interval and offset time may solve this issue. The post includes screenshots showcasing the problem and solution, and a user confirms that the issue has been resolved. The team has been alerted to this issue. Read the entire article here...

How to Pinpoint CPU-Heavy Processes Across Your VDI Fleet with ControlUp

Posted on June 3, 2026

This thread walks through a real customer question: how do you find which processes are eating the most CPU across a large VDI estate (200 servers) over a long period, so you know what to optimize? It starts in ControlUp Dashboards. Using the VDI process data, you can build a widget showing top processes by CPU, then narrow it to the machines you care about using global filters (filter by folder, or switch to query filters with IS / IS NOT). A table beats a bar chart for a top-50 view, and any filters and time frames you set are saved in the URL, so you can bookmark or share the exact view. The built-in Gallery dashboards (notably "Big Screen Dashboard VDI") already include a processes-by-CPU widget out of the box. The harder part is the one the customer really cared about: getting a meaningful picture across all machines rather than a single noisy spike on one box. The data is stored per process per 5-minute timeslot, not pre-aggregated per machine, so the practical approach that emerged was: Filter to the folder containing all target machines. Use CPU usage P95 to strip out short, expected spikes (with a fallback to average CPU, since P95 returned N/A in some environments — a possible bug worth a support ticket). Add metrics under Advanced: computer_name (unique count) to see how many machines run the process, and process_name (count) to see how often it appeared (each record ≈ a 5-minute aggregate). The processes worth optimizing are the ones combining high CPU + high machine count + high record count. Worked example: a process showing ~1,080 records across 197 machines roughly translates to ~90 hours of activity over 7 days, or a few minutes per machine per day. The same method surfaced candidates like CompatTelRunner.exe, WerFault.exe, and WEM-related activity for further investigation. To go deeper, the App Trends and App Statistics reports let you drill into a specific app, and product_name data helps identify what's actually behind generic process names like setup.exe. A few important caveats came up: averages hide spikes (10% average could be one minute at 100%), process counts are per machine, and hypervisor-level CPU (e.g., XenServer) can disagree with in-VM agent data when hosts are over-provisioned — which is also why a Sizing Recommendations report may suggest removing vCPUs even on a machine that looks maxed out. Bottom line: use the dashboard to identify the heavy processes (folder filter + P95/avg CPU + machine count + record count), then use the App Trends report to dig into the details per app. Read the entire article here...

Certificates for Teams integration on ControlUp Academy Updated

Posted on April 23, 2026

A user reported an issue with adding the Teams integration in workflows for testing. The ControlUp team acknowledged it as a devops issue and provided an update that the certificate has been updated. The user is advised to try their integration again. Read the entire article here...

Widget Wednesday #18: New Filter UI and Unified Filtering Experience

Posted on April 22, 2026

Widget Wednesday #18 introduces a redesigned filter UI in ControlUp Dashboards with expanded filtering options, unified variables and filters, and improved usability for faster, more flexible data analysis. Read the entire article here...
  • Page 1
  • Page 2
  • Page 3
  • Interim pages omitted …
  • Page 10
  • 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..