Omnissa App Volumes Install Guide

The Omnissa App Volumes Installation Guideprovides information on how to install, deploy, and upgrade Omnissa App Volumes®.

Omnissa App Volumes Install Guide December 16, 2024 Release Version: Omnissa App Volumes - 2410

Contents About This Book . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3 Introduction to App Volumes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4 System Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7 Installing App Volumes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12 Using App Volumes on a Persistent Virtual Desktop . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12 User Accounts and Credentials . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15 Install App Volumes Manager . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16 Deploy App Volumes Manager Using App Volumes Installer . . . . . . . . . . . . . . . . . . . 16 Deploy App Volumes Manager Silently . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21 Deploy App Volumes Manager through Azure Marketplace . . . . . . . . . . . . . . . . . . . 22 Workflow for deploying App Volumes Manager using Azure Marketplace . . 24 Prerequisites for Deploying App Volumes Manager through Azure Marketplace . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34 Resources Used in App Volumes Deployment on Azure . . . . . . . 36 Install App Volumes Agent . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37 Install App Volumes Agent Silently . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38 Install App Volumes Application Capture Command-Line Program . . . . . . . . . . . . . . . . . . . . . 41 Verify License . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42 Scaling App Volumes Manager . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42 Supported App Volumes Scenarios . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44 Upgrading App Volumes Components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45 Upgrade App Volumes Manager . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45 Perform Rolling Upgrades . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46 Considerations for Performing Rolling Upgrades . . . . . . . . . . . . . . . . . . . . 47 Managing Packages and AppStacks in App Volumes Manager . . . . . . . . . . . . . . . . 48 Configuring visibility and management of App Volumes Manager 2.x UI . . . . . . . . . . 49 Upgrade App Volumes Agent . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49 Upgrade App Volumes Agent Silently . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50 ©2024 Omnissa. All Rights Reserved 2

About This Book About This Book The Omnissa App Volumes Installation Guide provides information on how to install, deploy, and upgrade Omnissa App Volumes®. Intended Audience This information is intended for experienced IT system administrators who are familiar with virtual machine technology and datacenter operations. ©2024 Omnissa. All Rights Reserved 3

Introduction to App Volumes Introduction to App Volumes Omnissa App Volumes provides a system to deliver applications to desktops through virtual disks. Applications are delivered by attaching a standard VMDK or VHD file to a virtual machine. You can centrally manage the applications with App Volumes Manager and there is no need to modify the desktops or individual applications. Applications delivered using App Volumes based on assignments look and feel natively installed to the end user. All Application Programs are packaged as fully installed and delivered in real-time to the user’s session. App Volumes can be used in a non-persistent virtual desktop or persistent virtual desktop environment. When installing App Volumes agent, you can choose one of the options as per your requirement. For information about using App Volumes in a persistent virtual desktop environment, see Using App Volumes on a Persistent Virtual Desktop. The Omnissa App Volumes Installation Guide provides information on how to install, deploy, and upgrade Omnissa App Volumes®. This information is intended for experienced IT system administrators who are familiar with virtual machine technology and datacenter operations. App Volumes Components A typical App Volumes environment consists of a few key components that interact with each other and an external infrastructure. ©2024 Omnissa. All Rights Reserved 4

Introduction to App Volumes Component Description Web-based interface integrated with directory services (for example: Active Directory) and vSphere. Consists of services that orchestrate application delivery and interface the vSphere environment. You can use App Volumes Manager for the following tasks: App • Manage assignments of volumes to users, groups, and target computers. Volumes • Collect Application Packages and Writable Volumes usage information. Manager • Maintain a history of administrative actions. • Automate assignment of applications and Writable Volumes for agents during desktop startup and user login. See Install App Volumes Manager and the Configuring App Volumes Manager section in the administration guide. App A Microsoft SQL Server database that contains configuration information for Application Packages, Writable Volumes, and users. See Volumes System Requirements. database App Software installed on VDI or server farm base image on which application packages and Writable Volumes are delivered. See Install App Volumes Volumes Agent. agent Application An Application represents a collection of packaged versions of that Application. Users, Groups, Computers, or OUs (Organizational Units) can be entitled to receive a current Package or be assigned to a specific Package. Package A Package stores one or more Programs required for an Application to run. A single Package can be delivered to multiple computers and one or many users. Writable Volumes provide storage for application profile settings, documents, and installed applications. The mode of storage is Writable determined by the template that is selected during creation. Volume Note: Users cannot have more than one Writable Volume assigned to them. For more information about using Writable Volumes, see the Omnissa App Volumes Administration Guide at Omnissa Product Documentation. Programs Programs are installed during the packaging process. When an Application is assigned and a Package is delivered to a desktop, the Programs are then visible inside Windows under Programs and Features and available from the Start Menu. Packaging A clean virtual machine that contains the necessary programs for installation into Application Packages. The desktop must have the App Desktop Volumes agent installed and configured to connect to the App Volumes Manager. Target A VDI desktop, physical client computer, Remote Desktop Services (RDS) Host or Citrix XenApp Server where users log in to access their Computer applications delivered from the Package. The target computer must have the App Volumes agent installed and configured to connect to the App Volumes Manager. VMware App Volumes uses vCenter Server to connect to resources within the vSphere environment. See Configuring a Machine Manager section vCenter in the App Volumes administration guide. Server ©2024 Omnissa. All Rights Reserved 5

Introduction to App Volumes Component Description You can use Storage Groups to automatically replicate Application Packages or distribute Writable Volumes across many datastores. They are also used to define a group of datastores that should all contain the same Application Packages. Some of the attributes for the group, such as template location and strategy, only apply when using the group for distributing writable volumes. The distribution strategy setting controls how Writable Volumes are distributed across the group. • Spread. Distribute files evenly across all the storage locations. When a file is created, the storage with the most available space is Storage selected. Group • Round Robin. Distribute files by sequentially using the storage locations. When a file is created, the storage with the oldest used time is selected. You can manage the capabilities of storage groups by selecting required storage and ignoring unwanted or slow-performing storages while mounting volumes. When you mark a storage as Not Attachable, the App Volumes Manager ignores the storage while mounting volumes. For example, you can set up two vCenter Server instances. Each server can have a local storage and shared storage capability. You can mark the slower-performing storage as Not Attachable. This storage is ignored by the App Volumes Manager while mounting volumes and can be used solely for replication of Application Packages. App Standalone, software program that captures an application install into a package in the .vhd and .vmdk file formats. Use this program to Volumes easily automate the process of capturing applications by working with packages outside of App Volumes Manager console. The program Application can also be used to test and validate the captured application before delivering the application package to end users. The command-line Capture capture program must be installed on a virtual machine that has no other App Volumes components. You can run the program on the Command- Windows command line and Windows PowerShell. For the install procedure, see Install App Volumes Application Capture Command-Line Line Program. For information about using the command-line capture program, command-line options, and capture workflows, see the Program Omnissa App Volumes Administration Guide at Omnissa Product Documentation. ©2024 Omnissa. All Rights Reserved 6

System Requirements System Requirements Before you install Omnissa App Volumes, ensure that your system meets certain requirements. Database, Browser, and Infrastructure Requirements ©2024 Omnissa. All Rights Reserved 7

System Requirements Component Details App Volumes Manager supports the following Microsoft SQL databases: • SQL Server 2022 • SQL Server 2019 • SQL Server 2017 • SQL Server 2016 SP2 • SQL Server 2014 SP1 and SP2 • SQL server 2014 Enterprise SP3 64-bit Database • Azure SQL Database • Azure SQL Managed Instance For High Availability, App Volumes supports the following database features: • SQL Server Clustered Instances • SQL Server Mirroring • SQL Server Always On availability groups Use App Volumes Manager on one of the following supported browsers: • Internet Explorer 9 or later Browser • Mozilla Firefox 28 or later • Safari 7 or later • Google Chrome 21 or later • Microsoft Windows Server 2025 Datacenter and Standard • Microsoft Windows Server 2022 Datacenter and Standard • Microsoft Windows Server 2019 Datacenter and Standard App Volumes Manager • Microsoft Windows Server 2016 Datacenter and Standard • 8 vCPU required • 10 GB RAM • 1GB disk space • Microsoft Windows 11, version 24H2 App Volumes Agent (client OS) • Microsoft Windows 11, version 23H2 • Microsoft Windows 11, version 22H2 ©2024 Omnissa. All Rights Reserved 8

