SCCM 2007 Primary Site Installation

This post is a step by step procedure on how to install SCCM 2007 Primary site and also preparing the Windows Server for SCCM server installation.
SCCM 2007 SP2 Software is used here, you can download from the below Microsoft link.
http://www.microsoft.com/en-us/download/details.aspx?id=23152

Install SQL server as per the steps mentioned in this link.



AD schema has to be extended, the steps mentioned in this link can be used for the same.

I have broken down the steps into 3 sections:

A] Configuring Windows Server for SCCM Installation
B] SCCM Site Pre-requisite checks and Installation
C] Verifying Installation of SCCM

This is first primary and it is central site in this lab environment.

A] Configuring Windows Server for SCCM Installation:

The below TechNet link provides the detailed Windows Server requirements.
http://technet.microsoft.com/en-us/library/cc431377.aspx

1. Login to server>>> Verify OS version. It should meet the windows server requirements defined in the above link.

2.Check the disk size and decide which drive to install SCCM on-it should meet the minimum recommended size by Microsoft.

3.Add computer to SCCM SERVERS AD group as shown below.This group should have full control permissions on Systems Management Container in AD.

4. Check the installation permissions of the account with which SCCM 2007 is installed
The account must be created in the Active Directory Domain Services database. The account must have administrator rights on the following computers.
• The site server computer
• The computer running SQL Server, if it is remote from the site server
• The SMS Provider computer, if it is not installed on the site server or site database server
Here am using “SCCMADMIN” which is local admin on the server computer.

5. Add required roles for SCCM and Features on Site Server.

       

Features:

• Remote Differential Compression (RDC Feature)

Site servers and branch distribution points require Remote Differential Compression (RDC) to generate package signatures and perform signature comparison

• BITS-Back Ground Intelligence Transfer Service.

Addition of BITS feature will add the following Web Server components

Common HTTP Features:

* Static Content
* Default Document
* Directory Browsing
* HTTP Errors
* HTTP Redirection

Application Development:
* .Net Extensibility
* ISAPI Extensions

Health and Diagnostics:

* HTTP logging
* Logging Tools
* Request Monitor
* Tracing

Security
* Request Filtering Performance 
*Static Content Compression Management Tools 
*IIS Management Console
*IIS 6 Metabase Compatibility

Roles:
• Web Server (required for MP&FSP)
• File Services 
• Windows Deployment Server (required only if using PXE point)
• Windows Server Update Services (WSUS- required only if using SUP)
We cannot install WSUS along with other roles, install it separately

On Web Server role>>Enable WebDAV, asp , windows authentication, IIS 6 wmi compatibility

6. Enable WebDAV and create an Authoring Rule

Use the following procedure to enable WebDAV and create an Authoring Rule for Windows Server 2008 and Windows Server 2008 R2:

Navigate to Start / All Programs / Administrative Tools / Internet Information Services (IIS) Manager to start Internet Information Services 7 Application Server Manager.

a) In the Connections pane, expand the Sites node, and then click Default Web Site if you are using the default Web site for the site system or SMSWEB if you are using a custom Web site for the site system.

b) In the Features View, double-click WebDAV Authoring Rules.

c) With the WebDAV Authoring Rules page displayed, in the Actions pane, click Enable WebDAV.

d) In the Actions pane, click Add Authoring Rule.

e) In the Add Authoring Rule dialog box, for Allow access to, select All content.

f) For Allow access to this content to, select All users.

g) For Permissions, select Read, and then click OK.

Use the following procedure to change the property behavior of WebDAV on Windows Server 2008 and Windows Server 2008 R2:

a) In the WebDAV Authoring Rules page, in the Actions pane, click WebDAV Settings.

b) In the WebDAV Settings page, for Property Behavior, set Allow anonymous property queries to True.

c) Set Allow Custom Properties to False.

d) Set Allow property queries with infinite depth to True.

e) For a distribution point that is enabled for Allow clients to transfer content from this distribution point using BITS, HTTP, and HTTPS, for WebDAV Behavior, setAllow hidden files to be listed to True.

f) In the Action pane, click Apply.

g) Close Internet Information Services (IIS) Manager.

Below are the screenshots for WEBDAV Configuration in Windows Server 2008 R2.

WEBDAV enabled and authoring rule added.

B] SCCM Primary Site Pre-requisite checks and Installation.

7. Open the SCCM installable extract and double click on splash.hta to run the pre-requisite checker as shown.

Select Primary Site Option; enter SQL Server name and SDK Server name which is the SMS provider location. Click ok.

This will  run the Pre-requisite checker and check for  any errors.

Here, the prerequisite check is complete. The only warning is WSUS Software. We need to install WSUS if the site server is going to be used as Software Update Point.

Will do this later, for now we can start the installation of SCCM 2007

8. Initiate the Configuration manager 2007 installation from the SCCM media as shown.

a]Start:
Click on Install Configuration Manager 2007 SP2

