9-SCCM 2012 Installation Guide

7/31/2019 9-SCCM 2012 Installation Guide

1/19

SCCM 2012 Installation Guide

This post is intended to guide you with the required installation steps for SCCM2012. We are assuming a simple install with a unique Primary Site Server and a

remote SQL Database Server with a named instance.

For this tutorial we will take 6 main Steps:

Step1 - The LAB enviromentStep2 - Extend Active Directory Schema

Step3 - System Container creation and Permissions AssignmentStep4 - Site Server Prerequisites

Step5 - SQL Server considerationsStep6 - SCCM 2012 intallation

Step1 - The LAB enviroment

For this LAB, we setup an Active Directory infra-structure with the followingcharacteristics:

TSTDC1.lab.local -> A domain controller for the domain lab.localTSTSCCM.lab.local -> The site server machine witch will host the Site Server

role and most of the system rolesTSTSQL.lab.local -> The SQL Server machine, witch will host the DatabaseSystem role and the Reporting Services Point role. The SQL Server version

installed is SQL Server 2008 SP2 with CUP7. A named instance called SMSIST1 issetup and ready to use

CLT01.lab.local -> A Windows 7 client machine that represents the commonusers computers in a domain

All Server systems are running Windows Server 2008 R2 SP1.

All computer are join to the domain lab.local

We also create some domain accounts for various purposes:

SQL_SA -> a domain user account used for SQL server servicesSCCM_SA -> a domain user account for use in various SCCM services, like, push

install, Network Access Account, etc
http://msfttech.blogspot.com/2012/03/sccm-2012-installation-guide.htmlhttp://msfttech.blogspot.com/2012/03/sccm-2012-installation-guide.htmlhttp://msfttech.blogspot.com/2012/03/sccm-2012-installation-guide.html


2/19

SCCMadmin -> a domain user account with admin rights in the SCCM infra-structure

Reports_SA -> a domain user account for use with reporting services

NOTE: We may not be using all mention accounts in this guide, this is just a

simple and basic creation of Active Directory accounts for a SCCM enviroment

Step2 - Extend Active Directory Schema

Extending Active Directory Schema for SCCM 2012 is a simple process thatconsists in running an exe file in one of you Domain Controllers. As there aren'tany changes in the Schema extensions since SCCM 2007, if you have previouslyupgrade your AD Schema with this extensions you do not need to Upgrade it

again.

To extend the AD Schema follow this steps:

1. Logon to a Domain Controller with an account that have Domain and SchemaAdmin privileges

2. Access the SCCM 2012 media content, by network browse or directly fromthe DVD.

3. Navigate to \SMSSetup\Bin\x64\ and execute Extadsch.exe

4. Verify the log file generated in c:\ ExtADSch.log to confirm that the upgradewas successful
http://2.bp.blogspot.com/-iRKyGcrl088/T1LQVAf2DrI/AAAAAAAAACE/tP9hiH85f5I/s1600/SchemaExtensions1.png


3/19

5. If applicable, wait for the Active Directory Replication to take place or forceit with repadmin tool or Active Directory Sites and Services snap-in

Step3 - System Container creation andPermissions Assignment

Now we need to create a new container under Active Directory SystemContainer, and then we need to assign Full Control permissions in this container

for each Site Server computer account. In our case we are only installing aPrimary Site Server, so we just need to assign permission to one computer

object (TSTSCCM).

1. From a Domain Controller with a Domain Administrator account open ADSI

Edit snap-in (adsiedit.msc)2. Select the top node of the left pane, right click and choose connect to,

accept the default naming context and click OK.3. In the container CN=System, right click and select new -> object
http://4.bp.blogspot.com/-FSNYclByFsU/T1LQVxOTk6I/AAAAAAAAACI/zlIdDwfhZt8/s1600/SchemaExtensions2.png


4/19

4. Choose Container in the Class type menu and hit next

5. In the value field for the container object write System Management andpress next
http://1.bp.blogspot.com/-U4MMculKVHQ/T1NgaveXQYI/AAAAAAAAACc/xEDoumCJU5I/s1600/SystemManagementCreation2.pnghttp://1.bp.blogspot.com/-5nASbJWAaGM/T1OXw_7OOSI/AAAAAAAAADE/_hJ18qkSLZs/s1600/Systemcontainer1.PNG


