System Center 2012 Configuration Manager 

SCCM2012.twynham.tctrust.net 

http://SCCM2012  IIS Default for group policy is not needed if you are using SCCM push, read more 

about it here http://technet.microsoft.com/en‐us/library/bb632380.aspx  

Remote Differential Compression for site server and branch distribution point computers 

Site servers and branch distribution points require Remote Differential Compression (RDC) to 

generate package signatures and perform signature comparison. By default, RDC is not installed on 

Windows Server 2008 or Windows Server 2008 R2 and must be enabled manually. 

Use the following procedure to enable Remote Differential Compression for Windows Server 2008 

and Windows Server 2008 R2. 

1. On the Windows Server 2008 or Windows Server 2008 R2 computer, navigate to Start / All 

Programs / Administrative Tools / Server Manager to start Server Manager. In Server 

Manager, select the Features node and click Add Features to start the Add Features Wizard. 

2. On the Select Features page, select Remote Differential Compression, and then click Next. 

3. Complete the rest of the wizard. 

4. Close Server Manager. 

Delegate Permission to the System Management Container

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 Ok, then Next. Choose Create a Custom Task to Delegate, click next, make sure this folder, existing objects in this folder and creation of new objects in this folder is selected.

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.

Extent the AD schema for sccm

Perform the below on your Active Directory server, simply browse the network to your SCCM server \\sccm\d$ and locate the folder where you uncompressed SCCM 2012 and find \SMSSetup\Bin\x64\Extadsch.exe, right click and choose Run As Administrator.

Open SQL ports

Create a OU for your SCCM server and allow port 1433 and 4022 for SQL replication with group policy – Select Computer Configuration, Policies, Windows Settings, Windows Firewall with Advanced Security and select Inbound Rules, choose New and follow the wizard for opening up TCP port 1433, repeat for port 4022.

If using group policy refer to step 2 below Image

To open a port in the Windows firewall for TCP access

1. On the Start menu, click Run, type WF.msc, and then click OK.

2. In the Windows Firewall with Advanced Security, in the left pane, right-click Inbound Rules, and then

click New Rule in the action pane.

3. In the Rule Type dialog box, select Port, and then click Next.

4. In the Protocol and Ports dialog box, select TCP. Select Specific local ports, and then type the port

number of the instance of the Database Engine, such as 1433 for the default instance. Click Next.

5. In the Action dialog box, select Allow the connection, and then click Next.

6. In the Profile dialog box, select any profiles that describe the computer connection environment when

you want to connect to the Database Engine, and then click Next.

7. In the Name dialog box, type a name and description for this rule, and then click Finish.

To open access to SQL Server when using dynamic ports

1. On the Start menu, click Run, type WF.msc, and then click OK.

2. In the Windows Firewall with Advanced Security, in the left pane, right-click Inbound Rules, and then

click New Rule in the action pane.

3. In the Rule Type dialog box, select Program, and then click Next.

4. In the Program dialog box, select This program path. Click Browse, and navigate to the instance of SQL

Server that you want to access through the firewall, and then click Open. By default, SQL Server is at

C:\Program Files\Microsoft SQL

Server\MSSQL10_50.MSSQLSERVER\MSSQL\Binn\Sqlservr.exe. Click Next.

5. In the Action dialog box, select Allow the connection, and then click Next.

6. In the Profile dialog box, select any profiles that describe the computer connection environment when

you want to connect to the Database Engine, and then click Next.

7. In the Name dialog box, type a name and description for this rule, and then click Finish.

Install .net frame work and IIS WCF activation and BITS

In Server Manager select Features, Add Features, Select .NET Framework 3.5.1, also

select WCF Activation and when prompted answer Add Required Role Services click next

and next again, you can also add BITS(make sure the BIT and IIS service is running/restart

after install).

SQL Server

Install SQL on D:\Program Files... and when running setup.exe right click and choose

Run as Administrator, Select all options on install, click on account name and enter

admin username and password.

Click next and finish install (takes a long time).Make sure SCCM computer is a member

of the built-in administrators.

Check TCPIP properties for listening IP address in SQL Server Configuration Manager

Start up the SQL Server Configuration Manager, and expand SQL Server Network

Configuration on the left pane, highlight Protocols for <Instancename> and double

click on TCPIP in the right pane

Click on IP addresses

Change IP2 to enabled yes

Leave default IP

Change IP4 to enabled yes

Leave default IP

After you install SQL Server 2008, you must install SP2/3 and then CU6 and finally install

KB2603910.

So install it in this order:

SQL Server 2008 -SQL Server 2008 SP2 -SQL Server 2008 Cumulative Update 6 -KB2603910

Install Configuration Manager 2012

When the wizard appears, click on Install, click next and then select Install a

Configuration Manager Primary Site

Click next, and then create a folder on your D/E Drive called rc_updates

 

Click next on your Language of choice and enter your site installation settings install on D/E 

not C: 

 

 

Click next, leave the FQDN as default 

Install the primary site as a standalone site 

Select Configure the Communication method on each site system role and review all setting.

 

 

 

 

Any warnings can be fixed after the install  

 

After the install has finished restart the server.