Chapter Excerpt

Upgrading SMS 2003 sites to System Center Configuration Manager 2007

Solutions provider takeaway: The process of upgrading your primary and secondary sites in SMS can be confusing at times, but this chapter excerpt guides solutions providers through this procedure step-by-step.

Upgrading a Primary Site

About the book:
This chapter excerpt on Migrating to System Center Configuration Manager (SCCM) 2007 (download PDF) is taken from the book System Center Configuration Manager 2007 Unleashed. This book is an all-inclusive guide to SCCM 2007. You will learn best practices for such tasks as designing, deploying, configuring and securing SCCM 2007 and backing up its components. This book will also guide you through all of the different aspects of SCCM 2007, including patch and compliance management, site maintenance, how to set up the Data Center Manager and configuring asset intelligence.

After completing the prerequisites outlined in the previous sections, you are ready to upgrade your primary site.

You should also verify client push installation is disabled on your site prior to the upgrade. This will allow you more control over the client upgrade process. The "Upgrading SMS 2003 Clients" section of this chapter discusses upgrading clients.

Perform the following steps to upgrade your primary site:

  1. Launch an upgrade to Configuration Manager 2007 by choosing Install Configuration Manager 2007 from the splash screen of the installation media.
    • You can access the splash screen by double-clicking splash.hta from the installation CD or other location where you have the installation files available.
    • You can also run setup.exe directly from the SMSSETUPbin<processor architecture> directory on the installation media.
  2. After reviewing the important reminders on the Setup Wizard welcome screen shown in Figure 9.12, click Next.
  3. FIGURE 9.12 The Configuration Manager 2007 Setup Wizard welcome screen

  4. Setup will detect that you have an existing SMS or ConfigMgr primary site on your server and provide the available options to upgrade or remove the site, as displayed in the Available Setup Options screen in Figure 9.13. Make sure that Upgrade an existing Configuration Manager or SMS 2003 installation is selected and then click Next.
  5. Review the license terms in the Microsoft Software License Terms dialog box shown in Figure 9.14. Then select "I accept these license terms" if you wish to continue. You may also choose to print the license terms. Click Next to continue.
  6. You have the opportunity to participate in the Customer Experience Improvement Program. This is an optional program to provide feedback to Microsoft, and your choice does not affect the upgrade process.
  7. After entering your selection, you will need to enter your 25-digit product key, generally found on the installation CD case or supplied as part of your volume license agreement.
  8. FIGURE 9.13 The Configuration Manager 2007 Setup Wizard installation options

    FIGURE 9.14 The Microsoft Software License Terms dialog box

  9. After you provide the product key, the wizard will prompt you to download the latest prerequisite updates. The download can take a considerable amount of time, so you may want to download the updates in advance. Make the appropriate selection in the dialog box shown in Figure 9.15, and choose Next to enter or browse to the updated prerequisite components location.
  10. FIGURE 9.15 The Updated Prerequisite Components dialog box

  11. Once you download the updated prerequisites or supply the path to the existing files, Setup runs a prerequisite check to verify your site meets all required prerequisites.
  12. When the prerequisite check completes successfully, click Begin Install to upgrade your site. This will take some time -- the actual time depends largely on your installa-tion settings and the size of the site database. Figure 9.16 shows the Setup Actions Status Monitoring screen, which provides a detailed view of the actions Setup is performing and the status of each action.
  13. If you have ITMU installed, Setup detects its presence and launches the ITMU Setup Wizard displayed in Figure 9.17. You can either complete the ITMU upgrade now, or cancel it and use the SMSITMU.MSI installer file located in the SMSSETUPSUMSCANTOOLS<processor architecture> folder on the Configuration Manager installation media to upgrade the scan tools after completing your Configuration Manager upgrade. If you do not upgrade ITMU during the upgrade, it will be necessary to upgrade it later for it to work properly for SMS clients with ConfigMgr 2007.

    If you choose to upgrade ITMU at this point, the ITMU upgrade process prompts you to download the latest security updates catalog from the Web or supply an alternate location for the catalog, as shown in Figure 9.18.

    Once you complete this dialog box and click Next, Setup finishes the ITMU upgrade and displays the Setup Complete dialog box, shown in Figure 9.19.

    The upgraded ITMU can deliver patches to SMS 2003 clients in your ConfigMgr site. As the message in the dialog box in Figure 9.19 indicates, you will need to ensure that your clients have Microsoft Installer (MSI) 3.1 or later if you use ITMU to deliver updates for Microsoft Office or other Windows Installer--based updates to

    FIGURE 9.16 The Setup Actions Status Monitoring dialog box

    FIGURE 9.17 The ITMU Setup Wizard welcome dialog box

    those clients. To provide continuity of service, you should plan to deploy the appro-priate MSI version to your clients before upgrading your site.

    About the authors:
    Kerrie Meyler is an independent consultant and trainer with more than fifteen years of experience in the IT industry. While in field technical sales at Microsoft, Meyler focused on infrastructure and management and presented at numerous product launches. She has also authored Microsoft Operations Manager 2005 Unleashed.

    Greg Ramsey, a Microsoft Most Valuable Professional for Systems Management Server, has been working with SMS and desktop deployment since 1998. Ramsey has written numerous articles for myITforum.com, including Removing Drivers From the Driver Store in ConfigMgr Using PowerShell.

    Byron Holt is an experienced IT professional and SMS and Configuration Manager engineer and has worked at Microsoft on the Active Directory and Enterprise Manageability support teams. Holt is presently on the security engineering team at McAfee Inc.

    For Configuration Manager clients, you will need to install WSUS and complete the additional steps required for ConfigMgr software updates. Chapter 15 discusses software updates and patch management. The "Migrating WSUS to Configuration Manager" section of this chapter discusses migrating from standalone WSUS to ConfigMgr WSUS. Chapter 15 also discusses using ITMU to support SMS 2003 clients in your ConfigMgr environment.

  14. FIGURE 9.18 The ITMU security updates catalog download dialog box

    FIGURE 9.19 The ITMU Setup Complete dialog box

  15. After ITMU Setup completes, the focus returns to the Configuration Manager Setup Action Status Monitoring dialog box previously displayed in Figure 9.16. The Next button is enabled when all actions complete; at this time, all the actions should now show a green success indicator.
  16. Clicking Next brings up the completion dialog box shown in Figure 9.20. Click the View Log button to check for any errors and confirm the end of the log includes the message "Installation and configuration processes are done."
  17. Confirm that the following services have started:
    • SMS_EXECUTIVE
    • SMS_SITE_COMPONENT_MANAGER

    FIGURE 9.20 The completing Configuration Manager setup dialog box

    • SMS_SITE_SQL_BACKUP
    • SMS_SITE_VSS_WRITER

  18. Finally, you should open the Configuration Manager console and review the site system status and component status. Chapter 21, "Backup, Recovery, and Maintenance," describes how to check ConfigMgr status.