5/19

Now that the System Management Container its created we need to give FullControl permission on this container and in all his descendant objects to every

Site Server computer account. To do this follow this steps:

1. Again from ADSI Edit select the System Management Container, go to itsproperties

2. In the security tab add the Site Server computer account to the ACL andassign full control permissions to it

3. Click on advanced tab, select the Site Server computer account and clickedit
http://3.bp.blogspot.com/-jJQ2SbEZXYU/T1OZPtXTWfI/AAAAAAAAADM/xdFQYxWEols/s1600/SystemManagementCreation4.PNGhttp://4.bp.blogspot.com/-RrKiQVE9I8E/T1NgewOlNvI/AAAAAAAAACk/9vAEGE69FsA/s1600/SystemManagementCreation3.png


6/19

4. In the permission entry for System Management windows, from the Apply todrop dwon box menu choose This object and all descendant objects, click OK

all the way down until all windows are closed.

5. Again, wait or force replication between Domain Controllers if applicable

Step4 - Site Server Prerequisites

So, our Active Directory preparations tasks are done, now we focus on the SiteServer preparation. As mentioned we are going to install a stand alone PrimarySite Server. For that, we need to install a bunch of feature and application in

the Site Server computer (TSTSCCM).
http://1.bp.blogspot.com/-1Gqv3FE3pG8/T1OaTxCboJI/AAAAAAAAADc/SKRfjQkccDU/s1600/SystemManagementCreation6.PNGhttp://2.bp.blogspot.com/-UfA4LbpDY7s/T1OZ8RE2G8I/AAAAAAAAADU/h7wc_0Grh68/s1600/SystemManagementCreation5.PNG


7/19

You can review the prerequisites for the various roleshere, to simplify theprocess we will just run a power shell command to install all the features we

need in one shoot.

1. On your Site Sever computer, open a power shell command prompt and

type:

Import-module servermanager Add-WindowsFeature Web-Common-Http,Web-Static-Content,Web-Default-Doc,Web-Dir-Browsing,Web-Http-Errors,Web-Http-

Redirect,Web-Asp-Net,Web-Net-Ext,Web-ASP,Web-ISAPI-Ext,Web-ISAPI-Filter,Web-Http-Logging,Web-Log-Libraries,Web-Request-Monitor,Web-Http-Tracing,Web-Basic-Auth,Web-

Windows-Auth,Web-Url-Auth,Web-Filtering,Web-IP-Security,Web-Stat-Compression,Web-Mgmt-Tools,Web-WMI,NET-

Framework,RDC,BITS -Restart

2. Download and install .NET Framework 4 -here3.There are some optional windows features / roles that you could install,depending on what kind of functionality you want to use from SCCM, for

example, if you plan on using Software Updates you will need the WSUS roleinstalled on the site system you install the SCCM SUP (Software Update Point)

role, likewise if you plan on using OSD (Operating System deployment), you will

need the WDS (Windows Deployment Services) installed. In our case we willjust add this roles in a later time, note that for WDS, you dont need to installthe role manually like WSUS, in SCCM 2012, the role is installed automatically

once you enable the PXE role.4. Add the Site Server computer account (TSTSCCM) and the SCCMadmin user tothe local administrators group of your Primary Site Sever computer (TSTSCCM).
http://technet.microsoft.com/en-us/library/gg682077.aspx#BKMK_SupConfigSiteSystemReqhttp://technet.microsoft.com/en-us/library/gg682077.aspx#BKMK_SupConfigSiteSystemReqhttp://technet.microsoft.com/en-us/library/gg682077.aspx#BKMK_SupConfigSiteSystemReqhttp://www.microsoft.com/download/en/details.aspx?displaylang=en&id=17718http://www.microsoft.com/download/en/details.aspx?displaylang=en&id=17718http://www.microsoft.com/download/en/details.aspx?displaylang=en&id=17718http://4.bp.blogspot.com/-4SUv_ZcBtuA/T1ObODoCJwI/AAAAAAAAADk/mk3i6vOpQZU/s1600/prerequisites-siteserver.pnghttp://www.microsoft.com/download/en/details.aspx?displaylang=en&id=17718http://technet.microsoft.com/en-us/library/gg682077.aspx#BKMK_SupConfigSiteSystemReq


