Finally! By now, you have spent a considerable amount of time reading the first seven chapters of this book. You have studied the terminology, examined those components you plan to install, and carefully designed your ConfigMgr 2007 hierarchy, paying very close attention to wide area network (WAN) links and administrative requirements. You have also documented and verified your site boundaries, and have determined whether you will operate in mixed mode or "go native." Due to its nature, a successful Configuration Manager (ConfigMgr) implementation requires substantial planning.
By submitting your personal information, you agree that TechTarget and its partners may contact you regarding relevant content, products and special offers.
This chapter covers installation of the central site server and basic configuration tasks. It also reviews multisite installation considerations as well as discusses the installation of primary and secondary child sites. In addition, the chapter discusses troubleshooting approaches for site installation and configuration.
You may notice the use of multiple site servers in this chapter. The lab environment used in this book has a central site (CEN) running on Bluebonnet, and four primary sites, all in the SCCMUnleashed.com domain. Here are the primary sites reporting to the central site:
- DAL (Dallas) -- Running on the Wildflower server
- HOU (Houston) -- Running on the Mockingbird server
- BXL (Brussels) -- Installed on the Tumbleweed server
- BEJ (Beijing) -- Installed on the Roadrunner server
This chapter discusses the installation of Configuration Manager 2007 on the central site server, and uses the BXL primary site for examples as well. The CEN, DAL, and BXL sites are running Configuration Manager 2007, whereas HOU and BEJ run SMS 2003. Chapter 9, "Migrating to Configuration Manager 2007," steps through the process of upgrading the HOU primary site to Configuration Manager 2007. The Configuration Manager console installs as part of your site server installation; Chapter 10, "The Configuration Manager Console," includes a discussion of installing the console on other systems.
You are almost ready to begin the ConfigMgr site installation. Before launching the installation program (setup.exe), assess the points in this section to ensure you have completed all prerequisites. If you have multiple ConfigMgr sites and/or servers in your design, verify you have that information documented, including what servers handle which ConfigMgr site roles, as well as required prerequisites for each server. Review the following questions:
- Will you configure the central site for mixed mode or native mode? Chapter 6, "Architecture Design Planning," discusses site security modes.
- Will your hierarchy contain all primary sites, or primary and secondary sites? Will you need any branch distribution points?
- Will you install all site components on your central site, or distribute them over multiple servers?
- How much drive space do you need on each site server? See Chapter 6 for disk space requirements.
- Do you need to extend the Active Directory (AD) schema?
- Is your hardware sufficient?
Chapter 2, "Configuration Manager 2007 Overview," introduces primary and secondary sites as well as the use of branch distribution points.
Chapter 6 discusses distributing components across multiple servers.
Chapter 3, "Looking Inside Configuration Manager," discusses extending the schema.
See Chapter 4, "Configuration Manager Solution Design," and Chapter 6 for hardware requirements and planning.
These are questions you will want specific answers for before deploying your first production ConfigMgr site. If the answers are not completely clear, do not pass Go! Spend some additional time reviewing the previous chapters, particularly Chapter 6.
Before starting the installation process for ConfigMgr, verify you have installed and configured all software prerequisites. The next sections briefly describe those requirements. For additional information on prerequisites when installing Configuration Manager, refer to http://technet.microsoft.com/en-us/library/bb694113.aspx.
Configuration Manager 2007 depends on a number of Windows components. Depending on your site design, you may not need all components on each ConfigMgr site in your hierarchy. Table 8.1 provides a brief overview of the Windows components required for each site server and site role. See http://technet.microsoft.com/en-us/library/bb680717.aspx for a complete list of ConfigMgr-supported configurations.
TABLE 8.1 Windows Components Required for ConfigMgr Roles
|Distribution point||WebDAV (Web Distributed Authoring and Version) extensions.|
|To allow content transfer from the distribution point using BITS, HTTP, and HTTPS, you must also have IIS 6.0 (or later) and BITS.||BITS-enabled distribution point.|
|IIS (Internet Information Services) 6.0 or later.||BITS (Background Intelligent Transfer Service). WebDAV extensions.|
|Branch distribution point||Remote Differential Compression (RDC). This is installed by default on Windows Server 2003.
|Management point||IIS 6.0 or later.
|Fallback status point||IIS 6.0 or later.|
|Software update point||Windows Server Update Services (WSUS version 3.0) or later, depending on the ConfigMgr service pack level.
IIS 6.0 or later.
|Server locator point||IIS 6.0 or later.|
|Reporting point||IIS 6.0 or later.
ASP (Active Server Pages).
|System Health Validator point||Windows Server 2008, Enterprise, Datacenter, and Standard Editions.|
|Site servers||All site servers must be a member of an Active Directory domain.
RDC (installed by default on Windows Server 2003).
|ConfigMgr console||.NET Framework 2.0.
Microsoft Management Console (MMC) 3.0.
|Multicast-Enabled Distribution Point||Windows Server 2008,
Windows Deployment Services, and IIS with ISAPI Extensions.
|Virtual Application Streaming||BITS, IIS 6.0 or later.|
|Client Status Reporting||Microsoft .NET Framework 2.0, Office Web Components.|
|SQL Reporting Services Reporting||Microsoft SQL Server 2005 Reporting Services, IIS 6.0.|
Windows Server 2008 will have some default components configured differently from Windows Server 2003. For example, WebDAV extensions require a separate download, and Remote Differential Compression is not enabled by default. For instructions on configuring these components for Windows Server 2008, review the article on configuring Windows Server 2008 for site systems at http://technet.microsoft.com/en-us/library/ cc431377.aspx.
All primary sites use Microsoft SQL Server 2005 with Service Pack 2 or greater for the Configuration Manager database. Consider using Enterprise edition if you are planning to use clustering with more than two nodes or if you have a very large site. SQL Server Standard edition will be sufficient for almost all environments.
Microsoft now supports upgrading the site database to SQL Server 2008 if you apply a hotfix:
- For the base or Released to Manufacturing (RTM) version of ConfigMgr 2007, apply the hotfix discussed at http://support.microsoft.com/kb/955229. Apply the hotfix to the following servers:
- Primary site servers using SQL Server 2008 to host the site database.
- Secondary site servers reporting to primary sites that use SQL Server 2008 to host the database.
- Systems with the Configuration Manager 2007 console installed and connecting to a site that uses SQL Server 2008 to host the database.
- Servers hosting a remote Systems Management Server (SMS) provider.
- For ConfigMgr Service Pack (SP) 1, follow the instructions at http://support. microsoft.com/kb/955262. If applicable, apply the hotfix to the following servers:
- Primary site servers using SQL Server 2008 to host the database.
- Systems with the Configuration Manager console installed and connecting to a site using SQL Server 2008 to host the database.
- Servers hosting a remote SMS provider.
Windows Server Update Services
If you plan to use ConfigMgr to deploy Microsoft security patches, you must install WSUS 3.0 (for ConfigMgr 2007 RTM) or WSUS 3.0 SP 1 (for ConfigMgr 2007 SP 1). For information on WSUS with ConfigMgr, see http://technet.microsoft.com/en-us/library/bb693886. aspx. Chapter 15, "Patch Management," discusses using ConfigMgr 2007 for security patch management.
The Prerequisite Checker
Running the ConfigMgr prerequisite checker confirms whether your system meets the minimum installation requirements for ConfigMgr 2007. The prerequisite checker verifies requirements such as administrative rights, SQL Server version, .NET Framework version, eXtensible Markup Language (XML) version, MMC version, and required Windows updates and hotfixes. Microsoft provides a complete list of setup prerequisite checks at http://technet.microsoft.com/en-us/library/bb680951.aspx.
The ConfigMgr prerequisite checker automatically runs during site installation. You can also run it separately by using one of the following methods:
- Select the prerequisite checker from the ConfigMgr installation menu (Splash.hta) in the root of the installation media.
- Call setup.exe with appropriate command line arguments. For example, to verify the prerequisites for a secondary site, open a command prompt (Start -> Run, and type cmd) and type
Setup.exe /prereq /sec
For a complete list of arguments, see http://technet.microsoft.com/en-us/library/ bb681060.aspx.
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.