System Requirements Component Details • Microsoft Windows 11, version 21H2 • Microsoft Windows 10, version 22H2 Enterprise and Pro • Microsoft Windows 10, version 21H2 Enterprise and Pro • Microsoft Windows 10, version 21H1 Enterprise and Pro • Microsoft Windows 10, version 20H2 Enterprise and Pro • Microsoft Windows 10, version 1809 Enterprise (LTSC Only) • Microsoft Windows 10, version 1607 (LTSB Only) • Microsoft Windows 10, version 2021 (LTSC Only) • Microsoft Windows Server 2025 Datacenter and Standard • Microsoft Windows Server 2022 Datacenter and Standard • Microsoft Windows Server 2019 Datacenter and Standard • Microsoft Windows Server 2016 Datacenter and Standard • 64-bit versions of Microsoft Windows only • 1 GB RAM • 1 vCPU • 16 GB disk space System requirements for the command-line capture program is the same as that of the App Volumes Application Capture Command-Line Program App Volumes agent. Note: .NET Framework 3.5 is required for using PowerShell. Hypervisor (if using VMDK) VMware ESXi and vCenter Server 6.5 or later File share (if using VHD) SMB version 3 Directory Microsoft Active Directory domain, 2003 functional level or later. Read-only account access. 256 disks Storage Virtual Adapters and Devices Virtual SCSI Targets Per Virtual Machine (PVSCSI only) Note: This value is supported in ESXi 6.7 and later. If you are using ESXi versions earlier than 6.7, then the number of disks supported is 64. ©2024 Omnissa. All Rights Reserved 9

System Requirements Component Purpose Port number • TCP 80 App (HTTP) Volumes Agent and Manager communications • TCP Manager 443 (HTTPS) Manager and Manager communications App Note: Multiple App Volumes Manager components can communicate with each other in scenarios such as Scaling App Volumes Volumes Manager or in application synchronization. TCP 443 Manager (HTTPS) For more information about application synchronization, see the Configure Multiple App Volumes Instances for Application Synchronization section in the Omnissa App Volumes Administration Guide 4, version 2111 and later at Omnissa Product Documentation. App Volumes Database communication TCP 1433 SQL (SQL) Database App ESXi TCP 443 Volumes (HTTPS) Manager vCenter Server Note: For more information about the App Volumes ports, see the Ports and Protocol information. ©2024 Omnissa. All Rights Reserved 11

Installing App Volumes Installing App Volumes Installing Omnissa App Volumes involves installing the App Volumes Manager, App Volumes agents, and related components. Before installing App Volumes, ensure that you have created and set up the required user accounts and Active Directory credentials. Using App Volumes on a Persistent Virtual Desktop Using Omnissa App Volumes on a persistent virtual desktop allows an end user to install and uninstall applications in the presence of App Volumes application packages. These changes continue to exist even if there are no packages assigned to the user or App Volumes is removed from the virtual desktop. In a persistent virtual desktop environment, end users can install, modify, update and uninstall applications in the base volume but not those which are delivered as application packages. App Volumes can be configured on a persistent virtual desktop by selecting the appropriate machine type option. This option is available when installing the App Volumes agent. Note: By default, App Volumes is set up to work in a non-persistent virtual machine. Machine Type Options Persistent machines Machines that retain user data and installed applications on the operating system disk across sessions. Persistent virtual desktops are often managed by a user endpoint management system or the end user themselves. Non-persistent or multi-session machines Machines that refresh regularly and user data and settings are not persisted on the operating system disk. Non-persistent machines are managed centrally by re-imaging the operating system with updates. In the non-persistent virtual desktop environment, any application installed by the end user is removed after the user logs out of the desktop or when the virtual machine is shut down. In such an environment, to make user- specific data persistent and portable, you can use a Writable Volume. For more information about Writable Volumes, see the Omnissa App Volumes 4 Administration Guide at Omnissa Product Documentation. Considerations When Using App Volumes on a Persistent Virtual Desktop You must be aware of the following best practices and limitations when using App Volumes on a persistent virtual desktop: • Separate base images must be used when installing App Volumes agent for persistent and non- persistent pool deployments. • The virtual machine on which App Volumes agent is installed with persistent desktop enabled cannot be used as a packaging virtual machine. If you intend to use this virtual machine as a packaging computer, create a clean snapshot or take a ©2024 Omnissa. All Rights Reserved 12

Installing App Volumes backup of this machine. Revert to this snapshot or the backup before packaging new application packages. • Writable Volumes must not be used on a persistent virtual desktop. If a user has a Writable Volume assignment, then such a user must not be assigned to a persistent virtual desktop. • You can install the latest Windows Update and keep the Update activated. For information about installing App Volumes agent, see Install App Volumes Agent. For more information about upgrading the App Volumes agent, see Upgrade App Volumes Agent. Install and Upgrade Scenarios for Using App Volumes in a Persistent Pool Deployment in Horizon 8 The following table explains how to install and upgrade App Volumes agent in an existing non-persistent (instant- clone) or persistent (full-clone) pool deployment to enable using App Volumes in a persistent pool deployment. ©2024 Omnissa. All Rights Reserved 13

Installing App Volumes Existing pool Is App Volumes installed? Use App Volumes in a persistent pool deployment deployment To install App Volumes agent on the base (golden) image, follow the Patching an Instant-Clone Desktop Pool procedure. Non- No Persistent For information about this procedure, see the Patching an Instant-Clone Desktop Pool section in the Desktops and Applications in Horizon 8 documentation at Omnissa Product Documentation. To install App Volumes agent in a persistent pool deployment, follow the Customize Machines by Placing Them in Maintenance Mode After Pool No Creation procedure. Note: At step 6 in the procedure, you can use a solution such as SCCM Persistent Important: If a system Writable Volume is present, then you to automate the installation of App Volumes agent on all VMs in the pool. cannot install App Volumes agent in a persistent pool deployment. Location of the system Writable Volume is For information about this procedure, see the Customize Machines by C:\{00000000-0000-0000-0000-000000000000}. Placing Them in Maintenance Mode After Pool Creation section in the Desktops and Applications in Horizon 8 documentation at Omnissa Product Documentation. • You cannot use versions of App Volumes earlier than App Volumes 4, 2406 in a persistent pool deployment. If you have used App Volumes in an earlier version, then upgrading App Volumes agent to App Volumes 4, 2406 or later, versions is not allowed. Persistent Yes To install App Volumes agent, follow the steps that are described in the previous row. • You can upgrade from App Volumes 4, 2406 to App Volumes 4, 2410 and later, even when the App Volumes packages are getting virtualized. ©2024 Omnissa. All Rights Reserved 14

