Avalanche powered by Wavelink

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

Avalanche Upgrade Process

If you already have Avalanche servers installed, then you will want to perform an upgrade to preserve existing data. During an upgrade, the installer for Avalanche 6.2 migrates the profiles, users, and navigation tree; removes any Avalanche services that are installed locally; and installs the new version. Some data in the Enterprise Server database may be restructured.

For a video tutorial of upgrading Avalanche, see this video on YouTube:

Upgrade Process Video

What gets migrated/upgraded:

•profiles

•users

•the navigation tree

•Certificate Manager

What doesn't get migrated:

•reports (scheduled or completed)

•software packages

•scheduled deployments

•mobile device details

•LDAP user accounts

Completed reports (in PDF, XML, or CSV format) are not migrated, but they are not deleted and can still be accessed through the file system. When you install Avalanche 6.2 at a different location than your original server, software packages are not copied to the new environment and must be moved manually.

Supported Versions for Migrating to Avalanche 6.2

•Avalanche SE 5.3.0.572

•Avalanche MC 5.3.0.543

•Avalanche MC External DB 5.3.0.543

•Avalanche MC 5.3.1.50

•Avalanche MC External DB 5.3.1.50

•Avalanche 6.0

•Avalanche 6.1

If you have an earlier version than those listed above, you must first upgrade to Avalanche 5.3.1 before upgrading to 6.2.

When upgrading from Avalanche 5.3 to 6.2, we suggest you use a cloned environment. If you upgrade from Avalanche 6.0 or newer, you may choose to upgrade in place.

For information about the upgrade process, see the following pages:

•Upgrading to a Cloned Environment (Recommended)

•Upgrading Avalanche in Place

•Upgrading Mobile Device Servers