Step by Step Guide Installing SCCM 2007

Step by step guide installing SCCM 2007 Part 1
System Center Configuration Manager 2007 is the solution to comprehensively assess, deploy, and update
your servers, clients, and devices—across physical, virtual, distributed, and mobile environments. Optimized
for Windows and extensible beyond, it is the best choice for gaining enhanced insight into, and control over,
your IT systems.
In this article we will cover the ZTI - Zero Touch Installation.
This guide covers integeration of various technologies which are mentioned below:
1. Windows 2008 R2 x64 BIT.

2. SQL 2008 SP1.
3. Windows Deployment Services.
4. Microsoft Deployment Toolkit - MDT
5. Internet Information Services 7.5.
6. System Center Configuration Manager 2007 - SCCM.
Prerequisites for Installing Configuration Manager

This Guide will be split in various parts & currently I am not even sure how many parts will there be in the
end but I will update this as I go along.
Planning & Installation SCCM 2007

1. Install Windows 2008 ( PILOT-DC-01 + PILOT-SCCM-01 )
2. Configure Domain controller & Configure DNS
3. Configure DHCP
4. Install & configure Windows Deployment Server ( WDS )
5. Perform Windows Update.
6. Create Users for SCCM
7. Install & configure IIS 7.5 ( Internet Information Services )
a. Install relevant IIS features.
b. Install & configure Webdav.
c. Install Desktop Experience
d. Configure Authentication + Authorization + Install Remote Differential Compression + BITS
e. Configure Application Config file & than test WebDav
8. Install SQL 2008 ( including sp1 )
9. Install WSUS.
10. Extend Active Directory Schema.
Step 1: Extend the Active Directory schema.
Step 2: Create the System Management container.
Step 3: Set security permissions on the System Management container.
Step 4: Add the Site Server to the Administrators Security Group.
11. Add DHCP Scope options for PXE.
12. Install System Center Configuration Manager 2007 - SCCM
13. Install System Center Configuration Manager 2007 - ( SP2 )
a. Uninstall AIK & Install AIK version compatible with Windows 7.
Configuring SCCM 2007

It is suggested to install SCCM first in an test environment then install in real
environment
14. Configure the Network Access Account.
Depending on the media you are using the SCCM build versions may vary accordingly.
RTM 4.00.5931.0000
SP1 4.00.6221.1000
SP2 BETA 4.00.6425.2000
SP2 Release Candidate 4.00.6468.2001
SP2 Final 4.00.6487.2000
SP2 + R2 No Build changes ( Only features are
added )
Before we go ahead let me quickly cover the setup we are working with.
Fully qualified domain name (FQDN): PILOT.LOCAL
PILOT-DC-01: Domain Controller
Property Value Property Value

IP address 192.168.1.200 Subnet mask 255.255.255.0
Default gateway 192.168.1.254 DNS 192.168.1.200
PILOT-SCCM-01: System Center Configuration Manager 2007 - SCCM
Property Value Property Value

IP address 192.168.1.201 Subnet mask 255.255.255.0
Default gateway 192.168.1.254 DNS 192.168.1.200
How to Install Windows Server 2008 Step by Step

Windows Server 2008 R2 builds on the award-winning foundation of Windows Server 2008, expanding existing technology and adding
new features to enable organizations to increase the reliability and flexibility of their server infrastructures. New virtualization tools,
Web resources, management enhancements, and exciting Windows 7 integration help save time, reduce costs, and provide a platform for
a dynamic and efficiently managed data center. Powerful tools such as Internet Information Services (IIS) version 7.5, updated Server
Manager and Hyper-V platforms and Windows PowerShell version 2.0 combine to give customers greater control, increased efficiency,
and the ability to react to front-line business needs faster than ever before.
Let's take a quick look how we cna isntall Windows 2008 R2 in a couple of minutes.
Component Requirement
Minimum: 1.4 GHz (x64 processor)
Processor
Note: An Intel Itanium 2 processor is required for Windows Server 2008 for Itanium-Based Systems

environment
Minimum: 512 MB RAM
Memory
Maximum: 8 GB (Foundation) or 32 GB (Standard) or 2 TB (Enterprise, Datacenter, and Itanium-Based
Systems)
Minimum: 32 GB or greater
Foundation: 10 GB or greater
Disk Space Requirements
Note: Computers with more than 16 GB of RAM will require more disk space for paging, hibernation, and dump
files
Display Super VGA (800 � 600) or higher resolution monitor
Other DVD Drive, Keyboard and Microsoft Mouse (or compatible pointing device), Internet access (fees may apply)

environment
environment
environment
environment
environment
environment
environment
In this part we will prepare the earlier install
of Windows 2008 & configure Active Directory
+ DNS.
How to install Active Directory on Windows 2008
Before you start following this article you must be aware this is simply a lab setup and you need to assign
relevant ip address, hostnames & domain names which are relavant to your enviroment / organisation.
I will be using the following:
Hostname=PILOT-DC-01
IP address=192.168.1.200
Subnet Mask=255.255.255.0

