Support for deploying App-V packages
Right now people have to use the MSI packages generated by the App-V sequencer, rather than having native handling for the .AppV package format as SCCM does. This means that people have to resort to powershell scripting, or squeezing scripts into MST transforms in order to use App-V features such as custom configuration files or connection groups.
Also the MSI packages are very unreliable since they were mainly created for test scenarios rather than live deployments - for example they fail to uninstall when an application is in use, and you have to remove the previous version manually before installing a newer version. Native App-V integration would fix all of this!
Thom McKiernan commented
From my understanding you can now do this:
"MDM services can be used to publish App-V packages to clients running Windows 10, version 1703 (or later). All capabilities such as App-V enablement, configuration, and publishing can be completed using the EnterpriseAppVManagement CSP."
It would be good to know what success people have had with this
Any updates on this from Microsoft?
Roy Essers commented
No updates yet? App-V is a core compenent in the OS now... should it not be obvious to also support it in Intune?
Rob de Roos commented
We would love this option. Software distribution is a realy important issue at the moment for Intune MDM. App-V or Win32 application deployment is absolutely neccesary to have if we would like to roll out Intune more.
App-V on Windows 10 will only work on Windows 10 Enterprise! Well done Microsoft for making your product even more limiting!
Alan Dooley commented
Now App-V is baked into 1607 this is a must.
Stephen Leuthold commented
App-V is baked into the Windows 10 OS now. What is the status on native App-V support for Windows Intune?
Any way we could get a statement from the Intune team on this? This would be a huge value add for us the education market.