1. ADM360 Chapter One – The Planning: SMS 2003 Deployment Planning Paul Barcoe-Walsh Product Manager Enterprise Management Division Microsoft

2. SMS 2003 SMS 2.0 BeforeAfterDuringBeforeAfterDuring SMS 2003 150 Clients During

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

4. Planning Overview

5. High-level Process Deployment / Migration is in three high-level phases Preparedness Deployment Optimization Each phase has sub-phases Information Gathering/Planning Testing Pilot Roll-out

6. Factors Affecting Roll-Out Environmental Service Level Agreement How much inventory How much sw dist Mgmt Maturity /Demarcation Security requirements AD requirements SQL requirements IIS requirements SMS 2.0 Client-base make-up % of clients meet prerequisites % of clients that will be Advanced Clients SMS 2003 No Windows 95 or earlier support No Windows ME or Windows XP Home No NetWare support No SQL Server 6.5 support

7. 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 2003 Use of Advanced Client Differences between use of Standard and Advanced Client Infrastructure Requirements

8. Mainframe Branch Office Local Servers Approx. 122 Secondary Sites Each Primary supports: 2 Regional Offices 100 Branches (2 Primaries support the central data centers) 10 Primary Sites Hierarchy Structure ? Central Site

9. SMS 2.0 Site System Roles MeteringDatabase SMS Site Database DistributionPoint Site Server ClientAccessPoint LogonPoint

10. Deployment/Migration Starts when first pilot begins Ends when last SMS 2.0 client is upgraded Key decisions are made here Based on preparedness and requirements for optimization

11. 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?

12. Preparing Active Directory SMS 2003 can integrate with Active Directory in many functions: Discovery of user, group, and computer accounts Publishing Server Locator Point and Management Point for client lookup Publishing of roaming boundaries If you are moving to Active Directory, recommended prior to SMS 2003 deployment Simplifies administration of SMS 2003 Collapse domains if required Permit schema extensions? Configure Active Directory sites SMS can use Active Directory sites for site boundaries

13. Determining SMS 2003 Security Mode Decide on SMS 2003 security mode Standard security is similar to SMS 2.0 Limited security Many accounts to manage in the domain/Active Directory Advanced is secure Much more secure than Standard security Fewer accounts to manage (only group accounts) Requires Active Directory Can switch from Standard to Advanced after installation/upgrade

14. Client Agents – Which To Choose? FeatureStandard ClientAdvanced Client Inventory (HW/SW)  Mobile aware inventory  Basic SW Distribution  Mobile-aware SW Distribution  Remote Control   Metering  Client PlatformsWindows 98, NT4, Win2k, WinXP Win2k, WinXP Windows 2003 Server Installation MethodsDiscovery, Script, Manual, Pre-stage Discovery, Script, Manual, Pre-stage and Group Policy

15. 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 !!

16. Preparing for the Migration

17. Before Upgrade Make sure you have valid backups ! Suggested pre-upgrade steps Tempdb 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

18. Deployment Readiness Wizard Overview 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 Tests Database 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 automatically Also stops if any errors detected (red conditions) Upgrade continues with warnings (orange conditions)

19. Deployment Readiness Wizard SMS 2.0 Site Boundaries demo demo

20. 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 problems Tidy existing databases (reduce history data etc) Tune SQL Server

21. SQL Server Readiness Tasks demo demo

22. 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 ~ 12GB SQL Log File Size ~ 289 MB SQL Log Used ~ 21MB 78,256 machines 1x 800Mhz Proc 256 MB RAM Conversion performance: ~1 hour 46 minutes 106 minutes 6,360 seconds

23. Upgrading Strategies demo demo

24. MeteringDatabase SMS 2003 Site Systems Changes SMS Site Database Management Point Management Point ServerLocatorPoint DistributionPoint ReportingPoint Site Server ClientAccessPoint SMS 2003 Site Systems LogonPoint

25. Capacity Planning For SMS 2003 Hardware Upgrade Considerations Hardware Sizing Site system overhead SMS 2.0 vs. SMS 2003 load comparison

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

27. SMS Hardware Sizing Medium Primary Site: 1,000-5,000 clients Memory needs grow with number of clients Disk IO starts to become possible bottleneck Processing capacity requirements increase as inventory and package frequency increases Disk Layout Raid 1 – OS/SQL Exec Raid 5 SMS Directory Raid 5 SMS data Raid 1 SMS Log

