How to: Setup SCCM 2012 R2

I previously posted instructions on how to setup SCCM 2012, the first release. While this was a huge improvement on 2007, even more has changed and been improved upon since, with extended support and integration for App-V 5.0, managing clients on MACs, Linux, Android etc. In honesty this post may be a little bit overkill as not a whole lot has changed in the setup but I recognized this as an opportunity to clarify on certain aspects of the Setup. Also, there has been a couple of changes in the setup of the requirements e.g. installing the SDK, no need to extend the schema on Server 2012. So that’s where the value will likely come in this post.

So first, let’s cover the the pre-requisites required on your SCCM Server.

Configure your Server\Install your pre-requisites

On your SCCM Server you should Add the following roles: Windows Desktop Services, .Net Framework, WSUS, Remote Differential Compression, IIS, BITS and ADDS Snap-in Tools.


Static Content Compression

Health and Diagnostics

HTTP logging


Request Monitor

Common HTTP Features

HTTP Errors

HTTP Redirection

Basic Authentication

Windows Authentication

Static Content

Default Document

Request Filtering

Directory Browsing

HTTP Errors

HTTP Redirection

IP and Domain Restrictions


Management Tools

IIS Management Console

IIS Management Scripts and Tools

Management Service

IIS 6 Management Compatibilty

IIS 6 Metabase Compatibility

IIS 6 WMI Compatibility

IIS 6 Scripting Tools

IIS 6 Management Console

Application Development


.NET Extensibility


ISAPI Extensions

ISAPI Filters

On the server in question. If you use Windows Firewall you will need to set exception for port 1433 and 4022 as these are used by SCCM


You need to browse to ASDI Edit which should be on your server now. You need to connect to your SCCM server. You need to create a container called System Management. Navigate to the System Container and then create the System Management Container within. Next modify the security properties on the System container and ensure the SCCM Server itself has Full Control.

Continue reading


App-V 5.0 Integration with SCCM 2012

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.

Continue reading


Application Compatibility – Deployment – Part 6

There’s a few considerations when deploying your OS and the Applications. Firstly, in terms of planning you need to get yourself a deployment schedule. It’s a good idea to get a good pilot group early on with only a small number of applications and who represent non-Techie users. It’s also a good idea to get your Service Desk some Windows 7 secondary machines or VM’s in order to provide support for both environments as your roll out. Once you are satisfied with the results of your first pilot group you should move onto a second pilot with a more varied group of applications. The first pilot should be used for fleshing out your process and also verifying that the image is solid rather than stress testing your applications. IT teams are bad candidates to be early pilot users as they do not reflect the majority of your user base (assuming!!) When you have deemed your processes and image are equipped to handle the migration you can begin to roll out to a wider base and at a quicker rate. This may partly be dictated by the readiness of applications but you should also consider external variables. Some departments may have training scheduled or possibly peaks in productivity which means they can only migrate during certain intervals. All Departments and Upper Management types need to be consulted.

The number of machines which can be deployed in a fixed time would also be dictated by tools being used and hardware and network resources. Is Multicasting a possibility on your network, if so you don’t have to worry about saturating the network but you may want to try and benchmark test how long it will take to do 50-100 machines at once. If you are using Unicasting you should really consult with your network team for guidance on what your threshold should be.

You should also consider your help desk capacity to support these users in case your pilot failed to highlights some repeatetive questions that may come their way en masse or even possibly issues with Data missing or a corrupted deployment.

For application deployments through a Distribution Tool you should ensure the tool does not have anything set which may interfere with the applications being deployed to Windows 7 or later e.g. An Operating System check. Are any properties changed in your MSI’s just being over-rided by your Distribution Tool?

Deploying applications for Windows 7 has not really changed from Windows XP. You should just beware of the different possible gotchas as mentioned above. You will likely also use the same deployment tool to deploy your OS to the users. Be that with tools such as Marimba, SCCM, Altiris etc. Or perhaps, if you would like to go for a more cost effective solution for OS Deployment you might consider using WDS. For more on this you can read my post HERE

That completes this series for migrating to Windows 7. I hope this was informative and useful to anybody who may have been seeking information on this.

Thanks for reading,