A ControlUp Cloud implementation is composed of three main components; a Console for real time environment monitoring and management, Monitor to monitor your environment 24/7 and upload historical and analytics data to our cloud infrastructure, and Agents to communicate with the Console and Monitor.
ControlUp Console Requirements
ControlUpConsole.exe is the main executable used for data display and task invocation. There is no setup routine necessary in order to start using ControlUp. Just download the executable and run it on your admin station or a management server.
ControlUp console was tested on:
- Windows 7
- Windows 8 and 8.1
- Windows 10
- Windows Server 2008, Windows Server 2008 R2
- Windows Server 2012, Windows Server 2012 R2
- Windows Server 2016.
ControlUp Console is the primary user interface for monitoring and managing your resources.
- The Console requires no database.
- All the data you see in it is stored in RAM, which allows for blazingly fast manipulation of data. As a result, ControlUp Console memory usage can be intensive, depending on the number of managed machines.
- A RAM footprint of about 1GB (Working Set) is normal when managing an enterprise with up to 500 live user sessions, while thousands of sessions can bring the console’s RAM usage up to several gigabytes.
In larger environments we recommend using a high-performance server for running the console. There are also some performance optimizations you should consider in order to reduce the amount of resources used by ControlUp Console. Please refer to the Advanced Settings documentation page for more details.
Prerequisites for ControlUp Console
- Domain joined desktop or laptop, Windows VM, or can be published as a XenApp application.
- .Net 4.5
- No installation required. Simply download the executable from our website.
- AD account with privileges on the machines you wish to Monitor/Manage
- Credentials (a service account is best) and URL for your hypervisor (XenServer, VMware, Hyper-V)
- AD account with help-desk or higher permissions in the 7.15 environment (and the Broker IP or host name)
- Firewall exceptions inside the company for RPC/WMI and ports 40705 and 40706 (or Windows firewalls off)
- Internet connectivity from the monitor and Console machines (it can be via proxy)
ControlUp Monitor Requirements
ControlUp Monitor is a component principally equivalent to ControlUp Console, but without an interactive user interface. Once installed and started, ControlUp Monitor signs into your ControlUp organization and connects to your managed computers. The Monitor starts receiving system information and performance updates from your organization, just like an additional ControlUp Console user. The primary difference between a Monitor and a Console is the fact that the Monitor runs as a Windows service, requiring no user interaction and allowing for continuous monitoring of your resources.
Benefits of ControlUp Monitor
ControlUp Monitor offers a number of benefits to admins who require continuous monitoring of their resources:
- After a Monitor is installed in the organization, monitoring of resources is a continuous process, running 24/7 regardless of the presence of active ControlUp Consoles in the network. Multiple Monitor instances automatically provide mutual backup and high availability for monitoring.
- Monitors can be configured to alert ControlUp users about incidents that cannot be detected by ControlUp Console. For example, only the Monitor records “Computer Down” incidents, since detection of this incident requires continuous monitoring.
- ControlUp Monitor can be configured to export data tables to disk for future analysis using ControlUp Reporter. The scheduled export process runs in the background and ensures continuous logging, which cannot be guaranteed using the interactive Console.
- The Monitor is mandatory for uploading data to ControlUp Cloud Insights and for exporting activity files for the Insights On-Premises
Respectively, the following limitations apply to ControlUp organizations which do not have a Monitor instance installed:
- Monitoring of resources and alerting about system issues can only occur if at least one instance of ControlUp Console is active and connected to the entire organization.
- “Computer Down” incidents cannot be detected or recorded.
- In order to support historical reporting and trending analysis, at least one instance of ControlUp Console has to be connected to the entire organization and configured to export data tables to disk.
Prerequisites for ControlUp Monitor
ControlUp Monitor can be deployed to any computer running Windows Server 2008 or later. It requires the .NET Framework 3.5 features to be enabled and RPC access to be enabled at the installation phase. In addition, in order to enable the Monitor Service to connect to all your managed computers, you will need to assign domain credentials to the Monitor Service as described below in the "Domain Identity" section of the Monitor Deployment guide.
The ControlUp Agent is a lightweight service that gets installed on the managed computers in your organisation. Installing the Agent on your systems allows you to use ControlUp Real Time Console to perform in depth monitoring, advanced systems management, and in depth configuration evaluation.
ControlUp agents have minimal performance impact
- CPU usage – consistently 0% to 1%
- RAM consumption – 60 to 90 MB
- I/O – zero disk activity
- No software hooks, no drivers and no reboot needed
Prerequisites for ControlUp agents
- Windows OS (all versions supported, from Windows XP to Server 2012 R2)
- .Net Framework 3.5 SP1 or 4.5
- Single incoming TCP port (by default 40705) open for ongoing console/monitor communications
- RPC and WMI access for initial deployment via the console, if access not available manual installation can be done using an MSI package