Install and Configure System Centre Configuration Manager 2007 R2

System Centre Configuration Manager 2007 R2 is built with Microsoft Operation Framework and IT Information Library. Most common uses of System Centre Configuration Manager (SCCM) are software and operating systems deployment. But you can do more then these two common use. SCCM is also used for configuration management, change management, operation management, Assets, Update, patches, driver management, software metering and lots more. Here, I am going to talk basic installation and configuration of SCCM as most of the config and requirements would be different in different organisation.

Systems Requirement

Windows Server 2003 R2 or Windows Server 2003 SP2 or Windows Server 2008 SP2 or Windows Server 2008 R2

Site Server must be a member of Microsoft AD domain

Active Directory Certificate Services

SQL Server 2005 SP2 or latest

IIS with ASP

Web Dav 7.5

.Net Framework (Windows Server 2008 feature) 

BITs Server Extension (Windows Server 2008 feature)

Remote Differential Compression (Windows Server 2008 feature)

Windows Server Update Services 3.0 SP2 (Windows Server 2008 Role)

Microsoft Report Viewer (By default installed with WSUS 3.0 SP2)


 1 2 3 4 5 6 7 8 9 10 11

To install SCCM in native mode, you need certificates to be installed in SCCM server.

12 13 14 15 16 17 18 19 20 21  23 24 25


You just finish installing SCCM. Now you have install WSUS. A complete Guide is available in WSUS Installation link.

SCCM Configuration

In this part, you have to determine what you want to config and achieve through this deployment. Here, I am going to tell pretty basic config and where to go in SCCM R2 console to do admin tasks. However, I reckon, after going through this config you will be able to work around and understand configuration of SCCM you need.

Installation and Site Role Configuration

Expand the Site Management node by selecting Site Management>Site Settings>Site Systems>New Roles

There are several roles available here, you have to make choice of roles depending on your deployment structure and plan.

Client Installation

Site Management>Site Settings>Client Agents>Computer Client Agent

Site Management>Site Settings>Boundaries>New Boundaries>IP Range

Site Management>Site Settings>Discovery Methods

Site Management>Site Settings>Client Installation Method>Client push Installation>Right Client Property

Navigate to Computer Management>Collections>All Systems

These above task are incomplete because you have to decide IP range, discovery methods and client push property.

Software Distribution

Site Database>Computer Management>Software Distribution>Packages>Actions>Packages from definition>Configuration manager client update

Site Database>Computer Management>Software Distribution>Advertisement>Right client>New>Advertisement

This is pretty simple part, you have to package software which you one to deploy and advertise them through SCCM console.

Software Updates

In the Configuration Manager console, go to System Center Configuration Manager>Site Database>Site Management> Site Settings>Site Systems.

Depending on whether you create a new site system server or add the Software Update Point role to an existing site system. Depending on which you choose, take the next step:


New Site System with Software Update Point

Right-click Site Systems> click New>choose Server.


Add the Software Update Point Role to an Existing Server

Right-click the site system you want to use, and then click New Roles.

Site Management>Site Settings>Component Configuration>Software update Point Component>Right Click>Property

Site Management>Site Settings>Component Configuration>Software distribution>Right Click>Property

This part is basically integrating WSUS with SCCM. WSUS and SCCM can be single server or separate server. You have to make secure of http port because SCCM’s default http port config is port 80 and WSUS can be deployed using port 8530.

Operating System Deployment

Distributing the Boot Image Package

From within the Configuration Manager console, expand Site Database>Computer Management>Operating System Deployment> select Boot Images.

You will notice two boot images for various platforms, one for x64 bit (Boot Image [x64]) and the other for x86 devices. For the purpose of this book, we will concentrate on the x86 boot images, but there is basically no difference in configuring one or the other. The images are configured during the installation of Configuration Manager 2007. However, there are no distribution points assigned for either of the boot images.

To configure a distribution point, expand Boot Images>Boot Image (x86), and click Distribution Points.

Right-click Distribution Points, and select New Distribution Point. This opens the New Distribution Points Wizard’s Welcome page; click Next to continue.

Select the distribution point you want to use on the Copy Package page, and click Next.

Then on the Wizard Completed page, click Close. It will take some time to copy the boot image package up to the distribution point.

Developing a Task Sequence for Creating a Capture Image

In the Configuration Manager console, expand Site Database> Computer Management>Operating System Deployment.

From within the Operating System Deployment node>right-click Task Sequences>select Create Task Sequence Media.

On the Select Media Type page, select Capture Media, and then click Next. By selecting Capture Media, you will be creating the capture media that will be used to capture the operating system image.

On the wizard’s Media Type page, you can select the type of media to create.

For this example, select DVD Set, specifying the media file location, and click Next.

On the Boot Image page, specify the boot image and distribution point you want to use. Click Browse, and select the boot image. Click Next to continue.

Click Next on the Summary page, and Configuration Manager 2007 will begin creating the capture media ISO file.

Finally, you will be presented with the Wizard Completed page, where you can click Close.

You can now burn that ISO file to a DVD and use that DVD to boot up the computers in which you will be building your operating system image.

Creating an Image of a Reference Computer

