Microsoft Official Course

Trainer: Binduraj
10747-D /10748-C
SCCM 2012 R2 SP1
Deploying & Administering
System Center 2012 R2
Configuration Manager
 Introduction
Binduraj
MCSE 2000, MCSA 2012, MCT
CCNA
RHCT
Microsoft Trainings
Windows Server 2003 / 2008 R2 / 2012 R2
Active Directory 2003 / 2008 R2 / 2012 R2
Exchange Server 2003 /2007/2010 /2013 /2016
SCCM 2007 /2012 R2 /1511/1602
SCVMM R2 / HyperV
PowerShell 1.0 /2.0 /3.0 /4.0

Binduraj
Microsoft Learning

Course
Course 10747
10747 D:
D: Administering
Administering System
System Center
Center
2012
2012 Configuration
Configuration Manager
Manager

Course
Course 10748
10748 C:
C: Deploying
Deploying System
System Center
Center
2012
2012 Configuration
Configuration Manager
Manager

http://www.microsoft.com/learning/
Microsoft Certification Program

Exam number Core exam for the following

and title track
70-243: Microsoft System Center
2012 Configuration Manager, Certification track: TS
Configuring

http://www.microsoft.com/learning/
 Course Outline
 Module 1: Overview of Microsoft System Center 2012 R2
Configuration Manager
 Module 4: Managing the Configuration Manager
Client
 Overview of the System Center 2012 Family of Products  Overview of the Configuration Manager Client /Supported
 Benefits of Implementing System Center 2012 Configuration Clients
Manager in an Organization  Deploying Configuration Manager Clients /Overview of the
 Overview of the Configuration Manager 2012 Hierarchy Client Installation Process
 What Is a Central /Primary / Secondary Site?  Client Push/Software Update Point/Group
Policy/Manual/Logon Script/Software Distribution
 Configuration Manager Site System Roles
 Managing Client Agents
 How Data Flows and Replicates in a Hierarchy
 Configuring and Monitoring Client Status
 Monitoring Site and Component Status
 Managing Components by Using Configuration Manager
 Module 5: Managing Inventory and Software
Service Manager Metering
 What Are Configuration Manager Log Files?  Overview of Inventory Collection
 Module 2: Planning and Deploying a Stand-Alone Primary  Configuring Hardware /software Inventory
Site  Managing Inventory Collection/Initiating Inventory Cycle
on a Client/Viewing Inventory Results
 Planning a System Center 2012 Configuration Manager  Configuring Asset Intelligence/Software Metering
Stand-Alone Primary Site Deployment
 Troubleshooting Inventory Collection
 Extending the Active Directory Schema
 Module 6: Querying and Reporting Data
 Installing a Configuration Manager 2012 Site Server
 Introduction to Queries
 Performing Post-Setup Configuration Tasks /Verifying the
Installation/Status Messages/Configuring Boundaries and  Managing Queries
Boundary Groups/Installing site System Roles  Overview of SQL Server Reporting Services /Prerequisites
 Module 3: Discovering and Organizing Resources for Configuration Manager Reporting /Configuring SQL
Server Reporting Services / Report Subscriptions
 What Is Resource Discovery?  Module 7: Managing Software Deployments by Using
 Overview of Discovery Methods Packages and Programs
 Active Directory® Discovery Methods/Network  Configuring Software Distribution /Software Distribution
Discovery/Heartbeat Discovery? Concepts
 Overview of Client Assignment  Configuring Packages and Programs
 Overview of User and Device Collections  Distributing Content to Distribution Points
 Maintenance Windows  Deploying Programs to Configuration Manager Clients
 Overview of Role-Based Administration /Reports on RBA
 Course Outline  Module 11: Managing Operating System Deployment
 Module 8: Creating and Deploying Applications  Overview of Operating System Deployment /Operating
System Deployment Terminology
 Overview of the Configuration Manager Application  Preparing the Site for Operating System Deployment
Model
 Overview of Operating System Deployment Scenarios
 Applications vs. Packages
 Bare-Metal/In-place upgrade/Operating system refresh/side-
 What Is Software Center? by-side migration
 Creating Applications  Capturing an Operating System Image
 Deploying an Application to a User or a Device  Module 12: Implementing Endpoint Protection in
 Configuring the Application Catalog Configuration Manager 2012
 Module 9: Managing Application Deployment  Overview of Endpoint Protection in Configuration Manager
 Configuring Requirements and Dependencies for
 Prerequisites for the Endpoint Protection Feature
Deployment Types  Configuring and Monitoring Endpoint Protection Policies
 Configuring Multiple Deployment Types and User Device  Client Settings for Endpoint Protection
