ADM360Chapter One – The Planning: SMS 2003 Deployment Planning

Paul Barcoe-Walsh

Product Manager

Enterprise Management Division

Microsoft

SMS 2003

SMS 2.0

Before AfterDuringBefore AfterDuring

SMS 2003150 Clients

During

Agenda

This chapter describes strategies to upgrade from SMS 2.0 to SMS 2003, and contains the following topics:

Planning Overview

Preparing for the migration

Upgrading strategies

Post upgrade migration planning

Planning Overview

High-level Process

Deployment / Migration is in three high-level phases

Preparedness

Deployment

Optimization

Each phase has sub-phasesInformation Gathering/Planning

Testing

Pilot

Roll-out

Factors Affecting Roll-Out

EnvironmentalService Level Agreement

How much inventory

How much sw dist

Mgmt Maturity /DemarcationSecurity requirements

AD requirements

SQL requirements

IIS requirements

SMS 2.0Client-base make-up

% of clients meet prerequisites

% of clients that will be Advanced Clients

SMS 2003No Windows 95 or earlier support

No Windows ME or Windows XP Home

No NetWare support

No SQL Server 6.5 support

Preparedness

Everything that needs to be done before deploying SMS 2003

Focus on Information Gathering, Planning, Lab Testing

Checking health of existing hierarchy

Meeting pre-requisites of SMS 2003

Gathering requirements for SMS 2003Use of Advanced Client

Differences between use of Standard and Advanced Client

Infrastructure Requirements

MainframeBranch OfficeLocal Servers

Approx. 122 Secondary SitesApprox. 122 Secondary Sites

Each Primary supports:Each Primary supports:2 Regional Offices2 Regional Offices100 Branches100 Branches(2 Primaries support the central (2 Primaries support the central data centers)data centers)

10 Primary Sites10 Primary Sites

Hierarchy Structure ?Central SiteCentral Site

SMS 2.0 Site System Roles

MeteringMeteringDatabaseDatabase SMS SiteSMS Site

DatabaseDatabase

DistributionDistributionPointPoint

SiteServer

ClientClientAccessAccessPointPoint

LogonLogonPointPoint

Deployment/Migration

Starts when first pilot begins

Ends when last SMS 2.0 client is upgraded

Key decisions are made hereBased on preparedness and requirements for optimization

Optimization

Starts when first site upgraded to SMS 2003

Deploy Active Directory

Change site boundaries to Active Directory Sites

Change to Advanced Security

Client agents – which to choose?

Preparing Active Directory

SMS 2003 can integrate with Active Directory in many functions:

Discovery of user, group, and computer accountsPublishing Server Locator Point and Management Point for client lookupPublishing of roaming boundaries

If you are moving to Active Directory, recommended prior to SMS 2003 deployment

Simplifies administration of SMS 2003Collapse domains if required

Permit schema extensions?Configure Active Directory sites

SMS can use Active Directory sites for site boundaries

Determining SMS 2003 Security Mode

Decide on SMS 2003 security modeStandard security is similar to SMS 2.0

Limited securityMany accounts to manage in the domain/Active Directory

Advanced is secureMuch more secure than Standard securityFewer accounts to manage (only group accounts)Requires Active Directory

Can switch from Standard to Advanced after installation/upgrade

Client Agents – Which To Choose?

Feature Standard Client Advanced Client

Inventory (HW/SW) Mobile aware inventory

Basic SW Distribution Mobile-aware SW Distribution

Remote Control Metering Client Platforms Windows 98,

NT4, Win2k, WinXP

Win2k, WinXP Windows 2003

Server

Installation Methods Discovery, Script, Manual,

Pre-stage

Discovery, Script, Manual, Pre-stage and Group Policy

Do I still require that NetBIOS $#!+?

SMS 2003

…using Active Directory

…and Advanced Security

…with Advanced Clients

No NT Network Browser !

No WINS for name resolution !!

Preparing for the Migration

Before Upgrade

Make sure you have valid backups !

Suggested pre-upgrade stepsTempdb large enough ?

Site DB free space? – Auto grow by %

SMS log large enough – 50% of Site DB (more critical when you start on replicated sql)

Delete inventory history

Perform database checks – DBCC’s

Run the Deployment Readiness Wizard

Deployment Readiness WizardOverview

To help determine manual preparation steps for upgrade, use the SMS 2003 Deployment Readiness Wizard (DRW)Launched as apart of setup

Can also be run as a standalone program

Verifies:Platforms and Operating System SMS Version TestsDatabase Tests SMS 2.0 Features Tests

Must be run within 24 hours of attempted upgrade If not run within past 24 hours, setup will run it automaticallyAlso stops if any errors detected (red conditions)Upgrade continues with warnings (orange conditions)

Deployment Readiness Wizard SMS 2.0 Site Boundaries

demodemo

Aiding Database Conversion

Perform a test conversion of existing primary site databases

Test on backup of existing 2.0 databases

