2. Wally Mead Senior Program Manager Microsoft Corporation Session Code: MGT302

3. Session Agenda Prerequisites for Configuration Manager 2007 Deploying Configuration Manager 2007 Deploying site systems Understanding Boundaries Considerations for upgrading from SMS 2003

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

5. 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 recommended SQL Server 2005 SP2/SP3 or SQL Server 2008 IIS for a number of site systems.NET Framework 2.0 MMC 3.0 Access to specific required client components Can be downloaded during install or prior to Setup

6. 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 RTM No support for Server Core installations as site systems Requires Windows Server Update Services (WSUS) 3.0 SP1 For WSUS server For site server, WSUS admin console required if WSUS installation is remote from site server (which is recommended)

7. Additional Items Prerequisite Check Will Identify The Configuration Manager Prerequisite Check will also check for: Administrative rights on site systems Sysadmin rights to SQL Server instance WSUS requirement Minimum of the WSUS administrator console Or entire WSUS Server installation Active Directory schema extensions 8.3 file name support

8. Service Pack 1 Prereq Updates The Configuration Manager SP1 Prerequisite Check adds support for: SQL Server Service Principle Name registration One of the biggest deployment issues we see today – the lack of proper SPN registration of SQL Server FQDN for site systems Recommended to use FQDNs Installed version of the WAIK SP1 requires WAIK 1.1, and you may have to manually deinstall WAIK 1.0 WSUS 3.0 SP1 Required for Configuration Manager SP1

9. Validating prerequisites for Configuration Manager 2007 SP1

10. Active Directory Requirements Configuration Manager site systems are required to be in an Active Directory environment Active Directory schema extensions are not required, however highly recommended Network Access Protection (NAP) does require AD schema extended for Configuration Manager Without the AD schema extended for Configuration Manager, you are required to have a server locator point to assign clients to the Configuration Manager site

11. 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 systems Should 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

12. Extending Active Directory for Configuration Manager Configuration Manager Setup will NOT extend the AD schema as SMS 2003 Setup could You must manually extend the AD schema Run SMSSetup\Bin\I386\Extadsch.exe Check C:\Extadsch.log for success Prior to Configuration Manager Setup is preferred LDF file will be provided also Must manually grant site server rights to publish to AD

13. Extending the Active Directory schema

14. Configuration Manager 2007 R2 Prerequisites Configuration Manager R2 adds new capabilities to the SP1 product Requires Configuration Manager SP1 If you want to use SQL Server Reporting Services, you must have SRS installed and configured Not installed nor configured as part of the R2 installation Multicast support is limited Windows Server 2008 distribution points Only used for OSD to download content when running in WinPE

15. Session Agenda Prerequisites for Configuration Manager 2007 Deploying Configuration Manager 2007 Deploying site systems Understanding Boundaries Considerations for upgrading from SMS 2003

16. Site Installation/Upgrade Primary Site Installation CD/Network share Interactive deployment Scripted (the standard file you know today) Secondary site installation Same as primary Secondary site push installation ~150MB package sent over the network

17. Site Modes Mixed mode Equivalent to SMS 2003 Advanced Security with data signing from clients implemented Available 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

18. Site Modes (2) Native mode Full mutual authentication using PKI-based machine certificates New installs or migration of mixed mode sites Required for Internet-based client management Cannot report to a mixed mode site Should keep sites consistent in the hierarchy Secondary sites the same as parent

19. Installing a Configuration Manager 2007 SP1 primary site

20. Session Agenda Prerequisites for Configuration Manager 2007 Deploying Configuration Manager 2007 Deploying site systems Understanding Boundaries Considerations for upgrading from SMS 2003

21. Site System Roles Most site system roles remain the same: Site server (primary and secondary) Site database server Management point Server locator point Reporting point Distribution point The only roles that were removed are: Client access point Sender component server

22. New Site System Roles Operating system deployment State migration point PXE service point Software updates management Software update point (WSUS 3.0 server) Network access protection System health validator

23. New Site System Roles (2) Client deployment and distress Fallback status point Software distribution Branch distribution point Also supports OSD and SUM SMS Provider can now be on a 3 rd computer SMS 2003 required it on the site server or the site database server

24. Site System Deployment Tips Ensure you have a fallback status point (FSP) in your hierarchy Then you can generate client deployment reports Don’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

25. Site System Deployment Tips (2) Separate site systems for easier troubleshooting Software update point Management point Reporting point Fallback status point Separate site system roles also provide higher scalability numbers

26. Configuration Manager Site System Roles 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

27. ConfigMgr SP1/R2 Site Systems 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 Distribution Point Multicast AVM streaming

28. Deploying Configuration Manager 2007 site systems

29. Session Agenda Prerequisites for Configuration Manager 2007 Deploying Configuration Manager 2007 Deploying site systems Understanding Boundaries Considerations for upgrading from SMS 2003

30. Differences from SMS 2003: Site Boundaries and Roaming Boundaries are gone No longer Site Properties Boundaries 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”

31. Boundaries flow up the hierarchy Hierarchy wide view of all boundaries Makes it easier to identify overlapping boundary scenarios Still a bad thing in Configuration Manager Works with SMS 2003 sites Cannot create SMS 2003 boundaries Except for SMS 2003 child secondary sites

32. Configuring Boundaries

33. Session Agenda Prerequisites for Configuration Manager 2007 Deploying Configuration Manager 2007 Deploying site systems Understanding Boundaries Considerations for upgrading from SMS 2003

34. Upgrade In place Server emphasis Retains existing data Feature Packs All 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

35. Hierarchy Considerations Top-down upgrade is required Higher version is always the parent Can 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

36. Hierarchy Considerations (2) Always run a Testdbupgrade prior to upgrade Interoperability SMS 2003 sites can report to Configuration Manager sites SMS 2003 clients can be assigned to a mixed mode Configuration Manager site Configuration 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

37. Session Summary System Center Configuration Manager 2007 is the replacement for Systems Management Server Available for more than a year now Deployment is very similar to the SMS 2003 deployments you’ve already done There are new site system roles to be aware of System requirements are greater than SMS 2003

39. 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 Required Slide Speakers, TechEd 2009 is not producing a DVD. Please announce that attendees can access session recordings at TechEd Online. Required Slide Speakers, TechEd 2009 is not producing a DVD. Please announce that attendees can access session recordings at TechEd Online.

40. Related Content Breakout Sessions (session codes and titles) Whiteboard Sessions (session codes and titles) Hands-on Labs (session codes and titles) Required Slide Speakers, please list the Breakout Sessions, TLC Interactive Theaters and Labs that are related to your session. Any queries, please check with your Track Owner. Required Slide Speakers, please list the Breakout Sessions, TLC Interactive Theaters and Labs that are related to your session. Any queries, please check with your Track Owner.

41. Track Resources Resource 1 Resource 2 Resource 3 Resource 4 Required Slide Track Owners to provide guidance. Please address any queries to your track owners. Required Slide Track Owners to provide guidance. Please address any queries to your track owners.

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

43. © 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. Required Slide