8/19

5. You should run windows update and patch your server to the highest level

This should install all the main prerequisites you need for your Primary SiteServer installation

Step5 - SQL Server considerations

Has told, we are using a separate server for hosting the SQL server Databaseand the Site System Database role. We also decide to use a named instance for

SMS Database, witch intern needs some additional configurations comparedwith using just the default instance.

We are not going to do a step by step on how to install SQL, we are just goingto mention some relevant aspects that you need to take in consideration when

building you SQL Sever.

1. You could see the supported versions of SQL Serverhere2. You only need to install the Database Engine feature for each site server, ofcourse Management Tools could come in handy, Reporting Services is optional,but you probably would install it, since reporting in SCCM 2012 is only through

Reporting Services, no more Reporting point role :)
http://technet.microsoft.com/en-us/library/c1e93ef9-761f-4f60-8372-df9bf5009be0#BKMK_SupConfigSQLDBconfighttp://technet.microsoft.com/en-us/library/c1e93ef9-761f-4f60-8372-df9bf5009be0#BKMK_SupConfigSQLDBconfighttp://technet.microsoft.com/en-us/library/c1e93ef9-761f-4f60-8372-df9bf5009be0#BKMK_SupConfigSQLDBconfighttp://1.bp.blogspot.com/-5_n-KKiTmfQ/T1ObOqD2gEI/AAAAAAAAADs/ER9qONWOEk8/s1600/prerequisites-siteserver2.pnghttp://technet.microsoft.com/en-us/library/c1e93ef9-761f-4f60-8372-df9bf5009be0#BKMK_SupConfigSQLDBconfig


9/19

3. You must use a dedicated instance of SQL Server for each site, in other

words, you cannot host two Database from two different Site Servers in thesame SQL instance, it could be in the same server though, but in separated

instances4. Limit SQLServer memory to 80 - 90% of the addressable memory if the SQL is

in a dedicated Server. if the SQL is co-located with the Site Server computerlimit the memory to 50 - 80%. You can do this with SQL Server Management

Studio, by selecting the top SQL Server instance node, going to its properties,and in the memory page define a limit for the maximum server memory

5. If you configure you SQL Server service to run with a domain user account(best practice) you might have to register a SPN (Service Principal Name) in

Active Directory for that domain account. You will need to register two SPN forthe account, one for the NETBIOS name of the SQL Server and other for the

FQDN. to do that, on a domain controller, open a command prompt and type:

setspn A MSSQLSvc/:1433

setspn A MSSQLSvc/:1433
http://1.bp.blogspot.com/-Zr6HCe_iKdc/T1QMdwFjIKI/AAAAAAAAAGk/oEXsEnU7q38/s1600/Capture.PNGhttp://1.bp.blogspot.com/-UyVkeppZNhM/T1OxB4KbZRI/AAAAAAAAAD0/4ZEZLw54TFs/s1600/SQL1.PNG


10/19

in our example we have:

setspn A MSSQLSvc/TSTSQL:1433 LAB\SQL_SAsetspn A MSSQLSvc/TSTSQL.lab.local:1433 LAB\SQL_SA

After registering the SPNs you could check them by typing:

setspn L

once again in our example:

setspn L LAB\SQL_SA

6. Open Firewall ports on you SQL server, you could just turn off WindowsFirewall, however if you like to take advantage of windows firewall security

just ensure you open the necessary ports, the script below will do that for you,

just copy and paste it in a notepad, save it as a *.bat file, and run it from acommand prompt

@echo ========= SQL Server Ports ===================@echo Enabling SQLServer default instance port 1433netsh firewall set portopening TCP 1433 "SQLServer"@echo Enabling Dedicated Admin Connection port 1434netsh firewall set portopening TCP 1434 "SQL Admin

Connection"@echo Enabling conventional SQL Server Service Broker port