Provides an insight that sites will convert (no issues!)

Provides conversion timings where databases are large

Minimise potential problemsTidy existing databases (reduce history data etc)

Tune SQL Server

SQL Server Readiness Tasks

demodemo

Sample: Conversion Baseline

SMS 2.0 Central site SP4 + HRP (hotfix rollup pack) SQL Sever 2000 SP3 Site Db File Size ~ 35GB Site Db used size ~ 12GBSQL Log File Size ~ 289 MBSQL Log Used ~ 21MB78,256 machines 1x 800Mhz Proc 256 MB RAMConversion performance:

~1 hour 46 minutes 106 minutes 6,360 seconds

Upgrading Strategies

demodemo

MeteringMeteringDatabaseDatabase

SMS 2003 Site Systems Changes

SMS SiteSMS SiteDatabaseDatabase

ManagementManagementPointPointServerServer

LocatorLocatorPointPoint

DistributionDistributionPointPoint

ReportingReportingPointPoint

SiteServer

ClientClientAccessAccessPointPoint

SMS 2003 Site SystemsSMS 2003 Site SystemsSMS 2003 Site SystemsSMS 2003 Site Systems

LogonLogonPointPoint

Capacity Planning For SMS 2003 Hardware Upgrade Considerations

Hardware Sizing

Site system overhead

SMS 2.0 vs. SMS 2003 load comparison

Load

Recommended Hardware

Inventory 5x week Software Distribution 10 pkgs/week

1Ghz 512 MB RAM

SMS Hardware Sizing Small Secondary Site: 50-100 Clients

At Small sites - processing, memory and disk IO are not big issues (unless box is running other workloads)

It’s better to have an SMS site sharing a server with other workload than connect to a dedicated site server over a slow speed link

Load Recommended Hardware

Inventory 5x week Software Distribution 10 pkgs/week

Dual 1 Ghz 512MB – 1GBRAM Minimum of 3 disks Recommended - 11 disk

SMS Hardware Sizing Medium Primary Site: 1,000-5,000 clients

Memory needs grow with number of clientsDisk IO starts to become possible bottleneckProcessing capacity requirements increase as inventory and package frequency increasesDisk Layout

Raid 1 – OS/SQL ExecRaid 5 SMS DirectoryRaid 5 SMS dataRaid 1 SMS Log

Load Recommended Hardware

Inventory 5x week Software Distribution 10 pkgs/week

Quad 1Ghz+ 4GB RAM Mimimum 14 disks

SMS Hardware Sizing Large Primary Site: 20,000-50,000 clients

Memory needs continue to grow with clientsDisk IO will be the bottleneckSeparate hardware volumes and channels for performance

Channel 1- 4 volume RAID5 array - SQL DatabaseChannel 1- 2 volume RAID1 Array for NT system – SQL Master - SwapChannel 2 - 6 volume RAID5 array for SMS Channel 2 - 2 volume RAID1 array for SQL Log

Capacity Planning For SMS 2003 Site System Overhead

Role x86 x86

Primary 194.3m 140M

Secondary 105m 93M

CAP 30m 30M

Server Loc. Point N/A 5M

Mgmt Point N/A 15M

Reporting Point N/A 3M

Metering 8.9m Included (Pri/Sec)

Logon Point 14.8m N/A

v20 disk v03 disk

SMS 2003 PerformanceSignificant performance improvements in key areas:

Feature SMS 2.0 SMS 2003

Inventory Performance Full Inventory

Delta Inventory

AD Discovery

Clients per Site

25/min25/min 140/min140/min5 times 5 times fasterfaster

32/min32/min 225/min225/min 7 times 7 times fasterfaster

31/min31/min 150/min150/min 5 times 5 times fasterfaster

2K per 2K per CAPCAP

25K per 25K per MPMP

12 times 12 times moremore

Upgrade ConsiderationsSMS 2003 Requirements

Site servers Windows 2000 SP2SQL Server 2000 SP3

SQL Server 7.0 SP3

Server Logon PointsWindows 2000 SP2IIS

Distribution PointsWindows 2000 SP2IIS (BITS)

Reporting PointWindows 2000 SP2IIS

Management PointWindows 2000 SP2IIS

Reporting PointsWindows 2000 SP2IIS

Client Access PointsWindows 2000 SP2

SMS Database ServerWindows 2000 SP2

Maintaining 2.0 Sites

Secondary!

Migration Strategies

Direct UpgradeUpgrade existing 2.0 SP4 site servers

Maintain existing 2.0 child sites if required

Maintains existing infrastructure and inventory data

Parallel InstallInstall new sites

Migrate clients to new sites

Allows change in infrastructure to accommodate new design or hardware

Upgrade Methods

Replace / Wipe ReloadComplete de-install of old sites and clients

Install SMS 2003 sites

Useful for small sites

sites with little data

sites which have been poorly maintained

Direct UpgradeOvernight Upgrade

