adm363 chapter two – sms 2003 migration and interoperability paul barcoe-walsh product manager...

46
ADM363 Chapter Two – SMS 2003 Migration and Interoperability Paul Barcoe-Walsh Product Manager Enterprise Management Division Microsoft

Upload: ernest-roberts

Post on 05-Jan-2016

214 views

Category:

Documents


0 download

TRANSCRIPT

Page 1: ADM363 Chapter Two – SMS 2003 Migration and Interoperability Paul Barcoe-Walsh Product Manager Enterprise Management Division Microsoft

ADM363Chapter Two – SMS 2003 Migration and Interoperability

Paul Barcoe-Walsh

Product Manager

Enterprise Management Division Microsoft

Page 2: ADM363 Chapter Two – SMS 2003 Migration and Interoperability Paul Barcoe-Walsh Product Manager Enterprise Management Division Microsoft

Agenda

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

Chapter 1: The Planning “Recap”

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

Page 3: ADM363 Chapter Two – SMS 2003 Migration and Interoperability Paul Barcoe-Walsh Product Manager Enterprise Management Division Microsoft

The Recap

Page 4: ADM363 Chapter Two – SMS 2003 Migration and Interoperability Paul Barcoe-Walsh Product Manager Enterprise Management Division Microsoft

Chapter 1: The Planning Recap

PreparednessFocus on Information Gathering, Planning, Lab Testing

Checking health of existing hierarchy - DRW

Decide pre-requisites of SMS 2003

DeploymentDefine the Deployment/Migration Strategy

Top-down approach

OptimizationMigrate to Advanced Client

Change site boundaries to AD Sites

Change to Advanced Security

Page 5: ADM363 Chapter Two – SMS 2003 Migration and Interoperability Paul Barcoe-Walsh Product Manager Enterprise Management Division Microsoft

SMS 2.0

SMS 2003

SMS 2.0Primary Site

SMS 2.0Secondary Site

SMS 2.0

Before AfterDuringBefore AfterDuring

Mixed hierarchy: SMS 2003 / SMS 2.0

SMS 2003150 Clients

During

Page 6: ADM363 Chapter Two – SMS 2003 Migration and Interoperability Paul Barcoe-Walsh Product Manager Enterprise Management Division Microsoft

MeteringDatabase SMS Site

Database

ManagementPointServer

LocatorPoint

DistributionPoint

ReportingPoint

SiteServer

ClientAccessPoint

SMS 2003 Site Systems

LogonPoint

Site Systems Changes

Page 7: ADM363 Chapter Two – SMS 2003 Migration and Interoperability Paul Barcoe-Walsh Product Manager Enterprise Management Division Microsoft

MMS 2003 CommNet Status

demodemo

Page 8: ADM363 Chapter Two – SMS 2003 Migration and Interoperability Paul Barcoe-Walsh Product Manager Enterprise Management Division Microsoft

Software Distribution:Advanced Client

demodemo

Page 9: ADM363 Chapter Two – SMS 2003 Migration and Interoperability Paul Barcoe-Walsh Product Manager Enterprise Management Division Microsoft

Site Configurations

Page 10: ADM363 Chapter Two – SMS 2003 Migration and Interoperability Paul Barcoe-Walsh Product Manager Enterprise Management Division Microsoft

SMS 2003 Site Configurations

SMS 2003 Configuration Options:Site Boundaries

System roles

Discovery methods

Installation methods

Page 11: ADM363 Chapter Two – SMS 2003 Migration and Interoperability Paul Barcoe-Walsh Product Manager Enterprise Management Division Microsoft

SMS 2003 Configuration Options

demodemo

Page 12: ADM363 Chapter Two – SMS 2003 Migration and Interoperability Paul Barcoe-Walsh Product Manager Enterprise Management Division Microsoft

Roaming Boundaries

You specify the roaming boundaries of your site

IP subnets

IP address ranges

AD sites

Clients in these boundaries can access content from the site’s DPs

Page 13: ADM363 Chapter Two – SMS 2003 Migration and Interoperability Paul Barcoe-Walsh Product Manager Enterprise Management Division Microsoft

Roaming Boundaries

You can divide the roaming boundary space into two separate areas:

Local roaming boundariesFast, stable network

Remote roaming boundariesSlow or unstable network such as RAS or wireless networks

Advanced Clients can use BITS “download and execute” for software

Supported on Primary and Secondary sites

SC04 – Mobile Clients with SMS 2003 Fri 10:15

