On-premises Installation Prerequisites 7.4 and Lower

Note: For versions 7.4 and below. If you are installing version 8.1 or higher, see these prerequisites.

ControlUp On-Premises Architecture

ControlUp On-Premises mode enables organizations to install the ControlUp back-end components on their on-premise private cloud / data-center. The following drawing is a high-level overview of ControlUp 7.x architecture when working in On-Premises mode:  


 On-Premises Server Prerequisites:

Supported Operating Systems

  • Windows Server 2016 Fully Patched
  • Windows Server 2012 R2 Fully Patched
  • Windows Server 2008 R2 Fully Patched


  • Free space of 50 GB
  • 4 GB of RAM
  • 2 vCPUs
  • The server part of a Domain
  • Disable the UAC
  • Microsoft .Net Framework 4.5.1
  • Microsoft .Net Framework 3.5
  • PowerShell 5.X or above


Supports Microsoft SQL versions are supported (both Standard and Enterprise editions):

  • SQL 2008 is NOT supported (R2 as well)
  • SQL Server 2012 (Note: Some of the builds are not supported)
  • SQL Server 2014
  • SQL Server 2016
  • SQL Server 2017
  • Note:
    • We strongly recommend having a dedicated clean server for the installation.
    • The ControlUp database needs to be moved to a supported SQL.
    • In the on-premises upgrade, the wizard defines the new SQL details.
    • In On-Prem v7.4, the installer has the option to auto-install a standalone SQL express (an automated process by the installer).
    • It is recommended to separate the ControlUp server from the SQL server for better performance
    • In case of upgrading from v5\v6, you will need to upgrade from v5 > v6 > v7 etc. Upgrade from 5 to 7 not supported. 
    • Run the exported upgrade SQL script on the ControlUp DB (follow the installation guide)
    • SQL DataBase recommended size - 10GB

Email Alerts Feature

Requires a local SMTP Server.

 Required Files

  • Please coordinate with ControlUp Support to receive the installation media for ControlUp On-Premises


  • ControlUp On-premises requires a license file provided by ControlUp
    • The license is a XML file
    • If you’re conducting a trial (POC), the installer will issue you a 21 days license automatically.
    • In order to receive the file, please follow the steps described in the ControlUp On-premises installation guide.

  Required AD Users & Groups

  • ControlUp Users Group
    • Members of this group will be authorized to use the ControlUp console.
    • Global - Security AD groups are supported. (Universal & Domain-Local not).
    • 'Domain Users' group is not supported.
  • ControlUp Service Account
    • The ControlUp service account runs the ControlUp On-premises server services, IIS Pools and will have db_owner right on the SQL database
    • Make sure the User Account is an Administrator on the on-premises server
    • Note – the installation wizard supports configuring a different account for the SQL database user
  • Primary Monitor Account -
    • Account defined in the monitor settings -> Identity 
    • The Monitor primary AD account require the "Log on Locally" user right on the Monitor service VM, so please verify 2 things:
      • the account has the "Allow log on locally" user right
      • the account is not part of the "Deny log on locally" user right

Related Ports

  • In order for the solution to work, you need few ports to be open:
    • On-premises server <-> ControlUp Console: Port 443
    • On-Premises server <-> SQL server: Port 1433 (need to verify with DBA)
    • ControlUp Console <-> ControlUp Agent: Port 40705
    • ControlUp Console <-> ControlUp Monitor: Port 40706


  • During the installation, we add IIS and LDS Roles to the ControlUp On-Premises Server
    • If the IIS is already installed and contains any other sites, they will be overwritten

 ControlUp’s Insights Server Prerequisites:

 Supported Operating Systems

  • Windows Server 2016 Fully Patched
  • Windows Server 2012 Fully Patched
  • Windows Server 2012 R2 Fully Patched


  • Free space of 50 GB (as a starting point)
  • CPU: 12 CPU cores at 2Ghz or greater speed per core
  • RAM: 12 GB
    • Recommended - 16GB RAM.
  • RAID: 0 or 1+0
  • 800 IOPS~ disk capabilities.


  • Make sure the server does not have splunk already installed, we do not support parallel installations.
  • RAID 0 disk configurations do not provide fault-tolerance. Confirm that a RAID 0 configuration meets your data reliability needs before deploying a Splunk Enterprise indexer on a system configured with RAID 0.