4022netsh firewall set portopening TCP 4022 "SQL Service

Broker"@echo Enabling Transact-SQL Debugger/RPC port 135

netsh firewall set portopening TCP 135 "SQL Debugger/RPC"@echo ========= Analysis Services Ports ==============

@echo Enabling SSAS Default Instance port 2383netsh firewall set portopening TCP 2383 "Analysis Services"

@echo Enabling SQL Server Browser Service port 2382netsh firewall set portopening TCP 2382 "SQL Browser"

@echo ========= Misc Applications ==============@echo Enabling HTTP port 80

netsh firewall set portopening TCP 80 "HTTP"

@echo Enabling SSL port 443netsh firewall set portopening TCP 443 "SSL"

@echo Enabling port for SQL Server Browser Service's'Browse' Button

netsh firewall set portopening UDP 1434 "SQL Browser"@echo Allowing multicast broadcast response on UDP (Browser

Service Enumerations OK)netsh firewall set multicastbroadcastresponse ENABLE


11/19

7. During SQL installation in the collation tab, you should set the DatabaseEngine to use SQL_Latin1_General_CP1_CI_AS

8. During SQL server installation in the account provisioning tab, you should setthe authentication mode to Windows Authentication and in the SQL Server

Administrators add the SCCMadmin user and the current user from witch youare installing SQL.

9. As we told, when using a named instance you do need to make sameadditional configurations. SCCM Site Server do not support Dynamic Ports, andSQL Server named instances use dynamic ports by default, so we need to fix

that.a. Logon to your SQL Server and open SQL Server Configuration Manager

b. Expand SQL Server Network Configuration, select Protocols for "you instancename". From the central pane, double click on TCP/IP protocol

c. In TCP/IP Properties windows select the IP Addresses tab

d. Now for every IP configuration, from IP1 through IPAll, delete the "0" in theTCP Dynamic Ports field, leaving it just empty and fill in the TCP Port of every

IP with the value of 1433. Click OK to close the window
http://3.bp.blogspot.com/-PNnJ7f9cnBQ/T1O0Eu8mrdI/AAAAAAAAAEM/lid_EMh14XQ/s1600/SQL4.PNGhttp://1.bp.blogspot.com/-kOZhCsd6wq8/T1OzejxY5_I/AAAAAAAAAEE/_soLCR6s6DI/s1600/SQL3.PNG


12/19

e. To apply the changes, go to SQL Server Services node, select your SQL Serverinstance and do a restart to the service

10. Add the Site Server computer account (TSTSCCM) and the SCCMadmin userto the local administrators group of the SQL Server (TSTSQL)

11. Make sure you have all necessary SQL patches, the minimum Service Packsand CU (Cumulative Updates)

Step6 - SCCM 2012 intallation

Active Directory is prepared our Site Server prerequisites installed and our SQLServer up and running, we are finally ready to kick the SCCM installation.

From your Site Server computer, with your SCCMadmin account follow thissteps:
http://2.bp.blogspot.com/-Y6_g8Q0Afqk/T1P0jiXm1AI/AAAAAAAAAEc/Y9DK3OC2cGM/s1600/SQL7.PNGhttp://1.bp.blogspot.com/-EBP_Hurj8gY/T1P0jCBFJ_I/AAAAAAAAAEU/E7R6nmOe120/s1600/SQL6.PNG


13/19

1. Navigate to your installation media and execute splash.hta2. In the configuration Manager Setup windows click install

3. In the Getting Started window, select Install a Configuration ManagerPrimary Site and click next

4. In the prerequisites licenses page accept all three license terms and clicknext
http://4.bp.blogspot.com/-pdti7RmtKRY/T1P1e-PMnkI/AAAAAAAAAEw/RXPNZCV7vSo/s1600/SCCMinstall1.PNGhttp://4.bp.blogspot.com/-JJPACAY1zPc/T1P1eB5dDpI/AAAAAAAAAEk/HUh0K3SoM6k/s1600/SCCMinstal16.PNGhttp://1.bp.blogspot.com/-FYFZskSqGxM/T1P1eQD0nAI/AAAAAAAAAEo/oRg_E9Tj4_k/s1600/SCCMinstal17.PNG


