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)

Restoring a secondary site server

As we cannot back up a secondary site, we need to recover a secondary site from a primary site. We can restore a secondary server from the Configuration Manager console. Right-click on the secondary site in Configuration Manager and choose Recover secondary site. Remember that there are a few of prerequisites that need to be in place in order to perform a successful restore:

  • The server to which we want to restore the secondary site server needs to have the same FQDN as the old server.

  • It needs to have the same security rights as the old server.

  • It should use the same installation path as the old server used.

  • It needs to have SQL Express installed before recovering. The SQL Express version needs to be the same as it was before and should have the same instance.