In an enterprise production deployment, it is recommended that ControlUp Insights On-Premises is provided with dedicated hardware resources, especially I/O. Running the system on virtual machines is supported, but performance is expected to degrade when hardware resources are allocated from a shared pool.

Daily Indexing Volume

The daily amount of data ingested into the Insights database is a key parameter that will be used for deployment and capacity planning. This parameter can be estimated using the following calculations:


  • For end-user computing workloads using shared desktops (e.g. in a server-based computing scenario using Remote Desktop Services) - 3MB per user/day.
  • For end-user computing workloads using private desktops (e.g. in a VDI scenario) - 6MB per user/day.
  • For general-purpose servers (e.g. infrastructure servers / DC / database / DNS / file servers, etc.) - 8MB per server/day.


The following example demonstrates a calculation of daily indexing volume for a virtualized environment with 1000 shared desktop users (peak concurrent), 500 personal desktop users (peak concurrent) and 30 general-purpose servers:


Resource type


MB / day

Expected Daily Indexing Volume

Shared desktop users

1000 (peak concurrent)


3,000 MB

Personal desktop users

500 (peak concurrent)


3,000 MB

General-purpose servers



240 MB



6.24 GB


The end result of the calculation above (6.24 GB) is the daily indexing volume that will be used for the capacity planning of Insights database storage as described below.

Insights Database

The sizing of storage for hosting the Insights database is based on the daily indexing volume multiplied by the number of days for which data is expected to be retained in the database, and by then multiplied by an additional constant which estimates the overhead associated with summary indexing and other auxiliary data accumulated in the database.

For example, an environment in which the daily indexing volume is 6.24 GB and the retention requirement is 365 days, the amount of disk space required for the Insights database is expected to be 2.28 TB. This estimate should be multiplied by 1.3 to predict indexing overhead, resulting in a total storage volume of 2.96 TB.


Data File Share

The data file share is a temporary storage location in which activity files are queued before ingestion into the Insights database.

The recommended amount of free space available on the data file share depends on the daily indexing volume.

By default, activity files are not removed from the data file share after being successfully ingested into the Insights database. It is therefore recommended that the data file share has sufficient capacity to accommodate activity files for the maximal period of time during which Insights On-Premises Server might be down.

 For example, to accommodate for 7 days of downtime in the example environment described above, the data file share size should be 6.24 GB x 7 days = 43.68 GB.


  • Please give modify permissions to the Monitors primary AD account on the shared folder of the data activity files (both share and NTFS).
  • Please add the Monitor's primary AD account to the local Performance Log Users Group (On the Monitor server).
  • The Monitor's primary AD account requires the permission "Log on Locally" on the Monitor VM where the service is installed.
  • The Monitors primary AD account can not be assigned the group policy "Deny log on locally"
  • Until further notice, we do not remove the activity files from the shared folder. Please make sure you have enough free space and the needed hardware to support the IOPS activity.
  • The IOP Server's AD machine account must have read access to the file share via both NTFS and Share permissions. 

ControlUp Real Time Console

 Supported Operating Systems

  • 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

 The only software prerequisite for the console is Microsoft .NET 4.5. Please ensure this prerequisite is met before running ControlUp or when upgrading from older (pre-v6) versions of ControlUp.


ControlUp Monitor

 Supported Operating Systems

  • Windows Server 2012 or later

Other Prerequisites

  • .Net Framework 4.5
  • RPC Access (at the installation phase)
  • Powershell 5.0 (for Windows PS API)
  • The Monitor's primary AD account requires the "Log on Locally" user right on the Monitor service VM (the service account defined in the monitor settings-> identity tab). So please verify 2 things:
    • The account has the "Allow log on locally" user right.
    • The account is not part of the "Deny log on locally" user right.


 For Any Sizing recommendations please refer to this KB article: ControlUp Sizing Guidelines






Powered by Zendesk