SCCM 2012 SP1 – Installation step by step

Dear All,

I would like to share with you my notes from the field concerning the basic installation of SCCM 2012 SP1.

This post is a compilation from the excellent site http://www.windows-noob.com, Microsoft TechNet and my personal notes.

Server 1: SCCM all roles
Server 2: SCCM distribution point
Server 3: SQL Server

  1. SQL Server

    1. Installation

I will not detail the complete installation of SQL server, but just give the basic features that we need to install.

Database Engine Services

Reporting Services – Native

Management Tools – Basic

—    Management Tools – Complete

During the SQL server installation process, select the following module.

The SQL server services must run under a service account.

Select the collation SQL_Latin1_General_CP1_CI_AS

Concerning the reporting, select Install and configure.

Installation completed.

 

  1. Configuration

Now, SQL will only set and use the port TCP 1433 to the first Default Instance. The Instances installed afterwards get a dynamic choosen port set.  Configmgr 2012 does not support dynamic port for SQL.

When SQL Service is restarted and firewall ports a opened we can Go Ahead with the Configmgr Setup.

 

The SSB Port is also something to think of, depending on Your configuration.

 

Based on the name of the Instance, Configmgr will detect the port configured automatically. 🙂

When SQL Service is restarted and firewall ports a opened we can Go Ahead with the Configmgr Setup.

 

The SSB Port is also something to think of, depending on Your configuration.

 

Based on the name of the Instance, Configmgr will detect the port configured automatically. 🙂

 

 

SCCM Installation:

  1. System Management Container

 

Note: Perform the following on the Active Directory Domain Controller as a Domain

Administrator

 

Open ADSI Edit, click on Action, Connect To and click Ok, Double Click on Default Naming Context

and the DC= that appears below it. Click on the + and scroll down to CN=System.

Right Click on CN=System and choose New, Object

Choose Container from the options, click Next

Enter System Management as the value. Click

Next

Click Finish

 

  1. Delegate Permission to the System Management Container

Note: Perform the following on the Active Directory Domain Controller as a Domain

Administrator

Open Active Directory Users and Computers. Click on view, select Advanced Features.

Select the System Management Container, and right click it, choose All Tasks and Delegate

Control.

 

When the Welcome to Delegation of Control Wizard appears click next, then click Add. click

on Object Types, select Computers. Type in your SCCM server name and click on Check Names,

it should resolve.

 

 

click next, select the 3 permissions General, Property-Specific and Creation-deletion of specific

child objects are selected then place a check mark in FULL CONTROL, and click next then Finish.

Failure to do the above will mean that the System Management Container in AD will NOT

POPULATE with ConfigMgr site info needed by the Clients and you will see many errors in your site

status warning you of same.

Note: Repeat the above for Each site server that you install in a Hierarchy.

 

  1. Extend the Active Directory schema for Configuration

Note: Perform the following on the Active Directory Domain Controller as a Domain Administrator

Note:-The Active Directory schema extensions for Configuration Manager 2012 are unchanged from those used by Configuration Manager 2007. If you extended the schema for Configuration Manager 2007, you do not need to extend the schema again for Configuration Manager 2012.

Perform the below on your Active Directory server, simply browse the folder where you uncompressed SCCM 2012 and find

SMSSetupBinx64Extadsch.exe, right click and choose Run As Administrator.

A command prompt window will appear briefly as the schema is extended, check in c: for a log file

called ExtADSch.log it should look similar to this

 

  1. SCCM Installation

    1. Drives configuration (Server 1 – Server 2)

By default SCCM will install the files (Packages, Updates,…) on the drive with the most empty space. If you want to avoid than SCCM install files in a specific drive, you have to create an empty file on the root of the C: Drive

NO_SMS_ON_DRIVE.SMS

  1. Prerequisites

    1. Files to download

You can either download them as part of the Site installation experience, or download them using a utility that comes on the ConfigMgr installation media called SETUPDL.EXE. Using this tool you can perform the download before installation takes place on a server or workstation that has Port 80 access to the Internet.

Just open a CMD prompt, create yourself a destination directory (spaces are supported in RTM), navigate to the SC12CM’s media SMSSETUPBINX64 directory and point SETUPDL.EXE at the newly created folder.

Example:

 

D:SMSSETUPBINX64SETUPDL.EXE C:SC12CM-Prerequisite

Here’s the output from SETUPDL.EXE:

 

Downloader for ConfigMgr Setup

 

SETUPDL [options] destination

 

destination Specifies the directory for downloaded files.

 

Options:

/verify Verify the manifest and contents at the destination, but do not download

