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

The Recap

Chapter 1: The Planning Recap Preparedness Focus on Information Gathering, Planning, Lab Testing Checking health of existing hierarchy - DRW Decide pre-requisites of SMS 2003 Deployment Define the Deployment/Migration Strategy Top-down approach Optimization Migrate to Advanced Client Change site boundaries to AD Sites Change to Advanced Security

SMS 2.0 SMS 2003 SMS 2.0 Primary Site SMS 2.0 Secondary Site SMS 2.0 BeforeAfterDuringBeforeAfterDuring Mixed hierarchy: SMS 2003 / SMS 2.0 SMS Clients During

Metering Database SMS Site Database Management Point Server Locator Point Distribution Point Reporting Point Site Server Client Access Point SMS 2003 Site Systems Logon Point Site Systems Changes

MMS 2003 CommNet Status demo demo

Software Distribution: Advanced Client demo demo

Site Configurations

SMS 2003 Site Configurations SMS 2003 Configuration Options: Site Boundaries System roles Discovery methods Installation methods

SMS 2003 Configuration Options demo demo

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

Roaming Boundaries You can divide the roaming boundary space into two separate areas: Local roaming boundaries Fast, stable network Remote roaming boundaries Slow 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

Configuring Roaming Site Boundaries demo demo

Server Locator Point Overview Server Locater Points are used to start the client installation process Similar 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 installation Place 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 Server Site database or replica Server Locator Points can be found through WINS or AD

Server Locator Points Site Server Client SMS Site Database Where’s my CAP? Server Locator Point WINS Where’s the SLP? Client Access Point Active Directory

Management Point Overview Management points are used to interface with Advanced clients Similar 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 Server Site database or replica Management Points can be found through WINS or AD

Management Points Site Server Client SMS Site Database Management Point Client policy retrieval Client data reporting

Configuring the Site Server: Server Locator Point Management Point demo demo

Client Agents Which to choose? Standard client Based on SMS 2.0 code base Not optimized for mobile systems Advanced Client Designed specifically to improve management of mobile systems Brand new code base

Advanced Client Architecture Advanced Client is driven by SMS policy Policy is XML with embedded MOF SMS policy is obtained from a Management Point SMS Policy is persisted locally Client leverages BITS Background Intelligent Transfer Service A service provided by the Windows OS Allows data to be sent with checkpoint-restart and bandwidth throttling

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 SLP Can run Capinst for automated assignment Can run Smsman pointed to assigned site’s CAP Automated push installation of either client Automated push installation can be configured for clients or site systems Can install Advanced client on an existing standard client Deinstalls the standard client, then installs the Advanced client

Advanced Client Installation demo demo

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 Advanced Site 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)

Setup Advanced Security demo demo

Advanced Client Roaming

Roaming Scenarios Regional roaming When 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 roaming When the client is located within the roaming boundaries of any site in the SMS hierarchy Supported only with Active Directory deployed Fallback When 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

Global Roaming Primary Site Assigned Site Roaming Site Primary Site Management Point Location Content Location Content Active Directory Policy

Interoperability

SMS 2003 Site Server SMS CAP WIn16 Domain XYZ WinNT SMS 2.0 SP4 Site Server Locator Point Mgmt Point SMS CAP Win9x Domain ABC Win2k WinXP Win03 WinNT

SMS 2.0 and SMS 2003 Features Interoperability Client Discovery and Installation Server 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 95Windows 98NT 4Windows 2000 and later Standard Clients SMS 2.0 clientSMS 2003 Standard Client Advanced Clients SMS 2.0 client SMS 2003 Advanced Client

SMS 2.0 and SMS 2003 Features Interoperability Collections and Queries Collections 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 Inventory Propagated 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 Inventory Propagated up to SMS03 16-bit clients assigned to SMS2.0 site will not details about file creation dates is discarded

SMS 2.0 and SMS 2003 Features Interoperability Software Distribution Create and advertise programs to SMS2.0 sites Based on user accounts or user groups only 32-bit clients Status messages are propagated up to SMS03 Advanced 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

Software Distribution demo demo

SMS 2.0 and SMS 2003 Features Interoperability Remote Tools Propagated up to SMS03 Can’t run Remote Tools for 16-bit clients SMS03 Remote Tools console still makes requests using IPX and NetBios – thus SMS03 Administrator console can control those clients Reporting Propagated up to SMS03 SMS03 Report Viewer will not view reports created by Crystal Reports on 2.0 sites Can’t Export/import up nor down

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

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

SMS Data Flow

i SMS 2003 Site to Site Data Flow SMS 2003 Central Site SMS 2003 SMS 2.0 (SP4)

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

SMS 2003 Chapter Two Summary 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

Questions and Answers

Community Resources Most Valuable Professional (MVP) Newsgroups Converse online with Microsoft Newsgroups, including Worldwide User Groups Meet and learn with your peers

Suggested Reading And Resources The tools you need to put technology to work! TITLE Available Microsoft® Systems Management Server 2003 Administrator's Companion: /15/03 Today Microsoft® Windows® Server 2003 Administrator's Companion: Microsoft Press books are 20% off at the TechEd Bookstore Also buy any TWO Microsoft Press books and get a FREE T-Shirt

evaluations evaluations

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