You can deliver App Volumes applications to any Windows endpoint such as VDI (Virtual Desktop Infrastructure), physical windows devices, and cloud PCs. To deliver these applications, you must install Omnissa App Volumes components. Before installation, ensure that your system meets specific requirements.
Some of these components such as database, file share, and directory service require configurations and permissions. This information is covered across App Volumes documentation, in the context of installation, configuration and administration, and management of App Volumes. For App Volumes Administration Guide see Omnissa Product Documentation.
Caution: If the App Volumes agent machine hibernates or goes to sleep, then App Volumes applications delivered as VHD packages from remote SMB file shares fail to work as the packages stop getting virtualized. Additionally, native applications might also be impacted. For example: File Type Associations for (native) applications might be lost. As a result, such files might not open with their expected (native) application until the machine is restarted.
It is recommended to not hibernate (Windows sleep state S4) or put the App Volumes agent machine to sleep (Windows sleep state S1 and S3).
For more information about the sleep states, see this Microsoft documentation.
Managed mode and Standalone mode are the deployment mode options in App Volumes. For information about the App Volumes deployment model, see Choose Your App Volumes Deployment Model.
Managed Mode (deployment with App Volumes Manager)
The following are database, browser, and infrastructure requirements:
| Component | Description |
|---|---|
| Database | App Volumes Manager supports the following Microsoft SQL databases:
|
| Browser |
App Volumes Manager is supported on the latest stable versions of all major modern browsers. For the best performance, compatibility, and security, it is recommended to keep your browser up to date. Supported browsers include the following:
|
| App Volumes Manager |
|
| App Volumes Agent (client OS) |
|
| App Volumes Application Capture Command-Line Program | System requirements for the command-line capture program is the same as that of the App Volumes agent. Note:
|
| Hypervisor |
|
| File share (if using VHD) | SMB version 3 |
| Directory service |
|
| Storage Virtual Adapters and Devices Virtual SCSI Targets Per Virtual Machine (PVSCSI only) | 256 disks 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. |
The following are network requirements:
| Component | Purpose | Port number |
|---|---|---|
| App Volumes Manager | Agent and Manager communications |
|
| App Volumes Manager | Manager and Manager communications Note: Multiple App Volumes Manager components can communicate with each other in scenarios such as Scaling App Volumes Manager or in application synchronization. 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. | TCP 443 (HTTPS) |
| App Volumes SQL Database | Database communication | TCP 1433 (SQL) |
| App Volumes Manager | ESXi | TCP 443 (HTTPS) |
| vCenter Server | ||
| Note: For more information about App Volumes ports, see Network port information for Omnissa App Volumes and Ports and Protocol. | ||
Standalone Mode (deployment with device management tools)
| Component | Description |
|---|---|
| App Volumes Agent (client OS) |
|
| App Volumes Application Capture Command-Line Program | System requirements for the command-line capture program is the same as that of the App Volumes agent. Note:
|
| Device Management Tools | Omnissa Workspace ONE UEM, Microsoft Intune, or Microsoft Configuration Manager (SCCM) |
Was this page helpful?