environment
Domain name=PILOt.LOCAL
Forest = New
Partition: NTFS ( 60 GB )
The Virtual machine used has been installed as of date when this article was written with a default install of
Windows 2008 R2 x64 BIT + all MS critical updates.
Configure IP Address details as required. As this is the only DNS server and the first DC we will point the
DNS to itself.

environment
Start Server Manager and select Roles > Add Roles
Click Next >

environment
Once you select Active Directory Domain Service you will see this dialogue box it is self explanatory. :)
Click ok

environment
Click Next > & move ahead.

environment
environment
Some Useful tips on this page if you would like to reaand than move ahead pelase do so.
Click next >

environment
environment
Click Next >

environment
once the wizard is complete
Click Close >

environment
There are various ways you can start and compelte the DCPROMO wizard. We choose to install it using the
Server Manager indicated in the screenshot below.

environment
Click advanced check box.
Click Next >

environment
Read the text carefull before you move ahead.
Click Next >

environment
Select New Domain in a New Forest.
Click Next >

environment
Decide your FQDN for the new forest root domain. I have chosen to go with the
PILOT.LOCAL.
Click Next >

environment
DCPROMO wizard verifies if this name is already in use on the same VLAN etc....

environment
We have used the default name PILOT as the NETBIOS name, you can change it if you choose too.

environment
Set you FFL right now we have decided to use Windows 2008 R2 as that is the first DC + no other
DC in this domain. We also would like to research and test the new FFL features. Please make your
appropriate choice here as this change is irreversible.
Click Next >

environment
The wizard will install DNS & configure it for you.
Click Next >

environment
Click Yes >

environment
We currently only have a single partition so we ahve no choice of changing these paths but
please make your partition choice.
Click Next >
Enter your recovery mode password and record it safely.
Click Next >

environment
You can export these settings and also could use the answer file to run the same wizard again
with relevant changes tot he file for any options you want for example: We could ahve done all of
the above using command line and the answer file.
1. A new DC & in a new forest.

2. A Addtional DC in an existing forest.
3. etc..
The wizard applies all the configuration we did earlier.

environment
Click Finish & Reboot.

environment
After reboot we can verify the DNS server has been auto installed and configured by the DCPROMO wizard.
All we need to do now is create the DNS reverse lookup zone as that is done manually.

environment
Click Next >
Click Next >

environment
Click Next >
Define your ip subnet details.

environment
Click Next >
Click Next >

environment
Click Finish >
Now the reverse lookup zoone shows up in DNS.
The domain controller does show up in ADUC.

environment
New SYSVOL & NETLOGON shares are also available & accessible.
For any further troubleshooting or for verification you can run dcdiag.exe
netdiag.exe
log the results into a text file and view the outcome.
The reason for me walking you through these steps is to ensure they are done in a methodical approach &
steps are not skipped out of sequence.
How to Install and Configure Windows Server 2008 DHCP

Server
Dynamic Host Configuration Protocol (DHCP) is a network protocol that enables a server to automatically
assign an IP address to a computer from a defined range of numbers (i.e., a scope) configured for a given
network.

environment
When a computer uses a static IP address, it means that the computer is manually configured to use a
specific IP address. One problem with static assignment, which can result from user error or inattention to
detail, occurs when two computers are configured with the same IP address. This creates a conflict that
results in loss of service. Using DHCP to dynamically assign IP addresses minimizes these conflicts.
To start the DHCP installation process, you can click Add Roles from the Initial Configuration Tasks window
or from Server Manager Roles > Add Roles.
When the Add Roles Wizard comes up, you can click Next on that screen.
Next, select that you want to add the DHCP Server Role, and click Next.

environment
environment
Click Next >

environment
I have taken this opportunity to configure some basic IP settings and configure my first DHCP Scope.
Click Next >

environment
Next, enter Primary & Secondary DNS Servers (as you see above)
Note: I have not entered any ip is the alternate dns simply because I only have a single DC right currently.
Click Next >

environment
environment
I dont use WINS on my network and I clicked Next

environment
Configure your scope details according to your network.

environment
Click next >

environment
environment
Account with permission in AD.
Click Next >

environment
environment
Done

environment
Verify your configuration by opening your DHCP server. You can now carry on creating further scopes if your
network has more than 1 vlan or you can modify the settings configured earlier.
Configure a client pc to obtain ip address.