Installing App Volumes User Accounts and Credentials Users and administrators require certain account permissions to install and manage Omnissa App Volumes components. User Accounts You can create user accounts and grant privileges for different roles. User names must contain only ASCII characters: • To integrate App Volumes with vCenter Server, you must create a service account within a vCenter Server with administrator privileges. Optionally, you can create a service account with privileges granted by a custom user role. • If you plan to use a direct connection to the ESXi host or plan to use the Mount to Host option with a vCenter Server connection, you must have administrator privileges on all ESXi hosts. Active Directory Credentials App Volumes Manager connects to Active Directory using the service account. To prepare for installation, you must create an account within the Active Directory domain that meets the following requirements: • Has read access to the Active Directory domain. Administrator privileges are not required. • Has a password that does not expire. Note: If a User in a Group belongs to a domain different from the domain of the Group, then the service account must have the following permissions: • List contents • Read all properties • Read all permissions These permissions must be applied to the User, Group, and the Org Unit where the User and Group are members. If your environment contains domains that are configured for one-way or two-way trust, you can configure separate credentials to access these domains. These credentials are used when connecting to any trust instead of the primary domain credentials. Database Credentials When installing App Volumes Manager, if you select Windows Integrated Authentication as the database connection method and your database server is remotely hosted, then ensure that you can connect to the SQL server from the Windows server (used for App Volumes Manager installation) with Windows Authentication. Administrators Group Access to App Volumes Manager is restricted to the App Volumes administrators group. When you perform the initial configuration, you must provide the name of the directory service (for example: Active Directory) security group that will have access to App Volumes Manager. ©2024 Omnissa. All Rights Reserved 15

Installing App Volumes Local administrator privileges are required for the following actions: • Install App Volumes components on target servers. • Use writable volumes with user-installed applications. • Package Application Packages. Note: The service account user of the directory service is not required to be an administrator. Install App Volumes Manager App Volumes Manager is a web console used for administration and configuration of Omnissa App Volumes and assignment of application packages and Writable Volumes. App Volumes Manager can be installed in multiple ways such as using the App Volumes (setup.msi) installer, Microsoft Windows Installer for silent installation, and through Azure and AWS Marketplaces. For AWS Marketplace deployment, see the App Volumes Deployment for Amazon AppStream 2.0 at Omnissa Product Documentation. Deploy App Volumes Manager Using App Volumes Installer Install App Volumes Manager using the setup.msi installer. Prerequisites • 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. 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: ©2024 Omnissa. All Rights Reserved 16

Installing App Volumes Option Description Install local SQL Server Express The database is installed automatically. Database Use the SQL Server database of your choice. Connect to an existing SQL Server Database Note: It is recommended that you use this option for production environment. 5. Select the database connection method. ©2024 Omnissa. All Rights Reserved 17

Installing App Volumes Option Description Windows Integrated With this option, your SYSTEM account (account with which you access App Volumes Manager server) Authentication (automatically credentials are automatically used for authentication. For a remote SQL server database, ensure that you use this server’s SYSTEM provide owner permissions to this account in the new database to App Volumes Manager server. account) ◦ 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. SQL authentication ◦ 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. ©2024 Omnissa. All Rights Reserved 18

Installing App Volumes 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. ©2024 Omnissa. All Rights Reserved 19

Installing App Volumes Option Action Choose a new Select the Overwrite existing database (if any) check box. database. Note: When you upgrade App Volumes or install an additional instance of App Volumes Manager, this check box must not be selected. 1. 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 Use the existing has access to the desired database. database. 2. 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. ©2024 Omnissa. All Rights Reserved 20

Installing App Volumes 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. 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. For more information, see the App Volumes administration guide on Omnissa Product Documentation. Deploy App Volumes Manager Silently You can install App Volumes Manager silently using the Microsoft Windows Installer (MSI). You might want to perform a silent installation when you want to run the installation unattended. Prerequisites • You must have administrator privileges on the machine where you want to perform the silent installation. • Ensure that your Windows Server has the latest OS security updates. See the Microsoft KB https://support.microsoft.com/en-us/kb/2919355 for more information. • Ensure that you have msodbcsql.msi which installs the ODBC 17.10 driver. msodbcsql.msi is present in the Omnissa App Volumes ISO at Installation\Manager. You can download the ISO from the All Downloads page. • Access vc_redist.x64.exe executable from the App Volumes Manager folder and run the executable. ©2024 Omnissa. All Rights Reserved 21

Installing App Volumes Procedure 1. Open a command prompt and run the following command to install the ODBC driver: msodbcsql.msi /qn IACCEPTMSODBCSQLLICENSETERMS=YES /norestart 2. Install App Volumes Manager.msi with the following parameters: The valid values for the DEPLOYMENT_PLATFORM parameter are as follows: ["AWS", "Azure", "Dell EMC", "General", "Google Cloud", "Oracle Cloud"]. If no other value of DEPLOYMENT_PLATFORM suits your requirement, then you can select General. ◦ Note: To deactivate the SQL server certificate validation during silent installation, use the ENABLESTRONGENCRYPTION parameter. This is an optional parameter. Local database with Windows authentication - IS_SQLSERVER_SERVER=(local)\SQLEXPRESS IS_SQLSERVER_DATABASE=svmanager_production RESET_DB=1 ALLOW_HTTP=1 ENABLESTRONGENCRYPTION=0 DEPLOYMENT_PLATFORM=platform ◦ Remote database - IS_SQLSERVER_SERVER=ip_address IS_SQLSERVER_DATABASE=database_name RESET_DB=0 ALLOW_HTTP=1 IS_SQLSERVER_USERNAME=username IS_SQLSERVER_PASSWORD=password IS_SQLSERVER_AUTHENTICATION=1 DEPLOYMENT_PLATFORM=platform Important: Non-ASCII characters are not supported in the database_name. Example: msiexec /i "App Volumes Manager.msi" /qb IS_SQLSERVER_SERVER=(local)\SQLEXPRESS IS_SQLSERVER_DATABASE=svmanager_production RESET_DB=1 ALLOW_HTTP=1 DEPLOYMENT_PLATFORM=Azure Deploy App Volumes Manager through Azure Marketplace App Volumes Manager can be installed in the Microsoft Azure Marketplace for Remote Apps and Desktops experience. You can use the Azure Marketplace offer and deploy an Azure virtual machine image with App Volumes Manager already installed and partially configured. The Azure Marketplace offer also has the capability to integrate Azure Virtual Desktop with App Volumes Manager which allows you to entitle applications directly in Azure Virtual Desktop. The rest of the configuration can be done using the App Volumes Manager admin UI. The integration between Azure Virtual Desktop and App Volumes Manager triggers an automatic synchronization between App Volumes Manager and Azure Virtual Desktop resulting in App attach packages getting created. Administrators can assign these App attach packages to host pools, create application groups, and assign the application groups to the user or user groups. Important • App Volumes Manager uses Microsoft Entra ID as the domain for the integration with Azure Virtual Desktop. Entra ID cannot be used with standalone desktops for application management. • If you only have Active Directory, then in addition to selecting the Azure Virtual Desktop integration when deploying App Volumes Manager through the Azure Marketplace offer, you need to use Microsoft Entra Connect to synchronize entities from your Active Directory to Entra ID. For more information about Microsoft Entra Connect, see the Microsoft documentation. ©2024 Omnissa. All Rights Reserved 22

Installing App Volumes Deployment Considerations Note the following regarding this deployment: • The Azure Marketplace solution is not supported for Omnissa App Volumes 2.x. • The Azure Marketplace solution with Azure Virtual Desktop integration is supported for App Volumes 4, version 2410 and later only. Configuration Scenarios of Azure Marketplace Deployment of App Volumes Manager Based on your environment and requirements, you can determine which configuration scenario to choose when deploying App Volumes Manager in Azure Marketplace. Environment Azure Virtual Azure Virtual Azure Virtual Desktop with Active and Desktop with Entra ID Desktop with Entra ID Directory (Legacy) Requirements (hybrid) Registered domain in App Entra ID Entra ID Active Directory Volumes Manager Availability of AVD Integration functionality in Yes Yes No the Azure Marketplace Offer Yes You need to use Requirement of Microsoft Entra Yes Microsoft Entra No Connect to Connect synchronize entities Microsoft Entra Connect must be installed from your Active on the Active Directory Domain Controller. Directory to Entra ID. For more information, see Hybrid Identity. Azure Virtual Desktop host Entra ID Entra ID Active Directory pool domains Supported Application Desktop and Desktop and RemoteApp Group type in RemoteApp RemoteApp Azure Automatic application Automatic application Application synchronization occurs synchronization occurs Manual configuration such as creating synchronization between App Volumes between App Volumes application groups, application properties with Azure Manager and Azure Manager and Azure such as application path, icon path, and Virtual Desktop Virtual Desktop when Virtual Desktop when other related information is required. these are integrated these are integrated ©2024 Omnissa. All Rights Reserved 23