To begin creating an image of the reference computer, insert the DVD that was created from the OSDCapture.ISO file you created earlier. Run TSMBAutorun.exe located in the SMS\Bin\i386 folder on the DVD. This opens the Image Capture Wizard

Clicking Next opens the Image Destination page, allowing you to specify where to copy the image when the capture is completed. Fill in the correct information>click Next. As you can see, we copied the WIM file to our site server.

You will now be able to add some information about the image on the Image Information page. This page allows you to fill in the Created By, Windows Version, and Description fields for the WIM file.

On the Summary page, click Finish to begin the capture phase. An Installation Progress window appears, telling you that the capture wizard is working and running in the background. When the capture is complete, a System Restart message will appear, and the system will reboot.When the system reboots, it will boot into WinPE, begin the capture phase of the system.

You have wait for while for operating system is being captured.

Once the image capture is complete, you will be prompted with the Image Capture Wizard success message. Clicking OK will allow the machine to reboot and return to the operating system.

Packaging and Advertising the Image

Now you need to configure the image as a new package. Its ready to deploy to another system:

Open the Configuration Manager console, and expand Site Database>Computer Management>Operating System Deployment.

The WIM file that you just created needs to be created as an available operating system for Configuration Manager 2007. To add this WIM file, click Operating System Images under the Operating System Deployment node, and click Add Operating System Image from the Action pane.

This opens the Add Operating System Image Wizard’s Data Source page, Ensure that the Path field points to the location where the WIM file was created, and click Next.

The General page, allows you to customize the Name, Windows Version and personalized Comments fields for the image file. Fill in the appropriate information, and click Next.

The Summary page will be displayed, so click Next, and then finally the Wizard Completed screen will appear. On this page, click Close.

Distributing and Deploying the Image

Expand Site Database>Computer Management >Operating System Deployment> Operating Systems Images, and expand the image.

You will see the same node structure under this package as you would for a normal package.

Right-click the Distributions Point node, and select New Distribution Point. The same

New Distribution Point Wizard will display, allowing you to select the distribution point you want to use to distribute the image file.

To verify that the package has been successfully installed on the distribution point, while in the Operating System Images node, expand the Windows OS folder, expand the Package Status node, and click the Package Status folder.

Within this folder, you will see the status of the package. When the package has been successfully installed on the distribution point, the Installed column will change from 0 to 1.

Creating PXE Service Points

From within the Configuration Manager console, browse to Site Database, then expand Site

Management>Site Code>Site Settings>Site Systems.

This presents a list of all the site systems configured within your environment. Expand the Site Systems node, and select the server to which you want to add the role of PXE site service point. Right-click the server, and select New Roles.

On the New Site Role Wizard General page, click Next.

You will be presented with the System Role Selection page. Select PXE Service Point> click Next

You will see the PXE Service Point Configuration dialog box. This dialog box informs you that Configuration Manager 2007 must have some UDP ports opened on the server. Click Yes to continue enabling a PXE service point.

The New Site Role Wizard continues and presents the PXE>General page, This will allow you to configure how Configuration Manager allows incoming PXE requests. Click Next when you’re done.

Next the PXE Database page appears, allowing you to configure the account to use to connect with the database.

After you have configured the settings on this page, click Next.

On the Summary page, click Next to apply the settings, and configure the PXE service point.


Now you have to create a task Sequence for deployment, advertising the task sequence and setup a Computer Association. This is just starting point of SCCM. There are heaps of task need to be completed before you can enjoy full functionality of SCCM. I would recommend further study on MOF and SCCM .

7 thoughts on “Install and Configure System Centre Configuration Manager 2007 R2

  1. Hi Raihan,

    I have got a bit of confusion that how can we install the services on the servers like, DNS, DHCP, IIS, FTP, SCCM, WSUS, EXCHANGE SERVER etc. As of my knowledge we should use different different servers for each service. But how can we implement in the company.


    • Hello Madhav,

      DC and DNS resides in same server. sometime administrator put DHCP in DC. thats not a problem. IIS+FTP can be one server or two servers. But rest of the roles are each separate domain member server.



  2. Hi Raihan,

    Can you please tell me where we need to install SCCM, is it in the DC or somewhere else. I was tried to install it on DC but there was a pop up saying use a normal account to install it. So can you please tell me clearly where to install the primary site and secondary site etc.


    • Hello,

      Do not install any application on DC. thats not a best practice. Please install SCCM on a domain member server. Primary site and secondary sites are two domain member server resides in internal networks. Regards, Raihan


      • Is the person, who is dealing with 2nd & 3rd line support, do manage the server operations?

        If dealing with 2nd & 3rd line support what software you use. Like ITIL etc.
        What is multi domain?
        How can we do the server lockdown?
        Shall we configure more than one scope in the same DHCP server?.
        As an administrator do we work directly on server?. If not how ca we?. If so with what admin account we log in?


      • Q1. depends organogram. r u talking about desktop support, server support, wintel, network support?
        Q2. Again there are lot of software available such as remedy, HPOV etc
        Q3. More than one domain
        Q4. use GPO
        Q5.It depends on your networks, VLANs etc
        Q6. Yes you do. Using Domain Admin or Local Admin into the Server, or Service Account

        You should do some homework. Please do not request any homework.


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 )

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

This site uses Akismet to reduce spam. Learn how your comment data is processed.