Affinity  Module 13: Managing Compliance Settings
 Simulated Deployment  Overview of Compliance Settings
 Retiring / Uninstalling Applications /Application
Supersedence
 Configuring Compliance Settings - CI/CB/CP
 Viewing Compliance Results
 Module 10: Deploying and Managing Software
Updates  Configuring Remediation

 Overview of Software Updates /Prerequisites for the

 Module 14: Managing Mobile Devices Without Intune
Software Updates Feature  Processes used to manage Internet-based clients
 Synchronizing the Software Update Catalog Metadata  Configuring PKI for Configuration Manager
 Preparing the Configuration Manager Site for Software  Creating Certificate Templates for ConfigMgr
Updates
 Deploying Certificates for Configuration Manager
 Managing Software Updates
 Preparing the Infrastructure for Mobile Device Management
 Creating Software Update Groups and Deployment
Packages  Enrolling a Mobile Device
 Sort, filter, or search the All Software Updates list  Managing Compliance Settings for a Mobile Device
 Software Updates Reports  Configuring Mobile Device Management
 Monitoring and Troubleshooting Software Updates  Deploying Applications to Mobile Devices
Course Outline
 Module 15: Configuring Wake On LAN, Power Management, and Remote Control
 Configuring Wake On LAN
 Benefits of Wake On LAN/Methods for Transmitting Wake-up Packets/Prerequisites for Implementing Wake On LAN
 Overview of Out of Band Management
 Configuring Power Management Settings
 Configuring Remote Control/Auditing Remote Access
Introduction
• Name
• Company affiliation
• Title/function
• Job responsibility
• Network administration, help desk, system administration
experience
• Microsoft System Center Configuration Manager
experience
• Current or planned use of Configuration Manager
• Your expectations for the course
Introduction to Adatum, Ltd
• In the labs throughout this course, you will work for
Adatum, Ltd.
• As you complete the labs, you will configure and maintain
a System Center 2012 Configuration Manager
environment to provide a complete systems management
solution for your organization.
 Virtual Machine Environment
Virtual machine Used as:
Domain Controller for the adatum.com domain. Contains
the following:
DC  Active Directory Domain Services
 DNS
 Active Directory Certificate Services
Configuration Manager primary site
CM  System Center 2012 Configuration Manager
 Microsoft SQL Server 2012
SVR1 Server in the adatum.com domain

C1 Client computer with Windows 8.1

C2 Client computer with Windows 7 SP1

Reference Computer – To Capture OS Image

Master
Microsoft Official Course
®

Module 1

Overview of System Center 2012 R2

Configuration Manager
Module Overview

Introduction to System Center 2012 R2 Configuration

Manager
Overview of the System Center 2012 R2 Configuration
Manager Architecture
Managing Configuration Manager by Using Configuration
Manager Administration Tools
• Using Tools for Monitoring and Troubleshooting a
Configuration Manager Site
Overview of the System Center 2012 Environment

Configuration Manager

Manage clients on
the organizational
network and the Internet

Single admin console

Configuration Manager Admin Console
 Overview of System Center 2012 R2
Configuration Manager
Asset Change Administrative
management management features

Hardware and Application Compliance Role-Based

Software Management Settings Administration
Inventory

Software Update Power Remote

Asset Intelligence Management Management Management

Client
Health Reporting
Software Metering Operating System
Deployment
Endpoint
Protection Monitoring
Content
Management
 Overview of Configuration Manager 2012 Site
System Roles
Default Site System Roles
Core Roles Default Optional Roles
• Site server • SMS Provider • Management point
• Component server • Site database • Distribution point
• Site system server

Optional Site System Roles New Roles

• Asset Intelligence • Application Catalog website
synchronization point point
• Fallback status point • Application Catalog web service
• Out of Band service point point
• Reporting services point • Enrollment point
• Software update point • Enrollment proxy point
• State migration point • Endpoint protection point
• System health validator point
 Site Server
• The Configuration Manager
site roles created when
Configuration Manager is
installed are:
 Site server – core
Configuration Manager
functionality
 Component server– any
server hosting the SMS
Executive service
 Site system– any server
hosting a role
• Only the site system role
has configurable properties
Site Database
Site Database Server
• All Configuration Manager sites have a server hosting the site
database role
• The site database role:
• Runs on SQL Server
• Can be a default instance or a named instance
• Can be an clustered SQL Server
• The site database server role can be moved using site maintenance
• Secondary sites use SQL Server Express by default

