• Insights On-Premises OVA-Based Upgrade Guide 8.x to 8.5

    This guide explains the installation steps for the Insights On-premises (IOP) server. This article is part of the On-Premises Upgrade Guide 8.x to 8.5. Use this upgrade guide only if you:

    Table of Contents:

    Upgrade IOP Server

    The IOP server can be deployed in two different modes - as a cluster or standalone. Each of these modes can run with static IP addresses (preferred) or with DHCP. This guide explains the upgrade steps for static IP addresses. 

    Important: If you are using IOP server(s) in a DHCP environment, contact our Support team at support@controlup.com.

    Upgrade a Standalone IOP Machine

    This section describes the upgrade of a standalone machine that uses a static IP address. A standalone installation consists of only one machine therefore perform the upgrade on that dedicated IOP machine.

    1. Open your vCenter Client with a user that is assigned to the Administrator role.
    2. Create a new IOP server using the new OVA file with the version you want to upgrade to. In our case, version 8.5.
      Perform the installation according to the Insights On-Premises Virtual Appliance Installation - Version 8.5 guide.

      Note: During the installation process for the new IOP, you need to enter a unique display name for the virtual machine (see Step 5). Make sure that you choose a different display name as two machines can not have the same display name.

      Important: When entering the new template properties, provide the same details as the old appliance. For example, hostname, DNS domain, IP, Gateway, password, etc.

    3. Wait until the import and creation process of the new IOP server is finished. Do not turn on the machine yet. 
    4. SSH into your old IOP server. 
    5. Log in as the root user.
    6. Stop the IOP services by running the following command and wait until all services are stopped:
      iopcmd stop
      1.png

    7. Shut down the machine by running the following command:
      shutdown -P 0

    8. On the old IOP server, note the storage that is used.
      2.png

    9. Open the storage on which the old IOP server is hosted. Select the Datastores view on the IOP server and then click on the datastore the machine is on.
      3.png

    10. Select the Files tab and search the old IOP machine on the left side menu.
      4.png
    11. Select the vmdk file, which has the format [VirtualMachineName]_1.vmdk, and click Copy to.
      5.png

    12. In the Select Destination window, select the new IOP server and click OK. The copy of the virtual disk to the new IOP server starts.
      Important: Make sure to have enough free disk space on the destination datastore before you copy the vmdk file to the new IOP machine.
      6.png

    13. Click the Monitor tab > Tasks and watch the status of the copy process. Wait until the copy file task is finished.
      7.png

    14. Select the new IOP server from the left side menu and right-click on it. Select Edit Settings.
      8.png

    15. Click the X sign to remove the Hard disk 2 with 50 GB.
      9.png

      Check the Delete files from datastore checkbox to confirm the deletion of the device.
      10.png

    16. Click OK. Once the operation completes, proceed to the next step. 
    17. Right-click the new IOP server and select Edit Settings
    18. Click the ADD NEW DEVICE button on the top right-hand side of the screen and click the Existing Hard Disk option.
      11.png

    19. In the Select File screen, select the storage and the new IOP server. Select the VMDK that you copied in Step 12. Click OK to confirm the file. 
      12.png

    20. A new hard disk is shown in the settings. Confirm by clicking OK

      Note: The size of the new hard disk must be the same as the size of the exported HDD.


      13.png

    21. Wait until the reconfiguration task is finished.
      14.png

    22. Verify that the upgrade was successful.
      1)    Power on the new IOP machines and wait until the machine is booted. 
      2)    From your Real-Time Console, open the Insights portal by browsing the IP of the IOP server.
      3)    Log in to the portal and check if data that existed before the upgrade is shown in the portal.
    23. Install the new IOP Forwarder on all monitor machines by running the iop_forwarder-[IOPVersion].msi. Follow the installation instructions from the IOP Forwarder installation guide
    24. Remove the old IOP server once you confirm that old and new metrics data are shown in Insights.
      To delete the machine, open the vSphere client, right-click the old IOP virtual machine, and select Delete from Disk. 
      test.jpg


    Click YES to delete the disk.
    ConfirmDeletion1.png



    Upgrade IOP Cluster Machines

    This section describes the upgrade in a cluster environment that uses static IP addresses. In a clustered environment, you have a master node and one or more data nodes that all need to be upgraded. 

    This section describes the upgrade for clustered IOP servers that use static IP addresses

    Follow these steps for the master node and each data node.

    Start with the upgrade of the master node:

    1. Open your vCenter Client with a user that is assigned to the Administrator role.
    2. Create a new IOP server using the new OVA file with the version you want to upgrade to. In our case, version 8.5.
      Perform the installation according to the Insights On-Premises Virtual Appliance Installation - Version 8.5 guide.

      Note: During the installation process for the new IOP, you need to enter a unique display name for the virtual machine (see Step 5). Make sure that you choose a different display name as two machines can not have the same display name.

      Important: When entering the new template properties for the master and data node(s), make sure to use the same virtual appliance password, hostname, DNS domain, IP/Subnet in CIDR notation, Default Gateway, and DNS settings as your old IOP machines.

      An example is shown below:
      StaticIPAddresses.png

    3. Wait until the import and creation process of the new IOP server is finished. Do not turn on the machine yet. 
    4. SSH into your old IOP machine.
    5. Log in as the root user.
    6. Stop the IOP services by running the following command and wait until all services are stopped:
      iopcmd stop
      1.png

    7. Shut down the machine by running the following command:
      shutdown -P 0
    8. On the old IOP server, note the storage that is used.
      iop_master.png

    9. Open the storage on which the old master node is hosted. Select the Datastores view on the old IOP server and then click on the datastore the machine is on.
      38_Datastore.jpg

    10. Select the Files tab and search the old IOP machine on the left side menu.
      FIleMaster.png
    11. Select the vmdk file, which has the format [VirtualMachineName]_1.vmdk, and click Copy to.
      FileMaster2.png

    12. In the Select Destination window, select the new IOP server and click OK. The copy of the virtual disk to the new IOP server starts.

      Important: Make sure to have enough free disk space on the destination datastore before you copy the vmdk file to the new IOP machine.


      Destination.png
    13. Click the Monitor tab > Tasks and watch the status of the copy process. Wait until the copy file task is finished.
      7.png

    14. Select the new IOP server from the left side menu and right-click on it. Select Edit Settings.
      EditSettingsNew.png
    15. Click the X sign to remove the Hard disk 2 with 50 GB.
      RemoveHDD.png
      Check the Delete files from datastore checkbox to confirm the deletion of the device.
      10.png
    16. Click OK. Once the operation completes, proceed to the next step. 
    17. Right-click the new IOP server and select Edit Settings
    18. Click the ADD NEW DEVICE button on the top right-hand side of the screen and click the Existing Hard Disk option.
      NewExistingDisk.png
    19. In the Select File screen, select the storage and the new IOP server. Select the VMDK that you copied in Step 12. Click OK to confirm the file. 
      ChooseNewHDD.png
    20. A new hard disk is shown in the settings. Click OK to confirm. 

      Note: The size of the new hard disk must be the same as the size of the exported HDD.


      NewHDD.png
    21. Wait until the reconfiguration task is finished. The upgrade of the master node is completed.
      ReConfigureOK.png

      The next step is to upgrade the data nodes. Before you can start to upgrade the data nodes, you need to follow these steps on each of the data nodes:

      On each data node:

      1. Remove the data containers by running this command
        docker stop iop_data && docker rm iop_data
        23_DataNodeStop.jpg
      2. Set the same password, new IP / DNS of the master node for each data node by running this command:
        iopcmd install -t data -pwd <SAME PASSWORD> -m <NEW_MASTER_IP>

        <SAME PASSWORD> is the password for the old appliance.
        <NEW_MASTER_IP> is the IP address of the new IOP master that we deployed in the previous chapter.
        25_DataNodeNewIP_OK.jpg
    22. Once you executed both commands from above on all your data nodes, create new data nodes by following steps 1-21 for each data node.
    23. Once you finish the deployment for all master/data nodes, verify that the upgrade was successful.
      1)    Power on all new IOP machines and wait until they are booted. 
      2)    From your Real-Time Console, open the Insights portal by browsing the IP of the master node.
      Important: If the IP of the new master node is different from the old master node, configure the new IP in the COP configuration. Go to the Control Panel, right-click ControlUp Server, and select Change
      ControlPanelIP.png
      In the configuration window, click Insights On-Premises (IOP) Configuration.
      InsightsConfiguration.png
      Enter the new IP address and, if changed as well, the folder for the Activity and Backup files. 
      InsightsNewConfiguration.png

      3)    Log in to the portal and check if data that existed before the upgrade is shown in the portal.
    24. Install the new IOP Forwarder by running the iop_forwarder-[IOPVersion].msi. Follow the installation instructions from the IOP Forwarder installation guide
      Important: If the IP of the new master node is different from the old master node, enter the new IP of the master node and, if changed, the new folder for the Activity files, in the IOP Forwarder installation wizard. 
      IOP_Forwarder_new_configuration.png
    25. Remove the old IOP server(s) once you confirm that old and new metrics data are shown in Insights. Open the vSphere client, right-click the old IOP virtual machine(s) and select Delete from Disk. 


    DeleteFromDisk.png

    Click YES to confirm the deletion of the old IOP machine and its associated disks.

    ConfirmDeletion1.png

     

     

  • On-Premises Upgrade Guide 8.x to 8.5

    Upgrading a ControlUp On-premises (COP) environment with Insights On-Premises (IOP) brings new features and security patches. The security benefits alone are reason enough to upgrade your existing environment to a newer version. Read the Release Notes of our On-premises versions to learn more about the latest version's features and bug fixes.

    This upgrade guide describes the upgrade process of your COP environment. Read the When to use this Upgrade Guide as some specific versions can only be upgraded by our Support Team. In the use case described, we upgrade from version 8.1 to 8.5. Follow the instructions carefully as it is crucial to perform the upgrade in the right order. Failure to do so may result in a faulty installation and/or loss of data. 

    To perform the upgrade, follow the steps in this order:

    1. Verify that you can use this upgrade guide
    2. Verify that you meet the prerequisites
    3. Prepare for the Upgrade
    4. Upgrade COP Server
    5. Upgrade Real-Time Console
    6. Upgrade Monitors and Agents
    7. Upgrade IOP Server
    8. Install Solve for On-Premises

    When to use this Upgrade Guide

    The IOP and COP server versions that are installed in your environment determine if you can use this upgrade manual or not. 

    IOP Version

    IOP versions are provided with an update suffix in the file name. For example: iop12c-8.1.733.57.60-u3.ova represents update 3 of IOP version 8.1. Use this upgrade guide if you are updating from:

    • 8.1 Update 3 to 8.5
    • 8.1 Update 4 to 8.5
    • 8.2 Update 1 to 8.5
    • 8.2 Update 2 to 8.5

    Note: For upgrading from OVA 8.1 update 2 or below, write an email to our support team at support@controlup.com and do not use this upgrade guide.

    Check Installed IOP Version

    To check the IOP version that is running in your environment, open your vSphere Client and check the version that appears in the Notes section of your IOP machine(s). A version without an update number means an old IOP version is running and the upgrade must be performed by our support team.
    50_CheckIOPVersion.jpg

    COP Version

    This manual is relevant only if you use ControlUp Server 8.1.5.20 or higher. If you use a lower version, contact our support team at support@controlup.com. In this case, do not use this upgrade guide. 

    Check Installed COP Server Version

    To check the currently installed version, open the Control Panel and check the ControlUp Server version.

    CheckCOPServer.png

    Prerequisites

    Before you can start the upgrade, make sure that you meet the following requirements:

    General Prerequisites

    • An environment with an installed ControlUp On-Premises version 8.1.5.20 or higher. 
    • Installation files for the new version you want to install. If you don’t have those, contact our support team at support@controlup.com.
    • A valid commercial license for ControlUp On-Premises (not trial).
    • A user with administrative privileges to run the installation files.
    • A snapshot of your dedicated ControlUp virtual machine(s). This must be available before the upgrade.

    Prerequisites for the IOP upgrade

    • Access from your local computer to your vSphere (Web) Client. Make sure to open the necessary network ports for the vSphere Client. For more information, see TCP and UDP Ports for the vSphere Client.
    • A vCenter user with the Administrator role. 
    • The OVA file for updating the IOP appliance that is provided by our support team. 

    Prepare for the Upgrade

    Before you start with the upgrade, perform the following steps: 

    1. Log into your Real-Time Console and go to Settings > Monitors > Monitor Settings. Back up the configuration of your monitors by taking screenshots of the details from each of the dialogs opened with all the tabs on the left side menu.
      2_BackUpMonitorSettings.jpg


    2. Stop all monitors and consoles that are currently running in your environment. Go to Settings > Monitors and stop the monitors by clicking the Stop button 7_StopButton.jpgfor each monitor.
      StopAllMonitors.png

      Wait until the monitors are stopped. Once a monitor is stopped, a green Play button 6_PlayButton.jpgappears and the Status column changes to Stopped.
      StartMonitors.png
    3. Back up the ControlUp configuration files. Locate the %appdata% containing the ControlUp folder,  and copy the ControlUp folder to a secure location.
      3_BackUpConfiguration.jpg

    4. Go to C:\Program Files\Smart-X\ControlUp Server. Save the Server Settings folder to a secure location. This saves time after the upgrade so you don’t have to manually enter the organization’s details again.

      8_ServerSettings.jpg
    5. Optional and recommended: Back up the SQL database. For details, see here.
    6. Optional and recommended: Back up script-based actions if you created and are running any of your own scripts. For more information see here.
    7. Stop the IOP Forwarder service on all your ControlUp Monitor machines. You can use the following PowerShell command (run as administrator):
      stop-service SplunkForwarder

    Upgrade the COP Server

    The upgrade instructions for the COP server vary, depending on how the ControlUp database was deployed in your initial COP Server installation. Follow the instructions according to your deployment.
    If you use a ControlUp database on a dedicated SQL server, then you're using production mode.
    If you use an SQL Express installation on your COP server, then you use the light mode.

    Follow the upgrade instructions according to the mode you use in your environment. Before you start the upgrade, make sure to perform these two steps:

    1. Copy the ControlUp directory that you backed up in Step 3 of the Prepare for the Upgrade section into the %appdata% directory. 
    2. Create the C:\Program Files\Smart-X\ControlUp Server\ path (this path was deleted during the uninstallation). Copy the ServerSettings folder that you backed up in Step 4 of the Prepare for the Upgrade section into it.

    Upgrade Instructions for Production Mode:

    1. Run the installation file for the new ControlUp Server version as an administrator. In the new window, click Upgrade and wait until the installation is complete. 
      UpgradeButton.png
    2. The Upgraded Successfully message indicates that the upgrade was performed successfully.
      UpgradeSuccessful.png

      Important: If the upgrade failed, contact our support team at support@controlup.com

    3. In the Control Panel, check that the new version was installed. 
      ControlPanelCheck.png

    Upgrade Instructions for Light Mode:

    1. Uninstall your currently installed ControlUp Server version. Open the Control Panel and run the Programs and Features applet. Right-click ControlUp Server and select Uninstall. Follow the prompts to uninstall.

      15_Uninstall.jpg
    2. Confirm the uninstallation by clicking Yes.
      ConfirmUninstallation.png
    3. Run the new installation file of the ControlUpServer[COPversion].exe as an administrator and follow the installation instructions from the ControlUp On-Premises Server installation guide.
    4. During the installation, you have the option to import script-based actions. Browse the SQL backup file that you created from your previous COP installation and click Continue to start the import of your SBA backup.
      SBAImport.png
    5. Once the installation is finished, check in the Control Panel that the new version was successfully installed.
      CheckServer.png

    Upgrade Real-Time Console

    1. Run the new installation file OnPremisesConsole[bitversion]-[COPversion].exe as an administrator and follow the installation instructions.
    2. Once completed, open the Real-Time Console, enter your COP server name and confirm by clicking Continue.
      29_ConsoleFirstStep.jpg
    3. In the Real-Time Console, click Help > About and confirm the new version.
      VersionHelp.png

    Upgrade Monitors and Agents

    The next step is to upgrade your ControlUp Monitors and Agents. As the ControlUp Monitors and Agents are still running with the old version, you need to upgrade them as well. 

    Upgrade Your Monitors

    1. From the ControlUp Management Console screen click the Settings ribbon and then Monitors. The Manage ControlUp Monitors screen appears.
      Monitors.png
    2. From the Monitors tab, you can see a version mismatch of the ControlUp Monitors. All monitors with outdated versions must be updated.
      MismatchRichtig.png

    3. Right-Click the monitor and select Upgrade. Repeat this step for all monitors so that no monitor appears with a version mismatch. 
      MismatchRichtig2.png
    4. Once the upgrade is finished, check that the monitor started successfully and the Version column shows the updated version.
      Missmatch3.png

     

    Upgrade Your Agents

    For agents with old versions that were installed from the Real-Time Console:

    To update the ControlUp Agent on a selected machine:

    In the Real-Time Console, right-click the machine on which you want to upgrade the Agent, select Agent Control > Upgrade/Install Remote Agent. Confirm the popup message by clicking OK and wait until the agent is updated. 
    UpgradeAgent.gif

    To update the ControlUp Agent on all added machines:

    In the Real-Time Console, right-click the organization name, select Agent Control > Upgrade/Install Remote Agent. Confirm the popup message by clicking OK and wait until the agents are updated. 
    UpgradeAgentAllMachines.gif

    Note: The agents which were deployed with the old ControlUp version on the master image via an MSI file must be upgraded with the corresponding ControlUp Agent version that you upgraded to. You need to run the MSI file manually on each managed machine. The MSI files are available in our Download Center.

    Upgrade IOP Server

    After upgrading the COP Server, Real-Time Console, ControlUp Monitors, and ControlUp Agents, it's time to do upgrade your IOP server(s). Open the Insights On-Premises Upgrade Guide 8.x to 8.5 and follow the instructions for the IOP upgrade carefully. 

    Install Solve for On-Premises

    The Solve web app is available for ControlUp on-premises environments starting with version 8.5.

    To learn about Solve, read Welcome to Solve.
    For installation instructions, see Solve On-Premises Installation - Version 8.5.

    How-To: Back up the ControlUp Database

    To create a database backup:

    1. Open an SQL management tool of your choice. 
    2. Connect to the server instance where the ControlUp database is located.
      In the Light version, the database is stored on the COP server.
      In the Production version, the database is stored on a dedicated server. 
    3. Right-click the ControlUpDB and select Backup.
      10_SQLBackup.jpg
    4. Choose a backup name and path where the backup file should be stored.
      11_SQLBackup.jpg

    5. Select the options Overwrite all existing backup sets and Verify backup when finished.
      12_SQLBackup.jpg

    6. Start the backup by clicking Backup and wait until the backup is finished.
      13_SQLBackupFinished.jpg

    7. Check that the backup file was successfully created.
      14_SQLBackupCheckFile.jpg

     

    How-To: Back up Script-Based Actions

    This optional step is recommended if you created and run you own scripts in your ControlUp environment. The COP installation includes the option of installing all the script-based actions available in the ControlUp community. 

    To back up script-based actions:

    1. Open an SQL management tool of your choice. 
    2. Right-click the ControlUpDB and select Tasks > Generate Scripts.
      16_GenerateScripts.jpg

    3. In the Introduction wizard, click Next >
    4. Click Select specific database objects. Expand the Tables tree and select the following tables. 
      - CloudStore
      - SBA_EULA
      - SBAExecutionRecord
      - SBARecord
      17_GenerateTables.jpg
    5. Click Next >. In the Set Scripting Options dialog, click Advanced.
      18_AdvancedButton.jpg
    6. In the Advanced Scripting Options dialog, scroll down the list of options and change the Types of data to script from Schema Only to Data only, and click OK.
      19_TypesToScript_DataOnly.jpg

    7. In the Set Scripting Options screen, select Save as script file and browse to the folder where you want to store the export SQL file by clicking Click Next > to see the summary windows.
      20_SetScriptingFile.jpg
    8. In the summary window, review the settings you select. Click Next >. 
    9. The script is generated when all steps are successfully executed. Click Finish to end the export of SBAs.
      21_SaveScripts.jpg

    10. Use a text editor to open the SQL file that you just exported. Replace the first two lines of the script with the following lines and save the script. In the first line, type the name of your ControlUp database, which in Light installations is always ControlUpDB.

      USE [CONTROLUPDATABASENAME]

      GO

      TRUNCATE table [dbo].[SBARecord]

      GO

      TRUNCATE table [dbo].[CloudStore]

      GO

      TRUNCATE table [dbo].[SBA_EULA]

      GO

      TRUNCATE table [dbo].[SBAExecutionRecord]


      22_Replace.jpg

  • How to Update SBA and AA-VE in an On-premise Environment

    These instructions show you how to update script-based actions (SBA) and automated actions (AA) / virtual export (VE) in an existing on-premise environment. 

    For basic information on SBA, refer to the Script-Based Actions article 

    During the installation phase, you need to select a SQL and LDIF file for importing script-based and automated actions to the ControlUp database. These files are provided with new CU releases. 

    ImportFiles.png

    As this article describes the update process, it is only relevant for existing ControlUp installations. Refer to the On-Premises Server Installation Guide document, if this is a fresh installation. 

    How to Update Script-Based Actions

    This chapter explains how to upgrade your existing script-based actions.

    Note: These steps can be performed without administrative privileges. 

    To update script-based actions:

    1. Right-click Start and select Programs and Features
    2. Select ControlUp Server and click Modify. The configuration dialog of the ControlUp Server appears. 
    3. Click Update SBAs.

      mceclip1.png
    4. Select the sql file and click Open. This starts the data import to the ControlUp database. 

      mceclip4.png

      Once the update is complete, the following popup is displayed:

      mceclip0.png

    How to Update Automated Actions & Virtual Expert Rules

    Updating automated actions in the database is very similar to updating SBAs. 

    Note: These steps must be performed with administrative privileges. Opening the configuration without administrative rights prevents you from clicking the Update VE & AA button. 

    To update automated actions:

    1. Right-click Start and select Programs and Features
    2. Select ControlUp Server and click Modify. The configuration dialog of the ControlUp Server appears. 

      mceclip1.png

    3. Click Update VE & AA. 

      mceclip0.png

    4. Select the ldif file and click Open.

      mceclip2.png
      Once the update is complete, the following popup is displayed:

      mceclip3.png



     

     

  • Upgrade Guide for Hybrid Cloud 8.x to 8.5

    This article describes the steps required to upgrade your ControlUp Hybrid Cloud infrastructure from version 8.x to 8.5.

    Prerequisites

    Make sure to meet the following requirements:

    1. Download the latest ControlUp version from here.
    2. Back up the ControlUp folder which holds the configuration of your ControlUp environment. 

      To back up the folder:
      1. Press CTRL + X and type %appdata%. Click OK. This opens the Roaming folder for your logged-in user. 
        appdata.png
      2. Select the ControlUp folder and copy it to a secure location. 

        mceclip0.png
    3. Ensure that all data collectors are up to date and compatible with the console/monitor version.
    4. Ensure the compatibility of the data collectors. For more information see here.

    Upgrade Procedure

    Before you start upgrading your Hybrid cloud environment, close all open ControlUp Real-Time Consoles that are running on your machine and launch the file for the new version of the Real-Time Console. If required, log in with your credentials to your existing organization. 

    To upgrade the ControlUp Monitors: 

    1. From the ControlUp Management Console screen click the Settings ribbon and then Monitors and the Manage ControlUp Monitors screen appears.
      mceclip2.png

    2. From the monitor tab, you can see under Details that there is a version mismatch.
      mceclip2.png
    3. Right-click on the monitor and select Upgrade. This starts the upgrade process for the selected monitor. 

    To upgrade the ControlUp Data Collectors: 

    • Locate the machines which are configured as data collectors in the organization tree. Right-click on the machine and select Agent Control and choose Upgrade/Install Remote Agent. This starts the deployment of the CU Agent on the selected machine. 
      mceclip0.png

    To upgrade the ControlUp Agents: 

    • We recommend having the agents upgraded as well to meet the same version as the other components and to have the latest fixes, features, and enhancements. 
    • You can perform the upgrade to all agents from the console as follows:
        • Right-click the organization name and select to upgrade all agents.
          UpgradeAgentAllMachines.gif
    • If you use Citrix PVS, MCS, or VMware Linked Clones images in your organization, you can download the ControlUp Agent MSI from this link and deploy it on the image itself.
    • ControlUp supports backward compatibility for the agents so it's not mandatory to upgrade the agents right away. 

    Data Collector Compatibility

    As mentioned above, it is crucial to ensure the compatibility of the data collectors. It's best practice to have dedicated machines as data collectors, however, by default, the console and monitor fill this role. To find out which settings hold the data collector role, follow the steps below. 

      1. From the directory tree, right-click your hypervisors connection, XenDesktop site, or NetScaler appliance and click Connection Settings and the Edit Connection tab appears.
      2. Open the dropdown of the data collectors by pressing the arrow.
        DataCollector_Hypervisor.png
        If a machine is shown up after you click the arrow, then this machine acts as a data collector. The agent on that machine must be updated.

        If no machine is shown after you click the arrow, then you don't use a data collector in your ControlUp environment. 
        DataCollectorExists.png
      3. Search for the data collectors in the directory tree.
        DataCollectorSearch.png
        If a data collector is not up to date, the machine appears with an mceclip5.png icon.
      4. To update the data collector, right-click the data collector and select Agent Control > Upgrade Remote Agent.

    If you require any assistance with the upgrade procedure or have a question, contact us at support@controlup.com

     

     

  • Upgrade Guide for Hybrid Cloud 7.x to 8.x

    This guide describes the actions required to upgrade your ControlUp Hybrid Cloud infrastructure from 7.x to 8.x. 

    The official release notes for v8 are available here.

    Version 8.x provides large-scale support and multi-monitor configuration across multiple sites. The infrastructure of the ControlUp Monitor component was redesigned to support workload sharing in large-scale environments. Follow the procedures described in this guide to reinstall the ControlUp Monitor.

    Prerequisites

    • Back up the ControlUp configuration folder before upgrading to the new version (%AppData%\ControlUp).
    • Ensure that there are no SSL errors while establishing the connection to ControlUp Cloud. The Root CA must be properly configured in the machine running the Console/Monitor.

    Pre-Upgrade Actions:

    Prior to upgrading, ensure that all data previously configured in the ControlUp v7.x Monitor is backed up so that it can be stored securely and be used later if needed.

    Back up your current console (v7.x) as follows:

    1. In the real-time console (v7.x), select the Settings tab,
    2. Click  Monitors.
      mceclip1.png
    3. The monitor window appears. Within the menu bar, click Settings.
      mceclip0.png

      Record all the details you have previously configured in the v7.x monitor. These credentials and settings must be re-entered in the new monitors' installation as described later in this article. 
      mceclip0.png

    Upgrade Procedure:

      1. Close any running ControlUp v7.x console instances and launch the new v8.x console.
      2. Enter your login credentials.
      3. Log on to your existing organization.
      4. A message window of the ControlUp Upgrade is displayed: 
        mceclip0.png
      5. Carefully read the instructions and click Continue.
        2019-10-23_15-58-57.png
        The console opens and displays the configuration. (machines, folders, etc.) 
      6. Ensure compatibility of data collectors.
        For the upgrade procedure to succeed, make sure that all data collectors are up to date and compatible with the console/monitor version. A ControlUp Agent can be configured as a data collector to view what is configured on your end, and if required, upgrade them for the new v8.x.
        1. To ensure data collector compatibility:
          1. Right-click your hypervisors/XenDesktop sites/NetScaler appliance and select Connection Settings
          2. In the Data Collectors tab, the default ControlUp Console / Monitor mode should appear.
          3. If a machine listed by a name such as 'MONITOR7416' appears (see image below) Preform an upgrade of the ControlUp agent on that machine.
            2019-10-23_15-50-46.png
          4. Locate the machine configured as a data collector in the folder structure.
            If the mceclip4.png icon appears, the installed agent is not up to date. Upgrade the installed agent per step 6.1.5.
          5. Right-click the machine and select Agent Control > Upgrade Remote Agent. 
            mceclip3.png 
      1. Upgrade v7.x monitors to v8.x. 
        If you are performing a new installation of the monitor, refer to the next section.
        To Upgrade the old monitors:
        1. Click Settings > Monitors. 
          mceclip5.png
        2. In the monitor window, highlight the monitor, right-click, and select Upgrade. mceclip1.png
        3. If you had more than one monitor in v7, in v8.x, when upgrading the 2nd monitor, you are prompted as follows:
          mceclip2.png
          • The first option takes the same configuration as the 1st monitor you upgraded to v8.x. (This is the preferable option.)
          • The second option takes the sole configuration of the monitor you're currently upgrading. 
      2. Set up a new v8.x monitor.
        1. Configure the monitors' prerequisites.
          To configure monitors for the new version:
          1. In the monitor window, click Add Monitors to Site.
            mceclip0.png
            If you do not have domain identity configured, you'll see the setting page to set it previous to adding the monitor. 

          2. Add the monitor's domain identity (mandatory) together with the data source's credentials.
            If these settings were not set in the past, you'll be prompted to enter these.
            mceclip1.png
            Configure an outbound proxy in the Proxy Settings section (mandatory if the monitor relies on a proxy).
            For further information on monitor's requirements and required permissions, see ControlUp Monitor Permissions & Security - Cloud ONLY.

            Note: When using SSL termination on the proxy, ensure that the proxy certificate is trusted by the machine running the Console/Monitor component. 

          3. When the configuration is done, click OK, and start installing the monitor component.
        2. Install a new v8.x monitor component
          1. Click Add Monitors to Site
            mceclip0.png
          2. The ControlUp Monitor Installation window displays:
            2019-10-23_16-07-07.png
          3. Select the servers on which you want to install the monitor component, and click Install.
            Note: if the naming convention is not consistent, the monitor component must be installed individually.
          4. Look at the Installation Progress column. Once the installation completes, click Finish.
            2019-10-23_16-08-31.png
          5. The monitors' icon should be green and will start connecting to the data sources shortly.
            2019-10-23_16-19-27.png

    The upgrade to version 8 is completed.
    The ControlUp agents in your environment can be upgraded as well so they can be compatible with the rest of the ControlUp components.

    If you require any assistance with the upgrade procedure or have a question, feel free to contact us at support@controlup.com.