Managed Machines

This article describes some common problems during Agent installation, and how to fix them. Issue #1 - “The Agent Authentication Key is misconfigured” This error appears when the agent was installed on the machine with the MSI package, but no au...

Issue After logging into a Windows machine, a domain user receives the following error message. Solution The Repair machine-domain trust relationship script can be used if the ControlUp Agent is installed on this machine. The script sho...

In order to troubleshoot effectively, our technical teams may need a detailed log of the ControlUp Monitor. The monitor machines do not automatically create log files, so you will need to manually initiate the creation of a log file. We use a third...

Issue You deployed the ControlUp Agent on an Azure machine (see the setup guide for Azure-AD joined machines ) and you can see the Azure machine in the Real-Time Console. However, in the web UI, the Azure machine is not associated in the Mac...

A recent Microsoft update may affect our ability to manage and deploy agents and monitors from the Real-Time Console. You may encounter issues only if not all your machines running the ControlUp Real-Time Console, Agents and Monitors have the late...

If a machine on which the ControlUp agent is deployed is running Windows 10 1809 or higher or Windows Server 2019 where the User Input Delay feature is enabled by default, you may encounter the list of leaked handles growing too large. This c...

The ControlUp Agent should typically consume 1%-2% of CPU resources and up to 200 MB of RAM. If the ControlUp Agent service is using more resources in your environment, please use this knowledge base article to review the possible causes before co...

Issue You try to connect to a ControlUp Agent, but it fails with the following error message: Could not connect to xxxxx cuAgent. The connection attempt lasted for a time span of xx:xx:xx. TCP error code 10061: No conne...

Issue You open the ControlUp console and fail to connect to your managed computers. You receive an error: " Failed to replace agent files to match version X" Reason The ControlUp console is trying to match the versions of the Console and t...

If you need to perform comprehensive ControlUp Agent troubleshooting, you should use the log4net tool. Download cuAgent.exe.log4net here . Save the file on the target machine where the cuAgent.exe resides. A log is automatically creat...

Issue The ControlUp Agent fails the uninstall process. Reason The agent was originally installed by MSI package and you tried to remove it via the Real-Time Console, or with an MSI package of a different ControlUp Agent version. This migh...

Issue: ControlUp Agent Error Failed to open connection to remote agent. Agent error This machine ( MachineName ) only accepts connections from organization ( OrgNameA ) Solution A managed machine can only belong ...

Relevant ControlUp Agent Error Messages Failed to perform the requested operation. This error may occur due to any of the following reasons: Your user account does not have the required rights over the remote computer. UAC might be enabled a...

Agent Error Message Failed to contact COMPUTERNAME using WMI with the following error: The RPC server is unavailable An error occurred querying service cuAgent on ComputerName Failed to contact ‘ COMPUTERNAME ‘ using WMI with the following...

The Issue: The ControlUp Monitor service does not connect to all monitored resources. The error you see is - "Failed to register for information events..." The Reason: The AD user defined in the Monitor settings as the user for authent...

Issue The monitor fails to connect to computers in the monitored resources list. The status is Disconnected , as shown in the screenshot below - Reason These computers are excluded from the ControlUp Monitor. Solution Go to the folder,...

The Issue: You try to connect to a managed computer but receive an error - "Unable to gain access to the computer" The Solution: Check if the user which logged in to windows and launched ControlUp, is part of the administrators' grou...

ControlUp requires a valid and reachable FQDN of a machine before adding it. However, you can add computers that are not part of an Active Directory domain to your ControlUp environment. In this article, we show you how to add a machine to Control...

Issue Each time I launch the ControlUp Real-Time Console and connect to the group of servers that I normally connect to, it attempts to update the Agent version running on these servers. This keeps happening eventhough the ControlUp Agent vers...

Issue When you try to connect to an endpoint after upgrading to a new ControlUp Real-Time Console version, the Console is trying to upgrade the agent but fails with error: Error message Failed to replace files to match ...

ControlUp Agent Error Message Failed to open connection to the remote agent. Failed to open connection. Could not connect to net.tcp://FQDN:40705/cuAgent. The connection attempt lasted for a time span of 00:00:XX:XX:XX. TCP error code 10060: ...

Relevant ControlUp Agent Error Messages Ping test: Communication failed. Error code: TIMED OUT Suggested Solution If you have ping disabled in your environment you can disable the ping test. Go to Settings -> Agent and uncheck the “Check if co...

If a brief network failure occurs, your managed computers may lose their connections to the console (icon color changes to red in the Navigation Tree). To prevent this, right-click the computer/s or folders of choice and select “Auto-Connect”. ...

When you deploy the cuAgent via the Real-Time Console, you have two ways to configure it. Temporary mode - The ControlUp Agent will be automatically uninstalled if the Console or Monitor are not connected with that agent, after a duration of 5 m...

Here’s a quick checklist for successfully adding a managed computer to the console: The managed computer name, as appears in Active Directory, should be resolvable to a valid IP address. A name resolution failure is indicated by the following er...