go to command prompt Start > Run > cmd > ipconfig /all
You will see tha a ip address has been allocated by the new scope to this client pc.
I am assuming that you have now installed PILOT-SCCM-01 Operating System.
Windows 2008 R2 x64 BIT
The Windows Deployment Services is the updated and redesigned version of Remote Installation Services
(RIS).
environment
In this lab because we want to use the rich features of System Center Configuration Manager 2007 & not
WDS; is capable of deploying images by itself with limited functionality.We will use WDS to assist us in this
process.
WDS is the PXE server for System Center Configuration Manager 2007. System Center Configuration
Manager 2007 hands off the request to WDS after checking it's own database to make sure it knows about
the computer.
Note: System Center Configuration Manager 2007 R2 also introduces the ( Unknown computers support )
once again.
Known issues with configuring Windows Deployment Services
If you are running Windows Deployment Services and a non-Microsoft DHCP server on the same computer,
in addition to configuring the server to not listen on port 67, you will need to use your DHCP tools to add
Option 60 to their DHCP scopes.
If DHCP is installed on a server that is located in a different subnet, then you will need to do one of the
following:
(recommended) Configure your IP Helper tables. All DHCP broadcasts on UDP port 67 by client computers
should be forwarded directly to both the DHCP server and the Windows Deployment Services PXE server.
Also, all traffic to UDP port 4011 from the client computers to the Windows Deployment Services PXE server
should be routed appropriately (these requests direct traffic to the server, not broadcasts).
Add DHCP options 66 and 67. Option 66 should be set to the Windows Deployment Services server, and
option 67 should be set to REMINST/SMSBoot/x64/pxeboot.com.
NOTE: In this lab WDS is also our SCCM server & DHCP is running on our Domain Controller !!!
Prerequisites for installing Windows Deployment Services:
Active Directory. PILOT-DC-01

DHCP. You must have a working Dynamic Host Configuration Protocol (DHCP) server with an active scope
on the network because Windows Deployment Services uses PXE, which relies on DHCP for IP addressing.
DNS. PILOT-DC-01
NTFS partition: The server running Windows Deployment Services requires an NTFS file system volume for
the image store.
To install the role by using the command line, run one of the following two commands:
For Deployment Server, run ServerManagerCmd -install WDS.

For Transport Server, run ServerManagerCmd -install WDS-Transport.
To install the role by using Server Manager, click Add roles, which is located in the Roles Summary pane.
Click Next and then select Windows Deployment Services.

environment
environment
Click Next >

environment
Click Next >
Click Next >
Click Finish
Note: In some documents you will come across where you will be instructed NOT to configure WDS & some
will recommend configuring WDS initial wizard & not importing any images.
From my testing you can do either and it works fine results are indentical.
I personally ensure that the PXE request delay (explained further in the article) in WDS is set to longer
than the PXE service point in SCCM.

environment
Right click > Configure Server

environment
environment
environment
environment
environment
Untick the " Add images "
Click Finish.

environment
environment
We need to allow WDS to respond to all ( Known & Unknown ) Computers.
Also set the PXE response delay to 1
Note: This will ensure that SCCM PXE service point will respond before WDS responds.

environment
We need to ensure that the WDS service is also set to " Automatic Delayed Start " this simply ensures
that WDS service does not fail at auto start or else everytime you restart the server WDS services will need
to be manually restarted.
When WDS service is set to "Automatic Delayed Start" this change is also reflected in the registry at the
following location.

environment
Step by step guide installing SCCM 2007 Part 5 we will configure Windows Update on both the servers i.e.
PILOT-DC-01 & PILOT-SCCM-01

environment
Reboot your servers and ensure all updates have been installed successfully.

Step by step guide installing SCCM 2007 Part 6 series we will now create accounts which will be used by
System Center Configuration Manager 2007 & SQL 2008.
Open ADUC and create two accounts:
1. SQL 2008.
2. SCCM 2007.
Step by step guide installing SCCM 2007 Part 7 A

Step by step guide installing SCCM 2007 Part 7 series will have multiple pages to this Part 7.
a. Install relevant IIS features.

b. Install & configure Webdav.
c. Install Desktop Experience
d. Configure Authentication + Authorization + Install Remote Differential Compression + BITS.
e. Configure Application Config file & than test WebDav.
environment
Install the following IIS features:
Role service Status

Web Server Installed
Common HTTP Features Installed
Static Content Installed
Default Document Installed
Directory Browsing Installed
HTTP Errors Installed
HTTP Redirection Installed
Web Dav Publishing Installed
Note: If the Operating System is NOT R2 than this needs to be

downloaded separately and installed as it is now integrated with R2 IIS
7.5
For IIS 7.0 you can download Webdav from the following locations.
Microsoft WebDAV Extension for IIS 7.0 (x64)
Microsoft WebDAV Extension for IIS 7.0 (x86)

Application Development Installed
ASP.NET Installed
.NET Extensibility Installed
ASP Installed
CGI Not installed
ISAPI Extensions Installed
ISAPI Filters Installed
Server Side Includes Not installed
Health and Diagnostics Installed
HTTP Logging Installed
Logging Tools Installed
Request Monitor Installed
Tracing Installed
Custom Logging Not installed
ODBC Logging Not installed
Security Installed
Basic Authentication Installed
Windows Authentication Installed
Digest Authentication Not installed
Client Certificate Mapping Authentication Not installed
IIS Client Certificate Mapping Authentication Not installed
URL Authorization Installed
Request Filtering Installed
IP and Domain Restriction Installed
environment
Role service Status
Performance Installed
Static Content Compression Installed
Dynamic Content Compression Not installed
Management Tools Installed
IIS Management Console Installed
IIS Management Scripts and Tools Installed
Management Service Installed
IIS 6 Management Compatibility Installed
IIS 6 Metabase Compatibility Installed
IIS 6 WMI Compatibility Installed
IIS 6 Scripting Tools Installed
IIS 6 Management Console Installed
FTP Publishing Service Not installed
FTP Server Not installed
FTP Management Console Not installed
Once these services have been installed test IIS to check if it does respond & the local firewall is not
blocking any ports.
http://localhost
This should display the IIS 7.5 welcome page.

