Deploying System Center Configuration Manager 2007: Part 1 Wally Mead

Senior Program ManagerMicrosoft CorporationSession Code: MGT302

Session Agenda

Prerequisites for Configuration Manager 2007Deploying Configuration Manager 2007Deploying site systemsUnderstanding BoundariesConsiderations for upgrading from SMS 2003

Site Deployment Changes

Both site and site system checking

Issues and resolutions clearly explained

Extensive install and upgrade checks

Prerequisite Checking

Real time notification of deployment

Setup won’t exit until the site is ready to be used

Detailed installation report available

Site Deployment Progress

Virtual Server 2005 R2 host/guest

Hyper-V support

Dropped Windows 2000 Server Platform Support

New site systems

Required for network access protection

FQDN, versioning and site capabilities

Updated AD Schema

Configuration Manager 2007 Prerequisites

The Configuration Manager site server requires:Windows Server 2003 SP1, SP2 or Windows Server 2003 R2

If not SP2 then a number of updates are recommendedSQL Server 2005 SP2/SP3 or SQL Server 2008IIS for a number of site systems.NET Framework 2.0MMC 3.0Access to specific required client components

Can be downloaded during install or prior to Setup

Configuration Manager 2007 SP1 Prerequisites

Configuration Manager SP1 is very similar to the RTM product

SP1 supports Windows Server 2008 for all site system roles

Was limited to System Health Validator role in RTMNo support for Server Core installations as site systems

Requires Windows Server Update Services (WSUS) 3.0 SP1

For WSUS serverFor site server, WSUS admin console required if WSUS installation is remote from site server (which is recommended)

Additional Items Prerequisite Check Will Identify

The Configuration Manager Prerequisite Check will also check for:

Administrative rights on site systemsSysadmin rights to SQL Server instanceWSUS requirement

Minimum of the WSUS administrator consoleOr entire WSUS Server installation

Active Directory schema extensions8.3 file name support

Service Pack 1 Prereq Updates

The Configuration Manager SP1 Prerequisite Check adds support for:

SQL Server Service Principle Name registrationOne of the biggest deployment issues we see today – the lack of proper SPN registration of SQL Server

FQDN for site systemsRecommended to use FQDNs

Installed version of the WAIKSP1 requires WAIK 1.1, and you may have to manually deinstall WAIK 1.0

WSUS 3.0 SP1Required for Configuration Manager SP1

Validating prerequisites for Configuration Manager 2007 SP1

demo

Active Directory Requirements

Configuration Manager site systems are required to be in an Active Directory environmentActive Directory schema extensions are not required, however highly recommended

Network Access Protection (NAP) does require AD schema extended for Configuration ManagerWithout the AD schema extended for Configuration Manager, you are required to have a server locator point to assign clients to the Configuration Manager site

AD Schema Compatibility

Configuration Manager can use AD if extended for SMS 2003 with limited functionality

Can’t publish new data or FQDN of site systemsShould upgrade the schema to Configuration Manager as soon as possible

SMS 2003 can publish to AD if extended for Configuration Manager 2007

Publishes what it is configured to publish, won’t publish Configuration Manager specific data

No new schema update with SP1 of Configuration Manager

Extending Active Directory for Configuration Manager

Configuration Manager Setup will NOT extend the AD schema as SMS 2003 Setup couldYou must manually extend the AD schema

Run SMSSetup\Bin\I386\Extadsch.exeCheck C:\Extadsch.log for success

Prior to Configuration Manager Setup is preferredLDF file will be provided also

Must manually grant site server rights to publish to AD

Extending the Active Directory schemademo

Configuration Manager 2007 R2 Prerequisites

Configuration Manager R2 adds new capabilities to the SP1 product

Requires Configuration Manager SP1If you want to use SQL Server Reporting Services, you must have SRS installed and configured

Not installed nor configured as part of the R2 installationMulticast support is limited

Windows Server 2008 distribution pointsOnly used for OSD to download content when running in WinPE

Session Agenda

Prerequisites for Configuration Manager 2007Deploying Configuration Manager 2007Deploying site systemsUnderstanding BoundariesConsiderations for upgrading from SMS 2003

Site Installation/UpgradePrimary Site Installation

CD/Network shareInteractive deploymentScripted (the standard file you know today)

Secondary site installationSame as primarySecondary site push installation

~150MB package sent over the network

Site ModesMixed mode

Equivalent to SMS 2003 Advanced Security with data signing from clients implementedAvailable for new installations and site upgrades

SMS 2003 upgrades will automatically install in mixed mode

Mixed mode provides interoperability with SMS 2003 SP2/SP3 sites

If your environment includes a mix of SMS 2003 and Configuration Manager sites, it is highly recommended that SMS 2003 is SP3

Site Modes (2)

Native modeFull mutual authentication using PKI-based machine certificatesNew installs or migration of mixed mode sitesRequired for Internet-based client managementCannot report to a mixed mode site

Should keep sites consistent in the hierarchySecondary sites the same as parent

Installing a Configuration Manager 2007 SP1 primary site

demo

Session Agenda

Prerequisites for Configuration Manager 2007Deploying Configuration Manager 2007Deploying site systemsUnderstanding BoundariesConsiderations for upgrading from SMS 2003

Site System RolesMost site system roles remain the same:

