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)

Backing up content

In order to perform a proper backup of the content library, we need to understand how the content library works in Configuration Manager 2012, which has been completely changed since 2007.

As shown in the following diagram, the content library is under the folder SCCMcontentlib (this folder is created on the disk with the most free space during setup):


If we want to move the content library from one drive to another, we can use the ContentLibraryTransfer.exe tool, which can be found on the toolkit for Configuration Manager Service Pack 1.

The content library consist of three folders: PkgLib, DataLib, and FileLib.

We have the PkgLib folder which contains a .ini file created with the ID name for each package. Each of the .ini file also contains a content ID to reference the data.

Then we have the DataLib folder, this contains a .ini file for each package and a folder for each package which contains each file in the source folder, these are just the signature hash files and...