SMS Provider
• The SMS Provider is the interface between the Configuration
Manager console and the site database
• During Configuration Manager installation, you specify a server
where to install the SMS Provider role
• The SMS Provider role cannot be installed on a clustered SQL Server
• The SMS Provider role can be moved using site maintenance
Management Point
• Provides policy and
content location
information to
clients
• Receives data from
clients
• Each primary and
secondary site must
contain at least one
management point
• Can be configured to
use HTTP or HTTPS
Distribution Point
• Contains package source
files, operating system
images, and patches
• Can be configured to use
HTTP or HTTPS
• Now includes the PXE and
Multicast functionality
• Can be included in
Distribution Point Groups
to manage content
distribution
• Can be associated with
one or more boundary
groups
Lesson 3: Overview of the Configuration
Manager 2012 Optional Site System Roles
• Application Catalog
• Asset Intelligence Synchronization Point
• Endpoint Protection Point
• Enrollment Point and Enrollment Proxy Point
• Fallback Status Point
• Out of Band Service Point
• Reporting Services Point
• Software Update Point
• State Migration Point
• System Health Validator Point
• Planning for Role Placement
Application Catalog
Application catalog is
implemented using two
roles:
1. Application Catalog
web service point
 Provides software
information from the
software library
2. Application Catalog
website point
 Web interface for end
users
• Both roles can be
configured for HTTP or
HTTPS
Asset Intelligence Synchronization Point
• Can be installed only at the
top of a hierarchy on a
central administration site
or stand-alone primary site
• Synchronizes asset
information with System
Center online
• Data generated from asset
intelligence is used to
create reports about:
 Software families
 Software categories
 Specific software titles
• Asset intelligence
information is viewed in
reports
Endpoint Protection Point
• Can be installed only on a
central administration site
or Stand-alone Primary site
• You must accept a separate
license agreement when
installing
• You can choose your level
of participation with the
Microsoft Active Protection
Service:
 No Participation
 Basic membership
 Advanced Membership
Enrollment Point and Enrollment Proxy Point
• Provide mobile device
depth management
functionality
 The enrollment point
processes requests and
interacts with the
Configuration Manager
database
 The enrollment proxy
point receives mobile
device enrollment
requests and forwards
them to the enrollment
point for processing
• The mobile device then
downloads the client from
the enrollment proxy
point
Fallback Status Point
• Fallback status point:

 Used by CCMSetup to
send state messages to
the site server during
client installation
 Uses only HTTP
• Clients can send state
messages when they
cannot connect to a
management point
Out of Band Service Point
• Out of band management
allows the management
of computers that have
the Intel vPro chipset and
have a supported version
of Intel AMT
• Before adding the out of
band service point to a
site server, you must
install a certificate that
supports AMT Provisioning
Reporting Services Point
• Is installed on a server
running the Microsoft SQL
Server Reporting Services
(SSRS)
• Provides tools and
resources to use the
advanced reporting
capabilities of SSRS
• New reports can be created
using the Reporting
Services Report Builder
Planning for Reporting Services
• Is installed on a server
running SSRS
• Provides tools and
resources to use the
advanced reporting
capabilities of SSRS
• New reports can be
created by using the
Reporting Services
Report Builder
• System Center 2012 R2
Configuration Manager
supports role-based
administration for reports
Software Update Point
• WSUS 3.0 or above must be
installed on the site system
that will host the Software
Update point
• You can install one software
update point per site
• Install the software update
point in the central
administration site first
• Install the software update
points in each child and
secondary site
• Each secondary site should
synchronize with its parent
• The CAS should synchronize
with Microsoft Update
Planning Roles for Operating System Deployment
State Migration Point
• A state migration point
is used for the side-by-
side operating system
deployment scenario
• The in place upgrade
scenario can use the
state migration point
or local storage
• You can install multiple
state migration points
to support the
deployment process
System Health Validator Point
• The system health
validator point works in
conjunction with a
Network Access Protection
server to monitor client
health
• A system health validator
point must be installed on
a Network Access
protection server
• The system health
validator point will
periodically query the
network access protection
server for health state
references
Overview of Role Placement

• When planning a hierarchy, you must consider limits on

role placement
• In a stand-alone primary site hierarchy, you can install
all roles on either the site server or separate servers
• In a multiple primary site hierarchy, there are limits to
where you can install a role. For example:
• The central administration site does not support any of the
client management roles
• Primary sites do not support the Asset Intelligence
synchronization role when they are part of a hierarchy
• Secondary sites do not support installing any roles to other
servers, except the distribution point role
Benefits of Implementing System Center 2012
Configuration Manager in an Organization

Key Benefits of Configuration Manager 2012

