Quickly Update the Aternity Management Server for Aternity v9.0 / 9.0.1

Update your Aternity on-premise to version 9.x from v7.1.x or 8.x for a significant step forward in new features and a new look.

During your update of each Aternity server, you can choose between the express update, or a custom update.

Important:

Always check the sizing before ANY update. Even minor Aternity upgrades like from 9.0 to 9.0.x have updated sizing, hence you may need to change your topology and hardware even with the same number of devices.

  • If you keep the same topology or security, choose the express update, which keeps your legacy settings in the updated servers.

  • If you are changing your topology or security, choose the custom update.

For example, if the updated requirements for your sizing state you must have a new standalone Aggregation Server, you must use the custom update to remove the legacy embedded Aggregation Server from within the Management Server, then run the setup again on a standalone server to freshly install a new Aggregation Server there.

Use the updated sizing to determine whether a component is embedded or standalone
  • (Trial demo deployments less than 100 devices) The Management Server PC can also have the Database Server, Analytics Server, Data Warehouse Server, and Aggregation Server, all on the same PC.

  • (Small deployments less than 3,000 devices) The Database Server is standalone. The Management Server PC has ALL the following: the Analytics Server, Data Warehouse Server, and Aggregation Server.

  • (Mid-sized deployments less than 25,000 devices) The standalone servers are: Database Server and Aggregation Server. The Management Server PC has ALL the following: Analytics Server and Data Warehouse Server.

  • (Larger deployments above 25,000 devices) The standalone servers are: Database Server, Data Warehouse Server and Aggregation Server. The Management Server PC should only have the Analytics Server.

Tip:

If your sizing requires you to update or create a standalone server, run the setup on each standalone computer.

Uninstall an embedded component during upgrade, then run setup to install it on a standalone server

Before you begin

Before updating the Management Server:

  • If you are running a version that predates v7.1.x, update to v7.1.x before updating to v9.x.

  • Check the correct sizing for your deployment before updating any of your Aternity servers.

  • If your legacy Agents communicate over TCP, you must first test then switch from TCP to HTTP(S).

  • Update the Aternity Database Server by verifying and then updating the Oracle database..

  • Update the Dashboard Server by uninstalling the previous version of Tableau and then running the setup to install the new version.

  • On the Dashboard Server, update the Dashboard Gateway component.

Procedure

  1. Step 1 Access the Aternity Management Server computer.
  2. Step 2 Log in to the computer as a local administrator.

    To verify you are a local administrator on this computer, not a domain administrator, open the System control panel, select Advanced system settings > Computer Name, and confirm the Change button is active.

  3. Step 3 Download the latest version of Aternity on-premise from our website.

    The setup package is for all Aternity servers.

    Download Aternity on-premise from the website
  4. Step 4 Stop the AternityPlatform service.
  5. Step 5 Right-click the setup and select Run as administrator to begin.
  6. Step 6 (Optional, recommended) Backup your existing server settings, as they may be useful for support and troubleshooting purposes.

    The size of the backup is roughly equal to the size of the installation, but does not include raw data files and archived reports.

    Backup to a subfolder under updates, like D:\data\Aternity\updates\backup_20160323-182419. We recommend that you use the default folder. Do NOT save the backup in the parent Aternity folder, D:\data\Aternity\.

    Backup the existing settings of the server
  7. Step 7 Select Express (Use Existing Settings).
    Important:

    Always check the sizing before ANY update. Even minor Aternity upgrades like from 9.0 to 9.0.x have updated sizing, hence you may need to change your topology and hardware even with the same number of devices.

    • If you keep the same topology or security, choose the express update, which keeps your legacy settings in the updated servers.

    • If you are changing your topology or security, choose the custom update.

    Select the express installation
  8. Step 8 If any Aternity Agents on existing monitored devices report to Aternity with TCP, you must first update them to HTTP(S).

    Cancel the setup and test your new configuration of Agents in HTTP or HTTPS.

    Only proceed after all devices report to Aternity with HTTP(S)
  9. Step 9 Review the settings from the existing server, and select Install to start the update.

    If it reports that the existing installation is corrupted, cancel the update and contact Customer Services.

  10. Step 10 (Optional) If you previously defined custom attributes and mapped them to a system attribute, you can change the mapping if required.
    Tip:

    Typically, you would not change these settings.

    For example if you had an attribute called MyCompanyPlace which you previously mapped to office, you can change the mapping to location by choosing MyCompanyPlace for the Location field.

    Change your legacy custom attribute mappings to Aternity 's attributes
    Field Description
    Frontline / Originating

    Displays whether the system obtains this attribute from the frontline client (like the remote desktop), or from the originating virtual server which hosts the virtual session.

  11. Step 11 Select Start AternityPlatform service and select Finish.
    Start the service of the Management Server

    The AternityPlatform service is the Management Server. You can verify it is running in the Windows Task Manager.

    Tip:

    If the setup completes but the AternityPlatform service did not start, verify you have local administrator privileges on the computer.