Topic Last Updated -- November 2007
You can install a secondary site from the Configuration Manager 2007 installation media, or you can connect to the installation files from a mapped network drive, hard disk drive, or another removable storage media at the secondary site.
To install a secondary site using Configuration Manager Setup
-
Ensure that the computer you want to use as the secondary site meets all the hardware and software requirements for Configuration Manager site systems. For more information about Configuration Manager supported configurations, see Configuration Manager Supported Configurations.
-
Log on to the new secondary site server computer with an account that has local administrative permissions.
-
Insert the Configuration Manager 2007 installation media into the server’s drive, or click spash.hta, located at the root of the installation files directory, on source files copied to a local drive on the server.
-
Click Configuration Manager 2007.
-
On the Welcome page, click Next.
-
On the Configuration Manager Setup Options page, click Install a Configuration Manager Site Server.
-
On the Microsoft Software License Terms page, click I accept these terms, and then click Next.
-
On the Configuration Manager Settings Configuration page, select to install Configuration Manager with Custom settings.
-
On the Configuration Manager Site Type page, select Secondary Site.
-
On the Destination Folder page, click Next to install the secondary site installation files in the default directory, or enter a custom installation directory.
-
On the Configuration Manager Site Information page, enter a unique three-digit site code and the site name for this site, and then click Next.
-
On the Configuration Manager Parent Site Settings page, enter the site code of the parent site and the name of the primary site server to which the secondary site will connect.
-
On the Updated Prerequisite Components page, select the appropriate option for obtaining client prerequisite component files. Files can either be downloaded as part of Setup, an alternate location where the client prerequisite component files have already been downloaded to can be used.
-
On the Updated Prerequisite Component Path page, specify the path to store client prerequisite component files downloaded during Setup or the path to the alternate location where client prerequisite component files have previously been downloaded to.
Note The Setup command line option Setup /download <path to files> can be used to download client prerequisite component files without running the complete Configuration Manager Setup wizard. -
On the Summary page, review the summary details for the secondary site installation before continuing. To make changes to any details, click Previous until you return to the page in the wizard where you set the detail. Once you are finished, return to the Summary page. To begin the secondary site installation, click Next.
-
When prerequisite checking has completed, review any messages in the results pane of the Prerequisite Check page to verify that all prerequisites have been met or that Configuration Manager Setup can resolve any prerequisites that have not been met for installation to continue. If Configuration Manager Setup cannot resolve issues found, review the ConfigMgrPrereq.log file located in the root of the system drive for more information about how to resolve any issues manually. When all discovered prerequisite check failures have been resolved, return to the Prerequisite Check page and re-run the setup prerequisites check.
Important Configuration Manager Setup cannot continue until all prerequisite checks have completed with no errors. -
Review the Installation Summary page to determine what installation steps Configuration Manager 2007 is taking as it installs the secondary site.
-
The Confirmation page displays whether or not the installation was successful and the details of the secondary site installation.
Note After the secondary site has been successfully installed, you must manually create the address to the secondary site in the parent site Configuration Manager console and ensure that the secondary site server computer account has been added to the local SMS_SiteToSiteConnection_<site code> group on the primary site server computer to enable site-to-site communications.