An MSI-wrapped VHD can be used to optimize application delivery on a Windows endpoint configured in the Local Copy package access mode because the MSI contains a compressed VHD. The MSI wrapper is downloaded and cached locally on the endpoint. After the download, the MSI is unwrapped, the VHD is virtualized, and the application is delivered to an end user even when the endpoint is offline.
MSI-wrapped VHD package generated using App Volumes Manager (Technical Preview)
When the Generate MSI when creating VHD package setting is turned on in App Volumes Manager, a .vhd and an .msi file are generated at the time of packaging. If the .msi file exceeds 2 GB, a .cab file is generated. These files are present at the same location and have the same name as the .vhd file. Though having different formats, the package is still considered as one and is represented as VHD + MSI. When this package is delivered to a Windows endpoint in the Local Copy package access mode, the MSI wrapper (.msi, .cab.) is preferred. If the MSI wrapper is missing, then the VHD (.vhd) is delivered.
Here are some considerations:
-
Though the MSI-wrapped VHD is preferred for application delivery, the VHD package must be available in the storage, which is accessible by App Volumes Manager.
-
The MSI-wrapped VHD is delivered to a Windows endpoint only when the endpoint is configured in the Local Copy package access mode.
For more information about package access modes, see Application Delivery Modes with App Volumes Manager in the App Volumes Installation Guide, version 2509 and later, at Omnissa Product Documentation.
-
For information about the Generate MSI when creating VHD package setting, see App Volumes Manager Configuration Settings Page.
-
The capture command-line program can be used to create the MSI wrapper from an existing VHD package. If the VHD package exists in App Volumes Manager, then the MSI wrapper gets automatically associated with the VHD package after a successful import. As a result, the package format changes to
VHD + MSI.You must understand the import behavior for the MSI-wrapped VHD package. See Understanding the Behavior of Imported Application Packages.
MSI-wrapped VHD package generated using the App Volumes Application Capture Command-Line Program
When using device management tools such as Omnissa Workspace ONE UEM, Microsoft Intune, or Microsoft Configuration Manager (SCCM) to manage the delivery and life cycle of App Volumes applications, only the MSI-wrapped VHD package can be used.
The capture command-line program is used to create an MSI wrapper from a VHD package. If the created MSI wrapper exceeds 2 GB, the output is an .msi file and a packageid.cab (CAB) file. Both files are necessary for installation, because the .msi file size limit is 2 GB. These files are present at the same location as the .vhd file and have the same name as the .vhd. However, both location and name can be changed using appcapture.exe parameters.
If the package has on-demand data available, then by default, the delivery type of the MSI wrapper is on-demand. Else, the delivery type of the package is classic. This delivery type can be changed from on-demand to classic using a parameter at the time of delivering the package to the endpoints.
For more information about delivering App Volumes applications to Windows endpoints, see Deliver App Volumes Applications to Windows Endpoints.
For more information about the App Volumes Application Capture Command-Line Program, see Using the App Volumes Application Capture Command-Line Program.
This MSI wrapper can be imported to App Volumes Manager. If the corresponding VHD package already exists in App Volumes Manager, then the MSI wrapper gets automatically associated with the VHD package after a successful import. You must understand the import behavior for the MSI-wrapped VHD package. See Understanding the Behavior of Imported Application Packages.
Was this page helpful?