Installing App Volumes Environment Azure Virtual Azure Virtual Azure Virtual Desktop with Active and Desktop with Entra ID Desktop with Entra ID Directory (Legacy) Requirements (hybrid) using the Integration using the Integration tab in App Volumes tab in App Volumes Manager admin UI. Manager admin UI. This tab allows you to This tab allows you to configure the configure the integration between integration between App Volumes Manager App Volumes Manager and Azure Virtual and Azure Virtual Desktop. Desktop. This integration This integration synchronizes the synchronizes the CURRENT packages CURRENT packages and certain application and certain application properties between properties between App Volumes Manager App Volumes Manager and Azure Virtual and Azure Virtual Desktop. Desktop. Assignment can be Assignment can be Assignment needs to be done in App done only in Azure done only in Azure Volumes Manager and Azure Virtual Virtual Desktop Virtual Desktop Desktop. Entitle User needs to be assigned to an applications User or user group can User or user group can application in App Volumes Manager admin be assigned to be assigned to UI and the same user must be assigned to application group in application group in the application group in Azure Virtual Azure Virtual Desktop. Azure Virtual Desktop. Desktop. If you want to use your existing App Volumes Manager registered with Active See Workflow for See Workflow for Directory domain or if you have already What to do deploying App deploying App deployed earlier versions (2406 and earlier) next Volumes Manager Volumes Manager of App Volumes Manager on Azure Virtual using Azure using Azure Desktop and want to upgrade to the current Marketplace. Marketplace. version of App Volumes Manager, then continue using the workflow as described in this documentation. Workflow for deploying App Volumes Manager using Azure Marketplace This workflow describes how to use the Azure Marketplace offering to deploy an Azure virtual machine image with App Volumes Manager already installed and partially configured. Additionally, the Azure Marketplace offering also has the Azure Virtual Desktop integration capability which integrates Azure Virtual Desktop with App Volumes Manager. As an administrator, you must perform the rest of the configuration using the App Volumes Manager admin UI. Note: When using any of the Microsoft applications in the procedure described in this task, see the relevant Microsoft documentation. However, ensure that you follow specific configurations required for deploying Omnissa App Volumes on Azure. ©2024 Omnissa. All Rights Reserved 24

Installing App Volumes Prerequisites • Ensure that you have read through the Configuration Scenarios of Azure Virtual Desktop Integration with App Volumes Manager. See Configuration Scenarios of Azure Virtual Desktop Integration with App Volumes Manager. • Ensure that you are aware of the requirements necessary for this workflow. For more information about these requirements, see Prerequisites for Deploying App Volumes Manager through Azure Marketplace. • The resources which can be automatically deployed as part of Azure Marketplace are as follows: Azure virtual machine, public IP address, Azure virtual network, Azure storage and file share, Azure private endpoint, and network security group. Ensure that you are aware of these resources. The rest of the components required is as follows: resource group, subnet, network interface, Azure virtual desktop host pool, and App Volumes agent. Note: Public IP address and Azure storage and file share are deployed only if you have opted for the automatic provision of these resources. For more information about these resources, see Resources used in App Volumes Deployment on Azure. • If you want to use an existing virtual network when configuring the basic details for deploying App Volumes using Azure Marketplace, ensure that you have created a virtual network which can be used in the Azure subscription. When deploying App Volumes in the Azure Marketplace, the same virtual network is required so that other components in the Azure infrastructure such as virtual machines (active directory domain services and App Volumes Manager) and file share can communicate with each other. It is recommended that all virtual machines reside in the same region as the virtual network. For information about how to create a virtual network, see the corresponding Microsoft documentation. • If you intend to integrate App Volumes Manager with Azure Virtual Desktop, then ensure that you have the following permissions: ◦ Microsoft.Authorization/roleDefinitions/write ◦ Microsoft.Authorization/roleAssignments/write ◦ Microsoft.ManagedIdentity/userAssignedIdentities/assign/action ◦ Microsoft.ManagedIdentity/userAssignedIdentities/read Procedure 1. In the Microsoft Azure portal, click Marketplace. 2. Search for the App Volumes: Apps on Demand offer. 3. Click the offer. 4. Follow the prompts. 5. Click Create. ©2024 Omnissa. All Rights Reserved 25

Installing App Volumes Fields Values Project Details To manage deployed resources, select the Subscription and Resource group. Alternately, you can also create a new resource group. 1. Enter the Region. 2. Enter the name of the virtual machine. 3. To remote desktop into the App Volumes Manager virtual machine, enter the credentials (user name and password) for the local administrator. Instance 4. Optional: Change the default size of the virtual machine as per the options provided. details 5. By default, a new public IP address is created. Alternately, you can also select any existing IP address for the virtual machine. Note: If you do not want to use a public IP address for the App Volumes Manager virtual machine, select None. 6. Depending on the public IP address created previously, you can create a DNS prefix for the public IP address. If you choose to access the App Volumes Manager admin UI in a browser using a public IP address, then you can keep the DNS name handy. Configure By default, a new virtual network and a corresponding subnet are created. Alternately, you can select an existing virtual virtual network and the corresponding subnet. networks ©2024 Omnissa. All Rights Reserved 27

Installing App Volumes Options Steps Local SQL Server This is the default option. No further action required. Express Database Note: It is not recommended to use this option for production environment. Enter the Database connection details as follows: 1. Enter the Host name. 2. Enter the Database Name. 3. Enter the Username and Password of the user account used to access the Remote SQL Server database. 4. Optional: If you have the relevant certificate to validate the SSL connection to SQL server, select the Enable Remote SQL SQL Server certificate validation checkbox. Server database By default, this checkbox is selected. Note: If you do not have a relevant certficate to validate the SSL connection to SQL server, then clear the Enable SQL Server certification validation checkbox. 5. To upload SQL Server certificate, click the folder icon and browse to a local directory where the CA certificate is present. 6. Select the file and click Open. ©2024 Omnissa. All Rights Reserved 29

Installing App Volumes ▪ If you want the Azure Marketplace offer to automatically provision storage with file shares, then perform the following: 1. Select Create new file shares. This is the default option. 2. Depending on your requirement: Option Procedure Leave the Integrate with The Azure Marketplace offer uses the IP address of the private endpoint as the file private DNS zone check box share address. This is the default option. blank As prerequisites, ensure that the following is configured: ▪ Create a private DNS zone with the instance name as privatelink.file.corewindows.net. ▪ In the private DNS zone, add the virtual network of the domain controller as the Select the Integrate with virtual network link. private DNS zone check box Adding the virtual network as the virtual network link ensures successful name resolution of the file storage account to the IP address of the private endpoint. 1. Select an existing Private DNS Zone. ▪ If you want to use an existing storage, then select Use existing file shares. After the Azure Marketplace offer is deployed, you must manually configure the storage in App Volumes Manager admin UI using existing file shares. ©2024 Omnissa. All Rights Reserved 31

Installing App Volumes e. Select the AVD Integration checkbox, then perform the following steps: Note: Ensure that you use App Volumes agent 2410 and later versions only. a. Enter the Entra ID details of the application that you registered earlier. b. Select the desired Managed Identity Type. ©2024 Omnissa. All Rights Reserved 32

