This post is based on integration of App-V 5.0 SP2 with SCCM 2012 R2 but can also apply to integration of App-V 5.0 with SCCM 2012 SP1. I will have a How to further down but, usually I post a conclusion and give my own perspective on things but considering I have covered quite a lot about App-V on my blog, I felt like posting this first for those I know who are familiar with App-V and don’t necessarily want to see the How to. So let me give a little of my own experience and insights with App-V 5.0 integration with SCCM 2012. I really was not a fan of App-V integration in SCCM 2007, in fact I am not much of a fan of SCCM 2007 in general! But SCCM 2012 is worlds apart from 2007, I really love it. I have used several Distribution tools in my short career but this is by far the most powerful and to me, most enjoyable to use. The fact it has a much better integration with App-V draws me in even more.
Why is it a good idea to use App-V 5.0 with SCCM 2012?
You get extra benefits when deploying your virtual applications through SCCM, a major coup is the ability to use the ‘Requirements’ section of the Deployment Type settings, this just like with a traditional application deployment, it allows you to set criteria for a deployment e.g. only deploy to machines with a certain amount of RAM, Disk space and lots more! Another great benefit is the virtual environments. There’s an option for you to create virtual environments which are basically a group of App-V Applications which have been imported into SCCM. These application are essentially set to allow visibility of one another. It’s as simple to use as clicking Add and picking which applications should be in the ‘group’. You can then set the priority of the applications, which should be the primary applications, which is secondary etc. This is like Connection Groups only even more straight forward and powerful.
If you’ve already got SCCM 2012 in your environment, you’ll have your back-end already configured complete with your Distribution points. Well, that’s all you need even for streaming as SCCM 2012 allows you to stream your applications from your DP’s. You also have the option of Download and Execute which will ensure the applications are cached on delivery versus on demand when the user launches the application. A reason why you may prefer that method is if you have a large set of users who work offline a lot and may be likely to not have the ability to stream.
How do I integrate App-V 5.0 with SCCM 2012?
First things first, When deploying App-V applications using SCCM, you still need to ensure the App-V Client is deployed to your end user devices. Note that the SCCM Client is used to deploy the advertisement and to control the App-V Client, it doesn’t completely replace the App-V Client.