environment
Step by step guide installing SCCM 2007 series Part 8 we will cover how to install SQL 2008 SP1 in
preparation for installing SCCM 2007.
Step by Step guide to installing SQL Server 2008
Step by Step guide to installing SQL Server 2008 in this article I plan to cover the installation of SQL
2008 std edition. The initial idea behind this article was to only integerate this article with the SCCM
2007 step by step guide but than I thought this can help others who dont need SCCM at all, hence a
entirely independant article for anyone who needs any help with installing SQL 2008.
What's new in SQL 2008
Component Requirement
2
Framework SQL Server Setup installs the following software components required by the product:
·.NET Framework 3.5 SP11
·SQL Server Native Client

environment
·SQL Server Setup support files
Software2 SQL Server Setup requires Microsoft Windows Installer 4.5 or a later version
After installing required components, SQL Server Setup will verify that the computer where SQL Server 2008 will be
installed also meets all the other requirements for a successful installation. For more information, see Check
Parameters for the System Configuration Checker.
Network Network software requirements for the 64-bit versions of SQL Server 2008 are the same as the requirements for the
Software 32-bit versions.
Supported operating systems have built-in network software. Stand-alone named and default instances support the
following network protocols:
·Shared memory
·Named Pipes
·TCP/IP
·VIA
Note Shared memory and VIA are not supported on failover clusters.
Virtualization SQL Server 2008 is supported in virtual machine environments running on the Hyper-V role in Windows Server 2008
R2 and Windows Server 2008 Standard, Enterprise and Datacenter editions. The virtual machine must run an operating
system supported for the specific SQL Server 2008 edition listed later in this topic.
In addition to resources required by the parent partition, each virtual machine (child partition) must be provided with
sufficient processor resources, memory, and disk resources for its SQL Server 2008 instance. Requirements are listed
later in this topic.3
Within the Hyper-V role on Windows Server 2008, a maximum of four virtual processors can be allocated to virtual
machines running Windows Server 2008 32-bit or 64-bit editions. A maximum of 2 virtual processors can be allocated
to virtual computers that are running Windows Server 2003 32-bit editions. For virtual computer that host other
operating systems, a maximum of one virtual processor can be allocated to virtual computers.
Notes:
·It is recommended that SQL Server 2008 be shut down before shutting down or the virtual machine.
·For more information about the Hyper-V role in Windows Server 2008, see the Windows Server 2008 Web site.
·Guest failover clustering is supported in SQL Server 2008. For more information about the supported versions of SQL
Server and operating systems for guest failover clustering, and the support for virtualization, see Support policy for
Microsoft SQL Server products running in a hardware virtual environment.
Internet Microsoft Internet Explorer 6 SP1 or a later version is required for all installations of SQL Server 2008. Internet
Software Explorer 6 SP1 or a later version is required for Microsoft Management Console (MMC), SQL Server Management
Studio, Business Intelligence Development Studio, the Report Designer component of Reporting Services, and HTML
Help.
Hard Disk Disk space requirements will vary with the SQL Server 2008 components you install. For more information, see Hard
disk space requirements later in this topic.

environment
Drive A CD or DVD drive, as appropriate, is required for installation from disc.
Display SQL Server 2008 graphical tools require VGA or higher resolution: at least 1,024x768 pixel resolution.
Other Devices Pointing device: A Microsoft mouse or compatible pointing device is required.
1
The following .NET Framework versions are required:
• SQL Server 2008 on Windows Server 2003 (64-bit) IA64 — .NET Framework
2.0 SP2
• SQL Server Express — .NET Framework 2.0 SP2
• All other editions of SQL Server 2008 — .NET Framework 3.5 SP1
For a detailed breakdown of Hardware & Software requirments for relevant version on SQL 2008
(please click here)
Now we will start by installaing SQL 2008 step by step including screenshots to assist you
all the way in this process.
Before you start the installation, you’ll need to install the .Net 3.5.1 Framework. This comes
pre-installed on Windows 2008 R2 Server, but for earlier versions of Windows, you’ll need to
install it first. This is a straightforward pre-requisite and is usually included as part of the
SQL Server 2008 installation. You can perform a Windows update and install this if it is not
part of your Operating system.

environment
When installation of .NET Framework 3.5 SP1 is complete, click close.
Windows Installer 4.5 is also required, and might be installed by the Installation Wizard. If
you are prompted to restart your computer, restart it, and then restart SQL Server 2008
setup.exe.
Reboot your server before starting your install of SQL 2008 SP1.

environment
Create a copy of you SQL media to your local partition of your server, if your media is
damaged and a file won’t copy, you get to find out now, rather than halfway through the
installation.
From the root folder, double-click setup.exe. To install from a network share, locate the root
folder on the share, and then double-click setup.exe. If the Microsoft SQL Server 2008
Setup dialog box appears, click OK to install the prerequisites, then click Cancel to exit SQL
Server 2008 installation.