b]Welcome screen

Click Next once you get the below screen.

c]Available Setup Options

Select “Install a Configuration Manager Site Server”

d]MS License Terms

Click next and accept the license terms.

e]Installation Settings

Select Custom settings and click next

f] Site type

Select “Primary Site” and click next.

g]Customer Improvement Program

Here, you can opt whether to be a part of customer improvement program. I have chosen “No”

h] Product key

Enter the product key and click next.

i] Destination Folder

Choose the “destination folder”. The default was root directory(C drive). Here, I have given E:\Program Files (x86)\Microsoft Configuration Manager as the destination folder.

j] Site Settings

The most important step is setting the site code and site name during the installation.

The following rules apply when you set the site code

 Do not use Microsoft Windows reserved names such as AUX, CON, NUL, or PRN as site codes.

 Setup does not verify that the site code entered is not already in use.

 Use Alphanumeric site codes- letters [A-Z], numbers [0-9] Ex : PR1,

 Changing the site code or site name after installation is not supported.

 Do not re-use site codes.

Reference: http://technet.microsoft.com/en-us/library/bb633287.aspx

Enter the appropriate site code , site name and click next.

Here, I have provided the site code as “PR1” and the site name as “Lab Primary Site”

k]Site Mode

By default, the native mode is selected. Change the selection to mixed mode and click next.

(Decide the pros and cons of implementing native mode and then proceed if you want more secure environment)

l]Client Agent Selection

Select the client agents required as shown.

m]Database Server

If the SQL server is installed on the same box, the default instance will be selected. Verify the same and the DB SMS_SiteCode (SMS_PR1 in this lab)

n] SMS Provider settings

If the SMS provider is installed on other computer, enter the SMS Provider server name or continue with the default auto filled server name.

o]Management Point

Next, you can choose whether to install Management point during the set up. I have chosen here to install MP.

p]Port settings: 

Use default port 80, click next. HTTPS is grayed out because it only works with Native Mode.

q] Updated pre-requisite components:

The next step is to check for the updated pre-requisite components available from Microsoft site.

Note that you have to create a folder to download or store these components on the system. These are used during the installation of SCCM.

If you have an internet connection, select the first option, point it to the folder that is created earlier.

If you already have the files downloaded, select the second option and click next.

In this case, I have created a folder “prereq-SCCM-SP2” prior to installation with all the updates and pre-requisite components downloaded.

Enter the path and the path here is \\SCCM2007\prereq-SCCM-SP2

This could take several minutes. When it is done a popup box will tell you, “Successfully downloaded all prerequisite components.” Click OK here and then it’s time for the next screen

r]Settings Summary:

This is a review of everything you choose throughout the wizard. If you need to change something you need to click the back button until you get back to the corresponding screen. After you click Next the Prerequisite Checker will run itself one more time.

s] Installation prerequisite check

Once the checker is run, select the “Begin Install” button to start installing SCCM.

t] Setup Action Status Monitoring:

Setup Action Status Monitoring: Here you will see actions go from Not Started to In Process to Competed

u] Complete Installation

Eventually you will get a screen that the setup is completed successfully. Click Finish and the installation is done!

C] Verifying Installation of SCCM

The below TechNet link provides the detailed steps on verification of Site installation

http://technet.microsoft.com/en-us/library/bb693526.aspx

The log files that need to be checked to verify successful installation are as follows.

You can use Trace32 error log reader to view the logs

• ConfigMgrSetup.log

Location: Root Directory (C drive here)

Search for: “Installation and Configuration processes are done”

• ComponentSetup.log

               Location: Root Directory (C drive here)
               Review it and check if there are components are having issues.

• Sitecomp.log

Location : <ConfigMgr install directory>\logs directory

Here it is E:\Program Files (x86)\Microsoft Configuration Manager\Logs

          Search for Waiting for changes to the “<ConfigMgr install directory>\Inboxes\Sitectrl.box”              or “<ConfigMgr install directory>\Inboxes\Sitecomp.box”

• Hman.log

Location : <ConfigMgr install directory>\logs directory

Here it is E:\Program Files (x86)\Microsoft Configuration Manager\Logs

Search: Wait for site control changes for maximum 3600 seconds. This entry indicates that Hierarchy Manager has completed its work for the site installation

And find information related to AD as shown in the log screenshot here.

• Inboxmgr.log

Location : <ConfigMgr install directory>\logs directory

Here it is E:\Program Files (x86)\Microsoft Configuration Manager\Logs

Search: “Waiting for changes in inbox definition, inbox rules and inbox replication files, max wait = 3600 seconds”. This entry indicates that Configuration Manager 2007 Inbox Manager has completed its work for the site installation.

To open the SCCM Administration Console, browse through Start>All Programs>Microsoft System Center> ConfigMgr Console

Please test it thoroughly in development before you do any changes in production.

Hope this has been informative for you.