14/19

5. In the prerequisites download page, specify a local folder to download allthe necessary additional files for the installation and click next. Wait for the

download to complete

6. In the server language selection window, select the languages you want to

install for your console and reports, click next

7. In the client languages selection window, select the languages you want tobe available for you clients, click next

8. In the site and installation setting page, specify the 3 digit Site Code foryour Site Sever, we are using LB1 in our LAB. Fill in a site name for your
http://3.bp.blogspot.com/-DbqwhCEdK7Q/T1P1gQmoYiI/AAAAAAAAAFE/kGy-97wQEJU/s1600/SCCMinstall12.PNGhttp://1.bp.blogspot.com/-0xWadjADROU/T1P1gsd6JrI/AAAAAAAAAFU/nq-NRa_a1Ww/s1600/SCCMinstall13.PNGhttp://1.bp.blogspot.com/-zrkCN3MvWig/T1P1iT-pg9I/AAAAAAAAAFc/aB5Mq2Fuxpk/s1600/SCCMinstall15.PNGhttp://3.bp.blogspot.com/-DbqwhCEdK7Q/T1P1gQmoYiI/AAAAAAAAAFE/kGy-97wQEJU/s1600/SCCMinstall12.PNGhttp://1.bp.blogspot.com/-0xWadjADROU/T1P1gsd6JrI/AAAAAAAAAFU/nq-NRa_a1Ww/s1600/SCCMinstall13.PNGhttp://1.bp.blogspot.com/-zrkCN3MvWig/T1P1iT-pg9I/AAAAAAAAAFc/aB5Mq2Fuxpk/s1600/SCCMinstall15.PNGhttp://3.bp.blogspot.com/-DbqwhCEdK7Q/T1P1gQmoYiI/AAAAAAAAAFE/kGy-97wQEJU/s1600/SCCMinstall12.PNGhttp://1.bp.blogspot.com/-0xWadjADROU/T1P1gsd6JrI/AAAAAAAAAFU/nq-NRa_a1Ww/s1600/SCCMinstall13.PNGhttp://1.bp.blogspot.com/-zrkCN3MvWig/T1P1iT-pg9I/AAAAAAAAAFc/aB5Mq2Fuxpk/s1600/SCCMinstall15.PNG


15/19

Primary Site Server, specify the installation path and choose whether or not toinstall the SCCM console on the Site Server, witch you probably would want to.

click next

9. In the primary site server installation window, just select whether you aregoing to join the Site Server to an existing hierarchy in witch case you must

specify the CAS Server FQDN, or whether to perform a Stand Alone install, notethat if you choose a Stand Alone install, you can not join the Primary Site

Server later to a hierarchy. In our scenario we are going to install a stand alonePrimary Site. click next

10. In the Database information page enter your Database locationinformation, SQL Server Database FQDN name, instance name (leave blank if

you are using the default instance) we are using a named instance calledSMSIST1. You should accept defaults for the Database name and for the SSB

port, click next
http://1.bp.blogspot.com/-4nwRIDOoa8o/T1P1fSCDMmI/AAAAAAAAAE4/CNmysSqxO2M/s1600/SCCMinstall10.PNGhttp://1.bp.blogspot.com/-hLOAZ-xLxQQ/T1P1f2eQfFI/AAAAAAAAAFA/GGpWCFDL0VY/s1600/SCCMinstall11.PNGhttp://1.bp.blogspot.com/-4nwRIDOoa8o/T1P1fSCDMmI/AAAAAAAAAE4/CNmysSqxO2M/s1600/SCCMinstall10.PNGhttp://1.bp.blogspot.com/-hLOAZ-xLxQQ/T1P1f2eQfFI/AAAAAAAAAFA/GGpWCFDL0VY/s1600/SCCMinstall11.PNG


16/19

11. In the SMS Provider Setting specify the SMS Provider FQDN, this probablywould be you Site Server, click next

12. In the client computer communication settings, choose configure thecommunication method in each site system role, click next

