Book Image

Microsoft System Center 2012 Endpoint Protection Cookbook

By : Andrew J Plue
Book Image

Microsoft System Center 2012 Endpoint Protection Cookbook

By: Andrew J Plue

Overview of this book

Microsoft System Center 2012 Endpoint Protection (previously known as Forefront Endpoint Protection 2012) protects client and server operating systems against threats with leading malware detection technologies. Built on Configuration Manager, it provides a unified infrastructure for client security and compliance management and "Microsoft System Center 2012 Endpoint Protection Cookbook" will help you get to grips with vital tasks for implementing this security tool. With the release of System Center 2012 Endpoint Protection, Microsoft is continuing its commitment to offering a cutting edge, enterprise- ready Anti-Virus solution. With its practical and easy to follow recipes, "Microsoft System Center 2012 Endpoint Protection Cookbook" fully prepares you for a simple, headache-free migration. This hands-on, practical cookbook will have you equipped with the knowledge to install and manage System Center 2012 Endpoint Protection like a pro in no time by following step by step recipes. You'll gain insight into a wide range of management tasks, such as building your SCEP infrastructure, deploying SCEP clients and building the perfect AV policies for your workstation and servers. You'll also benefit from a complete SCEP walk-through in a bonus appendix chapter. With "Microsoft System Center 2012 Endpoint Protection Cookbook" in hand, you will have the confidence to tackle essential tasks like deployment, policy and much more for SCEP.
Table of Contents (17 chapters)
Microsoft System Center 2012 Endpoint Protection Cookbook
Credits
About the Author
About the Reviewers
www.PacktPub.com
Preface
Index

Installing SCCM 2012 and SCEP in a standalone environment


Very few organizations would ever consider deploying something such as SCCM 2012 and SCEP in their production environment without kicking the tires first. Typically, what's done long before a decision is made to buy the product is something called a Proof of Concept (POC). During a POC, SCCM is installed in a lab environment that has its own AD domain and subnet.

It's always a good idea in the lab to have some workstations that are built off your corporate standardized image. This will allow you to deploy the SCCM and SCEP clients and give you the chance to verify that the clients are not going to adversely affect your applications or hamper the user experience.

Conducting a POC in a lab is not quite the same thing as building out SCCM and SCEP in a development environment; if you work for a medium to large-scale organization, a single SCCM server in a standalone primary site configuration would not be very representative of your production...