Running the Avalanche Installer

The Avalanche installer is designed to include all components of the service, including the Web Console, device servers, Certificate Manager, and Remote Control server. This installer allows you to create all services on the same computer through one installation process. If you want to install the device servers on separate computers, see Installing Device Servers.

Avalanche installs its own JRE and changes the JRE_HOME system variable. If you have a JRE already installed, it is not affected by Avalanche. However, any program using the JRE_HOME variable will be redirected to use the Avalanche JRE.

Do not install Avalanche on any machines currently running LANDESK Management Suite or Mobility Manager. This will prevent integration between applications.

To install Avalanche

1.Double-click the Avalanche installer.

2.Select a language and click OK.

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

4.Read the license agreement, click I accept the agreement, and click Next.

5.Browse to your preferred installation destination directory and click Next.

6.Select which components you want included on the installation and click Next.

7.Enter your SQL Server credentials and click Next.
The Hostname is the FQDN of the machine running SQL Server. The username and password were set during the Microsoft SQL Server installation process. The port used by Avalanche is 1433. 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 check box for Use Named Instance and enter the name of your custom instance.

8.Click Yes to create the Enterprise Server and Statistics Server databases. If you are upgrading Avalanche, the installer may upgrade your databases instead of creating new ones.

9.Click Next to accept the default shortcut location, or modify it as desired.

10.Select whether you will use an HTTP or an HTTPS connection between the Avalanche console and the Avalanche servers. If you select HTTPS, you will also need to upload a certificate. An HTTPS connection can be configured after installation if desired. For more information, see Accessing the Web Console Over an HTTPS Connection.

11.Click Next to accept the configuration information for the Central Web File Server.

12.Review the options for using API keys for remote servers. If you have existing remote device servers, you can enable the Allow legacy access option to allow those servers to continue to connect until they have been reinstalled with API keys. For information on creating API keys for device servers, see Using API keys for device servers.

13.Review your selected configuration information, and click Next to begin the installation.

14.Read the information about he encryption key, click Acknowledge, and click Next.

15.Click Finish to complete the installation.