environment
Click on the Configuration Checker to ensure you meet the requirments.
All my tests have passed as indicated above so we will move on further.

environment
Click on the Installation hyperlink on the left hand side of the screen >
Click on the "New Server stand-alone installation" link on the right side of the screen
as indicated above.
When the prerequisites are installed, the Installation Wizard will run the SQL Server
Installation Center. To create a new installation of SQL Server 2008, click New Installation
or Add Features to an Existing Installation.

environment
The System Configuration Checker will run a discovery operation on your computer. To
continue, click OK. Setup log files are created for your installation. For more information, see How to: View and
Read SQL Server Setup Log Files.
If any checks have failed, click on the Show details button or "View detailed report link" to
find out the cause, correct it, then click on the Re-run button to perform the checks again.
Note that the product key box may already be populated, depending on which edition you
have.
Note: I have removed the key from the above screenshot. :) Type your product key if it is
environment
not pre-populated. Basically this information is picked automatically from the ini file which is
located under the root of this installation media.
Click in the "I accept the license terms" check box, then click on the Next button again.

environment
Click on the Next button again
Feature Selection >
Select the components for your installation. A description for each component group
appears in the right pane after you select the feature name. You can select any combination
of check boxes.
You can also specify a custom directory for shared components by using the field at the
bottom of the Feature Selection page. To change the installation path for shared
components, either update the path in the field at the bottom of the dialog box, or click
Browse to move to an installation directory. The default installation path is C:\Program
Files\Microsoft SQL Server\100\.

environment
Click on the Next button

environment
Instance ID — By default, the instance name is used as the Instance ID. This is used to
identify installation directories and registry keys for your instance of SQL Server. This is the
case for default instances and named instances. For a default instance, the instance name
and instance ID would be MSSQLSERVER. To use a nondefault instance ID, select the
Instance ID check box and provide a value.
For most installations, keep the default settings.
Click on the Next button >

environment
The Disk Space Requirements page calculates the required disk space for the features that
you specify. Then it compares the required space to the available disk space.
This screen just tells you if you have sufficient disk space on the drive you’re installing to,
and what’s going to be installed where.

environment
On the Server Configuration — Service Accounts page, specify login accounts for SQL Server
services. The actual services that are configured on this page depend on the features that
you selected to install. You can assign the same login account to all SQL Server services, or
you can configure each service account individually. You can also specify whether services
start automatically, are started manually, or are disabled. Microsoft recommends that you
configure service accounts individually to provide least privileges for each service, where
SQL Server services are granted the minimum permissions they have to have to complete
their tasks.

environment
Note: If this install is only being used for SCCM on the SCCM server kindly change the
Authentication in the screenshot above to only windows authentication as SCCM 2007
will complain at the time of the installation pre req checks.

environment
Step by step guide installing SCCM 2007 Part 9 we will cover installation of WSUS. This can be done after
installing SCCM 2007. The Microsoft Windows Server Update Services (WSUS) 3.0 administrator console is
required on the Configuration Manager 2007 site server to allow the site server and remote Configuration
Manager consoles to configure and synchronize software update points. The WSUS 3.0 Administration
console can be installed using the wizard or installed silently from a command line.
We will need WSUS in future anyways in this lab so I have decided to not only install the console including
the full product 3.5 SP2.
Before a software update point can successfully be installed and configured on a site system server in
Configuration Manager 2007, Windows Server Update Services (WSUS) 3.0 must be installed on the server.
Note: DO NOT confgiure WSUS though the Configuration Wizard.
The WSUS 3.0 configuration wizard automatically starts after the Setup wizard completes. Because
Configuration Manager 2007 manages the WSUS settings, you should exit the configuration wizard after it

environment
opens.
Note: while this wizard is completing it takes a long period of time to download the new version from
Microsoft so please be patient and watch out for the window below to open and start eh installation.
Click Install

environment
Click Next

environment
Click I accept the terms of the License agreement, and then click Next.
Select Store updates locally, specify the path, (point it to a partition of your choice which has enough
free space to store the updates) and then click Next

environment
Click Next
Note: Do not install WSUS integrated with SQL 2008 if you have purchased a license which is the integrated
solution with SCCM 2007 on a single server i.e. SCCM & SQL bundle.
This is in breach of your license agreement as only SCCM database can reside on the installation of SQL
2008.
It is one of those weird things which I don’t understand why it had to be such when WSUS can be integrated
within SCCM I am sure they should allow the WSUS database on SQL 2008 as well.
*** Contact Microsoft Licensing for complete clarity ***

environment
If you decide to change this behaviour make sure you keep a note of this as this information will be required
when we confgure WSUS using SCCM.
Click Next >

environment
Click Next

environment
Click Finish
environment
Close

environment
DO NOT confgiure WSUS though the Configuration Wizard.
The WSUS 3.0 configuration wizard automatically starts after the Setup wizard completes. Because
Configuration Manager 2007 manages the WSUS settings, you should exit the configuration wizard after it
opens.

