After verifying the prerequisites and deciding whether to extend the Active Directory schema, you are ready to begin ConfigMgr site installation.
By submitting your personal information, you agree that TechTarget and its partners may contact you regarding relevant content, products and special offers.
TIP: Use SMS Trace to Monitor ConfigMgr Installation
SMS Trace (also called Trace32 and introduced in Chapter 3) is a utility in the ConfigMgr Toolkit used to view log files in real time. Download the ConfigMgr Toolkit from Microsoft at http://www.microsoft.com/downloads (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.
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 8.1, you have several options in the splash screen, including running the prerequisite checker, reviewing the release notes, and installing ConfigMgr.
- 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 8.2.
- 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.
- On the Installation Settings page displayed in Figure 8.3, you finally can start selecting those decisions you reviewed in the "Pre-Installation" section of this chapter prior to starting the installation. Choose between custom settings and simple settings:
FIGURE 8.1 System Center Configuration Manager Installation splash screen
Real World: Previous Installations of ConfigMgr or SMS
If you arrive at the Available Setup Options screen (shown in Figure 8.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.
FIGURE 8.2 Available setup options for Configuration Manager installation
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. Chapter 10 discusses using the ConfigMgr console.
FIGURE 8.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.
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.
FIGURE 8.4 Specifying a site type
you will be unable to change the site code or the site name after installation completes. Figure 8.5 uses the code CEN and the name CENTRAL SITE.
FIGURE 8.5 The Site Settings page
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 http://technet.microsoft.com/en-us/library/bb693556.aspx 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. The "Preparing for Native Mode" and "Enabling Native Mode" sections of this chapter give an example of configuring a site in native mode.
FIGURE 8.6 Specifying the site mode
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
FIGURE 8.7 The Client Agent Selection page
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 http://technet.microsoft.com/en-us/library/bb693554.aspx.
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.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.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.
FIGURE 8.8 Specifying the database server and instance
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 http://technet.microsoft.com/en-us/library/bb694290.aspx.
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.
- 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.
FIGURE 8.9 The Settings Summary page
FIGURE 8.10 The Installation Prerequisite Check page, with failures
FIGURE 8.11 The Setup Action Status Monitoring page
TIP: Always Review ConfigMgrPrereq.log and ConfigMgrSetup.log
If you are like the authors of this book, you will be very excited when you see the message in Figure 8.12 that reads "Setup completed all operations successfully." Although there is a very good chance that this message is completely accurate, it is highly recommended you take the time to review the logs. Installations have occurred that appeared (and reported) to be successful, but were not completely successful due to problems such as improper SQL configuration or improper rights between servers. The message in Figure 8.12 gives a good indication of success, but the logs give the best indication. Browse %SystemRoot%\ConfigMgrPrereq.log and %SystemRoot%\ConfigMgrSetup.log to view additional installation information.
With the central site installed, you can use the same procedures to install other primary site servers. You would then join the sites together, as discussed in the "Attaching to Parent" section of this chapter. You will also want to upgrade your site servers to the current service pack level and ConfigMgr 2007 Release 2 (R2), as discussed in the following sections.
FIGURE 8.12 Completing the Microsoft System Center Configuration Manager 2007 Setup Wizard
NOTE: Performing a Silent Installation of ConfigMgr
You can perform a silent/unattended installation of ConfigMgr. The article at http:// technet.microsoft.com/en-us/library/bb693561.aspx provides information on unattended setups and includes additional links to sample script files and command-line parameters.
Installing Configuration Manager 2007
Microsoft System Center Configuration Manager 2007 pre-installation tips
Microsoft System Center Configuration Manager 2007 installation steps 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.