/NoUI Don’t show any UI during the process

/? This help

 

When it’s running, you’ll see something like this:

The only limitation is that the tool is 64- bit (X64) and thus cannot run on an 32-bit (X86) OS.

 

And when it has finished the CMD prompt output will have the last line as:

 

INFO: setupdl.exe: Finish $$<Configuration Manager Setup><06-04-2012 14:10:41.4

71-60><thread=2244 (0x8C4)>

 

You could log all this by redirecting the output of SETUPDL.EXE using the > console output redirector.

 

 

Key things to make sure you have are an X64 OS and easy Port 80 internet access. Keep in mind that if you are in a Web proxy-based environment with proxy authentication enabled, you may have issues getting through.

 

  1. Server 2

  1. Roles and features

Install the following role : IIS

Options :

    Application Development:

    ISAPI Extensions

   

    Security:

    Windows Authentication

   

    IIS 6 Management Compatibility:

    IIS 6 Metabase Compatibility

    IIS 6 WMI Compatibility

 

Ensure to add the Server1 in the local administrator group of the Server2.

 

  1. Server 1

  1. Roles and Features

dism /online /enable-feature /all /featurename:netfx3 /source:d:sourcessxs /limitaccess


 

Import-Module servermanager

Add-WindowsFeature BITS,RDC,Web-WMI,WDS

 

  1. Assessment and deployment Kit

Download the http://www.microsoft.com/en-us/download/details.aspx?id=30652

 

During the installation process, select the following options.

 

  1. SCCM Installation

    1. Server 1 (Primary Site + All roles)

Click on Install

Click on Next.

Select Install a Configuration Manager Primary Site.

 

As We will install the Distribution Point role on a second server, uncheck the box Use Typical installation options for a standalone primary site.

Entry you product key.

Accept the license terms.

 

Click on Next.

Accept the license terms.

Click on Next.

As we already downloaded the needed files, choose Use previously download files.

 

Click on Next.

Select the language(s) for the SCCM server.

 

Click on Next.

Select the language(s) for the SCCM client.

 

Click on Next.

Enter a site code, it’s up to find a logic in that name.

 

Enter a site name.

 

Specify the installation folder.

 

Click on Next.

Select Install the primary site as a stand-alone site.

 

Click on Next.

Click on Yes.

Specify the db instance information.

 

Click on Next.

Click on Next.

Select Configure the communication method on each site system role.

 

Click on Next.

Install the management point role on the first server.

 

Install the distribution point on the second server.

 

This could be of course change later.

 

Click on Next.

Choose I don’t want to join the program at this time.

 

Click on Next.

Review the information.

 

Click on Next.

Review the warning information.

 

Click on Begin Install.

Installation in progress.

Installation is complete.

 

 

  1. Software Update point installation

Server 2

 

 

  1. Software Update Point Installation

On the server on which you want to install the Software update point, create a Source folder and Share it to everyone for read-only access.

Add Roles and Features.

 

Click on Next.

Click on next.

Click on Next.

Select Windows Server Update Services.

 

Click on Next.

Click on Next.

Click on Next.

Uncheck the WID Database.

 

Click on next.

Specify the folder when the sources will be stored.

Specify the DB Server.

Click on Install.

Installation in progress.

When the installation is complete, go to Windows Server Update Services.

Click on Run.

Click on close.

Click on Cancel, SCCM Will configure it.

Start up the ConfigMgr console, click on Administration in the Wunderbar, click on Site Configuration, and select Servers and Site System Roles, Right click on your server and choose Add Site System Role

Click on Next.

Specify you proxy information if needed and click on Next.

Select Software update point.

 

Click on Next.

Select WSUS is configured to use ports 8530.

 

Click on Next.

Click on Next.

Select Synchronize from Microsoft Update.

 

Click on Next.

Specify you Schedule.

Click on Next.

Select the classifications that you want to synchronize.

Select the product that you want synchronize.

Select the languages.

Click on Next.

Configuration is complete.

 

 

 

Tweet about this on TwitterShare on FacebookShare on LinkedInShare on Google+Email this to someoneShare on TumblrPin on PinterestDigg thisShare on RedditFlattr the authorBuffer this pageShare on StumbleUpon

About Christopher Keyaert

Christopher Keyaert is a Consultant, focused on helping partners to leverage the System Center and Microsoft Azure cloud platform. He is also a Microsoft Most Valuable Professional (MVP) for Cloud and Data Center Management and a Microsoft Certified Trainer (MCT).
This entry was posted in Configuration Manager. Bookmark the permalink.

Leave a Reply

Your email address will not be published. Required fields are marked *