Page 14: ADM363 Chapter Two – SMS 2003 Migration and Interoperability Paul Barcoe-Walsh Product Manager Enterprise Management Division Microsoft

Configuring Roaming Site Boundaries

demodemo

Page 15: ADM363 Chapter Two – SMS 2003 Migration and Interoperability Paul Barcoe-Walsh Product Manager Enterprise Management Division Microsoft

Server Locator Point Overview

Server Locater Points are used to start the client installation processSimilar to the logon point role in SMS 2.0

Maps clients to sites to complete installation

Clients communicate to SLP using HTTP

Can control which computers are SLPs

SLPs can kick off standard or mobile client installationPlace Capinst.exe, Smsman.exe, Client.msi, and a logon script in Netlogon share

Can use a script to detect which platform to install

Requires access to SQL ServerSite database or replica

Server Locator Points can be found through WINS or AD

Page 16: ADM363 Chapter Two – SMS 2003 Migration and Interoperability Paul Barcoe-Walsh Product Manager Enterprise Management Division Microsoft

Server Locator Points

SiteServer

Client

SMS SiteDatabase

Where’s my CAP?

ServerLocator

Point

WINSWhere’s the SLP?

ClientAccessPoint

ActiveDirectory

Page 17: ADM363 Chapter Two – SMS 2003 Migration and Interoperability Paul Barcoe-Walsh Product Manager Enterprise Management Division Microsoft

Management PointOverview

Management points are used to interface with Advanced clientsSimilar to the client access point role in SMS 2.0

Clients retrieve policies from MP

Clients report discovery, inventory, metering, and status data to MP

Clients communicate to MP using HTTP

Clients find a local distribution point through MP

Can control which computers are MPs

Requires BITS

Requires IIS

Requires access to SQL ServerSite database or replica

Management Points can be found through WINS or AD

Page 18: ADM363 Chapter Two – SMS 2003 Migration and Interoperability Paul Barcoe-Walsh Product Manager Enterprise Management Division Microsoft

Management Points

SiteServer

ClientSMS SiteDatabase

ManagementPoint

Client policy retrieval Client data reporting

Page 19: ADM363 Chapter Two – SMS 2003 Migration and Interoperability Paul Barcoe-Walsh Product Manager Enterprise Management Division Microsoft

Configuring the Site Server:Server Locator Point Management Point

demodemo

Page 20: ADM363 Chapter Two – SMS 2003 Migration and Interoperability Paul Barcoe-Walsh Product Manager Enterprise Management Division Microsoft

Client AgentsWhich to choose?

Standard clientBased on SMS 2.0 code base

Not optimized for mobile systems

Advanced ClientDesigned specifically to improve management of mobile systems

Brand new code base

Page 21: ADM363 Chapter Two – SMS 2003 Migration and Interoperability Paul Barcoe-Walsh Product Manager Enterprise Management Division Microsoft

Advanced Client Architecture

Advanced Client is driven by SMS policyPolicy is XML with embedded MOF

SMS policy is obtained from a Management Point

SMS Policy is persisted locally

Client leverages BITSBackground Intelligent Transfer Service

A service provided by the Windows OS

Allows data to be sent with checkpoint-restart and bandwidth throttling

Page 22: ADM363 Chapter Two – SMS 2003 Migration and Interoperability Paul Barcoe-Walsh Product Manager Enterprise Management Division Microsoft

Determining Client Installation Methods

Advanced clients can be installed through numerous methods:SMS software distribution to upgrade existing SMS standard (or SMS 2.0) clients

IntelliMirror/GPO deployment

Manual installation

Preinstalled image

Logon script through SLP and Capinst

Standard clients are installed through SLPCan run Capinst for automated assignment

Can run Smsman pointed to assigned site’s CAP

Automated push installation of either clientAutomated push installation can be configured for clients or site systems

Can install Advanced client on an existing standard clientDeinstalls the standard client, then installs the Advanced client

Page 23: ADM363 Chapter Two – SMS 2003 Migration and Interoperability Paul Barcoe-Walsh Product Manager Enterprise Management Division Microsoft

Advanced Client Installation

demodemo

Page 24: ADM363 Chapter Two – SMS 2003 Migration and Interoperability Paul Barcoe-Walsh Product Manager Enterprise Management Division Microsoft

SMS 2003 Security Migration

SMS 2003 will provide two security modes:Standard Mode (same as SMS 2.0, SMS service etc.)

Advanced Mode (dependent on AD)

Can transition from Standard to AdvancedSite Properties

Site Reset

(can’t go back again)

