SCCM 2007 – Part 1: Prerequisite Installation

Pre-requisites for installation of SCCM 2007

1.1         Software requirements for installing SCCM 2007 Server.

       The following software’s are required for completing SCCM 2007 server installation
  • Windows 2003 Standard Edition with Service Pack 2 or Windows Server 2008 plus all latest patches, updates and applicable hot fixes
  • Microsoft Internet Information Services (IIS) 6.0
  • Microsoft SQL Server 2005 Standard version
  • Microsoft SQL Server 2005 Service Pack 2
  • Windows Software Update Services (WSUS 3.0 with SP2)
  • Microsoft System Center Configuration Manager 2007 SP2 Media and R3.
  • Active Directory schema extension has to be performed

1.2         Pre- requisites for SCCM client agent installation.

  • OS like Windows XP SP2/Vista /2000 SP4 are supported. Client machines should be part of AD domain.
  • The following services need to be enabled on client machines:-
    • Automatic updates
    • DNS client
    • Remote Registry
    • Server
    • Windows Management Instrumentation (WMI)
  • Windows Management Instrumentation Driver Extension service needs to be set to manual.
  • Since Domain Administrator credentials will be used for SCCM installation .This user ID should have local administrative privilege on client machines.
  • Windows directory should be shared as Admin$. This administrative share should to be present on client machines.
  • Firewall on Windows XP SP2/Windows Vista machines should be disabled or the required ports should be added in to the exceptions list.
  • Minimum of 5 GB disk space for “System drive” needs to be available on client machines.
Server and site details are as given below:

Server Name
IP address
Site Mode
Site Code
Site Name
Central Primary Site
Bangalore Deskperts House

1.3         Creation of SCCMService account

SCCM service account is required for SCCM 2007 server installation and configuration. This account should have “Domain admin”, “Enterprise admin” and “Schema admin” rights.

Here the account has been created as DESKPERTS\sccmadmin as shown above.
Also create a security group in AD for SCCM. The group created here is SG-APP-CCL-SCCM2007
Add SCCM service account and SCCM server computer account to the CONTOSO\SG-APP-CCL-SCCM2007 group and also add all the site server computer accounts as shown below:-

2        Installing and Configuring IIS for SCCM 2007

IIS needs to be installed prior to installing SCCM 2007 on all site servers. The following below given steps detail the procedures that are required for configuring IIS. Log on to the server with the SCCM service account which has been created and then follow the below given steps.

2.1        To install IIS on Windows Server 2008 R2, follow the steps given below: –

To start Server Manager, click: Start Menu -> All Programs -> Administrative Tools -> Server Manager. The Server Manager window opens.

Right click on Roles and select Add Roles.

Click on Next on the Roles Wizard window as shown above.

 In Select Server Roles window select ‘Web Server (IIS)’ and click on Next

Web Server Role depends on WAS.
The Add Roles Wizard notifies you on any required dependencies; since IIS depends on the Windows Process Activation Service (WAS) feature, the following informational dialog displays. Click on ‘Add Required Role Services’ to continue.

Click on Next to continue as shown above.

The Add Roles Wizard displays a list of all IIS 7.0 features available to install as shown above
Note: – Features comprising the default install are pre- selected.
Select Additional IIS Features to Install Start by checking the box for ASP.NET. The following dialog displays.
The Wizards warns if adding an IIS feature will also cause other features to be installed.
Click on ‘Add Required Role Services’ to continue.

Click on Next on the role services window as shown above

Click on ‘Install’ on the confirmation window as shown above.

Click on Close to complete the wizard as shown above.


The following Web Server role services should be installed for SCCM 2007

IIS Role Services
Web Server
Common HTTP Features
Static Content
Default Document
Directory Browsing
HTTP Errors
HTTP Redirection
Webdav Publishing

Application Development
.NET Extensibility
ISAPI Extensions
ISAPI Filters

Health and Diagnostics
HTTP logging
Logging tools
Request Monitor

Basic Authentication
Windows Authentication
URL Authorization
Request Filtering
IP and Domain Restrictions

Static Content Compression

Management Tools
IIS Management Console
IIS Management Scripts and Tools
Management Service
IIS 6 Management Compatibilty
IIS 6 Metabase Compatibility
IIS 6 WMI Compatibility
IIS 6 Scripting Tools
IIS 6 Management Console

Open IIS manager and navigate to Default Web Site as shown below.

Select Default Web Site and select WebDAV Authoring Rules and click on Open Feature as shown above.

Click on Enable WebDAV

Click on Add Authoring Rules

Select All content, All users and provide Readpermissions as shown above.

Again click Add Authoring Role