• Empower user productivity

• Using the application catalog to allow users to
request software when they need it
• Unify management and security infrastructure
• Compliance settings allows you to ensure your
clients are configured in a secure manner
• Simplify IT administration
• Provides a unified infrastructure that gives a
single pane of glass to manage physical,
virtual, and mobile clients
New Features Provided with an Installation of
System Center 2012 R2 Configuration Manager
• Support for clients that run Windows 8, Windows 8.1,
Windows RT, Windows 8.1 RT, iOS, Mac OS X, and Android
• Support for Windows Server 2012 and Windows Server
2012 R2 to host site system roles
• Support for SQL Server 2012 to host Configuration
Manager databases
• Support for merging of System Center 2012 R2
Configuration Manager hierarchies
• Bulk reassignment of clients to alternate primary sites
• Configuration Manager Windows PowerShell cmdlets
Lesson 2: Overview of the System Center
2012 Configuration Manager Architecture
• Overview of the Configuration Manager 2012 Hierarchy
• What Is a Central Administration Site?
• What Is a Primary Site?
• What Is a Secondary Site?
• Configuration Manager Site System Roles
• How Data Flows and Replicates in a Hierarchy
Sites and Hierarchies
Single primary site Multiple primary sites in a
hierarchy
Central
Administration
Site

Primary
Site Primary Primary
Site Site

Secondary
Site

Secondary
Site
 Overview of the System Center 2012 R2
Configuration Manager Hierarchy
Central administration site SQL database

Primary site Primary site Primary site

SQL database SQL database SQL database

Secondary • Each site is identified by a unique three-character code
site
• The central administration site is for reporting and
management only
• Primary sites can be parents of secondary sites only
SQL • Secondary sites now have their own database
database
What Is a Central Administration Site?

A central administration site:

• Is required to use a multi-site hierarchy

• Must be the first site built if you use a multi-site hierarchy
• Is used for administration and reporting
• Requires a SQL database
• Does not process client data
• Does not support client assignment
• Has a limited number of site system roles
What Is a Primary Site?

To
To use
use Configuration
Configuration Manager,
Manager, you
you must
must have
have at
at least
least one
one
primary
primary site
site

Primary sites:

• Can be in a child relationship to a Central Administration site,

which can only be set during installation
• Cannot be a child to another primary site
• Manage clients in well-connected networks
• Require a SQL database
• Replicate their data to a Central Administration site if part of a
hierarchy
• Supports client assignment
• Consist of one or more systems hosting various site system roles
What Is a Secondary Site?

A secondary site:

• Is optional
• Must be in a child relationship to a primary site, which is set in the
secondary site during installation
• Is used when network bandwidth usage needs to be controlled
• Requires SQL Server Express or a SQL Server database to store
configuration information
• Replicates its collected client data to its parent site using file-
based replication
• Does not support client assignment
• Consists of one or more systems hosting various site system roles
Overview of Configuration Manager Sites
Install a central administration site to:

• Install multiple primary sites in a hierarchy

• Configure hierarchy-wide settings
• Manage all sites and objects in the hierarchy

Install multiple primary sites to:

• Increase the number of clients to manage

• Provide local connectivity for administration
consoles
• Independently manage content

Install a secondary site to:

• Manage the transfer of client data up the hierarchy
• Manage the transfer of content down the hierarchy
• Provide some site functionality for a remote site
Alternatives to Using a Secondary Site
Client to Primary site to secondary site
management point • Send global data, client policy
• Get policy • Get client inventory, state
• Send inventory, state • Distribute content

Client to Primary site to

distribution point distribution point
• Get content • Distribute content

Primary Primary
Site Site

Distribute Distribute
content content

Download policy Get policy Distribution

point
Upload client data Send inventory
Secondary and state
Site

Using
Using a
a secondary
secondary site
site Using
Using a
a distribution
distribution point
point
Considerations for Implementing Configuration
Manager Sites
Install a stand-alone primary site when you have:

• A centralized administration approach

• No more than 100,000 clients

Install secondary sites when you want:

• To offload the client communication from the primary site
• To provide tiered content routing between secondary sites with
the same parent

Install multiple primary sites in a hierarchy when you have:

• More clients than can be managed using a single primary site

• Multiple administrative teams that require local connectivity for
the Configuration Manager consoles
• A large number of remote locations
Planning a Multiple-Site Hierarchy
A central administration site:
• Supports up to 25 child primary sites
• Supports up to 400,000 clients in the hierarchy when using SQL Server
Enterprise for the site database
• Supports up to 50,000 clients in the hierarchy when using SQL Server
Standard for the site database