Step by step guide installing SCCM 2007 Part 10 I will cover how to prepare Active Directory 2008
Schema in preparation for installaing System Center Configuration Manager 2007.
Extending the Active Directory schema is a forest-wide action and must only be done once per forest.
Extending the schema is an irreversible action and must be done by a user who is a member of the Schema
Admins Group or by someone who has been delegated sufficient permissions to modify the schema. If you
choose to extend the Active Directory schema, it may be done before or after setup.

environment
While some Configuration Manager features are dependent on extending the schema, such as Network
Access Protection in Configuration Manager and global roaming, there may be workarounds for not
extending the schema to enable other Configuration Manager features.
Note: Before you proceed any further please ensure:
1. The account you are using for this part has Schema Admin rights in Active Directory. i.e. Schema Admins
Group.
2. The Domain controller has verified backups.
Four actions need to be taken in order to successfully enable Configuration Manager clients to query Active
Directory Domain Services to locate site resources:
Step 3: Set security permissions on the System Management container.
The Active Directory schema can be extended for Configuration Manager 2007 by running the ExtADSch.exe
utility or by using the LDIFDE command-line utility to import the contents of the ConfigMgr_ad_schema.ldf
LDIF file. Both the utility and the LDIF file are located in the SMSSETUP\BIN\i386 directory of the
Configuration Manager 2007 installation files.

Note: For extending schema there is no x64 BIT version of extadsch.exe you need to use x386 version
indicated below.
As indicated below this is a dump of the entire SCCM 2007 media CD.
Run extadsch.exe, located at \SMSSETUP\BIN\I386 on the installation media, to add the new classes and

environment
attributes to the Active Directory schema.
This screen will flash for a few seconds and close automatically. If you would like to look at the
details please read further.
Verify that the schema extension was successful by reviewing the extadsch.log located in the root of the
system drive.

environment
======ExtADSch.log log Output=======
<12-27-2009 13:32:00> Modifying Active Directory Schema - with SMS extensions.
<12-27-2009 13:32:01> DS Root:CN=Schema,CN=Configuration,DC=pilot,DC=local
<12-27-2009 13:32:02> Defined attribute cn=MS-SMS-Site-Code.
<12-27-2009 13:32:02> Defined attribute cn=mS-SMS-Assignment-Site-Code.
<12-27-2009 13:32:02> Defined attribute cn=MS-SMS-Site-Boundaries.
<12-27-2009 13:32:02> Defined attribute cn=MS-SMS-Roaming-Boundaries.
<12-27-2009 13:32:02> Defined attribute cn=MS-SMS-Default-MP.
<12-27-2009 13:32:02> Defined attribute cn=mS-SMS-Device-Management-Point.
<12-27-2009 13:32:02> Defined attribute cn=MS-SMS-MP-Name.
<12-27-2009 13:32:02> Defined attribute cn=MS-SMS-MP-Address.
<12-27-2009 13:32:02> Defined attribute cn=mS-SMS-Health-State.
<12-27-2009 13:32:02> Defined attribute cn=mS-SMS-Source-Forest.
<12-27-2009 13:32:02> Defined attribute cn=MS-SMS-Ranged-IP-Low.
<12-27-2009 13:32:02> Defined attribute cn=MS-SMS-Ranged-IP-High.
<12-27-2009 13:32:02> Defined attribute cn=mS-SMS-Version.
<12-27-2009 13:32:02> Defined attribute cn=mS-SMS-Capabilities.
<12-27-2009 13:32:03> Defined class cn=MS-SMS-Management-Point.
<12-27-2009 13:32:03> Defined class cn=MS-SMS-Server-Locator-Point.
<12-27-2009 13:32:03> Defined class cn=MS-SMS-Site.
<12-27-2009 13:32:03> Defined class cn=MS-SMS-Roaming-Boundary-Range.
<12-27-2009 13:32:03> Successfully extended the Active Directory schema.
<12-27-2009 13:32:03> Please refer to the SMS documentation for instructions on the manual
<12-27-2009 13:32:03> configuration of access rights in active directory which may still
<12-27-2009 13:32:03> need to be performed. (Although the AD schema has now be extended,
<12-27-2009 13:32:03> AD must be configured to allow each SMS Site security rights to
<12-27-2009 13:32:03> publish in each of their domains.)
======ExtADSch.log log Output=======
Configuration Manager does not automatically create the System Management container in Active Directory
Domain Services when the schema is extended. The container needs to be created once for each domain

environment
that includes a Configuration Manager site server that will publish site information to Active Directory
Domain Services.
NOTE: Because domains controllers do not replicate their System Management container to other domains
in the forest, a System Management container must be created for each domain that hosts a Configuration
Manager Site
1. Log on as an account that has the Create All Child Objects permission on the System container in Active
Directory Domain Services.
2. Open the ADSIEdit MMC console, and connect to the domain in which the site server resides.
3. In the console pane, expand Domain [computer fully qualified domain name], expand <distinguished
name>, and right-click CN=System. On the context menu, click New and then click Object
4. In the Create Object dialog box, select Container and click Next.

environment
5. In the Value field, type System Management and click Next.
6. Click Finish.

