Deploy App Volumes Manager Using App Volumes Installer

Install App Volumes Manager using the setup.msi installer.

Prerequisites

• Optional: To obfuscate PII data in App Volumes Manager logs, set the system environment variable, EnablePIILogging, to 0.

  If this setting is already present in the database, then the value of this setting overrides the value of the system environment variable.

  PII data can also be obfuscated after configuring App Volumes Manager using the PII Logging toggle. For more information about this toggle, see the App Volumes Manager Configuration Settings Page section in the Omnissa App Volumes Administration Guide at Omnissa Product Documentation.

• Download the Omnissa App Volumes installer.

  1. Go to the Customer Connect page.
  2. Click Downloads.
  3. In the Products A-Z listing, search for App Volumes and click Download Product.
  4. In the Download App Volumes page, navigate to the desired edition, and click GO TO DOWNLOADS.
  5. In the Download Product page, download the files.

• Ensure that you have the SQL server authentication details with you.

• Verify that your environment meets the system requirements.

  See System Requirements.

• Verify that your account has local administrator privileges on the target server.

Procedure

1. Run the setup.msi installer file in an elevated command prompt.

2. Read and accept the End-User License Agreement and click Next.

3. Select Install App Volumes Manager and click Next.

4. Select a database option:

   Option	Description
   Install local SQL Server Express Database	The database is installed automatically.
   Connect to an existing SQL Server Database	Use the SQL Server database of your choice. Note: It is recommended that you use this option for production environment.

5. Select the database connection method.

   Option	Description
   Windows Integrated Authentication (automatically use this server's SYSTEM account)	With this option, your SYSTEM account (account with which you access App Volumes Manager server) credentials are automatically used for authentication. For a remote SQL server database, ensure that you provide owner permissions to this account in the new database to App Volumes Manager server.
   SQL authentication	Add an SQL server user account for this database that has permission to create tables, views, and permission to read from and write to these objects. Any SQL server user account with create, read, and write database permissions can be used. It is recommended to use SQL authentication for remote SQL server database.

   A new ODBC connection named svmanager is created.

6. Enter the name of the database.

   Important: Non-ASCII characters are not supported in the database name.

7. Choose a new database or continue to use the existing one.

   Option	Action
   Choose a new database.	Select the Overwrite existing database (if any) check box. Note: When you upgrade App Volumes or install an additional instance of App Volumes Manager, this check box must not be selected.
   Use the existing database.	In the Name of database catalog to use or create: field, enter the name of the database. Alternately, you can also use the Browse button to search and select the desired database. Note: If the Windows Integrated Authentication database connection method is selected, ensure that the user account has access to the desired database. Clear the Overwrite existing database (if any) check box. Important: If old App Volumes Manager instances that pointed to the existing database are no longer online, then ensure that the records of all those instances are removed from the database.

8. If you do not have the relevant certificate to validate the SSL connection to SQL server, deselect the Enable SQL Server certificate validation check box and click Next.

   By default, Enable SQL Server certificate validation check box is selected.

9. Select the ports on which App Volumes Manager can listen for incoming connections.

   By default, communication occurs over SSL and the default value of the port is 443. Specify the port value as 80 (or equivalent) for App Volumes Manager to listen on a HTTP port.

10. (Optional) Check the Allow Connections over HTTP (insecure) box.

    If you have specified the App Volumes Manager to listen on an HTTP port in Step 7, you must select this box. Selecting this box deactivates SSL and all communication with App Volumes Manager becomes insecure .

    CAUTION: Do not enable HTTP in a production environment.

11. Click Next and enter the path where App Volumes Manager must be installed.

12. In the Ready to Install the Program, you can select the deployment platform which indicates where you intend to deploy App Volumes.

    Note: This parameter is used for information gathering only.

13. To begin the installation, click Install.

    Follow the prompt and complete the installation.

    Note: If you have chosen local SQL Server Express database, then you must restart your system at the end of the installation as instructed in the setup prompt.

What to do next

Log in to App Volumes Manager and configure the directory service, vCenter Server, machine managers, and storage. Configure the connection to the SQL database and SSL for App Volumes Manager. You can also configure various Admin Roles and recovery administrator credentials. For more information about Configuring App Volumes Manager, see the App Volumes Administration Guide at Omnissa Product Documentation.