ControlUp On-Premises Server Installation

The following article walks you through the steps to install the ControlUp On-Premises (COP) Server. The server functions as the host server for COP backend services, such as user management, historical data uploader, or other communication services.

The COP Server installer installs IIS web services, and if Light Mode is selected, it installs an SQL Server Express instance on the COP Server. You can also deploy the ControlUp database on an SQL Server instance in your environment.

Important for COP 8.7 and All Later Versions

Due to a security feature introduced in COP version 8.7, you must use a JSON Web Token (JWT) to connect any ControlUp Monitor to Solve On-Premises (SOP).

Prerequisites

Contact us at support@controlup.com to receive the latest installation files for all on-premises components.

Installation Files

• Installation file (ControlUpSetup.exe) for the latest COP version.
• Optional: Import files for Script-based Actions and Virtual Expert.

Prerequisites COP Server

• Windows Server 2016 or later.
• .NET Framework 4.8 or later.
• Member of an AD domain.
• The domain controller must be accessible during installation.

Required Certificate

For COP 8.6.5 and all later versions, you must install the DigiCert Trusted G4 (RSA default) certificate on each machine that you install the console. If you have the latest Windows updates installed, this certificate should already be installed on your machine(s). You can download the certificate here.

COP Server Sizing

For hardware requirements, see On-premises Installation Prerequisites - Version 8.x.

Installation Guide

1. Run ControlUpSetup.exe as an administrator. On the start screen, click Continue.
   
2. Agree to the terms and privacy policy and click Accept.
3. Create a trial license to generate a trial license that allows you to use all on-premises features for 21 days. If you click Paid license, you can add your existing license file or create a license request, which you must activate after the installation. Click Continue.
4. Provide the installation path of the COP server and click Continue. It is best practice to use the standard path: C:\Program Files\ControlUp Inc\ControlUp Server
5. In the Alternate Failover Server screen, leave blank and click Skip. You can configure a failover COP server after the system is installed and tested.
   
6. Configure the service account to grant the Log on as a service user privilege on the machine. For example, the ControlUp LDS instance, or as a service user for the IIS webservices.
7. Select the deployment type of the ControlUp database:

• Light Mode. Select if you are running in a proof of concept. We recommend not to this option for production environments. If you select this option, SQL Express will be installed on the COP server.
• Production Mode. Select if you want to use an existing SQL Server instance in your environment. To configure your DB in Production Mode, see ControlUp On-Premises Database. Click Continue.
  

8. Select the import file for script actions or click Skip to skip the import. You can import the file later.
9. Select the import file for the Virtual Expert or click Skip to skip the import. You can import the file later.
10. If you want to use your mail server, enter the details on the screen. Click Skip if you don't want to send emails, or click Continue.
    
11. Select the AD user group that contains users that should be allowed access to ControlUp.
    Important

    The user group you select must belong to the same domain as the currently logged-in user.

12. In the IOP configuration window, enter the details of your IOP server. Skip this step if you don't have an IOP installed or if you want to install the IOP server later.
13. Configure the IP address or FQDN of your SOP server and the key file that you need to download from your SOP instance. Skip this step if you don't have SOP installed or if you want to install and configure SOP later. Click Continue.
    
14. Review the installation details and click Install.
    
15. If the installation succeeds, the Installed Successfully message appears. If the installation fails, see Troubleshooting.

Troubleshooting

Detailed error description

During the installation, a ControlUp Server.msi.log file is written to C:\Users\ UserName\AppData\Local\Temp. If the installation fails, a detailed failure reason appears. You can click Open Failure Log to open the log file to help troubleshoot the problem. If you need further assistance, you can send the log file to our support team.

Digital signature error during installation

If you receive the following error message, you must verify that the DigiCert Trusted G4 (RSA default) certificate is installed on the machine. This is a prerequisite for installing COP server 8.6.5 or later versions.