Site server (primary and secondary)Site database serverManagement pointServer locator pointReporting pointDistribution point

The only roles that were removed are:Client access pointSender component server

New Site System RolesOperating system deployment

State migration point PXE service point

Software updates managementSoftware update point (WSUS 3.0 server)

Network access protectionSystem health validator

New Site System Roles (2)

Client deployment and distressFallback status point

Software distributionBranch distribution pointAlso supports OSD and SUM

SMS Provider can now be on a 3rd computerSMS 2003 required it on the site server or the site database server

Site System Deployment TipsEnsure you have a fallback status point (FSP) in your hierarchy

Then you can generate client deployment reportsDon’t place distribution points on remote site systems with unreliable or high-latency links

SMB is used to replicate content to distribution points

Use branch distribution points to handle poor network connectivity

Use BITS to download content

Site System Deployment Tips (2)

Separate site systems for easier troubleshootingSoftware update pointManagement point Reporting pointFallback status point

Separate site system roles also provide higher scalability numbers

Configuration Manager Site System Roles

SQL Server

SQL Server

Primary Site Server

Management Point

Server Locator Point

Reporting Point

PXE Service Point

State Migration Point

Distribution Point

Software Update Point

Fallback Status Point

System Health Validator

Branch DP

New Role

SMS 2003 Equivalent Role

ConfigMgr SP1/R2 Site Systems

SQL Server

SQL Server

Primary Site Server

Management Point

Server Locator Point

Reporting Point

PXE Service Point

State Migration Point

Software Update Point

Fallback Status Point

System Health Validator

Branch DP

Reporting Services

point

Asset Intelligence synch point

Out of band service point

Distribution Point• Multicast• AVM streaming

Deploying Configuration Manager 2007 site systems

demo

Session Agenda

Prerequisites for Configuration Manager 2007Deploying Configuration Manager 2007Deploying site systemsUnderstanding BoundariesConsiderations for upgrading from SMS 2003

Differences from SMS 2003:Site Boundaries and Roaming Boundaries are gone

No longer Site PropertiesBoundaries replace them

New node under Site Settings

Boundaries are either Fast or Slow“Fast” would be SMS 2003 “Local”“Slow” would be SMS 2003 “Remote”

Boundaries

Boundaries flow up the hierarchyHierarchy wide view of all boundariesMakes it easier to identify overlapping boundary scenarios

Still a bad thing in Configuration Manager

Works with SMS 2003 sitesCannot create SMS 2003 boundaries

Except for SMS 2003 child secondary sites

Boundaries (2)

Configuring Boundariesdemo

Session Agenda

Prerequisites for Configuration Manager 2007Deploying Configuration Manager 2007Deploying site systemsUnderstanding BoundariesConsiderations for upgrading from SMS 2003

UpgradeIn place

Server emphasisRetains existing data

Feature PacksAll SMS 2003 feature packs should be deinstalled prior to upgrade (ITMU is not required to be removed)

OSD and Device Management packages remain

Side-by-Side

Client emphasis

Upgrade and re-assign existing clients

Hierarchy ConsiderationsTop-down upgrade is required

Higher version is always the parentCan detach a section of the hierarchy if needed

Allows central site to remain SMS 2003 as a new hierarchy is created

Configuration Manager does NOT support any Legacy Clients in the hierarchy

Must remove all Legacy Clients from the hierarchy to upgrade the central site to Configuration Manager

Hierarchy Considerations (2)

Always run a Testdbupgrade prior to upgradeInteroperability

SMS 2003 sites can report to Configuration Manager sitesSMS 2003 clients can be assigned to a mixed mode Configuration Manager siteConfiguration Manager clients can roam to SMS 2003 SP2/SP3 sites

But cannot be assigned to an SMS 2003 site

No SMS 2.0 sites in the hierarchy

Session Summary

System Center Configuration Manager 2007 is the replacement for Systems Management Server

Available for more than a year nowDeployment is very similar to the SMS 2003 deployments you’ve already doneThere are new site system roles to be aware ofSystem requirements are greater than SMS 2003

question & answer

www.microsoft.com/teched

Sessions On-Demand & Community

http://microsoft.com/technet

Resources for IT Professionals

http://microsoft.com/msdn

Resources for Developers

www.microsoft.com/learning

Microsoft Certification & Training Resources

Resources

Related Content

Breakout Sessions (session codes and titles)

Whiteboard Sessions (session codes and titles)

Hands-on Labs (session codes and titles)

Track Resources

Resource 1

Resource 2

Resource 3

Resource 4

A slide outlining the 2009 evaluation process and prizes will be provided closer to the event.

© 2009 Microsoft Corporation. All rights reserved. Microsoft, Windows, Windows Vista and other product names are or may be registered trademarks and/or trademarks in the U.S. and/or other countries.The information herein is for informational purposes only and represents the current view of Microsoft Corporation as of the date of this presentation. Because Microsoft must respond to changing market conditions, it should not be interpreted to be a commitment on the part of Microsoft, and Microsoft cannot guarantee the accuracy of any information provided after the date of this presentation. MICROSOFT MAKES NO WARRANTIES, EXPRESS,

IMPLIED OR STATUTORY, AS TO THE INFORMATION IN THIS PRESENTATION.