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
Common HTTP Features
IP and Domain Restrictions
IIS Management Console
IIS Management Scripts and Tools
IIS 6 Management Compatibilty
IIS 6 Metabase Compatibility
IIS 6 WMI Compatibility
IIS 6 Scripting Tools
IIS 6 Management Console
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.