Recommend a “top-down” migration to Advanced Security Mode.

NOTE: The three new security groups are in Standard Mode as well as Advanced Mode

Site System Access Group

Site Address Access Group

Database Access Group

New groups:Local groups if site installed on a member server

Domain groups if site installed on a DC

Names can be overridden on setup (.ini file)

Page 25: ADM363 Chapter Two – SMS 2003 Migration and Interoperability Paul Barcoe-Walsh Product Manager Enterprise Management Division Microsoft

Setup Advanced Security

demodemo

Page 26: ADM363 Chapter Two – SMS 2003 Migration and Interoperability Paul Barcoe-Walsh Product Manager Enterprise Management Division Microsoft

Advanced Client Roaming

Page 27: ADM363 Chapter Two – SMS 2003 Migration and Interoperability Paul Barcoe-Walsh Product Manager Enterprise Management Division Microsoft

Roaming Scenarios

Regional roamingWhen the client is located within the roaming boundaries of a site that is part of the hierarchy of its assigned site

Supported with and without Active Directory deployed

Global roamingWhen the client is located within the roaming boundaries of any site in the SMS hierarchy

Supported only with Active Directory deployed

FallbackWhen the client is neither located within the roaming boundaries of any site in the SMS hierarchy, nor located within the site boundaries of its assigned site

Page 28: ADM363 Chapter Two – SMS 2003 Migration and Interoperability Paul Barcoe-Walsh Product Manager Enterprise Management Division Microsoft

Global Roaming

Primary Primary SiteSite

Assigned Assigned SiteSite

Roaming Roaming SiteSite

Primary Primary SiteSite

Primary Primary SiteSite

Primary Primary SiteSite

Management Management Point LocationPoint Location

Content Content LocationLocation

ContentContent

Active Active DirectoryDirectory

PolicyPolicy

Page 29: ADM363 Chapter Two – SMS 2003 Migration and Interoperability Paul Barcoe-Walsh Product Manager Enterprise Management Division Microsoft

Interoperability

Page 30: ADM363 Chapter Two – SMS 2003 Migration and Interoperability Paul Barcoe-Walsh Product Manager Enterprise Management Division Microsoft

InteroperabilitySMS 2003 Site ServerSMS 2003 Site Server

SMS CAPSMS CAP

WIn16WIn16

Domain XYZ

WinNTWinNT

SMS 2.0 SP4SMS 2.0 SP4SiteSite

Server Locator PointServer Locator PointMgmt PointMgmt Point

SMS CAPSMS CAP

Win9xWin9x

Domain ABC

Win2kWin2k WinXPWinXP Win03Win03 WinNTWinNT

Page 31: ADM363 Chapter Two – SMS 2003 Migration and Interoperability Paul Barcoe-Walsh Product Manager Enterprise Management Division Microsoft

SMS 2.0 and SMS 2003 Features Interoperability

Client Discovery and InstallationServer locator points – Eliminate LP’s

SMS 2003 SMSMan.exe – Run from 2.0 Cap

Client Push Installation method – you can target SMS 2.0 clients

Computers that reside in the overlapping boundaries SMS installs the following client types:

Logon Script Client Type

Windows 95 Windows 98 NT 4 Windows 2000 and later

Standard Clients

SMS 2.0 client SMS 2003 Standard Client

SMS 2003 Standard Client

SMS 2003 Standard Client

Advanced Clients

SMS 2.0 client SMS 2.0 client SMS 2.0 client SMS 2003 Advanced Client

Page 32: ADM363 Chapter Two – SMS 2003 Migration and Interoperability Paul Barcoe-Walsh Product Manager Enterprise Management Division Microsoft

SMS 2.0 and SMS 2003 Features Interoperability

Collections and QueriesCollections defined on SMS03 sites propagate down to SMS2.0

Not all 2.0 classes exist in SMS03.

Client Push Installation method – you can target SMS 2.0 clients

Can’t export queries from one version and import them into another

Hardware InventoryPropagated up to SMS03

16-bit clients assigned to SMS2.0 site will not

SMS_def.mof not compatible - specifically referencing tables changes / new tables

Software InventoryPropagated up to SMS03

16-bit clients assigned to SMS2.0 site will not

details about file creation dates is discarded

Page 33: ADM363 Chapter Two – SMS 2003 Migration and Interoperability Paul Barcoe-Walsh Product Manager Enterprise Management Division Microsoft

SMS 2.0 and SMS 2003 Features Interoperability

