App-V 5.0 Sequencing Decision Matrix
Below is a potentially helpful decision chart for considerations when choosing to have an App-V package vs. keeping an application native (local install). I had originally created it in October 2013 for my webcast with BDNA. But since that time, an even better flowchart has been created by Rory Monaghan, that I encourage you to visit review on his blog at http://rorymon.com/blog/?p=174.
Criteria |
App-V 5.0 SP2 |
Native Application |
DCOM Objects | Minimal or unused | Critical functionality |
Integration points with other applications | Minimal or if there is not time/resource restraints | If complex or if there are time/resource restraints |
Application installed size | Less than 4 GB | Greater than 4 GB |
Drivers | If drivers are not required at system boot, and have an automated install mechanism. | If drivers are required at system boot, or has complex driver automation |
Application requires updated versions frequently | App-V application when users do not have the ability to update themselves | Native application when users have the ability to update themselves |
Application compatibility fixes necessary | Successful bundling of a shim within the App-V package | Not successful bundling of the shim within App-V package |
Services | Normal services that run in their own process and are not required at system boot | Shared services that run inside svchost.exe or are required at system boot |
Middleware | Middleware application that is only required by other virtualized apps | Middleware application that is required by both native and virtualized apps |
Licensing | Single license can be embedded or added later | Multiple licenses that can only be used at install time |
Vendor support for the application virtualized | If yes or if low risk | If no and risk cannot be taken |
Multiple versions of application to be used | Yes if other App-V have been criteria met | Possible if no conflicts between multiple versions at once |
Conflicts between multiple versions of applications | Yes if other App-V have been criteria met | N/a |
Shell Extensions | Yes if other App-V have been criteria met | When App-V criteria cannot be met |
Compatibility issues with other applications | Yes if other App-V have been criteria met | N/a |
January 26, 2014 at 12:00 pm
[…] As a table/graph – https://t3chn1ck.wordpress.com/2014/01/26/app-v-5-0-sequencing-decision-matrix/ […]
February 14, 2014 at 11:28 am
You can sequence apps that are larger than 4GB with App-V 5.0. Do you just not recommend it?
February 15, 2014 at 11:54 am
Rory, that is a good observation, thanks for pointing that out. I compiled this list based upon past information and/or experience. For the package size, I’ve had both success and complications with some packages that were between the 4-5 GB mark. So you’re right in that it’s not a hard limit and could certainly work.