Migrating to Configuration Manager 2007 : Conducting an In-place Upgrade (part 5) - Upgrading Secondary Sites

7. 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 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 21 shows this node of the Configuration Manager console, displaying Beaumont as a secondary site under the Houston primary site. Figure 21. The Configuration Manager console focused on the parent primary site
2.	Choose Upgrade Secondary Site from the Actions pane on the far right side of the console to launch the wizard. Figure 22 shows the Upgrade Secondary Site Wizard’s Welcome screen. Figure 22. The Upgrade Secondary Site Wizard’s Welcome screen
3.	Clicking Next at the Welcome screen brings up the Secondary Sites page displayed in Figure 23. This page shows a list of secondary sites available for upgrade. Select the site(s) you wish to upgrade and click Next. Figure 23. The Upgrade Secondary Site Wizard site selection page
4.	The Installation Source Files page, displayed in Figure 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. Figure 24. The Upgrade Secondary Site Wizard’s Installation Source Files page
5.	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 secondary 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 ... Installing Site Component Manager under acct <NT AUTHORITY\SYSTEM> path <C:\SMS\bin\i386\sitecomp.exe> 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.