For the past several weeks I have been working in development on a project to implement both Microsoft’s System Center Configuration Manger 2012 (SCCM 2012) and their new Anti-virus solution Microsoft System Center Endpoint Protection 2012 (SCEP 2012).

I used a combination of Microsoft’s official System Center documentation and the help of several independent blogs across the web. The SCCM blogs have been especially helpful to me in my endeavor and I hope that the information that I present will be helpful to someone as well.

As the project has unfolded, I have been taking detailed notes with screenshots on the configuration so that this can be transitioned to our production environment in a smooth fashion.

Here are some things that are specific to my SCCM implementation:

– Management Point (MP) and Clients will communicate via HTTPS
– This will be a Primary Standalone configuration with a backend SQL server
– This will be for servers only, no mobile clients or desktop based systems

We want to secure the communication on our network between the MP and clients to ensure we comply with security regulations. This will be a Primary Standalone as there is only one datacenter involved in this deployment, so this is the best choice for our scenario.

Due to the complexity involved in a SCCM deployment, I will be breaking up the project into several different sections. Here are the sections for reference:

Part I – Pre-Configuration
Part II – Certificate Configuration
Part III – Installation
Part IV – Hierarchy Configuration
Part V – System Configuration – Security and Roles
Part VI – System Center Endpoint Protection Manager Role and Agent Configuration
Part VII – Client Initialization, Reporting, and Closing Thoughts

As of 09/17/2012 the Blog Series on Configuration Manager 2012 and Endpoint Protection 2012 is now feature complete!

System Center Configuration Manager and Endpoint Protection Manager 2012
%d bloggers like this: