Book Image

Deploying Microsoft System Center Configuration Manager

By : Jacek Doktór, Paweł Jarosz
Book Image

Deploying Microsoft System Center Configuration Manager

By: Jacek Doktór, Paweł Jarosz

Overview of this book

It becomes important to plan, design, and deploy configurations when administrators know that Configuration Manager interacts with a number of infrastructure components such as Active Directory Domain Services, network protocols, Windows Server services, and so on. Via real-world-world deployment scenarios, this book will help you implement a single primary site or multiples sites. You will be able to efficiently plan and deploy a multiple-site hierarchy such as central administration site. Next, you will learn various methods to plan and deploy Configuration Manager clients, secure them and make the most of new features offered through ConfigMgr 1706 like compliance, deploying updates operating systems to the endpoints. Then, this book will show you how to install, configure, and run SQL reports to extract information. Lastly, you will also learn how to create and manage users access in an ConfigMgr environment By the end of this book, you will have learned to use the built-in mechanism to back up and restore data and also design maintenance plan.
Table of Contents (19 chapters)
Title Page
Credits
About the Authors
www.PacktPub.com
Customer Feedback
Preface
5
Creating Client Settings for Servers and Workstations
11
Configuration Manager Assets
13
Site Server Maintenance Tasks

Boundary and boundary groups


Boundaries and Boundary groups are very important configuration elements, as misconfiguration in this field will result in a lack of communication between clients and the server and the impossibility of deploying new clients. This part of configuration retains the same set of settings as it used in ConfigMgr 2007, with just one significant difference. Starting from ConfigMgr 1706, just after the server is installed, the default boundary group for ConfigMgr site is created. Each site has defined its own default boundary group.

In the case of a small deployment, or deployments with only one site, all clients can use only one boundary group. In the case of a larger number of endpoints or many locations, additional boundary groups will be configured to manage access to shares and client-server communication in a well-controlled manner.

The main objective of boundary groups is to tell clients about the server to which they have been assigned. Apart from that, they help...