August 24, 2026

Deliver App Volumes Applications to Windows Endpoints

App Volumes has two deployment models - App Volumes Manager and device management tools - for delivering and managing the delivered applications on Windows endpoints. Depending on what deployment model is chosen, the delivery behavior varies.

If App Volumes Manager is chosen, then you have the option to deliver applications to a Windows endpoint using a shared storage or deliver the applications to a local storage which is present on the Windows endpoint. For a better understanding of the deployment models, see the Choose Your App Volumes Deployment Model section in the Omnissa App Volumes Installation Guide, version 2509 and later. To understand the application delivery modes with App Volumes Manager, see the Application Delivery Modes with App Volumes Manager section in the install guide.

Application delivery in Managed Mode (deployment using App Volumes Manager)

In shared storage mode, the Windows endpoint accesses packages placed on a shared storage. As a result, the endpoint must remain online for application delivery. This is the existing behavior in App Volumes.

In the local copy mode, MSI-wrapped VHD packages are locally downloaded on the Windows endpoint. After the download, the packages are virtualized and applications are delivered to the end user. Because local storage is used, applications are delivered to the end user even when the endpoint is offline and not connected with App Volumes Manager.

Packages are downloaded at this location: C:\ProgramData\Omnissa\AppVolumes\offlineCache\downloads\<Volume ID>

For more information about the MSI-wrapped VHD packages, see Using MSI-Wrapped VHD Package for App Volumes Delivery.

Application delivery in Standalone Mode (deployment using device management tools)

Using device management tools such as Workspace ONE UEM, Microsoft Intune, or Configuration Manager (SCCM), you can deliver an MSI-wrapped VHD package (.msi) to the Windows endpoint. To install or uninstall the App Volumes application on the endpoint, you can use MSI commands. If you want to use your own delivery method to deliver the applications, you can use the .vhd application package and PowerShell cmdlets to install and uninstall the applications.

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.

In this delivery method, there is no requirement for App Volumes Manager.

To understand the delivery behavior, see the Deliver App Volumes Applications Using Device Management Tools section in the Omnissa App Volumes Install Guide at at Omnissa Product Documentation.

How to deliver the packages to the endpoint

Parameters used with MSI command line

You can use parameters to change the package delivery type and list the application in Add/Remove programs when installing the App Volumes MSI application.

Package delivery type (DELIVERYTYPE)

If an application package has on-demand data available, then by default, the delivery type of the captured application package is on-demand. Else, the delivery type is classic.

To change the default delivery type at the time of delivering the .msi application package to the endpoint, DELIVERYTYPE parameter must be used. For the .vhd package, OnDemand or Classic must be specified as the value of the delivery type with the App Volumes PowerShell commandlet.

Whatever delivery type is selected at the time of installation, the same delivery type remains until the application is uninstalled. For example: if the delivery type is changed from on-demand to classic at the time of installing the application, then the delivery type cannot be changed back to on-demand. The delivery type remains classic at user login or logoff and endpoint reboot or shutdown.
List App Volumes MSI application in Add/Remove Programs (NOARP)

Whenever an MSI application is installed, an entry is created in Add/Remove Programs. Similarly, an entry is created even when an App Volumes MSI application is installed. If the App Volumes MSI application is installed silently, then such an entry is not created in the Add/Remove Programs list. This default behavior can be controlled using the NOARP parameter, which is optional.

This parameter has the following values:

1 – App Volumes MSI application entry is not listed in Add/Remove Programs

0 – App Volumes MSI application entry is listed in Add/Remove Programs

Procedure

Option Description

Option	Description
`.msi` format	Using the package, create an application in the endpoint manager. Use the MSI command to install the application: For example: `"application_package_name.msi"` If you want to use any of the optional parameters, then use the following command: `"application_package_name.msi" DELIVERYTYPE=Classic NOARP=0` Note: After the MSI is installed, the `.vhd` and `.json` files 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. To uninstall the application, use the corresponding MSI command.
`.vhd` format	If you want to use your own delivery method, then use the `.vhd` package and some of the PowerShell commands such as `Install-AppVolumesPackage`, `Uninstall-AppVolumesPackage`, `Swap-AppVolumesPackage`, and others. For more information about these commands and other PowerShell commands, see App Volumes PowerShell Cmdlets for Delivering Applications to Windows Endpoints.

.msi format

Using the package, create an application in the endpoint manager.
Use the MSI command to install the application:
For example:
"application_package_name.msi"

If you want to use any of the optional parameters, then use the following command:
"application_package_name.msi" DELIVERYTYPE=Classic NOARP=0

Note: After the MSI is installed, the .vhd and .json files 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.

To uninstall the application, use the corresponding MSI command.

.vhd format If you want to use your own delivery method, then use the .vhd package and some of the PowerShell commands such as Install-AppVolumesPackage, Uninstall-AppVolumesPackage, Swap-AppVolumesPackage, and others.
For more information about these commands and other PowerShell commands, see App Volumes PowerShell Cmdlets for Delivering Applications to Windows Endpoints.

Was this page helpful?