Installing Configuration Manager 2007 : Site Installation (part 1) - Installing ConfigMgr

3/25/2013 4:26:38 AM

After verifying the prerequisites and deciding whether to extend the Active Directory schema, you are ready to begin ConfigMgr site installation.

Tip: Use SMS Trace to Monitor ConfigMgr Installation

SMS Trace is a utility in the ConfigMgr Toolkit used to view log files in real time. Download the ConfigMgr Toolkit from Microsoft at (search for ConfigMgr Toolkit), and install it on your soon-to-be primary site. After you begin the ConfigMgr installation, launch Trace32 and open the ConfigMgr installation logs (%SystemRoot%\ConfigMgrPrereq.log and %SystemRoot%\ConfigMgrSetup.log). You will see the logs dynamically update as the installation proceeds.

1. Installing ConfigMgr

Perform the following steps to install the primary site:

Browse to your installation media and launch Splash.hta, found in the root of the installation media. As shown in Figure 1, you have several options in the splash screen, including running the prerequisite checker, reviewing the release notes, and installing ConfigMgr.

Figure 1. System Center Configuration Manager Installation splash screen

Review the release notes for late-breaking information about known issues, bug fixes, and other important information. When you are ready, select the option Install Configuration Manager 2007 to view the Welcome screen.

Verify you are ready to move forward and then click Next to choose a setup option, as shown in Figure 2.

Figure 2. Available setup options for Configuration Manager installation

Real World: Previous Installations of ConfigMgr or SMS

If you arrive at the Available Setup Options screen (shown in Figure 2) and see that you are unable to install a ConfigMgr site server, first confirm you are installing the site on a supported operating system. In addition, if the server previously had SMS or ConfigMgr installed, you may encounter this situation if the uninstall was not completely successful. If the Registry key HKEY_LOCAL_MACHINE\Software\Microsoft\SMS\Setup exists, delete it and retry the installation.

If the installation continues to fail, check the ConfigMgr installation logs (%SystemRoot%\ConfigMgrPrereq.log and %SystemRoot%\ConfigMgrSetup.log) for more information. You may be able to perform a little additional “clean-up.” If all else fails, you may need to resort to reinstalling the operating system on the server for a clean opportunity to install ConfigMgr.

Provided you are attempting to install on a supported server operating system (OS), select the option Install a Configuration Manager site server. Then click Next to view the license terms. Read the license agreement, and if you agree to the terms, click Next to proceed.

Tip: Install the ConfigMgr Console on a Workstation for Everyday Use

Another option on the Available Setup Options screen is Install or upgrade an administrator console. A common misconception for new ConfigMgr administrators is that you must run the Configuration Manager console on the site server. You can actually install it separately on a workstation operating system (such as Windows Vista or XP). While installing the console, you will select a site to manage. After installation, you can also attach to additional ConfigMgr primary sites and manage them all from a single console, without needing explicit administrative rights to the server.

On the Installation Settings page displayed in Figure 3. Choose between custom settings and simple settings:

Figure 3. Choosing to install using custom or simple settings

  • Custom settings allow you to specify the installation path, configure individual component settings and client agents, port settings, and more.

  • Simple settings are most useful in a test environment, but the authors recommend using custom settings so you are more aware of the configuration options and the process required for production deployment.

Choose the Custom settings option and click Next to continue.

On the Site Type page shown in Figure 4, select Primary site. Because you are installing your first site, this will also be your central site.

Figure 4. Specifying a site type

After you specify the site type, the wizard asks you to participate in the Customer Experience Improvement Program. Review the documentation at and be familiar with your corporate policies. Then choose whether to participate.

Joining the Customer Experience Improvement Program can help the Configuration Manager development team understand your pain points in Configuration Manager. You can change this option after installation by using the Help menu in the ConfigMgr console.

Specify the product key for your Configuration Manager installation. Enter a valid product key and then click Next to continue.

On the Destination Folder page, select the installation directory to install the software.

On the Site Settings page shown in Figure 5, enter the three-character site code, along with a site name (or description). Use those three characters wisely, because you will be unable to change the site code or the site name after installation completes. Figure 5 uses the code CEN and the name CENTRAL SITE.

Figure 5. The Site Settings page

On the next page, the wizard asks you to specify the desired site mode. If you choose to “go native” right now, have your signed security certificate ready to import.

If you will be supporting SMS 2003 clients or Windows 2000 systems in this site, the site will need to use mixed mode. Mixed mode is also required if your site has a parent site configured for mixed mode.

It is recommended you install the first site in mixed mode (although you can always switch back and forth; see for details). After completing installation and confirming everything is working properly, migrate the site to native mode. For this sample installation, select mixed mode for now.

Figure 6. Specifying the site mode

You are now ready to enable client agents for your site. As shown in Figure 7, enabling client agents is as simple as checking a box. With the exception of Network Access Protection, all client agents are enabled by default.

Figure 7. The Client Agent Selection page

On the Database Server page (shown in Figure 8), identify the SQL Server computer name and instance, and specify the ConfigMgr site database name. If the database name does not exist, the Configuration Manager setup program will create a new database if SQL Server is installed on the local system.

Figure 8. Specifying the database server and instance

If you specified SQL on a remote server, you must first create the database manually and add the machine account of the primary site server to the local Administrators group of the remote SQL server. Also during installation, the user account that is running the ConfigMgr install must have administrative rights on the SQL server, or be assigned the sysadmin SQL Server role on the remote SQL server. Microsoft provides detailed documentation on installing ConfigMgr with a remote SQL Server at

To specify a remote SQL database, simply enter the NetBIOS name of the remote SQL server and ensure that both you (as the installer) and the ConfigMgr site server have administrative rights to the SQL Server computer for installation and configuration.

