App Volumes agent can be installed on Windows endpoints thus allowing application delivery to devices such as physical desktops, laptops, and cloud desktops (Windows 365 Cloud PC). In the current version, App Volumes Manager is not used.
For App Volumes agent to virtualize an application package on an endpoint, the package must be delivered to the endpoint in the .msi or .vhd formats.
An MSI application can be created using the App Volumes Application Capture Command-Line Program.
The .msi application package can be delivered to a Windows endpoint using endpoint managers such as Workspace ONE UEM, Microsoft Intune, or Microsoft Configuration Manager. These applications can be installed and uninstalled using the MSI commands. After the application is installed, the application persists in the endpoint until the application is uninstalled. Even if the endpoint reboots, shuts down, or is not connected to the network, the application is always entitled to the user and remains functional . When the user logs back in (after a reboot or shutdown), the entitled application gets virtualized automatically .
During an application uninstall, the application remains delivered to the user until the user logs off. Subsequently, the application gets uninstalled only after the session ends.
.vhd packages can also be used to deliver to Windows endpoints. In this case, the packages can be installed, uninstalled, or swapped using App Volumes PowerShell commandlets.
Workflow for Delivering App Volumes Applications to Windows Endpoints
This workflow comprises of installing or upgrading App Volumes agent on the Windows endpoints, capturing new App Volumes application packages in the .msi format or generating a .msi package from an already captured application, and delivering these packages to endpoints using device management tools.
| Options | Description |
|---|---|
| Install App Volumes agent |
|
| Upgrade App Volumes agent | When upgrading from an earlier version, you must mandatorily use a production license. For more information about the licensing requirements, see Obtain a License for the Standalone App Volumes Agent Configuration and for more information about the upgrade procedure, see Upgrade App Volumes Agent and Upgrade App Volumes Agent Silently. |
Capture Application Packages
-
Ensure that you follow the System Requirements.
-
Install App Volumes Application Capture Command-Line Program.
-
Using the App Volumes Application Capture Command-Line Program, create an
.msiapplication package format.
For more information about using the program, see Using the App Volumes Application Capture Command-Line Program chapter in the Omnissa App Volumes Administration Guide at Omnissa Product Documentation.
Deliver App Volumes Applications
-
Ensure that the device manager has necessary configurations to manage your endpoints.
-
Using the
.msipackages, create the applications in the endpoint manager. -
With the help of the MSI commands, install the applications at the endpoints.
Note:
-
After the MSI is installed, the
.vhdand.jsonfiles of the application package are locally stored on the Windows endpoint at this location C:\ProgramData\Omnissa\AppVolumes\OfflineCache\<Volume ID>where <Volume ID> is the package volume ID
-
If you want to use your own delivery method, then you can use the
.vhdapplication packages and App Volumes PowerShell commandlets. -
Currently, there is no App Volumes Manager support for this delivery method. Hence, you can skip installing the App Volumes Manager component.
For more information about delivering the applications, see the Deliver App Volumes Applications to Windows Endpoints section in the Omnissa App Volumes Administration Guide at Omnissa Product Documentation.
Was this page helpful?