Upgrading Secondary Sites

You can upgrade a secondary site after you upgrade its parent primary site. Before upgrading your secondary sites, run the prerequisite checker on the parent primary site server again -- this time check the All Secondary Sites box on the Installation Prerequisite Check Options page, previously displayed in Figure 9.2, to verify the sites meet all prerequisites for the Configuration Manager upgrade. The prerequisite checker displays any errors or warnings in the results screen and generates the log file c:ConfigMgrPrereq.log on the secondary site server.

To upgrade a secondary site, perform the following steps:

  1. Run the Upgrade Secondary Site Wizard from its parent site. One way to start the wizard is to open the Configuration Manager console, expand the tree control in the left pane to System Center Configuration Manager -> Site Database -> Site Management and then click the parent primary site's site code. Figure 9.21 shows this node of the Configuration Manager console, displaying Beaumont as a secondary site under the Houston primary site.
  2. FIGURE 9.21 The Configuration Manager console focused on the parent primary site

  3. Choose Upgrade Secondary Site from the Actions pane on the far right side of the console to launch the wizard. Figure 9.22 shows the Upgrade Secondary Site Wizard's Welcome screen.
  4. Clicking Next at the Welcome screen brings up the Secondary Sites page displayed in Figure 9.23. This page shows a list of secondary sites available for upgrade. Select the site(s) you wish to upgrade and click Next.
  5. The Installation Source Files page, displayed in Figure 9.24, allows you to choose whether to copy the required files from the parent site or point to a location on the local server. The option to use a local CD or installation point allows you to conserve network resources and reduces the time required for Setup to run. If you use a local copy of the installation media, you must copy the files to the SMSSetup folder in the root of one of the local drives. After indicating the location of the installation files, click Finish to complete the secondary site upgrade.
  6. The primary site server now makes an RPC connection to the secondary site server and installs the SMS_Bootstrap service, which copies the necessary files for Setup and launches the setup process. The bootstrap and setup processes create the c:SMS_BOOTSTRAP.log and c:ConfigMgrSetup.log files, respectively, on the sec-ondary site server. When the upgrade completes successfully, you should see entries similar to the following in the ConfigMgrSetup.log:

SMS Setup full version is 4.00.5931.0000
Installing SMS Site Component Manager ...

FIGURE 9.22 The Upgrade Secondary Site Wizard's Welcome screen

Installing Site Component Manager under acct
path
Started Site Component Manager service
SMS Site Component Manager installation completed.
Done with service installation
Starting WMI.
Using default Timeout value.
Checking status of WinMgmt...
Verified that WinMgmt is running.
SMS Setup full version is 4.00.5931.0000

The upgrade will take several minutes to complete -- longer if you are copying files across a wide area network (WAN) link with limited available bandwidth. You can view the site properties in the ConfigMgr console to verify that the version is now 4.00.5931.000 (ConfigMgr 2007 RTM) or higher. You can also use the console to view the site status for any errors that may have occurred.


Migrating to Configuration Manager 2007
  SMS 2003 to System Center Configuration Manager 2007 migration
  SMS 2003 to System Center Configuration Manager 2007 in-place upgrade
  Upgrading to SQL Server 2005 and SC Configuration Manager 2007
  Upgrading SMS 2003 sites to System Center Configuration Manager 2007
  SMS 2003 to SC Configuration Manager 2007 post-upgrade considerations

Printed with permission from Sams Publishing. Copyright 2009. System Center Configuration Manager (SCCM) 2007 Unleashed by J Kerrie Meyler, Byron Holt and Greg Ramsey. For more information about this title and other similar books, please visit Sams Publishing.


This was first published in November 2009

There are Comments. Add yours.

 
TIP: Want to include a code block in your comment? Use <pre> or <code> tags around the desired text. Ex: <code>insert code</code>

REGISTER or login:

Forgot Password?
By submitting you agree to receive email from TechTarget and its partners. If you reside outside of the United States, you consent to having your personal data transferred to and processed in the United States. Privacy
Sort by: OldestNewest

Forgot Password?

No problem! Submit your e-mail address below. We'll send you an email containing your password.

Your password has been sent to: