Avalanche powered by Wavelink

> Getting Started > Installing Avalanche > Avalanche Upgrade Process > Upgrading from Avalanche 5.3

This page refers to an older version of the product.
View the current version of the User Guide.

Upgrading from Avalanche 5.3

After upgrading your databases, you can upgrade your enterprise and device servers. All services are upgraded with the same installer.

As part of the upgrade process, any previous versions of Avalanche installed locally will be uninstalled. Do not exit the uninstall dialog because this will corrupt the Avalanche upgrade.

Prior to beginning the upgrade process, Wavelink recommends the following actions:

Perform an enterprise-wide deployment from My Enterprise.

If you already have Wavelink Remote Control installed, either locally or on a different machine, you must remove the existing server and install Remote Control 4.1 using the Avalanche 6.1 installer. The installer will not remove the older version and installs Remote Control 4.1 within the Avalanche directory. Remote Control 4.1 is required for use with Avalanche 6.1 or newer.

If your current databases are not local to where you will install Avalanche 6.1, ensure the database server is set up for remote access. To configure this, see Allowing Remote Access to the Database.

If you are using Microsoft SQL Server currently and want the 6.1 databases to be on the same system, back up and restore the databases with different names in your existing installation of Microsoft SQL Server. During the Avalanche upgrade process, provide the server credentials to connect to and upgrade the new databases.

For more information on prerequisites for upgrading and a list of what is retained during upgrade, see Avalanche Upgrade Process.

To upgrade your enterprise server:

1.From the designated server, double-click the file you received to upgrade your enterprise server.

The Setup Wizard Welcome screen appears.

2.Select a language and click OK.

3.Review the Pre-Install checklist and then click Next to continue.

4.Browse to the install directory for your current version of Avalanche and click Next.

5.The Select Components screen appears. Select which components you want included on the installation and click Next. If you currently use Remote Control with your mobile devices, you must manually uninstall your existing Remote Control Server and install the Remote Control Server component bundled with Avalanche to retain this functionality. To manage certificates on your mobile devices through Avalanche, you must select the Certificate Management Server component.

6.Enter the SQL Server credentials and click Next. The Main DB Name defaults to Avalanche and the Stats DB Name to AvaStats. If you use a named instance instead of the default MSSQLSERVER instance, select the checkbox for Use Named Instance and enter the name of your custom instance. If you backed up and restored your original databases under different names, provide the login credentials and names for the new databases. If you are upgrading from PostgreSQL to Microsoft SQL Server, it will first ask for PostgreSQL credentials and then the next screen will ask for credentials for migrating to Microsoft SQL Server. The password for PostgreSQL was set during your initial install of Avalanche 5.3. When connecting to PostgreSQL from a clone, type localhost as the Hostname.

An alert appears to indicate an upgradable database version is detected. Click OK, as this upgrade will take place during the installation.

7.By default, Wavelink creates shortcuts in the Windows Start menu. Click Next to accept the shortcut, or modify it as desired and then click Next.

8.The New Installation Review Configuration screen appears, which indicates all of the activities that take place as part of the upgrade. Click Next to begin the upgrade process.

9.Click Finish to complete the upgrade.

Upon completing the upgrade process, you need to enter your Avalanche licenses using the Web Console. To activate your Avalanche 6.1 licenses, see Activating Licenses.

If a mobile device server is upgraded locally, it will appear in the Unassigned Server Locations region and must be reassigned to a folder. To assign a location, see Using the Navigation Tree.


This page refers to an older version of the product.
View the current version of the User Guide.

The topic was:

Inaccurate

Incomplete

Not what I expected

Other