13. In the site system role, check the Install a management point and install adistribution point, click next
http://2.bp.blogspot.com/-wq4KfwS8fdY/T1P1nPyLkLI/AAAAAAAAAGY/0hIdjIEJ2Qg/s1600/SCCMinstall9.PNGhttp://2.bp.blogspot.com/-JF5uaoFi6iI/T1P1jSZ8SKI/AAAAAAAAAFo/4gBVNZiqNHg/s1600/SCCMinstall3.PNGhttp://1.bp.blogspot.com/--HFipaw2WFI/T1P1jKx9d5I/AAAAAAAAAFg/BV_2O7s3Mzc/s1600/SCCMinstall2.PNGhttp://2.bp.blogspot.com/-JF5uaoFi6iI/T1P1jSZ8SKI/AAAAAAAAAFo/4gBVNZiqNHg/s1600/SCCMinstall3.PNGhttp://1.bp.blogspot.com/--HFipaw2WFI/T1P1jKx9d5I/AAAAAAAAAFg/BV_2O7s3Mzc/s1600/SCCMinstall2.PNGhttp://2.bp.blogspot.com/-JF5uaoFi6iI/T1P1jSZ8SKI/AAAAAAAAAFo/4gBVNZiqNHg/s1600/SCCMinstall3.PNGhttp://1.bp.blogspot.com/--HFipaw2WFI/T1P1jKx9d5I/AAAAAAAAAFg/BV_2O7s3Mzc/s1600/SCCMinstall2.PNG


17/19

14. Then a prerequisite checker will run to verify that all the requisites for theinstallation are OK. If you get some warnings its fine, you can proceed withthe installation anyway. You will probably get a warning about SQL Serverprocess allocation and about WSUS SDK, if like me, you decide to install it

later. Hit begin install, lay back and wait about 15 to 20 minutes
http://4.bp.blogspot.com/-5SXNTReALjI/T1P1kfZiw4I/AAAAAAAAAF4/jlV10gANC2w/s1600/SCCMinstall5.PNGhttp://1.bp.blogspot.com/-AMxA9dFvaGc/T1P1jzvNWuI/AAAAAAAAAFw/sKbWjdNv6ho/s1600/SCCMinstall4.PNGhttp://4.bp.blogspot.com/-5SXNTReALjI/T1P1kfZiw4I/AAAAAAAAAF4/jlV10gANC2w/s1600/SCCMinstall5.PNGhttp://1.bp.blogspot.com/-AMxA9dFvaGc/T1P1jzvNWuI/AAAAAAAAAFw/sKbWjdNv6ho/s1600/SCCMinstall4.PNG


18/19

15. Once the installation is done, click close, reboot the Server, open the SCCMConsole and enjoy, Congratulation, you have just installed you first SCCM 2012

Primary Site Server

TIP: you can view all the installation processes in real time, in your site servercomputer just go to \SMSSETUP\TOOLS\ on your installation media and run

CMTrace tool, then open the log file in c:\ConfigMgrSetup.log, this will showyou what is happening in the background during installation and let you identify

potential problems in an easy way.
http://1.bp.blogspot.com/-fvJmLssVcek/T1P1mCs6OHI/AAAAAAAAAGU/WwfKY5ov-ZA/s1600/SCCMinstall8.PNGhttp://4.bp.blogspot.com/-1ZBhexBoiOk/T1P1lh83pCI/AAAAAAAAAGI/GuA6crfFgT8/s1600/SCCMinstall7.PNGhttp://1.bp.blogspot.com/-fvJmLssVcek/T1P1mCs6OHI/AAAAAAAAAGU/WwfKY5ov-ZA/s1600/SCCMinstall8.PNGhttp://4.bp.blogspot.com/-1ZBhexBoiOk/T1P1lh83pCI/AAAAAAAAAGI/GuA6crfFgT8/s1600/SCCMinstall7.PNG


19/19
http://2.bp.blogspot.com/-ipcIbgoyrQw/T1P1k4EeXxI/AAAAAAAAAGA/aRr3KkJ8674/s1600/SCCMinstall6.PNG

9-SCCM 2012 Installation Guide

Documents

Transcript of 9-SCCM 2012 Installation Guide