Contents x
    On-Premises Installation Prerequisites
    • 08 Sep 2024
    • 3 Minutes to read
    • Print
    • Dark
      Light
    • PDF
    Contents

    On-Premises Installation Prerequisites

    • Updated on 08 Sep 2024
    • 3 Minutes to read
    • Print
    • Dark
      Light
    • PDF
    Article summary

    The number and size of the servers required to install ControlUp On-premises (COP) components depend on the size of the environment you need to monitor and the level of usage of ControlUp.

    COP Components

    • COP Server: Machine running backend web services such as user management, incidents management or configuration store running an AD LDS instance. The COP server needs to be installed on a dedicated AD-joined machine. Learn more.
    • COP Real-Time Console: Gathers and displays real-time health and performance data every 3 seconds. See installation instructions here.
    • Insights On-Premises (IOP): Data platform for historical reports. To install IOP, you can use a pre-configured OVA file or Linux-based installation packages.
    • IOP Forwarder: Required if you use IOP. This component must be installed separately on each ControlUp Monitor machine. The forwarder uploads the activity files from a specified location to the IOP server. This specified location can either be the local disk of the monitor machine or a network share.
    • Solve On-Premises (SOP): Web-based platform that lets you monitor your monitored resources in real-time and displays historical trends of your real-time metrics. Learn how to install and configure SOP.

    COP Components Prerequisites

    The table below outlines prerequisites for each COP component you need to install separately. For detailed requirements of the different IOP deployment types, see the IOP prerequisites guide.

    COP ServerConsole MachineIOP ServerSOP Server
    MachineWindows ServerWindows Server or
    Windows     		OVA deployment or Linux-based installation
    		OVA deployment
    Operating System Windows Server supported versions:
    2022,
    2019,
    2016
    		Windows Server supported versions:
    2022,
    2019,
    2016
    OR
    Windows 11, 10

    Supported for OVA:
    vSphere (ESXi) 7.0.3 or higher


    Supported Linux OS versions:
    • Photon OS 5.0 or higher
    • Ubuntu 20.04 or higher

    Supported for OVA:
    vSphere (ESXi) 7.0.3 or higher


    Supported Linux OS versions:
    • Photon OS 5.0 or higher
    CPU*2 CPUs 2 CPUs12 vCPUs2 vCPUs
    Memory*8 GB RAM 8 GB RAM12 GB RAM4 GB RAM
    Disk Space*10 GB 10 GB100 GB OS Drive
    50 GB Data    		30 GB
    Required Software & Permissions
    • .NET Framework 4.8 or higher
    • PowerShell 5.x or higher

    Recommended for the installation:

    • IP address or FQDN of the machine where the Insights server will be installed.
    • If you use your own SMTP server: the address of your SMTP server
    		.NET Framework 4.5 or higher

    For Linux:

    • Python 3.6
    • Docker 18.09.8 
       (or higher)

    IOP Forwarder (see below)

     

    *Minimum recommended. For details, see Sizing Guidelines for ControlUp v8.x.

    ControlUp Database

    COP uses a database to store data, such as incidents, events, or script actions. You must provide your own SQL Server instance.

    MSSQL Versions (Standard or Enterprise)Maximum Database SizeCollation

    • 2022
    • 2019
    • 2017
    • 2016
    • 2014
    		10 GBSQL_Latin1_General_CP1_CI_AS

    Additional Components

    Once you've installed the ControlUp application, console & Insights, you deploy the following from the ControlUp console to retrieve monitoring data:

    • ControlUp Agent: Lightweight component that enables rapid deployment and a minimal performance footprint on the managed machine. Every managed Windows machine that you want to monitor and remediate in your environment must have an agent deployed for data to be sent to the console. (Linux machines are monitored via an API.)
    • Data Collector: (Optional). Used for increased performance of the console & monitor. Collects metrics from external sources such as hypervisors, EUC environments, or Citrix ADC. To act as a data collector, the machine must have the ControlUp Agent installed.
    • ControlUp Monitor: Monitors assets 24/7 and enable triggers, alerts and automation. A functional monitor is required to access IOP and SOP.

    Can be installed on the same machine as the application server (see above) but not recommended for larger installations.

    ControlUp AgentData CollectorControlUp Monitor
    MachineNo server installation necessary. Deployed onto Windows machines that are monitored by ControlUp
    (Linux monitored via API).    		Windows Client OS or Windows Server that has the ControlUp Agent deployedWindows Server
    Operating system Windows Server supported versions:
    2022
    2019
    2016 (Core or Full)
    OR
    Windows 11, 10    		Windows Server supported versions:
    2022,
    2019,
    2016
    OR
    Windows 11, 10    		Windows Server supported versions:
    2022
    2019
    2016
    CPU*N/A 2 CPU2 CPU
    Memory*N/A 8 GB RAM8 GB RAM
    Disk Space*N/A 10 GB100 GB (for activity files backup)
    Required installed software.NET 4.5 or higher
    Active Directory    		ControlUp Agent
    .NET Framework 4.7.2 or higher (recommended)
    4.5 (supported)
    Citrix SDK to connect to the Citrix API (if connecting to & monitoring Citrix products)     		.NET Framework 4.8 (from 8.6.5)
    PowerShell 5.0
    (for Windows PS API)
    IOP Forwarder or access to shared directory where IOP Forwarder is installed*

    *Minimum recommended. For details, see Sizing Guidelines for ControlUp v8.x.

    Service Accounts

    ControlUp requires certain user permissions to have set up on your external sources, such as Hypervisors or EUC environments. You can find more information on required user permission here.

    Was this article helpful?
    What's Next