A primary site:
• Supports up to 250 secondary sites
• Supports up to 250 distribution points
• Supports up to 10 management points
• Supports up to 50,000 clients when SQL Server is on the site server
• Supports up to 100,000 clients when SQL Server is on a separate computer

A secondary site:
• Supports up to 250 distribution points
• Supports a single management point located on site server
• Supports communications from up to 5,000 clients
What Are Global and Site Data Types?
Global data is created by the administrator
• Includes collection rules, package metadata, software update
metadata, deployments, security scopes, and other objects
• Replicates to central administration site, all primary sites, and
secondary sites (subset of global data) using SQL replication

Site data is generated by the site systems and clients

• Includes collection members, hardware inventory, status
messages, and alert messages
• Found in the original primary site
• Replicates using SQL replication to central administration site

Content is replicated between sites using file-based replication

• Includes package content (such as software packages,

software updates, boot images, and operating system images)
• Found on primary sites, secondary sites, and distribution points
How Data Replicates Throughout the Hierarchy

•• SQL
SQL Replication
Replication is
is automatically
automatically configured
configured at
at installation
installation
•• Secondary
Secondary sites
sites receive
receive a
a subset
subset of
of global
global data
data

Global
Global data
data is
is configuration
configuration Site
Site data
data is
is operational
operational
information
information information
information

Central Administration Site

Primary
Primary Site
Site

Secondary
Secondary Site
Site

Parent-child
file-based replication

Secondary-to-secondary
file-based replication
 Implementing Configuration Manager 2012 for a
Global Organization
Example of a complex hierarchy implementation:

Central Administration Site

Primary
sites

Remote
Secondary Distribution
sites Point
Configuration Manager in a Global Organization

Example of a complex hierarchy implementation:

Central Administration Site

Primary Sites

Remote
Secondary Distribution Point
Sites
How Data Flows and Replicates in a Hierarchy
Central Administration
Site
Primary
Site Global Data
Primary
Site
Secondary Site Data
Site

Global data Site data

• Alert rules • Alert messages
• Client discovery • Asset intelligence CAL tracking
• Collections rules and count • Client Health data
• Configuration items metadata • Client Health history
• Deployments • Collection membership results
• Operating system images • Component and Site Status
• Package metadata Summarizers
• Program metadata • Hardware inventory
• Site control file • Software distribution status details
• Site security objects • Software inventory and metering
• Software updates metadata • Software updates site data
• System resource list • Status messages
How Configuration Manager Integrates with
Cloud Services
• Manage mobile devices by
integrating Configuration Manager
with Windows Intune:
• Supports Windows 8.1, Windows Phone 8,
iOS, and Android
• Enroll device, wipe device, install LOB apps

• Windows Azure supports cloud

distribution points:
• Support intranet and Internet-based clients
• Functions as fallback content location
• Content sent to cloud-based distribution
point is encrypted before being sent to
Windows Azure
Introduction to Deployment Scenarios
Determine the number of sites by identifying:
• Network infrastructure for Configuration Manager 2012
• Business requirements for Configuration Manager 2012
• Migration requirements from Configuration Manager 2007 to
Configuration Manager 2012
• The number of clients that need to be managed and their
locations
• The following characteristics of your organization:
• The AD DS forest structure
• The number of physical locations
• Available bandwidth between locations
• The location(s) of your IT support
staff
• The number of remote clients
Implementing Configuration Manager 2012
for a Small-to-Medium Organization

A single primary site typically includes:

Software
Software
• Site server Update
Update Site
Site
Point
Point Server
Server
• Site database Site
Site
• Management point Database
Database
• Distribution point
• Reporting services point
• Software update point
• Fallback status point
• Other roles as required
Implementing Configuration Manager 2012 for a
Medium-to-Large Organization
A primary site typically includes:
Software
• Site server Update Point Site Server
Site
• Site database Database
• Management point
• Distribution point
• Reporting services point
• Software update point
• Fallback status point
• Other roles as required

Secondary Remote
Secondary sites include: Site Server Distribution
Point

• Management point
• Distribution point
SCCM 2012
Quick overview
Infrastruct
Hierarchy Applicatio
ure
changes n Model Changes
●
One type of distribution point
●
New central administration site No more branch DPs
●
Rethink the way software is delivered ●
●
Should be first site created ●
Pull DP
●
Designed to be user-targeted (User
●
Can be added later (No in RTM Possible ●
Cloud DP
Device Affinity)
with SP1) ●
PXE is a property of the DP, more scalable
●
Supports dependencies, supersedence,
●
One level of primaries ●
Server 2003 and later, Vista SP2 and later
requirements, detection, uninstall
●
One level of secondaries (x86 and x64)
●
Multiple deployment types, depending
●
Settings and security don’t need to be ●
Single instance content library
on the situation
defined at the site level ●
WebDAV no longer used
●
Standard install, App-V, etc.
●
Can be more granular ●
Target the app, let ConfigMgr pick the Site servers are 64-bit only (except DP)
●
Replication uses SQL instead of inboxes ●