Installing App Volumes Option Description System System assigned managed identity is automatically created. App attach packages are granted access at the assigned same resource group level where the App Volumes Manager gets deployed. Manually create a user assigned managed identity. App Volumes Manager requires these permissions to create and manage App attach packages for these resource groups. Note: Ensure that the following permissions are set for the resource group: ▪ Microsoft.Authorization/permissions/read User ▪ Microsoft.Resources/subscriptions/resourceGroups/read assigned ▪ Microsoft.DesktopVirtualization/appattachpackages/read ▪ Microsoft.DesktopVirtualization/appattachpackages/write ▪ Microsoft.DesktopVirtualization/appattachpackages/delete 1. Click Add. 2. In the Add user assigned managed identity window, select the desired Subscription and User assigned managed identities. 3. Click Add. ©2024 Omnissa. All Rights Reserved 33

Installing App Volumes f. Click Next. g. In the Tags tab, create the desired tags. h. Click Review + Create. i. To start the deployment, click Create. Depending on the options you have chosen in the previous steps, the Azure Marketplace offer deploys all or some of the resources: Azure virtual machine, public IP address, virtual network, Azure storage and file share, private endpoint, and network security group. What to do next • For installing App Volumes agent, see Install App Volumes Agent. • If you have skipped the automatic storage provisioning (Use existing file shares), then you must manually add existing file shares to App Volumes Manager using the admin UI. For this configuration see Configure and Register the Machine Manager. • Complete the rest of the App Volumes Manager configuration. See Configuring App Volumes Manager. Note: ◦ Ensure that you configure the integration between App Volumes Manager and Azure Virtual Desktop from within App Volumes Manager. See Configure App Volumes Manager Integration with Azure Virtual Desktop. ◦ If you want to edit the registered Entra ID domain, see Register a Domain. • If all your entities are in Active Directory, then use Microsoft Entra Connect to synchronize entities with Microsoft Entra ID. For more information about Microsoft Entra Connect, see the Microsoft documentation. Prerequisites for Deploying App Volumes Manager through Azure Marketplace To deploy App Volumes Manager through Azure Marketplace, you must be aware of these requirements before the deployment. • On Azure, ensure that you have appropriate permissions to create virtual machines for App Volumes Manager, storage account, and fileshare. • Ensure that you have downloaded and installed the Omnissa App Volumes license file. App Volumes deployed in Azure Marketplace follows the Bring your own license pricing model. The offer when deployed, by default, has the default trial license. Hence, you must obtain the production license from the All Downloads page. To verify the license, see the Verify License section in the Omnissa App Volumes 4 Administration Guide. • Ensure that the App Volumes agent is downloaded. To download the App Volumes agent, perform the following: 1. Go to the Customer Connect page. ©2024 Omnissa. All Rights Reserved 34

Installing App Volumes 2. Click Downloads. 3. In the All Downloads page, search for App Volumes in the Products A-Z listing and click View Download Components. 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 are aware of the system requirements that are necessary for using App Volumes. For more information, see System Requirements. • For production environment, ensure that you have an existing SQL server database. By default, a local SQL Server Express Database is installed within the App Volumes Manager virtual machine. However, this option is not recommended for production environments. • Ensure that you have an Azure subscription and your Azure subscription must be registered for the Microsoft.DesktopVirtualization resource provider. For more information about Microsoft Azure, see the Azure documentation. • On Azure, ensure that you have appropriate permissions to create virtual machines for App Volumes Manager, storage account, fileshare, database, and manage Microsoft Entra ID. NOTE: Currently for App Volumes, Microsoft Entra ID can be used as the domain only when integrating App Volumes Manager with Azure Virtual Desktop. • In the Microsoft Entra ID admin center, navigate to App registrations and register App Volumes as an application. When registering the application in the Microsoft Azure portal, ensure that you use the following values for these fields: ◦ For the Redirect URI (Optional), select Platform as Web and the URI value as https://APP_VOLUMES_MANAGER_FQDN/entra_id_callback/ DIRECTORY(TENANT)_ID, where the Tenant ID is of your registered application. ◦ Select Supported account types as Accounts in this organizational directory only (). When you configure the integration between App Volumes Manager and Azure Virtual Desktop, the following information is required: Directory (tenant) ID, Application (client) ID, Secret ID, and Client Secret. After registering your application, keep this information handy. For more information about how to register an application in Microsoft Entra ID, see the Microsoft Documentation • Assign necessary API permissions to the App Volumes application in the Microsoft Azure portal. These permissions are required for the application to perform tasks in Azure. Go to the registered application and add the following Microsoft Graph API permissions to the application: Application.Read.All, Device.Read.All, GroupMember.Read.All, User.Read.All, and User.Read. Note: User.Read is a Delegated permission whereas the others are Application permissions. ◦ Ensure that you grant admin consent for these permissions. To grant admin consent, you must either be in an administrator role or a user with enough permissions to grant consent. ©2024 Omnissa. All Rights Reserved 35

Installing App Volumes Resources used in App Volumes Deployment on Azure When deploying Omnissa App Volumes for Azure Virtual Desktop Remote Apps, depending on the administrator choices, some resources are automatically provisioned as part of the Azure Marketplace and a few others can be created by the administrator. Following resources are automatically deployed by the Azure Marketplace offer wizard: Note: For more information about any of the Azure resources, see the relevant Microsoft documentation. • Azure Virtual Machine This resource is based on the latest Windows server OS with App Volumes Manager pre-installed on the virtual machine instance. • Public IP address A public IP address can be used make App Volumes Manager accessible from the public internet by configuring the IP address for the virtual machine which has the pre-installed App Volumes Manager. If administrators do not want to make the virtual machine accessible over a public internet, they have the option of selecting the value as None when configuring the IP address in the Azure Marketplace offer wizard. • Azure Virtual Network To ensure connectivity between App Volumes agent (installed on a session host virtual machine) and App Volumes Manager and Azure Storage, a virtual network peering must be configured between the virtual network where the Azure Virtual Desktop host pool is deployed and the virtual network of the virtual machine where the App Volumes Manager is installed. • Azure Storage and Azure File Share These resources are used by App Volumes as application storage for hosting the application packages which are mounted and delivered on Azure Virtual Desktop Host pools. Administrators can choose an automatic provision of the storage account and file shares by the Azure Marketplace offer. As a result, the storage is automatically configured. If administrators have opted to use the IP address of the private endpoint to access the storage account, then the UNC path of the delivery and staging file shares contain the IP address and the name of the private endpoint. To find the storage account associated with this IP address, navigate to the Private endpoint in the Azure portal and click the Private link resource. The storage account details are displayed. Note: When accessing the storage account from a public network, it is recommended that you perform the following: 1. Navigate to the Networking tab of the storage account. 2. In the Firewalls and virtual networks > Public network access section, select Enabled from selected virtual networks and IP addresses. 3. In the Firewall section, select Add your client IP address. Alternately, administrators can choose to use an existing storage and configure the file shares in the App Volumes Manager admin UI after the deployment. • Azure Private End Point A private end point is required to secure access to the Azure Storage. ©2024 Omnissa. All Rights Reserved 36