Select All content, Specified users (centrum\sccmadmin) and provied Read, Source and Write permissions as shown above.

The permissions provided in the authoring rule will appear as shown above.

Select WebDAV Settings and change the Property behavior as shown above and click on Apply to save the changes for WebDAV Settings.

3        Installing additional server features.

Go to Server Manager. Right click on Roles and add New Roles.
Select Remote Differential Compression and click Next.

Select Install on confirmation page.

Click Close on the Results page.

Go to Server Manager. Right click on Roles and add New Roles.

Select BITS and its sub-components. Click Next.

Click Install on the confirmation page.

Click Close on results screen.

4         Installing SQL 2008 and SP3

4.1        Installation of SQL server components

Go to Server Manager, features and right click select add new features. Select .Net Framework 3.5.1 features.

Select all .Net components. Click Next on feature selection.

Click Install on Confirmation page.

Click Close on results page.

4.2       Installation of SQL server 2008 SP3

Install SQL 2008 with Service Pack 3 using Local system account and Windows Authentication. SQL2008 needs to be installed with the default options.

5        Installation of WSUS server

WSUS 3.0 with SP 2 is required for patch management through SCCM. All Microsoft software updates required for client machines will be deployed through SCCM. WSUS will get integrated with Software Update Point in SCCM which will download the required updates from Microsoft database.
To install WSUS, run the setup and the installation wizard will begin as shown below:-

Click on Next to continue

On Server Roles Page Select Windows Server Update Services.

Select Add Required Role Services for WSUS prompt.

Click Next on Web Server page.

Leave default selection. Click Next on IIS Role Services page.

Click Next on WSUS page.

Click Install on Confirmation page.

Installation will progress and start downloading the latest WSUS update from internet.

WSUS SP2 installation wizard will appear.

Select to accept License agreement and click Next

Provide the destination to store updates and click Next

Provide the installation path as shown above and click Next

As IIS has been already installed, select to use existing IIS default web site and click Next

Click on Next on the summary page as shown above

The setup will take some time

Click on Finish to complete the setup of WSUS.

Click Close on the Results page.

After the installation of WSUS is complete, a new window to configure WSUS will open. Do not configure WSUS now and click on Cancel. WSUS will be configured through Software Update point present in SCCM after the installation of SCCM Primary site server.

6       Extending Active Directory Schema for SCCM 2007

In System Center Configuration Manager 2007, SCCM clients can use Active Directory to locate SCCM resources. Before SCCM clients can query Active Directory for these resources, the Active Directory schema must be extended and the SCCM resource information must be published to Active Directory. Clients running Windows 7, Windows XP, Windows 2000 or Windows Server 2003 will automatically detect the server locator points and management points without generating Windows Internet Name Service (WINS) traffic
The Systems Management container must be created and SCCM must be granted full control to the container so that SCCM publishes information to active directory. If SCCM is granted full control to the System container, SCCM can automatically create the System Management container under the System container.
If the necessary permissions are not granted, SCCM cannot publish any information to Active Directory, and SCCM clients cannot use features such as automatic site assignment and global roaming. By default, SCCM also generates status error message 4913 until it can successfully publish to Active Directory.
To extend the active directory schema, Run the command-line tool ExtADSch prior or post SCCM installation. This ExtADSch.exe can be located in the \SCCMSETUP\BIN\I386 folder on the SCCM 2007 CD.  The ExtADSch tool results can be found in the ExtADSch.log. These log files are created in the root directory of %system% drive.

To verify the Active Directory schema is extended, go to C: drive and open ExtADSch.log file as shown

Active Directory SCHEMA EXTENSION creates FOUR Classes and 10 Attributes. The details of which are provided below
·         MS-SMS-ManagementPoint
·         MS- SMS -ServerLocatorPoint
·         MS- SMS -Site
·         MS- SMS -RoamingBoundaryRange
Attribute common names that are implemented and used by SCCM 2007 sites include the following:
·         MS- SMS -Site-Code
·         MS- SMS -Assignment-Site-Code
·         MS- SMS -Site-Boundaries
·         MS- SMS -Default-MP
·         MS- SMS -Device-Management-Point
·         MS- SMS- MP-Name
·         MS- SMS -MP-Address
·         MS- SMS -Ranged-IP-Low
·         MS- SMS -Ranged-IP-High

Open Active Directory Users and Computers and switch to Advanced View. Navigate to System>System Management. The System Management container gets created after extending the schema in AD.  Add the Security Group created above and provide Full Control security for the System Management container as shown below: –

Leave a Reply

Fill in your details below or click an icon to log in: Logo

You are commenting using your account. Log Out /  Change )

Google photo

You are commenting using your Google account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )

Connecting to %s