deployment type ●
New console
●
Secondaries need SQL ●
Software Catalog for self-service ●
New DCM “Set” capability
●
Boundaries need to be grouped ●
Old-style ●
Remote control with Ctl-Alt-Del
●
Multiple types too (content vs. client
package/program/advertisement can ●
SQL Reporting only
assignment)
still be used, but should be transitioned ●
GUI-based inventory config
●
Collections are global ●
No more SMS_DEF.MOF
 Module 2
Planning and Deploying a
Stand-Alone Primary Site
Module Overview
• Planning a System Center 2012 Configuration Manager
Stand-Alone Primary Site Deployment
• Preparing to Deploy a Configuration Manager 2012
Primary Site Deployment
• Installing a Configuration Manager 2012 Site Server
• Performing Post-Setup Configuration Tasks
• Tools for Monitoring and Troubleshooting a Configuration
Manager 2012 Installation
Lesson 1: Planning a System Center 2012 Configuration
Manager Stand-Alone Primary Site Deployment

• Overview of Planning Tasks for a Configuration Manager

2012 Primary Site Deployment
• Planning a Configuration Manager 2012 Stand-Alone
Primary Site Deployment 
• Site Naming Conventions
• Client Communication Modes
• Discussion: Planning a Configuration Manager 2012
Stand-Alone Primary Site Deployment
Overview of Planning Tasks for a Configuration
Manager 2012 Primary Site Deployment

Task Description

Document your
• Identify and document network locations
and link speeds
network and computing
environment
• Determine the number of clients to be
managed
• Identify the Configuration Manager features
Identify business that will be used
requirements • Document administrative, user, and
security requirements
• Identify the number of sites to be installed
Design site architecture
• Identify the site system roles to be
installed
• Determine the site system configuration
• Identify the need to restructure the
Identify migration Configuration Manager hierarchy
requirements • Identify objects to migrate
• Identify sites and clients to migrate
 Planning a Configuration Manager 2012 Stand-
Alone Primary Site Deployment

A stand-alone primary site

typically includes the
following roles:
• Site server
• Site Server • Site database
• Management Point
• Distribution Point • Site Database
• Fallback Status Point • Reporting Services Point • Management point
• Distribution point
• Reporting services point
• Software update point
• Fallback status point

A
A stand-alone
stand-alone primary
primary site
site can
can span
span
multiple
multiple servers
servers and
and network
network locations
locations
Site Naming Conventions

Site code

• Three-letter code used to identify the site

• Must be unique in the hierarchy
• Cannot be changed after installation

Site name

• Text string used to describe the site for the

administrator
• Cannot be changed after installation
 Client Communication Modes

Configuration Manager 2007 Configuration Manager 2012

Site mode Client communication modes
Modes can be configured individually
for each role:
• Configured at the site level
• Management point
• All site roles use the same
• Distribution point
mode
• Software update point
• State migration point
Available modes: Available modes:
• Mixed • HTTP
• Native • HTTPS
• Can use self-signed certificates
Native mode requires PKI and
when communicating over HTTP
special templates to be
• PKI-issued certificates are required
configured
for HTTPS communication
Lesson 2: Preparing to Deploy a Configuration
Manager 2012 Primary Site Deployment

• Extending the Active Directory Schema

• Demonstration: Extending the Active Directory Schema
• Site Server and Site Database Requirements
• Site System Roles Requirements
• Installing and Configuring Prerequisites
• What Is Prerequisite Checker?
• Demonstration: Installing and Configuring Operating
System Prerequisites
Extending the Active Directory Schema

Configuration
Configuration Manager
Manager 2012
2012 uses
uses the
the same
same classes
classes and
and
attributes
attributes as
as Configuration
Configuration Manager
Manager 2007
2007

• Objects published by site systems in AD DS are used for:

• Client installation and automatic site assignment
• Port configuration for client-to-server communication
• Network Access Protection

• After extending the Active Directory schema, you must create