Installing App Volumes • Network Security Group The network security group is preconfigured with inbound and outbound firewall rules to allow the following: ◦ RDP (Remote Desktop Protocol) access to the virtual machine where App Volumes Manager is installed. ◦ HTTPS access to App Volumes Manager admin UI. Note: If you want to access the App Volumes Manager admin UI using HTTP (port 80, insecure), then you can manually configure the inbound port rule in the Azure portal, navigating to the Settings > Networking section of the virtual machine which has App Volumes Manager installed. Install App Volumes Agent After you have installed App Volumes Manager, install the App Volumes agent on the packaging computer and target desktops. For improved security when using the App Volumes agent, deactivate weak ciphers in SSL and TLS to ensure that Windows-based machines running the agent do not use weak ciphers when they communicate using SSL/ TLS protocol. See Disable Weak Ciphers in SSL and TLS in the Horizon 7 documentation. Important: Do not install the agent on the same machine where the App Volumes Manager is installed. You can also install the agent silently using the Microsoft Windows Installer (MSI). See Install App Volumes Agent Silently for more information. Prerequisites • Ensure that you have installed the App Volumes Manager and you have the host IP address and port number. • Verify that your environment meets the system requirements. See System Requirements. • Verify that your account has local administrator privileges on the target computer. • Windows Update ◦ For a non-persistent virtual desktop, install the latest Windows Update on the target computer and subsequently deactivate the Update. When you have application packages or Writable Volumes and the Windows Update is not deactivated on the target computer, the system volume or the Writable Volumes might get corrupted. ◦ For a persistent virtual desktop, you can install the latest Windows Update and keep the Update activated. • If you intend to use this virtual machine as a packaging computer, create a clean snapshot or take a backup of this machine. Revert to this snapshot or the backup before packaging new application packages. • Using Omnissa App Volumes on a persistent virtual desktop: ◦ Separate base images must be used when upgrading the App Volumes agent for persistent and non-persistent pool deployments. ◦ Ensure that you are aware of the rest of the considerations for Using App Volumes on a Persistent Virtual Desktop. Procedure 1. Go to the Customer Connect page. ©2024 Omnissa. All Rights Reserved 37

Installing App Volumes a. Click Downloads. b. In the Products A-Z listing, search for App Volumes and click Download Product. c. In the Download App Volumes page, navigate to the desired edition, and click GO TO DOWNLOADS. d. In the Download Product page, download the files. 2. Run the App Volumes installer. The same installer is used to install App Volumes Manager and the agent. 3. Read and accept the End User License Agreement and click Next. 4. Select Install App Volumes Agent and click Next. 5. Enter the IP address and port number. Note: The default port number for App Volumes Manager is 443. Enter 80 for the port number if you have configured App Volumes Manager to listen on an HTTP port. 6. (Optional) If you do not want the agent to validate the App Volumes Manager certificate, check the Disable Certificate Validation with App Volumes Manager box. Certificate validation is enabled by default. 7. Click Next. 8. In the Machine Type window, select the desired option. In addition to the information about the options provided in the installer window, see Using App Volumes on a Persistent Virtual Desktop. 9. Click Install and follow any on-screen instructions. 10. To exist the wizard after the installation is complete, click Finish. 11. To complete the agent installation, restart your packaging virtual machine. What to do next Configure SSL certificates for the agent. You can also deactivate SSL communication and certificate validation between App Volumes Manager and agent. For more information, see the Omnissa App Volumes Administration Guide on Omnissa Product Documentation. Install App Volumes Agent Silently You can install App Volumes agent silently using the Microsoft Windows Installer (MSI). You perform a silent install using the command line and you do not need to use the App Volumes installer. You can also upgrade the agent silently. See Upgrade App Volumes Agent Silently. EnforceSSLCertificateValidation parameter allows App Volumes agent to validate the App Volumes Manager certificate. This parameter has two values: 0 indicates that certificate validation is deactivated and 1 indicates that certificate validation is activated. By default, the value of this parameter is 1. NONPERSISTENT parameter allows you to use Omnissa App Volumes in a non-persistent virtual desktop or persistent virtual desktop environment. This parameter has two values: 0 indicates that App Volumes agent is installed to work in a persistent virtual machine and 1 indicates that App Volumes agent is installed to work in a ©2024 Omnissa. All Rights Reserved 38

Installing App Volumes non-persistent virtual machine. By default, the value of this parameter is 1. For more information about using App Volumes on a persistent virtual desktop, see Using App Volumes on a Persistent Virtual Desktop. Prerequisites • Ensure that you have installed the App Volumes Manager and you have the host IP address and port number. • Verify that your environment meets the System Requirements. • Verify that your account has local administrator privileges on the target computer. • Install the latest Windows Update on the target computer and subsequently deactivate the Update. When you have application packages or Writable Volumes and the Windows Update is not deactivated on the target computer, the system volume or the Writable Volumes might get corrupted. • If you intend to use this virtual machine as a packaging computer, create a clean snapshot or take a backup of this machine. Revert to this snapshot or back up before you package new Application Packages. Procedure 1. Open a Windows command prompt on your machine. 2. In the command prompt, access the App Volumes Agent.msi file location. 3. To install the agent, use the following command: ©2024 Omnissa. All Rights Reserved 39

Installing App Volumes Option Description msiexec.exe /i “App Volumes Agent.msi” /qn MANAGER_ADDR= App Volumes 4 MANAGER_PORT= EnforceSSLCertificateValidation= NONPERSISTENT= Update 1 and later Note: ◦ EnforceSSLCertificateValidation is an optional parameter. ◦ NONPERSISTENT parameter is available only from App Volumes 2406 and later. msiexec.exe /i “App Volumes Agent.msi” /qn MANAGER_ADDR= App Volumes 4 MANAGER_PORT= EnforceSSLCertificateValidation= Note: All parameters are mandatory. ©2024 Omnissa. All Rights Reserved 40

Installing App Volumes Install App Volumes Application Capture Command-Line Program To capture application installs into a package outside of App Volumes Manager console, you can install the standalone Windows, Omnissa App Volumes Application Capture Command-Line Program on a virtual machine. After the capture session, .vhd and .vmdk (monolithic sparse) package formats are created and are accompanied by a .json metadata file. Prerequisites • Download the App Volumes installer from the All Downloads page. • Ensure that no other App Volumes component is installed on the virtual machine where you intend to install the command-line capture program. If you have an App Volumes component installed on the machine, take a snapshot of the machine, clone it, and uninstall the component. If you have used the machine to package an application, then you must revert the machine to its original state. It is necessary to revert because the capture process can leave remnants that can adversely impact other application installs. • Ensure that your virtual machine has sufficient disk space for all the application packages that you intend to create. The amount of disk space required depends on the number and size of the programs that you intend to install during the capture process. Procedure 1. Run the setup.msi installer. The same installer is used to install App Volumes Manager and the agent. 2. Read and accept the End User License Agreement and click Next. 3. Select Install App Volumes Tools and click Install. 4. Follow any on-screen instructions. 5. To exit the wizard after the installation is completed, click Finish. 6. To complete the App Volumes Application Capture Command-Line Program installation, restart your virtual machine. What to do next For more information about how to use the command-line capture program, see the Omnissa App Volumes Administration Guide at Omnissa Product Documentation. ©2024 Omnissa. All Rights Reserved 41

Installing App Volumes Verify License You must enter the Omnissa App Volumes license information before configuring other components. A valid license is required to activate and use App Volumes. Prerequisites Ensure that you have downloaded and installed the App Volumes license file. TThe production license file can be downloaded from the All Downloads page. Procedure 1. From the App Volumes Manager console, click CONFIGURATION > License. 2. Verify the license information that is displayed. If you have an evaluation license, you can use App Volumes until the expiration date. 3. (Optional) To apply a different license, click Edit and browse to the location of the license you want to upload. 4. Click Upload to upload the App Volumes license file. 5. Click Next and follow on-screen instructions. Scaling App Volumes Manager To scale App Volumes Manager, you can install an additional App Volumes Manager component on multiple servers and point them to a shared SQL database. Multiple App Volumes Manager instances can be load balanced by a hardware load balancer. Alternatively, you can configure the App Volumes agent to communicate with multiple App Volumes Manager servers. Procedure 1. To install additional App Volumes Manager instances, follow standard installation procedures and point a new instance to the existing SQL database. Important: In the installation wizard, ensure that you have deselected the Create a new database or overwrite the existing database check box. Install App Volumes Manager 2. Register App Volumes Manager server. For detailed information, see the Register App Volumes Manager Server section in the Omnissa App Volumes Administration Guide at Omnissa Product Documentation. 3. Depending on whether you use the load balancer or configure App Volumes agent, perform the following steps: ©2024 Omnissa. All Rights Reserved 42