28. SMS Hardware Sizing Large Primary Site: 20,000-50,000 clients Memory needs continue to grow with clients Disk IO will be the bottleneck Separate hardware volumes and channels for performance Channel 1- 4 volume RAID5 array - SQL Database Channel 1- 2 volume RAID1 Array for NT system – SQL Master - Swap Channel 2 - 6 volume RAID5 array for SMS Channel 2 - 2 volume RAID1 array for SQL Log

29. Capacity Planning For SMS 2003 Site System Overhead Rolex86 Primary194.3m140M Secondary105m93M CAP30m30M Server Loc. PointN/A5M Mgmt PointN/A15M Reporting PointN/A3M Metering8.9mIncluded (Pri/Sec) Logon Point14.8mN/A v20 diskv03 disk

30. SMS 2003 Performance Significant performance improvements in key areas: FeatureSMS 2.0SMS 2003 Inventory Performance Full Inventory Delta Inventory AD Discovery Clients per Site 25/min140/min 5 times faster 32/min 225/min 7 times faster 31/min150/min 5 times faster 2K per CAP 25K per MP 12 times more

31. Upgrade Considerations SMS 2003 Requirements Site servers Windows 2000 SP2 SQL Server 2000 SP3 SQL Server 7.0 SP3 Server Logon Points Windows 2000 SP2 IIS Distribution Points Windows 2000 SP2 IIS (BITS) Reporting Point Windows 2000 SP2 IIS Management Point Windows 2000 SP2 IIS Reporting Points Windows 2000 SP2 IIS Client Access Points Windows 2000 SP2 SMS Database Server Windows 2000 SP2 Maintaining 2.0 Sites Secondary!

32. Migration Strategies Direct Upgrade Upgrade existing 2.0 SP4 site servers Maintain existing 2.0 child sites if required Maintains existing infrastructure and inventory data Parallel Install Install new sites Migrate clients to new sites Allows change in infrastructure to accommodate new design or hardware

33. Upgrade Methods Replace / Wipe Reload Complete 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

34. Direct Upgrade Overnight Upgrade SMS 2.0 SecondarySite SMS 2003 Standard Clients SMS 2.0 Clients SMS 2003 Advanced Clients SMS 2.0 Clients Clients Holding Site SMS 2003 Transition Site

35. Direct Upgrade Overnight Upgrade Benefits Fastest and easiest way to upgrade to SMS 2003 Replaces 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

36. Direct Upgrade “Phased Upgrade” MMS 2003 CommNet SMS 2.0 SecondarySite SMS 2003 StandardClients SMS 2.0 Clients SMS 2003 Advanced Clients SMS 2.0 Clients Clients

37. Client Upgrade Tool Direct Upgrade – Phase Upgrade demo demo

38. Post Upgrade Tasks Backup your site! Configure site boundaries Specify the IP subnets and/or Active Directory sites Roaming Boundaries Configure site settings: System roles Discovery Installation methods Client agents Reconstitute data not converted – if required

39. Upgrading Secondary Site Servers Download the upgrade from the parent site. Use this method: When there’s no Admin at the Secondary Site When 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 site When 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 administrator When network bandwidth is a concern.

40. 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 necessary Few 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 recommended More 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

41. SMS 2003 Site Server demo demo

42. SMS 2003 Planning Summary Planning Preparedness Deployment Optimization Preparing for the migration Make sure you have valid backups ! Tune SQL Server Deployment Readiness Wizard Upgrading strategies Capacity Planning For SMS 2003 Direct Upgrade Wipe/Reload Parallel Post upgrade migration planning Configure site boundaries Configure site settings Reconstitute data not converted

43. SC03 Chapter Two – Migration and Interoperability

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

45. Questions and Answers

46. Community Resources http://www.microsoft.com/communities/default.mspx Most Valuable Professional (MVP) http://www.mvp.support.microsoft.com/ Newsgroups Converse online with Microsoft Newsgroups, including Worldwide http://www.microsoft.com/communities/newsgroups/default.mspx User Groups Meet and learn with your peers http://www.microsoft.com/communities/usergroups/default.mspx

47. Suggested Reading And Resources The tools you need to put technology to work! TITLE Available Microsoft® Systems Management Server 2003 Administrator's Companion: 0-7356-1888-7 10/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

48. evaluations evaluations

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