and configure a System Management container either by:
• Using ADSIEdit to create the container and then granting the
site server full control permission on the System
Management container and all descendant objects
• Granting the site server full control permission on the
System container and all descendant objects and letting the
site server create the System Management container
automatically
Demonstration: Extending the Active
Directory Schema
In this demonstration, you will see how to:
• Use EXTADSCH to extend the Active Directory schema
• Create the System Management container by using
ADSIEDIT
• Assign Full Control permissions for the site server to the
System Management container
Site Server and Site Database Requirements

Site Server Site Database

• Windows Server 2008 x64 • SQL Server 2008 with SP2 and
Standard, Enterprise, and Cumulative Update 9
Datacenter • SQL Server 2008 with SP3 and
• Windows Server 2008 R2 Cumulative Update 4
Standard, Enterprise, and • SQL Server 2008 R2 with SP1 and
Datacenter Cumulative Update 6
• Windows Server 2012 Standard • SQL Server 2012
or Datacenter • SQL Server 2012 SP1
• Windows Server 2012 R2
Standard or Datacenter
Site System Roles Requirements

Management Point Requirements

Hardware Requirements Recommended

Processor 4 cores Intel Xeon
2.0 GHz or faster
Memory 8 GB
Free disk space 50 GB

Distribution Point Requirements

Hardware Requirements Recommended

Processor 2 cores Intel Xeon
2.0 GHz or faster
Memory 8 GB
Free disk space As needed to store content
Prerequisites for Installing and Configuring
Configuration Manager

• .NET Framework 3.5

• .NET Framework 4.5
• BITS
• Remote differential compression
• Additional prerequisites for specific roles include:
• WDS – PXE enabled distribution points
• WSUS – software update point
• Windows Automated Installation Kit – SMS providers
running System Center 2012 Configuration Manager
• Windows ADK – site servers running SP1 and R2
What Is Prerequisite Checker?

Prerequisite
Prerequisite Checker
Checker is
is a
a tool
tool that
that verifies
verifies
server
server readiness
readiness to
to host
host a
a specific
specific site
site system
system role
role

Prerequisite Checker:

• Is now a stand-alone application (prereqchk.exe)

• Can be used to validate prerequisites for:
• Site server
• Database server
• SMS provider
• Management point
• Distribution point
Demonstration: Installing and Configuring
Operating System Prerequisites

In this demonstration, you will see how to use Server

Manager to review the prerequisites for installing System
Center 2012 Configuration Manager
Lesson 3: Installing a Configuration Manager
2012 Site Server
• The Configuration Manager 2012 Setup Process
• Configuration Manager 2012 Setup Options
• Demonstration: Installing a Configuration Manager 2012
Primary Site
 The Configuration Manager 2012 Setup
Process
Configuration Manager Setup steps:
1. Getting Started
2. Product Key
3. Microsoft Software License Terms
4. Prerequisite Licenses
5. Prerequisite Downloads
6. Server Language Selection
7. Client Language Selection
8. Site and Installation Settings
9. Primary Site Installation
10. Database Information
11. SMS Provider Settings
12. Client Computer Communication
Settings
13. Site System Roles
14. Customer Experience
Improvement Program
Configuration
15. Settings Summary
16. Prerequisite Check
Configuration Manager 2012 Setup Options
• The Configuration Manager 2012 Setup Wizard allows you to:
 Install a Configuration Manager primary site server
 Install a Configuration Manager central administration site
 Upgrade an existing Configuration Manager 2012 installation
 Recover a site server
 Perform site maintenance or reset this site
 Uninstall a Configuration Manager site server
• The following site system roles can be installed during setup:
 Management point
 Distribution point
• Secondary sites can be installed only from the console
Demonstration: Installing a Configuration
Manager 2012 Primary Site
In this demonstration, you will see how to:
• Run Prerequisite Checker and verify that the prerequisites
are met for the installation
• Run the System Center 2012 Configuration Manager Setup
Wizard and select the option to install a Configuration
Manager 2012 stand-alone primary site
Lab Scenario
• You are the network administrator for Contoso, Ltd.
Contoso wants to deploy System Center 2012
Configuration Manager, but they need to evaluate the
functionality first. Thus, they have decided to perform a
Proof-of-Concept deployment in a lab environment. The
Proof-of-Concept deployment is limited to a stand-alone
primary site.
• You need to test the deployment by:
 Configuring prerequisites for the Configuration Manager
deployment
 Extending the Active Directory schema
 Installing a System Center 2012 Configuration Manager
