ControlUp Community

Connect, Learn, and Grow

ControlUp One Platform Support & News Resources

This resource hub brings together in-depth blogs, technical walkthroughs, release insights, and practical guidance from across the ControlUp platform. Whether you’re digging into new capabilities, exploring how features work under the hood, or looking for real-world operational context, these resources are designed to help you understand, apply, and get more value from ControlUp in day-to-day IT operations.

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

Posted on

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

Understanding ALERT RULES Licensing and Usage in ControlUp One EVENTS Tab

Posted on

Within the ControlUp One platform, the EVENTS tab includes an ALERT RULES section that is specifically designed for ControlUp for Desktops (CU4D). Users who do not have a CU4D license will encounter a license error when accessing the ALERT RULES tab, even though other areas like OVERVIEW and EVENT DETAILS function normally. This is because the ALERT RULES feature is directly tied to CU4D licensing and capabilities. The ALERT RULES in ControlUp One covers alerting for CU4D, ControlUp for VDI (CU4VDI), and Synthetic Monitoring; however, the creation and management of alert rules within this tab are exclusive to CU4D. For alerting related to ControlUp for VDI and Synthetic Monitoring, users must configure those alerts within their respective products. Once alerts are configured in each solution, they will be aggregated and displayed together in ControlUp One for centralized monitoring. In summary, the ALERT RULES function in the ControlUp One EVENTS tab is dedicated to CU4D alert creation, and attempting to access this function without the proper CU4D license will trigger a license error. Alert management for CU4VDI and Synthetic Monitoring requires using those individual products’ alerting tools, after which their alerts become visible collectively within the ControlUp One interface. This division maintains clear licensing boundaries and functional segregation across ControlUp’s different monitoring products. For more information, see ControlUp’s official documentation on alerting and licensing at https://docs.controlup.com and explore the ControlUp Academy for training on alert configuration and best practices at https://cuacademy.controlup.com. Read the entire article here...

ControlUp Remote Control Log Out Issues.

Posted on

Users had been logged out of ControlUp mid-remote control session. A member suspected the issue may have been due to active session time out. ControlUp support suggested checking the Audit logs to see if this was the case. Some users also reported being logged out of other SAML-authenticated apps. A rogue tab or SAML/IDP provider may be the cause of the issue. Read the entire article here...

ControlUp Community Meetup #14: Inside ControlUp DaaS IQ — A Deep Dive with PM Gilad Broun

Posted on

AVD management doesn’t have to be hard and expensive. If you run Azure Virtual Desktop, you know the pain: unpredictable costs, fragile PowerShell scripts, fragmented visibility, and tab-hopping between the Azure Portal, Intune, and a dozen custom tools just to keep the lights on. ControlUp’s answer is DaaS IQ — a purpose-built control plane for AVD that replaces the chaos with smart, reusable policies, centralized lifecycle management, and real-time cost intelligence.… Read the entire article here...

Remote Boot Alert and Script Configuration in ControlUp

Posted on

A user asked about tagging devices in ControlUp and having an alert and script run remotely upon booting up. They clarified that this was for ControlUp for Desktop and mentioned using tags and scripts to remove unwanted machines from the environment. Another user asked for more context and suggested checking if the alert was fired and showed in Events. The user planned to test and shared a screenshot of the script settings. Read the entire article here...

Troubleshooting Offline Windows Servers in ControlUp

Posted on

Some Windows servers appear as offline, but when a user logs in through the hypervisor's remote console, they show as online again. A screenshot was requested and a possible solution was suggested. It was advised to submit a case to support@controlup.com with logs and screenshots for further analysis. Different ways to change logging levels were shared and it was asked if the server has AV in place. A possible explanation was offered and it was mentioned that logs would provide more insight into the issue. One user stated that they had put in exceptions for the AV, and another needed to wait before reporting. Screenshot and log files were recommended to help find a solution. Read the entire article here...

Creating Workflows to Auto Tag Machines Based on Location

Posted on

A discussion was had about creating a workflow to auto tag machines based on location, with the trigger being logon or unlock. There is currently no native support for this type of trigger in ControlUp Workflows. The recommended workaround is to create a scheduled flow that runs every 5-15 minutes to update tags based on IP address and location data. Using controlUp One integration or Windows Event alerts were also suggested as alternative methods. Read the entire article here...