Installing App Volumes Option Procedure Use a load balancer Add the additional App Volumes Manager instances to the load balancer. 1. Modify the registry key HKLM\SYSTEM\CurrentControlSet\Services\svservice\Parameters as follows: ▪ Add ManagerN as the string value. N ranges between 0 to 9 ▪ Add FQDN of the App Volumes Manager and port as value data. By default, the port number is 443. For example: To add data for an additional App Volumes Manager instance whose IP address is Configure App 192.168.127.53 and port 443, perform the following: Volumes agent a. Open regedit.exe. b. Access the registry key Computer\HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\ svservice\Parameters. c. Right click on the registry key and select New > String Value. d. Add the value as Manager2. e. Double-click Manager2 and add the data as 192.168.127.53:443. 2. Click OK. 3. Restart the virtual machine on which you have installed the App Volumes agent. ©2024 Omnissa. All Rights Reserved 43

Installing App Volumes Supported App Volumes Scenarios The information presented here lists the possible and supported scenarios of applications and Writable Volumes assigned to user and computer entities with different types of virtual desktop pools. This information also includes the supported Omnissa App Volumes scenarios when used in RDSH environments. Note: For RDSH scenarios, a refresh at computer shutdown is required. The following table lists the possible scenarios for application and Writable Volumes when assigned to a user and computer in a virtual desktop pool and RDSH environments (Published Application and Published Desktop). Both instant-clone desktop pool and automated full-clone desktop pool have Floating and Dedicated user assignment options. For more information about creating and managing instant-clone desktop pools and automated full-clone desktop pools, see the Horizon Documentation. Virtual Desktop RDSH Infrastructure Assignment Volume Type Floating Dedicated Published Published Type Application Desktop Application Yes Yes Yes Yes User Writable Yes No No No Volume Application Yes Yes Yes Yes Computer Writable No No Yes Yes Volume ©2024 Omnissa. All Rights Reserved 44

Upgrading App Volumes Components Upgrading App Volumes Components You can upgrade the different components of Omnissa App Volumes by using the installer. If you have App Volumes 2.18 installed on your system, you can upgrade to the latest version without uninstalling your currently installed version. If you have installed an App Volumes version earlier than 2.18, you must first upgrade to 2.18 and then upgrade to the latest version. Upgrade App Volumes Manager Download and run the latest version of the Omnissa App Volumes installer to upgrade your App Volumes Manager. You can upgrade from App Volumes Manager 2.18 to the latest App Volumes Manager version. If you want to upgrade multiple App Volumes Managers which point to a central database, open services.msc and stop the App Volumes Manager service on each server. You must then run the installer on each server to upgrade App Volumes. The import functionality has changed in App Volumes 4, version 2012. For optimal import functionality, ensure all App Volumes Manager servers are upgraded to App Volumes 4, 2012 before performing import actions. For more information about the behavior of imported application packages, see the latest version of Omnissa App Volumes 4 Administration guide at Omnissa Product Documentation. For minor and maintenance upgrades, see Considerations for Performing Rolling Upgrades. Prerequisites • Download the latest App Volumes installer from All Downloads page. • Schedule a maintenance window to ensure that there is no service degradation during the upgrade process. • In the Windows Start menu, open Control Panel and click Administrative Tools > ODBC data source. Note down the database and server name defined in the system ODBC source svmanager. • Back up the App Volumes database using SQL Server tools. • Create a full server backup or snapshot of the App Volumes Manager server. • If you are using App Volumes Manager earlier than 2.18, you must first upgrade to App Volumes Manager 2.18 or later. Important: Before upgrading from App Volumes Manager 2.x, you must stop all instances of App Volumes Manager service. Procedure 1. Log in as administrator on the machine where App Volumes Manager is installed. 2. Locate the App Volumes installer that you downloaded and double-click the setup.msi file. 3. Select the App Volumes Manager component and click Install. ©2024 Omnissa. All Rights Reserved 45

Upgrading App Volumes Components A notification window with the upgrade process details is displayed. 4. Review the Operational Data Collection notice and click Next. 5. In the Ready to Install the Program section, select the platform type where you intend to deploy App Volumes Manager. If no other value of platform type suits your requirement, then select General. 6. Click Next to confirm the upgrade. 7. Click Install to begin the installation. A Status Bar shows the progress of the installation. The installation process takes from 5 through 10 minutes to finish. During this time, configuration information is first backed-up, new files are installed, and the configuration information is restored. 8. Click Finish to complete the installation. Results App Volumes Manager is upgraded. Note: All certificates that you had previously configured are retained and you do not need to reconfigure them. What to do next • Upgrade App Volumes Agent. • If the App Volumes version you have upgraded to has new or upgraded templates and you want to use these templates, see the Upload Templates section in the Omnissa App Volumes Administration Guide at Omnissa Product Documentation. • After you have upgraded App Volumes to the latest version, you can activate registration security. If you have a multi-manager setup, you must also register any additional App Volumes Manager servers. For details, see the Register App Volumes Manager Server section in the Omnissa App Volumes Administration Guide at Omnissa Product Documentation. Perform Rolling Upgrades A rolling upgrade is a deployment strategy in which a cluster of App Volumes Manager server instances is upgraded by taking one App Volumes Manager offline at a time. Such a strategy reduces the overall downtime. As only one App Volumes Manager server is taken offline at a time, the App Volumes Manager service is available and end users can continue to have the Applications and Writable Volumes attached to their virtual machines during the upgrade process. The rolling upgrade process is finished when you perform the procedure described in this section for all App Volumes Manager instances in the cluster. Prerequisites • If you are in the Administrators role, ensure that users in other administrator roles do not make any configuration or assignment changes from the App Volumes Manager admin UI. ©2024 Omnissa. All Rights Reserved 46

Upgrading App Volumes Components For other user roles, see Assigning and Managing Roles and Privileges in the Omnissa App Volumes Administration Guide at Omnissa Product Documentation. • Back up the Omnissa App Volumes database using SQL Server tools. • Be aware of the Considerations for Performing Rolling Upgrades. • Download the latest App Volumes installer from the All Downloads page. Procedure 1. In the load balancer, remove the App Volumes Manager server that you intend to upgrade first. 2. In the vCenter Server, take a VM Snapshot of the App Volumes Manager server by selecting the Snapshot the virtual machine’s memory option. 3. Make a note of the current time on the App Volumes Manager server. This timestamp is necessary when reviewing the App Volumes Manager log files which must be done for verifying that the rolling upgrade is successful. 4. In the Administrator role, log into the App Volumes Manager server and run the App Volumes installer. 5. Follow the prompts to install the App Volumes Manager. 6. After the installation is complete, perform the following steps: a. Ensure that App Volumes Manager is reachable and you can access the App Volumes Manager admin UI. b. Navigate to the App Volumes Manager Log folder, locate the svmanager_setup.log file, and ensure that exceptions or database errors are not present in the log file. 7. In the load balancer, add the App Volumes Manager server back which was removed in an earlier step. 8. Repeat the steps in this procedure for all the App Volumes Manager server instances in the cluster. 9. Verify the upgrade in the App Volumes Manager console by navigating to ACTIVITY > System Messages and ensure that there are no error messages from the upgrade. Considerations for Performing Rolling Upgrades To upgrade the App Volumes Manager servers without shutting down the services, you must be aware of certain guidelines. Important: Before upgrading from Omnissa App Volumes 2.x, you must stop all instances of App Volumes Manager service. You must be aware of the following considerations while planning for rolling upgrades: • Rolling upgrades can be performed from earlier versions of App Volumes 4. An upgrade from App Volumes 2.18 requires that App Volumes Manager services on servers must be stopped before performing the upgrade. • A full server backup or snapshot of the App Volumes Manager server must be taken. ©2024 Omnissa. All Rights Reserved 47