stand-alone primary site
Lab Review
• What prerequisites are needed for installing a stand-alone
Configuration Manager primary site?
• To validate server readiness for installation, Prerequisite
Checker verifies prerequisites for what components?
• What user rights are required to extend the Active
Directory schema?
• What setup options are available in the
Configuration Manager 2012 Setup Wizard?
Lesson 4: Performing Post-Setup Configuration
Tasks
• Verifying the Configuration Manager 2012 Installation
• Viewing Status Messages
• Overview of Status Summarizers
• Configuring Boundaries and Boundary Groups
• Installing Site System Roles
• Demonstration: Performing Post-Configuration Tasks
Verifying the Configuration Manager 2012
Installation
• Verify that services are started
• Start the Configuration Manager console
• View the installation logs
 ConfigMgrPrereq.log
 ConfigMgrSetup.log
 ConfigMgrSetupWizard.log
 ConfigMgrAdminUI.log
• View the Status Messages
Viewing Status Messages
• Each Configuration Manager
component generates Status
Messages
• Status Messages can be found in the
Monitoring section at:
 Site Status
 Component Status
• Use Status Message Viewer
• Use Status Message Reports
Installing Site System Roles

New roles can be installed:

• On an existing site server by using the Add Site System Roles
Wizard
• On a new site server by using the Create Site System Server
Wizard

Specific configurations of site roles

• Management point • Fallback status point
• Distribution point • Out-of-band service point
• Application Catalog website • Reporting services point
point • Software update point
• Application Catalog web • State migration point
service point • System Health Validator point
• Asset Intelligence • Endpoint Protection point
synchronization point
• Enrollment point
• Enrollment proxy point
Demonstration: Performing Post-Configuration
Tasks
In this demonstration, you will see how to:
• Create a new Active Directory site
• Configure Active Directory Forest Discovery to create a
new boundary from the Active Directory site
• Configure a boundary group and include the new boundary
• Install additional site system roles: Fallback Status Point
and Reporting Services Point
• Configure the management point and the distribution
point
 The Configuration Manager Console Panes
Ribbon
Navigation Pane

Results
Pane
Workspaces

Preview
Pane
The Assets and Compliance Workspace

• Has nodes for the users and devices

discovered in your hierarchy
• Has nodes for the collections used to
organize the users and devices in
your hierarchy
• Has other nodes that are used to
monitor and manage the software
and configuration settings on the
client devices in the hierarchy
The Software Library Workspace

• Is split into three main nodes

• Application Management is used to
create and manage the software
that will be deployed in your
hierarchy
• Software Updates is used to manage
the updates for operating systems
and software
• Operating Systems is used to
mange the operating systems being
deployed through Configuration
Manager
The Monitoring Workspace

• Centralizes all the features used to

extract information from the
database about the operations in
you hierarchy
• Alerts are administrator configurable
and provide pop-up in the
management console
• Queries can find any information
stored in the database
• Reporting helps provide
management friendly reports about
the stored data
• The status based nodes report
information reported by clients and
system processes about ongoing
operations
The Administration Workspace

• Provides management capability for

the Configuration Manager
components
• Hierarchy configuration contains the
settings for discovering users and
devices in your hierarchy
• Site configuration contains the
settings for the sites and the servers
in the sites
• Security contains the settings for the
security applied to you hierarchy
 Using Console Organization Features
• Some nodes allow you to
create folders
• Folders can be nested to
create a hierarchy of objects
• Objects can only be in one
folder

• Configuration Items, Baselines, Drivers,

and Applications can be categorized
• Categories are not stored in a hierarchy
• Categories are used with the Search
feature
• Objects can be tagged with multiple
categories
 Using Search
Selected node displayed for local searches

Type search phrase here

Use Add Criteria to make complex searches

• Search can be used to find anything you have access to in your

Hierarchy
• The Search bar is located at the top of the results pane
• Free text searches find the search phrase on any property
• Criteria searches allow you to specify the fields to search
• Local searches only search the current node
• Global searches are used to search all objects
Monitoring Site and Component Status
Managing Components by Using
Configuration Manager Service Manager
• Launched from the ribbon in the Monitoring workspace by using
the Start button when either the Site Status or Component Status
nodes are selected
• Displays content either by Components and then Server or by
Server and then Component
• Provides query option to see the current status
What Are Configuration Manager Log Files?

All client and site components in Configuration Manager record

process information in individual log files

By default, logging is enabled for all services

By default, server log files have a maximum size of 2 MB

By default, server logs are in the <InstallationPath>\LOGS

folder
Viewing Log files with the Configuration
Manager Trace Log Tool

The Configuration Manager Trace Log Tool is a manually installed tool

The Configuration Manager Trace Log Tool simplifies analysis of log files
because of its highlighting, filtering, and error-lookup features

Pause Button

Entries with Errors

specific text automatically
identified with the identified with a
Highlight tool red background