Book Image

Microsoft System Center Configuration Manager

By : Marius Sandbu
Book Image

Microsoft System Center Configuration Manager

By: Marius Sandbu

Overview of this book

Microsoft Configuration Manager is both extensive and complex, and for many, it is the primary tool for Enterprise management. With each new release, Configuration Manager continually proves itself to be the ultimate solution for managing both clients and mobile devices.This book covers in detailed and easy-to-understand steps how to set up highly available Configuration Manager roles and backend services such as SQL, DNS, and AD. You will learn how to plan for high availability, what kind of roles there are, and how they scale.The book starts by examining what needs to be taken into account when planning for high availability before moving on to focus on the different roles and how they can be set up. The book will also go through different scenarios as well as various backup and recovery procedures. You will learn how to identify bottlenecks within the different components and create sample design scenarios for high availability on Configuration Manager. The book will also look at the different high availability options and how to deploy them.
Table of Contents (12 chapters)

Site Server


The first and foremost important role that cannot be deployed as highly available is the Site Server role. It does not support network load balancing or other clustering features available in Windows Server. In order to make sure that you can restore the site in case of disaster, you have to use the built-in backup tasks. I will cover this in more detail in a later chapter.

Endpoint Protection

The Endpoint Protection role allows for management of endpoint protection agents.

If this role is unavailable for the clients, they will still continue to run as before but you cannot update the policy centrally. This role is not seen as critical for Configuration Manager and cannot be deployed as highly available. If something happens to your endpoint server, just reinstall the role on another server. It is important to know that this role can only be deployed once at the top of your hierarchy; so, if we have a CAS, we would place this role there. Same is true if we have a standalone primary...