environment
7. System Management object has successfully been created.
Step 3: Set security permissions on the System Management

container.
1. Open the Active Directory Users and Computers administrative tool.

environment
2. Click View, and then click Advanced Features > Expand the System container > Right-click System
Management. On the context menu, click Properties
3. In the System Management Properties dialog box, click the Security tab.
4. Click Add to add the site server computer account and grant the account Full Control permissions

environment
5. Click Advanced, select the site server’s computer account, and click Edit

environment
6. In the Apply onto list, select This object and all descendant objects, click OK

environment
7. Confirm the settings are displayed as configured earlier.

environment
environment
When all computers are in the same forest, manually add the site server computer account to the local Administrators group
on each computer. Complete this step before configuring the computer as a site system.
Click Start, point to Administrative Tools, and then click Active Directory
Users and Computers.
In the Active Directory Users and Computers console tree, go to pilot.local/Builtin.
In the details pane, right-click Administrators, and then click Properties.
In the Administrators Properties dialog box, click the Members tab, and then
click Add.
In the Select Users, Contacts, Computers, or Groups dialog box, click Object
Types.
In the Object Types dialog box, in Object types, select Computers, and then
click OK.
In the Select Users, Contacts, Computers, or Groups dialog box, in Enter the object names
to select, type PILOT-SCCM-01. Click Check Names, and then click OK.
Close any open windows.

Step by step guide installing SCCM 2007 Part 11 we will configure DHCP server with relevant options
required for SCCM. Thing to keep in mind is we have DHCP running on the Domain Controller & not the
SCCM server.
Open DHCP MMC
Right click the Scope options > Configure Option 67 and point it to the boot location of where the SCCM
files will be created & NOT the WDS boot files.

environment
Configure Option 67 and point it to the SCCM server i.e. PILOT-SCCM-01

environment
Review your settings.
Step by step guide installing SCCM 2007 Part 12 is the most exciting part where we actually get to install
the main product i.e. System Center Configuration Manager 2007. We will first run the Prerequisites check &
than start the final installation process.
Let's take a look how this is done.
Browse to the location where setup files have been copied.

environment
Start setup, if you have used a CD you will see the splash screen directly as it will auto play unless this has
been disabled.
Click on " Run the prerequisite checker "

environment
Enter the relevant fields & Click OK.
Once the checks have run and completed, the results will be shown as in the box below.

environment
So we can safely ignore this error and carry on as we really dont have any warnings to worry about.

environment
environment
environment
environment
environment
environment
environment
environment
environment
environment
environment
In Site code, type HAP
In Site name, type Pilot Headquarters Site.

environment
Click Configuration Manager Mixed Mode.
I will cover Native mode at a upcoming article but for now we will stick to the mixed
mode.

environment
environment
environment
environment
environment
environment
Select the appropriate option for obtaining client prerequisite component files. Files
can be downloaded as part of Setup, or they can be used from an alternate location
to which the client prerequisite component files have already been downloaded.
Specify the path to store client prerequisite component files downloaded during Setup or the path to the
alternate location to which client prerequisite component files have previously been downloaded.
Note:You can use the Setup command-line option Setup /download path_to_files to download client
prerequisite component files without running the complete Configuration Manager Setup Wizard.

environment
environment
The above screen indicates the files which have been downloaded by setup.

environment
environment
environment
environment
environment
environment
Once setup has completed you will also notice the " System Management "
Container is getting populated with additional SCCM 2007 objects.

Step by step guide installing SCCM 2007 Part 13 series we will now upgrade System Center Configuration
Manager 2007 SP1 to System Center Configuration Manager 2007 SP2. This is not a requirement but to
successfully deploy Windows 7 we will need SP2 & Windows® Automated Installation Kit (AIK) for
Windows® 7 installed on the System Center Configuration Manager 2007 server.
This article will cover installation of System Center Configuration Manager 2007 SP2.
This article will cover installation of Windows® Automated Installation Kit (AIK) for Windows® 7
Before we go ahead let's take a quick look at the fixes which resolved in this Service Pack
List of hotfixes and updates that are contained in System Center Configuration Manager 2007 Service Pack 2
RTM 4.00.5931.0000
SP1 4.00.6221.1000
SP2 BETA 4.00.6425.2000
SP2 Release Candidate 4.00.6468.2001
SP2 Final 4.00.6487.2000
SP2 + R2 No Build changes ( Only features are

environment
added )
Let's have a quick look at the BUILD & Version id on our System Center Configuration Manager 2007 pre
SP2 install.

environment
We have passed all pre req checks which is a little surprising as it is not true as you will eventually uncover
as you go along.
For downloading SP2 click here
Microsoft System Center Configuration Manager 2007 SP2 Update

environment
Extract the SP2 files to a location of your choice.

environment
Start SP2 Install

environment
Select Upgrade Click Next >

environment
Accept the Agreement.
Click Next >

environment
Select Yes
Click Next >

environment
This will download updates from Microsoft.
Click Next >

environment
environment
environment
environment
Once downloads are complete.
Clock ok > Click Next >

