Deliver App Volumes Applications to Windows Endpoints

App Volumes applications can be delivered directly to Windows endpoints using device management tools such as Workspace ONE UEM, Microsoft Intune, or Configuration Manager (SCCM). Such a capability allows you to install or uninstall App Volumes applications directly on these endpoints using MSI commands.

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.

To deliver applications in such a scenario, App Volumes agent must be directly installed on the Windows endpoints and there is no requirement for App Volumes Manager.

Prerequisites

• 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.

• Follow the Omnissa App Volumes licensing requirements.

  For more information about the licensing requirements and behavior, see the Obtain an App Volumes License section in the Omnissa App Volumes Install Guide at Omnissa Product Documentation.

• Ensure that App Volumes agent is already installed on the Windows endpoints. For more information, see the Install App Volumes Agent section in the Omnissa App Volumes Install Guide at at Omnissa Product Documentation.

• .msi and .vhd application package formats are used to deliver to the endpoints.

  Note: If you want to use your own delivery method, then you can use the .vhd format and App Volumes PowerShell commands.

  For more information about capturing an App Volumes application in either of these formats, see Capture an App Volumes Application.

Parameters that can be used when installing the App Volumes MSI application

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

  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

  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

How to deliver the packages