So… on December 19th of 2024, Omnissa released App Volumes 2412.
One change I’m most thrilled about: MSI for Windows Endpoints AND and discovered: Physical Endpoint support!
App Volumes now supports MSI-wrapped VHD packages, alongside traditional VHD and VMDK formats. This allows the App Volumes agent to operate independently within existing delivery infrastructures such as Workspace ONE UEM, Microsoft Intune, and Microsoft Configuration Manager.
and with the parameters of the command line tool
Used with the /new appcapture.exe command to create the .msi format of the application package along with the .vmdk, .vhd, and .json output files.
The .msi is required when delivering App Volumes application packages to Windows endpoints (such as physical desktops, laptops, and Windows 365 Cloud PC) using device management tools such as Omnissa Workspace ONE UEM, Microsoft Intune, or Microsoft Configuration Manager (SCCM).
We had VMDK for native attach, VHD for in guest attach and now MSI for (offline) physical support!
How are we going to use this new MSI?
We are going to need 3 things:
1. The AppVolumes Agent
2. The Package
3. The Deployment
I will do a manual deployment but the best the way to deploy the AppVolumes agent and MSI to endpoints are endless, think Omnissa Workspace One UEM, Recast Application Workspace, Intune or any other solution you can deploy applications with… Up to you, you know how to do this 😉
The AppVolumes Agent
When installing the agent, you will see the newly branded Omnissa look and feel. The setup a simple next next finish, except you will get a new option: Configure agent without App Volumes Manager.
This is the option you need for physical. But how do I manage the package assignments? Well, that’s why you need, for example WSO UEM to deploy and assign the MSI. Out of scope for now.
Another thing to keep in mind is the directory where the components are installed has changed. It is now in the Omnissa directory. This might impact your Antivirus exclusions for example!
The Package:
App Volume Tools
To capture the package, you will need a package machine but not with the full agent installed, instead install the App Volumes Tools
The Capture
In this example I will create a new package, Need for Speed Underground
To start the capture and create the MSI besides a VHD and VMDK execute the command:
appcapture.exe /new %packagename% /msi
You can now make the changes needed to create a package. Install the application and do the changes needed for the package.
When done, simply enter the command
Appcapture.exe /endThe package will be created:
The package machine will automatically reboot and the default location for the packages is
%programdata%\Omnissa\Appvolumes\packagesThere are 4 files now. The json file and the three (msi, vhd, vmdk) files.
So how powerful is this?
With just one capture I have the package I can use for my entire environment.
Any other hypervisor (VHD)
physical and persistent like Laptops or Microsoft CloudPC (MSI)
The Deployment:
If you do this manually, it is nothing more than double clicking the MSI.
and wait for the install to finish:
After installing and looking in the Program and Features you will find the application:
Browsing to C:\ProgramData\Omnissa\AppVolumes\OfflineCache\%GUIDofthepackage% you will find the json and VHD file. So yes the package does work offline!
Going in to Disk Management you will see the VHD file is mounted.
Does it work?!
"Rum dum dum dududududu du dum dum.. to the windowwwwww to the wall... Get low.."
of course it does!
Deinstallation:
Most likely, your boss will not like Need for speed - Underground on your laptop so... just remove the app from "program and features" and it's gone! After next logoff of course... need to finish the race first.
Conclusion
Awesome job Omnissa! I think this will get big!
1 package to rule them all!
Some useful sources:
Using Appvolumes on Windows Endpoints:
Deliver Appvolumes to Windows Endpoints :
Install Command line program (AppVolumes Tools): https://docs.omnissa.com/bundle/AppVolumesInstallGuideV2412/page/InstallAppVolumesApplicationCaptureCommand-LineProgram.html
Capturing Appvolumes with command line Tools(AppVolumes Tools)
https://docs.omnissa.com/bundle/AppVolumesAdminGuideV2412/page/CaptureanAppVolumesApplication.html
Any questions, remarks, feedback? feel free to leave a comment!
I could see some use for this if it could use a network share (say E:\apps) instead of local drive of each user (C:\ProgramData\Omnissa\AppVolumes\OfflineCache), i.e. one slice of disk resources would be used instead of many. But maybe it's not possible?