environment
environment
environment
So we get the error that SP2 is not compatible with the current version installed of Windows® Automated
Installation Kit (AIK).The initial version of Windows® Automated Installation Kit (AIK) deployed
automatically during SCCM SP1 setup is not correct for SCCM SP2 hence we need to upgrade before we
move ahead.
This is an ideal time to upgrade to a new version of Windows® Automated Installation Kit (AIK) for
Windows® 7 as this will enable us to deploy Windows 7 successfully.

environment
Let us uninstall the old version first !!!
Reboot

environment
environment
environment
environment
The newly installed version of Windows® Automated Installation Kit (AIK) for Windows® 7
Reboot
Start SCCM SP2 setup once again and you will see that WAIK error has disappeared.
The above error applies only to SCCM native mode.

environment
environment
environment
Reboot once SCCM SP2 install has completed.
Verify the new SCCM BUILD & Version

environment
Ensure the Service Pack has updated the default Boot Images.
In System Center Configuration Manager 2007 expand the Operating System Deployment node > boot
images > select your X64 / x86 boot image and review it's properties, the version should read
6.1.7600.16385

environment
Step by step guide installing SCCM 2007 Part 14 we will configure the System Center Configuration Manager
2007 client which needs an account to provide credentials when accessing the System Center Configuration
Manager distribution points, MDT 2010 deployment shares, and shared folders. This account is called the
Network Access account. The SCCM.NetAccess account was created earlier in the process to use as the
Network Access account.
To configure the Network Access account
Click Start, point to All Programs, and then point to Microsoft System Center. Point to Configuration Manager 2007, and
then click ConfigMgr Console.
In the Configuration Manager Console console tree, go to Site Database/Site Management/HAP - Pilot Headquarters
Site/Site Settings/Client Agents.
In the details pane, right-click Computer Client Agent, and then click Properties.
In the Computer Client Agent Properties dialog box, click the General tab. In Network Access Account, in Account
(pilot\SCCM.Netaccess)

environment
click Set.

environment
environment

Step by Step Guide Installing SCCM 2007

Transféré par

Informations du document

Description originale:

Titre original

Copyright

Formats disponibles

Partager ce document

Partager ou intégrer le document

Options de partage

Avez-vous trouvé ce document utile ?

Ce contenu est-il inapproprié ?

Droits d'auteur :

Formats disponibles

Step by Step Guide Installing SCCM 2007

Transféré par

Droits d'auteur :

Formats disponibles

Step by step guide installing SCCM 2007 Part 1

In this article we will cover the ZTI - Zero Touch Installation.

1. Windows 2008 R2 x64 BIT.

Prerequisites for Installing Configuration Manager

Planning & Installation SCCM 2007

Configuring SCCM 2007

Fully qualified domain name (FQDN): PILOT.LOCAL

PILOT-DC-01: Domain Controller

Property Value Property Value

PILOT-SCCM-01: System Center Configuration Manager 2007 - SCCM

Property Value Property Value

How to Install Windows Server 2008 Step by Step

It is suggested to install SCCM first in an test environment then install in real

It is suggested to install SCCM first in an test environment then install in real

I will be using the following:

It is suggested to install SCCM first in an test environment then install in real

It is suggested to install SCCM first in an test environment then install in real

Click Next >

It is suggested to install SCCM first in an test environment then install in real

It is suggested to install SCCM first in an test environment then install in real

It is suggested to install SCCM first in an test environment then install in real

Click next >

It is suggested to install SCCM first in an test environment then install in real

It is suggested to install SCCM first in an test environment then install in real

Click Close >

It is suggested to install SCCM first in an test environment then install in real

It is suggested to install SCCM first in an test environment then install in real

Click Next >

It is suggested to install SCCM first in an test environment then install in real

Click Next >

It is suggested to install SCCM first in an test environment then install in real

Click Next >

It is suggested to install SCCM first in an test environment then install in real

Click Next >

It is suggested to install SCCM first in an test environment then install in real

It is suggested to install SCCM first in an test environment then install in real

It is suggested to install SCCM first in an test environment then install in real

Click Next >

It is suggested to install SCCM first in an test environment then install in real

Click Next >

It is suggested to install SCCM first in an test environment then install in real

It is suggested to install SCCM first in an test environment then install in real

Click Next >

Enter your recovery mode password and record it safely.

Click Next >

It is suggested to install SCCM first in an test environment then install in real

1. A new DC & in a new forest.

The wizard applies all the configuration we did earlier.

It is suggested to install SCCM first in an test environment then install in real

It is suggested to install SCCM first in an test environment then install in real

It is suggested to install SCCM first in an test environment then install in real

Click Next >

It is suggested to install SCCM first in an test environment then install in real

Define your ip subnet details.

It is suggested to install SCCM first in an test environment then install in real

Click Next >

It is suggested to install SCCM first in an test environment then install in real

Now the reverse lookup zoone shows up in DNS.

The domain controller does show up in ADUC.

It is suggested to install SCCM first in an test environment then install in real

How to Install and Configure Windows Server 2008 DHCP

It is suggested to install SCCM first in an test environment then install in real

* Contact Microsoft Licensing for complete clarity *