SMS 2.0SMS 2.0SecondarySecondary

SiteSite

SMS 2.0SMS 2003SMS 2003StandardClientsSMS 2.0Clients

SMS 2003SMS 2003Advanced ClientsAdvanced Clients

SMS 2.0SMS 2.0

SMS 2.0SMS 2.0ClientsClients

SMS 2.0SMS 2.0ClientsClients

SMS 2.0SMS 2.0

Holding Holding SiteSite

SMS 2003SMS 2003

Transition Transition SiteSite

Direct UpgradeOvernight Upgrade Benefits

Fastest and easiest way to upgrade to SMS 2003Replaces SMS 2.0 Client with Standard Client

Replace Standard Clients with the Advanced Client “after” the overnight upgrade is completed.

Start using SMS 2003 without having to first establish Advanced Client infrastructure, such as Management Points

Direct Upgrade “Phased Upgrade” MMS 2003 CommNet

SMS 2.0SMS 2.0SecondarySecondary

SiteSite

SMS 2.0

SMS 2.0

SMS 2003StandardStandardClientsClients

SMS 2.0SMS 2.0ClientsClients

SMS 2003SMS 2003Advanced ClientsAdvanced Clients

SMS 2.0SMS 2.0ClientsClients

SMS 2.0SMS 2.0ClientsClients

Client Upgrade ToolDirect Upgrade – Phase Upgrade

demodemo

Post Upgrade TasksBackup your site!Configure site boundaries

Specify the IP subnets and/or Active Directory sites Roaming Boundaries

Configure site settings:System rolesDiscovery Installation methodsClient agents

Reconstitute data not converted – if required

Upgrading Secondary Site Servers

Download the upgrade from the parent site.Use this method:

When there’s no Admin at the Secondary SiteWhen network bandwidth is not a concern. You can upgrade up to five secondary sites at one time!!!

Initiate upgrade from the parent site using source files located at the secondary site.

Use this method:When you want to control the upgrade from the primary siteWhen network bandwidth is a concern.

Upgrade locally at the secondary site server by using the SMS 2003 product CD.

Use this method:When the secondary site has an administratorWhen network bandwidth is a concern.

Advanced Client vs Secondary Sites

Customers have asked: Now that SMS provides Management Points and the Advanced Client do they still need Secondary Sites?

Answer: it depends

Secondary Site might not be necessaryFew clients at location or very light software distribution needs and infrequent inventory

Distribution from clients uses BITS both upstream and downstream and is bandwidth aware

Recommend to use the Simple Schedule – not the Full Schedule (Inventory and Metering)

Secondary Site still recommendedMore than 10 or 20 clients per location at a 56kbps “usable” link

Multiple clients downloading software will each download a separate copy if there is no secondary site

Local management point prevents each client from downloading policy over the WAN

SMS 2003 Site Server

demodemo

SMS 2003 Planning Summary

PlanningPreparednessDeploymentOptimization

Preparing for the migrationMake sure you have valid backups !Tune SQL ServerDeployment Readiness Wizard

Upgrading strategiesCapacity Planning For SMS 2003 Direct UpgradeWipe/ReloadParallel

Post upgrade migration planningConfigure site boundariesConfigure site settingsReconstitute data not converted

SC03 Chapter Two – Migration and Interoperability

Agenda

This chapter describes the administration of a mixed-version SMS hierarchy :

SMS 2003 Configuration Options:System roles

Discovery

Installation methods

Client agents – which to choose?

Active Directory Schema Extensions

Interoperability of SMS 2.0 and SMS 2003 Features SMS Data Flow

Software Distribution

Questions and Answers

Community Resources

Community Resourceshttp://www.microsoft.com/communities/default.mspx

Most Valuable Professional (MVP)http://www.mvp.support.microsoft.com/

NewsgroupsConverse online with Microsoft Newsgroups, including Worldwidehttp://www.microsoft.com/communities/newsgroups/default.mspx

User GroupsMeet and learn with your peershttp://www.microsoft.com/communities/usergroups/default.mspx

Suggested Reading And Resources

The tools you need to put technology to work!The tools you need to put technology to work!

TITLETITLE AvailableAvailable

Microsoft® Systems Management Microsoft® Systems Management Server 2003 Administrator's Server 2003 Administrator's Companion: 0-7356-1888-7Companion: 0-7356-1888-7

10/15/0310/15/03

Microsoft Press books are 20% off at the TechEd Bookstore

Also buy any TWO Microsoft Press books and get a FREE T-Shirt

evaluationsevaluations

© 2003 Microsoft Corporation. All rights reserved.© 2003 Microsoft Corporation. All rights reserved.This presentation is for informational purposes only. MICROSOFT MAKES NO WARRANTIES, EXPRESS OR IMPLIED, IN THIS SUMMARY.This presentation is for informational purposes only. MICROSOFT MAKES NO WARRANTIES, EXPRESS OR IMPLIED, IN THIS SUMMARY.