Software DistributionCreate and advertise programs to SMS2.0 sitesBased on user accounts or user groups only 32-bit clients Status messages are propagated up to SMS03Advanced Clients can download package source files from

2.0 distribution points Settings in the Advanced Client tab and the Suppress program notifications ignored by 2.0 Courier Sender a SMS03 site will only be received on 2.0 if 2.0 is using SMS03 Courier Sender Manager - copy the file SMS/bin/i386/coursend.exe from an SMS03 site to the SMS/bin/i386/ folder on the 2.0 site

Page 34: ADM363 Chapter Two – SMS 2003 Migration and Interoperability Paul Barcoe-Walsh Product Manager Enterprise Management Division Microsoft

Software Distribution

demodemo

Page 35: ADM363 Chapter Two – SMS 2003 Migration and Interoperability Paul Barcoe-Walsh Product Manager Enterprise Management Division Microsoft

SMS 2.0 and SMS 2003 Features Interoperability

Remote ToolsPropagated up to SMS03Can’t run Remote Tools for 16-bit clientsSMS03 Remote Tools console still makes requests using IPX and NetBios – thus SMS03 Administrator console can control those clients

ReportingPropagated up to SMS03SMS03 Report Viewer will not view reports created by Crystal Reports on 2.0 sitesCan’t Export/import up nor down

Page 36: ADM363 Chapter Two – SMS 2003 Migration and Interoperability Paul Barcoe-Walsh Product Manager Enterprise Management Division Microsoft

Administrator Mixed-Version Hierarchy

Metering Server site system role is not available

The following maintenance tasks are not available:

Export Site Database

Export Site Transaction Logs

Export Software Metering Database

Export Software Metering Transaction Log

The Software Metering tool is not available

Page 37: ADM363 Chapter Two – SMS 2003 Migration and Interoperability Paul Barcoe-Walsh Product Manager Enterprise Management Division Microsoft

Administrator Mixed-Version Hierarchy

Repair Wizard – choose All Tasks and then choose Repair Site

Delete an SMS 2.0 secondary site only if connect directly to the parent of that secondary site

Update database statistics option enabled only when connected to an SMS 2.0 site

Page 38: ADM363 Chapter Two – SMS 2003 Migration and Interoperability Paul Barcoe-Walsh Product Manager Enterprise Management Division Microsoft

SMS Data Flow

Page 39: ADM363 Chapter Two – SMS 2003 Migration and Interoperability Paul Barcoe-Walsh Product Manager Enterprise Management Division Microsoft

ii

SMS 2003 Site to Site Data Flow

SMS 2003 Central SiteSMS 2003 Central Site

SMS 2003SMS 2003 SMS 2.0 SMS 2.0 (SP4)(SP4)

Page 40: ADM363 Chapter Two – SMS 2003 Migration and Interoperability Paul Barcoe-Walsh Product Manager Enterprise Management Division Microsoft

SMS 2003 Site to Site Data Flow

To allow or to prevent unsigned data flow:

Navigate to the Advanced Tab of the Site Properties

Select or clear the Do not accept unsigned data from sites running SMS 2.0 SP4 and earlier

Page 41: ADM363 Chapter Two – SMS 2003 Migration and Interoperability Paul Barcoe-Walsh Product Manager Enterprise Management Division Microsoft

SMS 2003 Chapter TwoSummary

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

Software Distribution

SMS Data Flow

Page 42: ADM363 Chapter Two – SMS 2003 Migration and Interoperability Paul Barcoe-Walsh Product Manager Enterprise Management Division Microsoft

Questions and Answers

Page 43: ADM363 Chapter Two – SMS 2003 Migration and Interoperability Paul Barcoe-Walsh Product Manager Enterprise Management Division Microsoft

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

Page 44: ADM363 Chapter Two – SMS 2003 Migration and Interoperability Paul Barcoe-Walsh Product Manager Enterprise Management Division Microsoft

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

TodayTodayMicrosoft® Windows® Server Microsoft® Windows® Server 2003 Administrator's 2003 Administrator's Companion: 0-7356-1367-2Companion: 0-7356-1367-2

Microsoft Press books are 20% off at the TechEd Bookstore

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

Page 45: ADM363 Chapter Two – SMS 2003 Migration and Interoperability Paul Barcoe-Walsh Product Manager Enterprise Management Division Microsoft

evaluationsevaluations

Page 46: ADM363 Chapter Two – SMS 2003 Migration and Interoperability Paul Barcoe-Walsh Product Manager Enterprise Management Division Microsoft

© 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.