Figure 8
shows the Database Server page with the name of the database server and the (default) site database name specified. The database will be installed on the default instance of the Bluebonnet central site server. If you want to use a named instance, simply enter it using the format specified in Figure 8.

Tip: Multiple Primary Sites—Use a Consistent Database Name

You may encounter a situation where it is necessary to modify your site database configuration. If you have multiple primary sites (which means you have multiple site databases, because each primary site has its own database), you may want to consider changing the database name to a consistent name (for example, “ConfigMgr”). Because using the default site database name results in a unique name for each database on each site, as shown in Figure 8.8, if you need to run a SQL script on each of your databases, you may have to change the script for each site. Using a consistent database name for all sites provides additional opportunities to automate configuration and maintenance changes.

The next page of the setup wizard is the SMS Provider Settings page. Specify the NetBIOS name of the server to install the SMS provider.

The SMS provider is your communication method between the ConfigMgr console and the ConfigMgr database. It is also the supported avenue to ConfigMgr data using Windows Management Instrumentation (WMI). The SMS provider is typically installed on the ConfigMgr primary site. You can also install the SMS provider on the SQL Server system or an entirely separate server. Do not install the provider on a clustered SQL Server instance or a SQL Server containing databases for multiple sites, because Microsoft does not support the provider in these scenarios. For larger sites, you may consider offloading the provider to increase performance. Microsoft provides documentation on choosing the SMS provider installation location at

On the Management Point page, choose to install a management point (MP) if you will be assigning clients to this site. All ConfigMgr clients require access to the management point to communicate with the ConfigMgr site. You can install the management point on the site server or a separate supported server operating system.
On the Port Settings page, select the default port (80) or use a custom port for client communications, provided you configured the site to use mixed mode. (If you’re configuring for native mode, HTTPS settings are also available for configuration.)

On the Updated Prerequisite Components page, you have the option to automatically connect to the Internet and download all prerequisite components, or you can specify an existing path to where you have previously downloaded the components. Setup will download several components, such as the Windows Update Agent, a WMI update, the Microsoft Remote Differential Compression Library, and a BITS update. Multiple supported languages are automatically downloaded as well.

Tip: How to Download Site Prerequisites Before Installation

Depending on your environment, you may not have access to the Internet from your ConfigMgr site, or you may have a slow Internet connection. Alternatively, you may be like us and prefer that everything you need is available before installing your site.

To download the prerequisites in advance, ensure you have Internet access, connect to your ConfigMgr installation media, and run the following command:

<Media Path>\SMSSETUP\BIN\I386\Setup.exe /DOWNLOAD <Destination>

Here, <Destination> is the location destination for your download—ensure this folder exists prior to running the setup command.

You can run this command from any supported Windows OS (Windows Vista, Windows XP, and so on). The download takes approximately 5 minutes with a high-speed Internet connection.

The Updated Prerequisite Component Path page will do one of two things, depending on your selection on the Updated Prerequisite Components page:

  • If you selected Check for updates and download newer versions to an alternate path, specify the path to download the files.

  • If you selected The latest updates have already been downloaded to an alternate path, simply specify the path so the installation can use those files.

Review the Settings Summary page, displayed in Figure 9, to ensure you entered all configuration information accurately. You can reconfigure some of these settings later, but others (such as Site Code and Site Name) are permanent. Click Next, which automatically launches the prerequisite checker.

Figure 9. The Settings Summary page

The Installation Prerequisite Check page verifies installation of all prerequisites, with results displayed in Figure 10. The complete list of setup prerequisite checks at provides detailed information of all ConfigMgr prerequisites. For any items that fail the check, double-click the individual result to see additional information. You should be able to remediate most problems while leaving the setup page open. If the server must be rebooted, you will need to restart the installation process from the beginning.

Figure 10. The Installation Prerequisite Check page, with failures

After correcting any items that failed prerequisite checks, click Run Check to rerun the prerequisite check. After all checks pass, click OK to begin the ConfigMgr site installation. During the installation process, review the installation log located at %SystemRoot%\ConfigMgrSetup.log. An installation progress page appears, as displayed in Figure 11.

Figure 11. The Setup Action Status Monitoring page

The Completing the Microsoft System Center Configuration Manager 2007 Setup Wizard page appears at the end of the installation. If you haven’t been watching the ConfigMgrSetup.log using SMS Trace (see the earlier note “Use SMS Trace to Monitor ConfigMgr Installation” regarding SMS Trace), click the View Log button to review the log, as shown in Figure 12.

Figure 12. Completing the Microsoft System Center Configuration Manager 2007 Setup Wizard

PS4 game trailer XBox One game trailer
WiiU game trailer 3ds game trailer
Top 10 Video Game
-   Uncharted 4: A Thief's End | E3 2015 Extended Gameplay Trailer
-   V.Next [PC] Kickstarter Trailer
-   Renowned Explorers [PC] Launch Date Trailer
-   The Void (Game Trailer)
-   World of Warships [PC] Open Beta Trailer
-   F1 2015 | Features Trailer
-   Battle Fantasia Revised Edition | Debut Trailer for Steam
-   Victor Vran [PC] Story Trailer
-   Star Wars Battlefront PC Alpha footage
-   Skyforge [PC] Open Beta Gameplay Trailer
-   Armored Warfare [PC] PvE Trailer
-   F1 2015 [PS4/XOne/PC] Features Trailer
-   Act of Aggression [PC] Pre-Order Trailer
-   Sword Coast Legends [PC] Campaign Creation E3 2015 Trailer
-   Sword Coast Legends [PC] Campaign Creation E3 2015 Dungeon Run Trailer
Game of War | Kate Upton Commercial