Upgrading App Volumes Components • Administrators cannot use the new functionality of the App Volumes Manager console until all App Volumes Manager instances within the cluster are upgraded to the desired version. • Before performing a rolling upgrade, all App Volumes Manager instances must be on the same version. • After upgrading the App Volumes Manager to the desired version, rolling back the upgrade might result in loss of new data that was created or updated in the database during the upgrade process. • App Volumes Agent must be upgraded only after upgrading all App Volumes Manager servers. Managing Packages and AppStacks in App Volumes Manager If you are upgrading from App Volumes Manager 2.x, you can manage both Packages and AppStacks in the App Volumes Manager UI. App Volumes Manager supports the co-existence of both Application Packages (for current version of App Volumes Agent) and AppStacks (App Volumes Agent 2.x). If AppStacks and Writable Volumes (2.x) are not in use, you can deactivate the VOLUMES (2.X) tab and other 2.x-related features in the App Volumes Manager UI by using the Enable Volumes (2.x) toggle switch. For example, this switch can be used to turn off 2.x-related features after migrating the AppStacks and Writable Volumes (2.x) from App Volumes Manager 2.x. Note: If you are upgrading from App Volumes Manager 2.x, the Enable Volumes (2.x) toggle switch is on by default. For information about how to use the toggle switch, see Configuring visibility and management of App Volumes Manager 2.x UI. Considerations before migrating from AppStacks to Packages The following AppStack functionalities are not available when managing Application Packages: • Limiting AppStack attachments. For more information, read the Limiting AppStack Attachments section in the Omnissa App Volumes 2.18 Admin Guide. • Option to attach an AppStack immediately. For more information, read the Assign an AppStack to a User section in the Omnissa App Volumes 2.18 Admin Guide. • Option to edit the type of Operating System to which an AppStack is attached. For more information, read the Edit an AppStack section in the Omnissa App Volumes 2.18 Admin Guide. Note: You can use the advanced setting in App Volumes Manager to allow package delivery to any operating system which is different from the operating system used during packaging. For more information about this setting, see Omnissa App Volumes 2103 Administration Guide at Omnissa Product Documentation. • AppStacks precedence For more information, read the AppStacks Precedence section in the Omnissa App Volumes 2.18 Admin Guide. • Reassign a Computer Writable Volume For more information, read the Reassign a Writable Volume to a Computer section in the Omnissa App Volumes 2.18 Admin Guide. ©2024 Omnissa. All Rights Reserved 48

Upgrading App Volumes Components You can access the Omnissa App Volumes 2.18 Admin Guide at Omnissa Product Documentation. Configuring visibility and management of App Volumes Manager 2.x UI When you upgrade from App Volumes Manager 2.x, the UI supports co-existence of both Application Packages and AppStacks. If AppStacks and Writable Volumes (2.x) are not in use after migrating from 2.x, you can deactivate the 2.x-related features in the UI by using the Enable Volumes (2.x) toggle switch. Prerequisites If you have decided to deactivate the 2.x-related UI features, ensure the following: • You have upgraded to the latest version of App Volumes Agent. • You have migrated AppStacks and Writable Volumes (2.x) to the latest version of Omnissa App Volumes template format. Procedure 1. From App Volumes Manager, go to CONFIGURATION > Settings. 2. On the Settings page, click Advanced Settings. 3. To deactivate the VOLUMES (2.X) tab and other 2.x-related information, click the Enable Volumes (2.x) toggle switch. By default, Enable Volumes (2.x) is on. 4. Refresh App Volumes Manager . VOLUMES (2.X) tab and other 2.x-related features are deactivated from the UI. Upgrade App Volumes Agent To upgrade your App Volumes agent, download and run the latest version of the Omnissa App Volumes installer. You can upgrade from App Volumes agent 2.18 to the latest App Volumes agent version. You can also upgrade the agent silently. See Upgrade App Volumes Agent Silently. Note: During the upgrade, if a failure occurs or the upgrade is cancelled, the installer for App Volumes agent rolls back to the previously installed version of the agent. After the rollback, the agent virtual machine must be restarted. Prerequisites • Download the latest App Volumes installer from the All Downloads page. • Schedule a maintenance window to ensure that there is no service degradation during the uninstall and subsequent upgrade process. • Upgrade the App Volumes Manager. Note: Ensure that the App Volumes Manager version used is the same version or a later version than ©2024 Omnissa. All Rights Reserved 49

Upgrading App Volumes Components the App Volumes agent. See Upgrade App Volumes Manager. • Unassign all AppStacks and writable volumes from the target computer where you plan to upgrade the agent. If you are upgrading in a persistent pool deployment, then you need not unassign the application packages. Upgrade occurs even when the application packages are attached to the target computer. • If you are using App Volumes Agent earlier than 2.18, you must first upgrade to App Volumes agent 2.18 or later. • Using App Volumes on a persistent virtual desktop: ◦ If you have used the beta version for this feature, you cannot directly upgrade to this version. You can only upgrade from an existing App Volumes agent version to this version. ◦ Separate base images must be used when upgrading the App Volumes agent for persistent and non-persistent pool deployments. ◦ Ensure that you are aware of the rest of the considerations for Using App Volumes on a Persistent Virtual Desktop. Procedure 1. Log in as administrator on the machine where the App Volumes agent is installed. 2. Locate the App Volumes installer you have downloaded and run the setup.msi file. 3. Select the App Volumes agent component in the Installer window and click Install. 4. To begin the installation, click Next. The installer backs up the configuration files and services. 5. When you see the confirmation message, click Finish. Upgrade App Volumes Agent Silently You can also upgrade the App Volumes agent silently using the Microsoft Windows Installer (MSI). You perform a silent upgrade using the command line and you need not use the Omnissa App Volumes installer. EnforceSSLCertificateValidation parameter allows App Volumes agent to validate the App Volumes Manager certificate. This parameter has two values: 0 indicates that certificate validation is deactivated and 1 indicates that certificate validation is activated. By default, the value of this parameter is 1. Note: During the upgrade, if a failure occurs or the upgrade is canceled, the installer for App Volumes agent rolls back to the previously installed version of the agent. After the rollback, the agent virtual machine must be restarted. Prerequisites • To ensure that there is no service degradation during the uninstall and subsequent upgrade process, schedule a maintenance window. • Upgrade App Volumes Manager ©2024 Omnissa. All Rights Reserved 50

Upgrading App Volumes Components • Unassign all application packages from the target computer where you plan to upgrade the agent. If you are upgrading to a persistent pool deployment, then you need not unassign the application packages. Upgrade occurs even when the application packages are attached to the target computer. Procedure 1. Open a Windows command prompt on your machine. 2. In the command prompt, access the App Volumes Agent.msi file location. 3. To upgrade the agent, use the following command: ©2024 Omnissa. All Rights Reserved 51

Upgrading App Volumes Components Option Description msiexec.exe /i “App Volumes Agent.msi” /qn MANAGER_ADDR= MANAGER_PORT= EnforceSSLCertificateValidation= Note: ◦ The following parameters are optional: MANAGER_ADDR, MANAGER_PORT, and EnforceSSLCertificateValidation. App Volumes ◦ When upgrading from versions earlier than App Volumes 4, version 2406, you cannot set the NONPERSISTENT parameter to 0. 4 For information about this parameter, see Install App Volumes Agent Silently. Update 1 ◦ When upgrading from App Volumes 4, version 2406 to App Volumes 4, version 2410 and later versions, using this parameter is optional because the parameter value set for upgrade is the same value which is set during installing App Volumes 4, version 2406. If you choose to use this parameter, ensure that the value of this parameter matches with the value used during installation. ◦ If you use the /norestart flag in the command, ensure that you restart the virtual machine after the command runs. This restart is necessary for the upgrade to complete. App msiexec.exe /i “App Volumes Agent.msi” /qn MANAGER_ADDR= MANAGER_PORT= Volumes EnforceSSLCertificateValidation= 4 Note: All parameters are mandatory. ©2024 Omnissa. All Rights Reserved 52