Troubleshooting connections to managed computers

Here’s a quick checklist for successfully adding a managed machine to the console:

• The managed machine name, as appears in Active Directory, should be resolvable to a valid IP address. A name resolution failure is indicated by the following error message: “No such host is known”.
  Removed AD Dependency

  You can deploy ControlUp Monitors on machines that are not joined to a local Active Directory (AD) domain. For details, see here.
• The machine’s operating system should be fully started, including the RPC services. If the boot process has not completed, a “There is no RPC access” error message will be displayed.
• The connection requires RPC access, which can be quickly tested by connecting to the administrative shares of the target machine, for example by entering machinenameAdmin$ in the “Start > Run” menu of your machine.
• Incoming cnnections to RPC ports must be enabled on the firewall.
• The default administrative shares should be enabled. Admin$ and C$ are both required.
• Verify that the required .NET Framework version is supported. Refer to the requirements document.
• Your domain account has full administrative privileges on the target machine. If using User Account Control, make sure you start ControlUp as an administrator.
• A corrupt WMI repository may prevent successful connection to managed machines. If your agent installation terminates with errors such as “Error occurred while trying to check if .NET is installed”, “Invalid class” or “Error querying service cuAgent”, you should look into rebuilding the WMI repository on your managed machine(s). The full process of troubleshooting WMI and rebuilding the repository is outlined here.