• On-premises Installation Prerequisites at a Glance for 8.1 and Higher

    The number and size of the servers required is determined by your company's size and level of use of ControlUp. While some of these can be installed on the same machine (for example for POCs), the Insights On-premises server must be installed on a separate server from the application and console. 

    Here is a quick description of each of the installed modules:

    • ControlUp Application Server: Backend components necessary for running ControlUp disconnected from any connections to the internet.
    • ControlUp Console: Gathers and displays current health & performance data. ControlUp's main frontend component. Can be installed on the same machine as the application.
    • Insights: Optional. Analyzes and reports 24/7 accumulated activity and performance data over time. Must be installed on a separate server from any of the other ControlUp modules. 
      • Insights On-Premises Forwarder (IOP Forwarder): Required if using Insights and requires a separate installation. Forwards the data from the monitor (see below) to the Insights server and must be installed either on a server with a shared activity folder that the monitors can access or on every monitor server. 
    ControlUp Module Application Server Console Insights Server
    Machine Windows Server Windows Server or
    Windows 
    OVA or Linux
    *Must be installed separately from Console and Application
    Operating system  Windows Server supported versions:
    2019,
    2016,
    2012 R2,
    2008 R2
    Windows Server supported versions:
    2019,
    2016,
    2012 R2,
    2008 R2
    OR
    Windows 10, 8, 8.1, 7

    Supported OVA:
    vSphere 6.5 and above.
    Supported Linux OS versions:
    Photon OS 3.0
    CentOS 7
     (or above)
    Ubuntu 16.4
     (or above)
    Red Hat Enterprise Linux 7.6

    CPU* 2 CPU  2 CPU 12 CPU
    Memory* 8 RAM  8 RAM 32 RAM
    Disk space* 10 GB  10 GB 100 GB OS Drive
    50 GB Data
    Required installed
    software/
    permissions/other

    - .Net Framework versions 4.7.2 (recommended),
    4.5, 3.5 (supported)
    - PowerShell 5.x or above

    Recommended for the installation:
    - IP address or FQDN of the machine where the Insights server will be installed.

    - Your SMTP server address

    .NET 4.5 or later

    For Linux:
    - Python 3.6
    - Docker 18.09.8 
     (or above)

    IOP Forwarder (see below)

     

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

    Database information

    Installation connects to a database which can be a SQL instance that already exists in your environment or one dedicated for ControlUp. 

    Server Versions Minimum Size Collation

    Microsoft SQL versions (Standard & Enterprise editions) - SQL Server 2017, 2016, 2014

    10GB SQL_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:

    • Agent: Lightweight component that enables rapid deployment and a minimal performance footprint on the managed machine. Every managed Windows machine that you want monitored in your environment must have an agent deployed for data to be sent to the console. (Linux machines are monitored via API.)
    • Data CollectorOptional. For increased performance of the console & monitor. Collects metrics from ‘external’ sources such as hypervisors, VMware, Citrix, NetScaler appliances, etc. Must be connected to an existing managed machine that has the ControlUp Agent deployed. 
    • ControlUp Monitor: Monitors assets 24/7 and enable triggers, alerts and automation. 
      Can be installed on the same machine as the application server (see above) but not recommended for larger installations. 
    ControlUp Module Agent Data Collector Monitor
    Machine No server installation necessary. Deployed onto Windows machines that are monitored by ControlUp
    (Linux monitored via API).
    Windows or Windows Server that has the ControlUp Agent deployed Windows Server
    Operating system  Windows Server supported versions:
    2019,
    2016 (Core or Full),
    2012 R2,
    2008 R2 (Full only)
    OR
    Windows 10, 8, 8.1, 7
    Windows Server supported versions:
    2019,
    2016,
    2012 R2,
    OR
    Windows 10, 8, 8.1, 7  
    Windows Server supported versions:
    2019,
    2016,
    2012 R2
    CPU* NA  2 CPU 2 CPU
    Memory* NA  8 RAM 8 RAM
    Disk Space* NA  10 GB 10 GB
    Required installed software - .NET 4.5 or later
    - Active Directory
    - ControlUp Agent
    - .Net Framework 4.7.2 or later (recommended)
    4.5 (supported)
    - Citrix SDK to connect to the Citrix API (if connecting to & monitoring Citrix products) 
    - .Net Framework 4.7.2 (recommended)
    - 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

    Additional resources

     

  • Insights On-premises Virtual Appliance Based Installation - Version 8.1 and Above

    The Insights On-premises (IOP) component captures, indexes, and correlates real-time data in a searchable repository from which you can view a variety of dashboards, graphs, reports, alerts, etc.

    The following are prerequisites for an Insights server in the On-premises topology.

    Insights On-premises v8.1 contains significant improvements in performance and user experience.
    This version of Insights is available in 2 installation modes:

    • Virtual Appliance - This option comes as an OVA that runs Photon OS Linux distribution.
      Currently, it only supports VMware ESXi 6.5 or higher.
    • Linux OS Installation - This option allows you to install the IOP on various Linux distributions.

    To read more about IOP 8.1 Virtual Appliance Based Installation, see here.

    IOP 8.1 contains the IOP Forwarder. This component forwards the activity files from the monitor servers to the IOP servers.

     

    Insights On-premises Prerequisites

    You can install IOP 8.1 as a Single (Standalone) variation or as a Cluster for better performance in larger environments.

    • Single (Standalone) - Recommended for companies with up to 5000 sessions, you need to prepare only one Linux server.
    • Cluster - Recommended for companies with 5000 sessions and more, in this variation you will need to prepare several Linux servers, 1 for the Master role and 1 Data role for every 5000 sessions.
      In cluster mode, you need to repeat the next chapters one time for the Master server and for each Data server.
      Sizing examples:
      # of Session # of Master nodes # of Data nodes
      6000 1 2
      9000 1 2
      11000 1 3

    Sizing Recommendations

    Mode Cores RAM Storage

    Single (Standalone) installation 

    Under 5000 Sessions

    12 Cores (Minimum)

    32 GB 

    100 GB OS drive

    500 GB DATA disk drive with 800 IOPs
    (SSD preferred)

    Clustered installation 

    Over 5000 Sessions

    Master Server

    12 Cores (Minimum)

    32 GB

    100 GB OS disk drive with 800 IOPs
    (SSD preferred)

    Data Servers (each)

    8 Cores (Minimum)

    16 GB

    100 GB OS drive

    1 TB DATA disk drive with 800 IOPs
    (SSD preferred) 

    Ports

    Port (tcp) Traffic Source Usage
    443 End-User IOP Interface.
    9997 CU Monitor\s Forwards data to IOP.
    Cluster Mode    
    8088 CU Monitors Sends monitor diagnostics to IOP servers.
    8089 CU Monitors
    Master Node
    Data Nodes
    Management port (Between Master and Data nodes).
    9887 Data Nodes Data Replication.

     

    Browser

    • IOP fully supports Chrome browser and the New Edge (based on chromium).

    OVA Deployment 

    To install Insights, the files must be prepared in advance. If you don’t have the installation files, contact support@controlup.com to receive them.

    To install the IOP OVA:

    1. Login to your V-Sphere with your Admin account.
    2. Right-click on one of your hosts, and choose Deploy OVF Template… and the Select an OVF template window appears.
      mceclip1.png
    3. Select the Local file and click Choose Files to choose the IOP OVA file.mceclip2.png
    4. Specify the virtual machine name and select the data center that the virtual machine will be under and select the host where the virtual machine will be deployed.
    5. Click Next on the Review details page once you have ensured that the details are correct.
    6. Select the Virtual Disk format and the virtual machine storage policy (both of the “thick” formats are recommended for better performance and flexibility) and the virtual machine storage policy.
    7. mceclip3.png.
    8. In the Customize Template page, specify the following for each section:
      1. Host Name Details:
        • Required: Host name of the appliance. (i.e. iop_server)
        • Recommended: The DNS domain name of the appliance.
      2. Networking:
        • For DHCP - leave them all empty
          Note: If you are installing a clustered IOP, it is recommended to use static network configuration, instead of a DHCP.
          • IP Address: IP + CIDR for the machine. (Default: DHCP)
            Example: CIDR notation for a static IP - 10.10.10.10/24 
          • Default Gateway - The default gateway address for this virtual machine. (Default: DHCP)
          • DNS - The IP address of the DNS server of the organization. (Default: DHCP)
      3. Credentials:
        • Required: Password for the root user of the virtual machine.
          • Password details:
            • It is recommended to use a strong password.
            • This is an Admin password for the IOP.
            • This password is to be used in all future for upgrades.
      4. Appliance Settings:
        • Required:
          • Machine type. (Standalone/Master/Data)
          • If you choose 'Data' as your machine type - specify the DNS/IP of the master appliance.
    9. Review the selected settings and click Finish and the virtual machine is ready for configuration, as describe in the following section.

    Post Installation Configuration

    Once virtual machine it is installed in must be configured before starting it.

    The default disk capacity for IOP data volume is set to 150 GB.

    To increase disk capacity for standalone/data machines:

    1. Right click on your virtual machine name from the list on the left.
    2. Choose the Edit Settings… option.
    3. Change the number for the Hard disk 2 option to the capacity you want.

    Finalizing the Virtual Based Appliance Installation

    Once all configurations have been set, you must launch the console and complete the installation to begin using it.

    To finalize the installation:

    1. Click on the green button to start the machine.
    2. To see the console logs, go to the Summary section in your virtual machine page, and click the Launch Web Console option under the image square.
    3. Choose the Web Console option and click OK. (The login to the virtual machine is “root”.)

    When the installation is complete, you can connect to your Insights by going to https://<Server_IP>.

    Once the installation is complete the IOP Forwarder must be installed in to receive activity files.

    Insights On-premises Forwarder Installation

    The Insights On-premises (IOP) Forwarder is a component that forwards the activity files from monitor servers to the IOP servers and requires a separate installation. It forwards the data from the ControlUp monitor to the Insights server and must be installed either on a server with a shared activity folder that the monitors can access or on every monitor server. 

    During the ControlUp On-premises installation you must choose a location for the Activity Files.
    If you choose a local folder, then you need to install the IOP Forwarder on each monitor. If you choose a shared location, you need to install only one IOP Forwarder.

    To install the IOP Forwarder:

    1. Login to your monitor windows machine.
    2. Contact support@controlup.com to receive the iop_forwarder_stable.msi
    3. Run the iop_forwarder_8.1.733.XX.msi file and click Next to begin the installation:
      f1.png
    4. Use the Folder dropdown menu to select where on the monitor machine the installer should be installed, and click Next to continue.
      f2.png
    5. Choose the type of installation (Standalone or Cluster) according to the type of Insights installation, and click Next to continue.
      f3.png
    6. Select the Activity Files path folder location and then enter the IP of your IOP Server machine, and click Next to continue.
      fw006.png
    7. Click Install and the forwarder is installed. A confirmation popup appears once the prcess is complete.
      f5.png
      fr05.png

     

  • Insights On-premises Linux-based Installation - Version 8.1 and Above

    CentOS-01.png Ubuntu-01.png RedHat-01.png

    The Insights On-premises (IOP) component captures, indexes, and correlates real-time data in a searchable repository from which you can view a variety of dashboards, graphs, reports, alerts, etc.

    Insights On-premises v8.1 contains significant improvements in performance and user experience.
    This version of Insights is available in 2 installation modes:

    • Virtual Appliance - This option comes as an OVA that runs Photon OS Linux distribution.
      Currently supported only on VMWare.
    • Linux OS Installation - This option allows you to install the IOP on various Linux distributions.

    To read more about IOP 8.1 Virtual Appliance Based Installation, see here.

    IOP 8.1 contains the IOP Forwarder. This component forwards the activity files from the monitor servers to the IOP servers.

    Insights On-premises Prerequisites

    You can install IOP 8.1 as a Single (Standalone) mode or as a Cluster mode for better performance in larger-scale environments.

    • Single (Standalone) - Recommended for companies with up to 5000 sessions, you need to prepare only one Linux server.
    • Cluster - Recommended for companies with 5000 sessions and more, in this variation you will need to prepare several Linux servers, 1 for the Master role and 1 Data role for every 5000 sessions.
      In cluster mode, you need to repeat the installation steps once for the Master server and then for each Data server.
      Sizing examples:
      # of Session # of Master nodes # of Data nodes
      6000 1 2
      9000 1 2
      11000 1 3

    Sizing Recommendations

    Mode  Cores RAM Storage

    Single (Standalone) installation 

    Under 5000 Sessions

    12 Cores
    (Minimum)

    32 GB 

    100 GB OS drive

    500 GB DATA disk drive with 800 IOPs
    (SSD preferred) mounted under /opt/iop_volumes/data/

    Clustered installation 

    Over 5000 Sessions

    Master
    Server

    12 Cores
    (Minimum)

    32 GB

    100 GB OS disk drive with 800 IOPs
    (SSD preferred)

    Data
    Servers
    (each)

    8 Cores
    (Minimum)

    16 GB

    100 GB OS drive

    1 TB DATA disk drive with 800 IOPs
    (SSD preferred)
    mounted under /opt/iop_volumes/data 

    Operation System

    • Linux Kernel 2.4
      • CentOS 7 (or above)
      • ubuntu 16.4 (or above)
      • Red Hat Enterprise Linux 7.6

    Required Packages

    • Python 3.6
    • Docker 18.09.8 (or above)

    Browser

    • IOP fully supports Chrome browser and the New Edge (based on chromium).

    Firewall Settings

    The following ports need to be opened, depending on the installation mode.

    Machine type
    Inbound open ports

    Single Standalone

    • 443
    • 9997
    Cluster - Master
    • 443
    • 8089

    Cluster - Data

    • 9887
    • 9997
    • 8089

    More information about each port:

    Port (tcp) Traffic Source Usage
    443 End-User IOP Interface.
    9997 CU Monitor\s Forwards data to IOP.
    Cluster Mode    
    8088 CU Monitors Sends monitor diagnostics to IOP servers.
    8089 CU Monitors
    Master Node
    Data Nodes
    Management port (Between Master and Data nodes).
    9887 Data Nodes Data Replication.

     

    Insights On-Premises Installation

    Checking the Prerequisites

    Before you start the IOP installation, check that the prerequisites are met.

    Check that the Python and the Docker are installed.

    Note: The Syntax can be different between the Linux OS versions.

    To check that the Python and the Docker are installed:

    1. Connect to your Linux CLI and enter 'python' and press Tab twice.
    2.  Run 'docker -v' in the CLI.
      • If the components are installed, the following message appears:
        Sen02.png
      • If the components are not installed:
        Sen01.png

    If you don't have the Docker installed, you can follow the instructions from one of the sites below:

    Once the Linux OS is ready, you can start the IOP installation.

    To start the IOP installation:

    Copy Files From Windows to Linux

    To install Insights on your Linux machine, the files must be prepared in advance. If you don’t have the installation files, contact support@controlup.com to receive them.

    1. Download the IOP package to your Windows machine.
      • iop_forwarder-8.1.733.XX.msi
      • iop_8.1_images_stable.tgz
      • iopcmd-8.1.733.XX.tgz
    2. Copy iop_8.1_images_stable.tgz and iopcmd-8.1.733.XX.tgz to your Linux machine. To copy files from Windows OS to Linux OS you can use the WinSCP tool.
      • Open the WinSCP tool and make a connection to your Linux.
        movefiles02.png
      • Copy the files to your Linux user home folder.
        movefiles01.png

        Screenshot_1.png

    Prepare the Files for the Installation

    1. Log in to your Linux machine.
    2. Move the iop_8.1_images_stable.tgz and iopcmd-8.1.733.<latest build number>.tgz file from the user folder to /opt folder.
      (For example, a typical file name would be: iopcmd-8.1.733.60.tgz if the latest build number published is built 60.) 
      • sudo mv iop_8.1_images_stable.tgz /opt/
      • sudo mv iopcmd-8.1.733.<latest build number>.tgz /opt/
    3. CD into “/opt/” directory and extract the installation file.
      • sudo tar zxvf iopcmd-8.1.733.<latest build number>.tgz
    4. Move the iop_8.1_images_stable.tgz to “/opt/iopcmd/iop_images.tgz” 
      • sudo mv /opt/iop_8.1_images_stable.tgz /opt/iopcmd/iop_images.tgz
    5. CD into "/opt/iopcmd/" directory.

    Installation Process

    Prior to installation there a few important things to note:

    1. Password:
      • It is recommended to create a strong" password.
      • The password is an Admin password for the IOP and will be used in the future for upgrades.
    2. Once the installation is complete, it is recommended to remove the iop_images.tgz from the /opt/iopcmd/ directory.
    3. Once the installation is complete, you can connect to your Insights by browsing to https://<Your Server_IP>.

    Single (Standalone) Installation

    • Run the Install command, and the installation begins
      • sudo ./iopcmd install local -t standalone -pwd <Your Password> -p iop_images.tgz
        • For example:
        • sudo ./iopcmd install local -t standalone -pwd abc123 -p iop_images.tgz

    Cluster Installation

    1.  Run the Install command on the Master server, and the installation begins.
      • sudo ./iopcmd install local -t master -pwd <Your Password> -p iop_images.tgz
        • For example:
        • sudo ./iopcmd install local -t standalone -pwd abc123 -p iop_images.tgz
    2. Once the installation is complete, run the Install command on the Data servers
      • sudo ./iopcmd install local -t data -m <DNS name or ip address of Master> -pwd <Your Password> -p iop_images.tgz

    Insights On-premises Forwarder Installation

    The Insights On-premises (IOP) Forwarder is a component that forwards the activity files from monitor servers to the IOP servers and requires a separate installation. It forwards the data from the ControlUp monitor to the Insights server and must be installed either on a server with a shared activity folder that the monitors can access or on every monitor server. 

    During the ControlUp On-premises installation you must choose a location for the Activity Files.
    If you choose a local folder, then you need to install the IOP Forwarder on each monitor. If you choose a shared location, you need to install only one IOP Forwarder.

    To install the IOP Forwarder:

    1. Login to your monitor Windows machine.
    2. Contact support@controlup.com to receive the iop_forwarder_stable.msi file.
    3. Run the file and the Welcome to the IOP Forwarder Setup Wizard screen appears. Click Next and the Select Installation Folder screen appears.
    4. f1.png
    5. Use the Folder dropdown menu to select where on the monitor machine the installer should be installed, and click Next to continue.
      f2.png
    6. Choose the type of installation (Standalone or Cluster) according to the type of Insights installation, and click Next to continue.
      f3.png
    7. Select the Activity Files path folder location and then enter the IP of your IOP Server machine, and click Next to continue.
      fw006.png
    8. Click Install and the forwarder is installed. A confirmation popup appears once the prcess is complete.
      f5.png
      fr05.png
  • Horizon Integration

    From version 8.1 and up, ControlUp allows VMware Horizon integration by monitoring and collecting metadata directly from the Horizon API. This allows ControlUp to display real-time Horizon specific information.

    Native API integration with VMware Horizon enables customers to add Horizon environments to the ControlUp Console, enabling:

    • Automatic discovery of Horizon components in both standard and Cloud Pod architecture.
    • Seamless association of Horizon components with entities from different data sources, such as hypervisors and in-guest agents for complete line-of-sight from infrastructure to process.
    • Connection server health status & license monitoring.
    • Enhanced session monitoring with Horizon performance metrics.
    • Horizon-focused presets for Horizon Pods, connection servers, pools, machines, and sessions views.
    • Enhanced Horizon environment management capabilities, including new Horizon specific:
      • Built-in actions
      • Security policy permissions
      • Script Actions
      • Automated Actions
      • Enhanced Virtual Expert rules and recommendations

    For Horizon integration, ControlUp Agent deployment is not required for this discovery process.

    The ControlUp Agent is required for monitoring the performance of your VDIs and connection servers, and for displaying processes running on your VDIs and connection servers.

    Note: Each session discovered by the Horizon connection is counted as one ControlUp license.

    Integration Requirements

    • Permissions
      • Read-Only
        • Manage Help Desk (Read only)
        • Direct Interaction
      • Actions
        • Enable Farms and Desktops Pools
        • Manage Machine
        • Manage Sessions
        • Manage Global Sessions (Cloud Pod architecture only)
    • Network
      • 443 open to all Horizon connection servers
    •  Support
      • Full Support - VMware Horizon v7.4 and up
      • Limited Support - VMware Horizon v7.0 to 7.3

    Horizon RDSH Monitoring

    From version 8.2 and up ControlUp can discover Horizon RDSH components and offer real-time visibility of RDS sessions and applications.

    The new RDSH objects in the Horizon integration are displayed on the organizational tree and data grids, with drill down relations for easy troubleshooting and navigation.
    The new views include real-time metrics displaying the current configuration, availability, aggregation counters, health status, and other metadata on the following objects:

    • Application Pools
    • Farms
    • RDS Hosts
    • RDS Desktop Pools
    • RDS Sessions
  • ControlUp Data Collector

    The Data Collector is responsible for collecting metrics from external sources such as VMware vCenter, Citrix Delivery Controllers, XenServer Poolmasters, AHV Clusters, and NetScaler appliances. Data collectors increase the performance capabilities of both your console and monitor. 

    Benefits of having a data collector 

    In the image on the left side, you see 2 consoles and a monitor both connected straight to the vCenter without a data collector. Each of these components is initiating its own API query to vCenter to gather data.

    With this configuration, the API gets 3 API queries each interval. In very large environments, the traffic can be substantial. 

    In the image on the right side, a data collector is deployed. The only entity that does the API query is the data collector and it saves the data locally on the machines memory buffer. The consoles & monitor, which are connected to the agent on the data collector (light connection), can read the data from the agent itself instead of performing their own API queries. 

    inline1865324782.png

    *Example shows 443 but can also be referred to 80\9440

    Data collector requirements 

    • A data collector is assigned 4 vCPUs and 8 GB of RAM. (View the Sizing Guidelines article for exact sizing information.)
    • The OS can be either a client or server. 
    • The machine must have the ControlUp Agent installed on it. 
    • .Net Framework v4.5
    • Depending on the type of port connection, you should enable ports 80/443/9440.
    • A pair of data collectors can be provided for high availability purposes. 
    • In the event of a failure of the data collector, a backup data collector assumes this role until the data collector is brought back online.
    • SDKs from Citrix must be deployed to the Data Collector to connect to the XenDesktop Delivery Controllers (you can download it from the following article).

    Note: If you have more than 5 external sources to connect to a data collector, please contact us for sizing recommendations at support@controlup.com

    Data collector configuration

    The following steps are strongly recommended to ensure optimal performance of ControlUp connections to the console and the monitor. It is a best practice to designate one or more machines in your ControlUp organization to act as a dedicated data collector for hypervisors. The steps below should be performed either while you add your hypervisors / EUC environments or after you have already added them. The data collector must be connected to every hypervisor / EUC environment in your environment.

    To configure a dedicated data collector:

    1. Add a managed machine to the console which will function as the data collector and will
      later be defined as the active data collector. You must designate this machine as the data collector for every hypervisor and EUC environment connection. 
    2. - To add the data collector to a new hypervisor or EUC environment, click either Add Hypervisor or Add EUC Environment in the top ribbon. You must set up the connection to the hypervisor or EUC environment in the top area of the dialog and then follow the steps below. 
      - To add a data collector to an existing hypervisor or EUC environment, right-click it in the organization tree and select Connection Settings .
        CD_ConnectionSettings.png
      For hypervisors, the Connection Options section below the connection to the hypervisor is where you designate data collectors. For EUC Environments it is in the Data Collectors tab. CD_ConnectionArea.png
      Tip: If you don't see the Connection Options area, click the down arrow at the side.
    3. By default the ControlUp Console/Monitor acts as a data collector so to designate a data collector you first have to remove this default. 
      Click Remove and then OK. The Controlp Console/Moniotor is removed as the default.
      CD_RemoveCU.png
    4. If you are in the connection options for a hypervisor, click +Add.
      If you are in the connection options for an EUC environment, click the Data Collectors tab and then click +Add.
    5. Select the managed machine you added to function as the designated data collector in step 1 above, and click OK.
      Your data collector is now configured for this connection.
    6. Repeat for every hypervisor/EUC environment. 

    You can also set a monitor as a data collector by installing the agent on the monitor machine and following this procedure.

  • Proxy Information for ControlUp - Hybrid Cloud

    Customers of ControlUp that are using a proxy in their environment should have the ControlUp cloud configuration servers whitelisted and open going out via the proxy. 

    The following URL's/IP addresses should be available via https (443):

    • fe1.controlup.com - 52.31.169.19
    • fe2.controlup.com - 52.22.91.133
    • fe3.controlup.com - 52.31.158.49
    • fe4.controlup.com - 52.23.86.15
    • US Load Balancers:
      • rt-app.controlup.com - 34.195.43.52
      • rt-app.controlup.com - 54.86.39.124
    • EU Load Balancers
      • rt-app.controlup.com - 18.200.38.56
      • rt-app.controlup.com - 52.212.202.250
    • mp.controlup.com
    • s3.amazonaws.com
    • Insights-hec.controlup.com

    If you have any further questions regarding proxy, feel free to contact us at support@controlup.com

  • Moving from On-Premises to Hybrid Cloud

    ControlUp users can choose to move from an On-Premises deployment to a Hybrid Cloud deployment.
    This action needs to be coordinated with your account manager in order to achieve this process because there are licensing differences.
    Moving to our Hybrid Cloud will require these following steps:

    1. License change from On-Premises to Hybrid Cloud. (for this step, please contact your account manager or support at support@controlup.com)
    2. Log in to your On-premises ControlUp Console.
    3. Uninstall & remove all Monitors.
    4. Chane Registry (on each computer where the Console is launched).
      • Go to HKEY_LOCAL_MACHINE > SOFTWARE > SMART-X > CONTROLUP > AGENT > PRIVATECLOUD and change the value of "IsUsingPrivateCloud" to 0.
    5. Log in to the same organization that you used on your ControlUp On-Premises environment.
    6. Launching the Console after the changes from the same machine will upload your configuration to the Cloud so it will be stored there and synced with the other Consoles in your organization. 

     

  • ControlUp Hybrid Cloud Implementation Requirements

    The ControlUp Hybrid Cloud implementation is composed of three main components:

    • Console - for real time environment monitoring and management.
    • Monitor - to monitor your environment 24/7, and uploading historical and analytical data to our Hybrid Cloud infrastructure.
    • Agents - to communicate with the Console and Monitor. 

    For information regarding communication ports for each of the components, see here

    ControlUp Console Requirements

    ControlUpConsole.exe is the main executable used for data display and task invocation. No setup is needed to start using ControlUp. Just download the executable and run it on your admin station or a management server.

    ControlUp console is compatible with:

    • 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 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 extremely 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, laptop, Windows VM, or can be published as a XenApp application. 
    • .Net 4.5
    • Download the executable from our website. (No installation required, run the executable with ease!)
    • 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 hostname
    • 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

    The ControlUp Monitor is a component principally equivalent to ControlUp Console but without an interactive user interface. 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.

    Prerequisites for ControlUp Monitor

    • Windows Server 2008 or above
    • .NET Framework 4.5 
    • RPC Access enabled at the installation phase

    Read more about the benefits of Control-Up Monitor and how to set it up here.

    ControlUp Agent

    The ControlUp Agent is a lightweight service that gets installed on the managed computers in your organization. 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 a 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 - Windows 7 to Windows Server 2019. (Windows 2003 is not supported.)
    • .Net Framework 3.5 SP1 or 4.5 and above.
    • 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 is not available, the agent can be installed manually using the MSI package.
  • 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:  

    Architecture_COP_2020.png

     On-Premises Server Prerequisites:

    Supported Operating Systems

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

    Requirements

    • 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

     Database

    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

     License

    • 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

    Appendix

    • 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

    Requirements

    • 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.

    Note: 

    • 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

    Count

    MB / day

    Expected Daily Indexing Volume

    Shared desktop users

    1000 (peak concurrent)

    3

    3,000 MB

    Personal desktop users

    500 (peak concurrent)

    6

    3,000 MB

    General-purpose servers

    30

    8

    240 MB

    Total

       

    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.

    Note:

    • 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

     

     

     

     

     

  • Managed Computers Requirements

    ControlUp supports managing computers that run:

    • Windows 7
    • Windows 8 (or 8.1)
    • Windows 10
    • Windows Server 2008 (Full installation only\core edition is not supported), Windows Server 2008 R2
    • Windows Server 2012
    • Windows Server 2016 (Core or Full Installation)
    • Windows Server 2019 (Full Installation)

    Managed computers should have:

    • Microsoft .NET Framework 3.5 installed or greater. 
    • Windows 7 or Server 2008 R2, the built-in .NET Framework feature should be enabled
    • Alternatively, .NET Framework 4.5 can be used on managed computers running Windows 8 / Server 2012 or later
    • ControlUp requires RPC access for remote agent installation and a single configurable incoming TCP port open (40705 by default) for agent communication. In case your managed computers are inaccessible using RPC, you can deploy the ControlUp agent using an MSI package. For more details, see “Add Managed Computers”.
  • Active Directory & DNS Requirements

    Active Directory is a prerequisite for managing computers using ControlUp. If your network includes computers that are not joined to a domain, you will be able to connect to these computers using ControlUp’s Remote Desktop view while other actions will not be available.

    The computer on which ControlUp Console is executed does not have to be a domain member. However, you will be required to enter valid domain credentials in order to manage computers in your environment.

    Full DNS name resolution is also mandatory for management connections using ControlUp. You should be able to access all of your managed computers using their Fully Qualified Domain Names (FQDN).

    As an exception to the above, virtual machines (including non-Windows guests) can be monitored via the hypervisor layer without the need for DNS resolution or AD domain membership. This agentless approach only enables access to VM-related data known to the hypervisor, not guest OS data.
    (Read more…)

    By default, ControlUp queries Active Directory for the DNS suffix when managed computers are added to the organization tree. For networks in which the domain name is not identical to the default DNS suffix of all computers, ControlUp supports for providing a custom DNS suffix during computer addition.
    (More details…)

  • Security Rights & Permissions

    By default, local administrative privileges on all managed computers are required in order to connect to these computers using ControlUp. Every time you attempt to run a management action using ControlUp, your Windows credentials will be evaluated according to your current ControlUp mode:

    • Enterprise Mode – in this mode ControlUp operates by evaluating both your current Windows credentials and the Security Policy configured using your organization’s central configuration. In Enterprise Mode the permissions may be restricted to limit access to ControlUp features for designated administrators, regardless of their existing Windows rights.
    • Standalone Mode – your Windows user account will always need to have full administrative rights on all target computers. If your account is not a local administrator on the managed computer, ControlUp agent will refuse the connection and you will not be able to monitor performance or execute management actions on that computer.

    For more information on configuring ControlUp permissions, see the Secure Your Organization chapter.

    For agentless monitoring of virtual machines, access permissions for the hypervisor are required.
    For more details, see Hypervisor Monitoring Requirements.

  • Hypervisor Monitoring Requirements

    Supported Hypervisor Platforms

    ControlUp supports VMware v4.x/5.x/6.x environments that are managed by vCenter. Standalone ESX/ESXi servers are not supported. ControlUp also supports Citrix XenServer v6.1 (with the Performance Monitoring Enhancement Pack, CTX135033), v6.2 and v7.0. For earlier versions, some performance columns not yet implemented in XenServer might be displayed as N/A. 
    Microsoft Hyper-V 2012 R2, Microsoft Hyper-V 2016 including standalone and clustered hosts. Please note that ControlUp Agent needs to be installed on the Hyper-V hosts to enable monitoring them as hypervisors (The console does not work on any version of Core, but the agent is fine as long as you have .Net 3.5.1 or .Net 4.6.2.).
    ControlUp Console supports two hypervisors platforms running on Nutanix (AOS), VMware vSphere and Nutanix Acropolis Hypervisor (AHV). You can now also manage your Nutanix AHV clusters - live, with real-time metrics in the familiar ControlUp way(https://support.controlup.com/hc/en-us/articles/360001166145-Connecting-to-your-Nutanix-AHV-hypervisor).

    Network Connectivity

    ControlUp data collection agents (ControlUp Console by default, or agents if explicitly designated) require https (tcp/443) access to the vCenter server or the XenServer pool master.

    Hypervisor Permissions

    VMware

    Required vCenter permissions: the Read-Only role is sufficient for all monitoring purposes. If you want to be able to use the built-in hypervisor-based VM power management functions, then you will need to create a custom role based on the Read-Only role, adding the following permissions:

    • In the Virtual Machine/Interaction category:
      • Power Off
      • Power On
      • Reset

    vSAN Prerequisites
    In order to retrieve vSAN metrics and metadata, please follow these requirements 

    System Requirements for the ControlUp Data Collector:
    PowerShell minimum Version 5.0 (with RemoteSigned execution policy)

    • VMware PowerCLI minimum Version 10.1.1.x  (if needed, Ignore Invalid SSL Certificates)
    • .NET framework version 4.5

    Example:  Set-PowerCLIConfiguration -InvalidCertificateAction Ignore -Scope AllUsers

    vSAN Requirements:

    • vSAN Performance service should be turned on
    • The user account configured for the hypervisor connection requires the "storage.View"

    XenServer

    If Active Directory authentication is enabled for the XenServer pool, then the Read-Only role is sufficient. If you want to be able to use the built-in hypervisor-based VM power management functions, then you will need to upgrade the user role to ‘VM Operators’.

    Nutanix

    ControlUp requires for the user\service account to have 'Viewer' only role for view only capabilities (the user that you connect your Console to the hypervisor with). If you want to perform VM power management & host maintenance actions, you'll need to grant the user\service account with the 'Cluster Admin' role.
    In order to use a dedicated user\service account that you already have configured in your environment - you'll need to add your organizational Active Directory to Nutanix by going into Prism, Click the Gear Icon> 'Authentication'. When you're finished with adding your AD - you can 'Test' the connection in ControlUp console and verify that it works. 
    If you don't want to connect your AD to your Nutanix cluster, you can create a local user in the Nutanix local management within Nutanix Prism. Click the Gear Icons > 'Local User Management' and add the user with the proper role required.