Step-by-Step Installation and Configuration of SCCM 2012 SP1
Site Types Configuration Manager 2012 introduces the central administrationsite and some changes to primary and secondary sites. The following tables summaries these sites and how they compare to sites in Configuration Manager 2007.
Centraladministrationsite The central administration site coordinates intersite data replication across the hierarchy by using Configuration Manager database replication. It also enables the administration of hierarchy-wide configurations for client agents, discovery, and other operations. Use this site for all administration and reporting for the hierarchy. Although this is the site at the top of the hierarchy in Configuration Manager 2012, it has the following differences from a central site in Configuration Manager 2007: •
Does not process client data.
•
Does not accept client assignments.
•
Does not support all site system roles.
•
Participates in database replication
Primarysite Manages clients in well-connected networks. Primary sites in Configuration Manager 2012 have the following differences from primary sites in Configuration Manager 2007: •
Additional primary sites allow the hierarchy to support more clients.
•
Cannot be tiered below other primary sites.
•
No longer used as a boundary for client agent settings or security.
•
Participates in database replication.
Secondarysite Controls content distribution for clients in remote locations across links that have limited network bandwidth. Secondary sites in Configuration Manager 2012 have the following differences from secondary sites in Configuration Manager 2007: •
SQL Server is required and SQL Server Express will be installed during site installation if required.
•
A proxy management point and distribution point are automatically deployed during the site installation.
•
Secondary sites can be tiered to support content distribution to remote locations.
•
Participates in database replication.
HardwareRequirements Note: The following page on Technet describes the recommended hardware requirements for a stand-alonePrimaryServer. Stand-alone primary site (SQL Server installed Locally) •
Up to 100,000 clients
•
SQL Server is installedon the site servercomputer
The following hardware requirements are recommended for a stand-alone Primary server. •
8 cores (Intel Xeon E5504 or comparable CPU)
•
32 GB of RAM
•
550 GB hard disk space for the operating system, SQL Server, and all database files
Step1. Createthe LabEnvironment We are going to create a StandalonePrimarySite in our LAB (creating a CAS and then another Primary is a bit more work, I may write up that process in the future), so let's get started, and to start off with I re-used/recycled my lab from Beta 2 by applying the day 1 snapshots effectively giving me a blank activated AD and blank SCCM 2012 server with the Operating System ready and activated. This is a huge advantage of doing labs in a virtual environment. The SCCM 2012SP1 server for this lab has a C: partition (OS) and 150GB D: partition (DATA). The Domain Controller (ADSERVER) is running Server 2008 R2 Datacenter, and is hosting the DHCP server and DNS roles. I chose to install Windows Server 2008 R2 Datacenter as the server OS for SCCM 2012 SP1. Once done I joined it to my domain (ADSERVER), verified DNS was working correctly via nslookupand was ready to begin the steps below.
CreatetwoServiceAccountsin AD UsersandComputers: Note: Performthe followingon the ActiveDirectoryDomainController(ADSERVER)serveras Local Administrator 1. SMSAdmin 2. SQLAdmin Providethe followingpermissionsto boththe accounts: 1. Domain Admins 2. Enterprise Admins 3. Schema Admins 4. Administrators 5. Domain Controllers
ProvideLocalAdministratorpermissionsto theseaccountson SCCMServer: Note: Performthe followingon the SCCM2012serveras Local Administrator On the SCCM server add the SMSAdminuser and SQLAdminto the LocalAdministrators group. Also add the SCCM Computer account to the Administrators group as shown below:
Step2. DownloadSCCM2012SP1 you can download it from Microsoft http://aka.ms/DLSCSUITE2012 . Systemrequirements SupportedOperatingSystems:Windows Server 2003 R2 x64 editions, Windows Server 2008, Windows Server 2008 R2 Site SystemRequirements •
Site servers and site roles require 64-bit OS (distribution points are an exception)
BranchDistributionPoints •
Branch distribution points have been deprecated and replaced with standard distribution points that can be hosted on Configuration Manager 2012 client operating system platforms, with the exception of Windows XP Professional Service Pack 3 and Windows XP Tablet PC SP3
•
Standard DPs can run on Windows Server 32-bit but will not support advanced functionality
ServerOperatingSystemRequirements •
Windows Server 2008 (64-bit) and Windows Server 2008 R2
•
Distribution points can run on Windows Server 2003
ClientOperatingSystemRequirements •
Windows XP professional SP3 – x86 and Windows XP SP2 pro for 64 bit systems
•
Windows Vista SP2 (x86,x64)
•
Windows Server 2003 R2 SP2 (x86,x64)
•
Windows Server 2008 (x86,x64)
•
Windows Server 2008 R2 (x86,x64)
•
Windows 7 (x86,x64)
DatabaseRequirements •
SQL Server 2008 SP2 with CU 7
•
SQL Server 2008 R2 with SP1 and Cumulative Update 4
•
SQL Server Express 2008 r2 WITH SP1 and CU 3 is supported only on secondary sites
•
SQL Reporting Services is ONLY reporting solution
For Supported Configurations information, visit http://technet.microsoft.com/enus/library/gg682077.aspx.
Step3. CreateTheSystemManagementContainer Note: Performthe followingon the ActiveDirectoryDomainControlleras a DomainAdministrator Open ADSIEdit, 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=Systemand choose New, Object
Choose Container from the options, click Next and enter SystemManagementas the value. Click Next and Finish. Press F5 to refresh ADSI Edit and you should now see the new System Management Container.
Step4. DelegatePermissionto the SystemManagement Container. Note: Performthe followingon the ActiveDirectoryDomainController(ADSERVER)as a Domain Administrator(SMSAdmin) Open ActiveDirectoryUsersandComputers. Click on view, select AdvancedFeatures. Select the SystemManagementContainer, and right click it, choose All Tasks and Delegate Control.
When the Welcometo Delegationof Control Wizard appears click next, then click Add. click on ObjectTypes, select Computers. Type in your SCCMserver name and click on CheckNames, it should resolve.
Click Ok, then Next. Choose Createa CustomTaskto Delegate, click next, make sure This folder, existingobjectsin this folderand creationof newobjectsin this folder is selected.
click next, select the 3 permissions General, Property-SpecificandCreation-deletionof specificchild objects are selected then place a check mark in FULLCONTROL, and click next then Finish.
Failure to do the above will mean that the SystemManagementContainer 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: Repeatthe abovefor Eachsite serverthat youinstall in a Hierarchy. Permissions can also be assigned this way: Clickon > Start > dsa.msc{enter}> View> Advanced
Expand "System" > Locate the container you created "System Management" > right click it and select properties > Security Tab > Add > Object Types > Tick Computers > OK.
Click Advanced > Find Now > Locate and add the SMSAdmin account you created earlier > Also add the SCCM Server itself > OK.
Grant allow "Full Control" to both the SMSAdmin user and the SCCM Server
Now click advanced > Select the SMSAdmin user > Edit
Change the "Apply to" section from "This object only" to "This object and all descendant objects" > OK > Apply > OK.
Repeat the above for the SCCMServer object
Step5. Extendthe ActiveDirectoryschemafor ConfigurationManager Note: Performthe followingon the ActiveDirectoryDomainController(ADSERVER)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 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 RunAs Administrator.
OR browse the installation media of SCCM 2012SP1 and then open SMSSetup\Bin\x64\ Extadsch.exe, right click and choose RunAs 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
Quote
<10-27-2011 07:31:43> Modifying Active Directory Schema - with SMS extensions. <10-27-2011 07:31:43> DS Root:CN=Schema,CN=Configuration,DC=server2008r2,DC=lab,DC=local <10-27-2011 07:31:45> Defined attribute cn=MS-SMS-Site-Code. <10-27-2011 07:31:45> Defined attribute cn=mS-SMS-Assignment-Site-Code. <10-27-2011 07:31:45> Defined attribute cn=MS-SMS-Site-Boundaries. <10-27-2011 07:31:45> Defined attribute cn=MS-SMS-Roaming-Boundaries. <10-27-2011 07:31:45> Defined attribute cn=MS-SMS-Default-MP. <10-27-2011 07:31:46> Defined attribute cn=mS-SMS-Device-Management-Point. <10-27-2011 07:31:46> Defined attribute cn=MS-SMS-MP-Name. <10-27-2011 07:31:46> Defined attribute cn=MS-SMS-MP-Address. <10-27-2011 07:31:46> Defined attribute cn=mS-SMS-Health-State. <10-27-2011 07:31:46> Defined attribute cn=mS-SMS-Source-Forest. <10-27-2011 07:31:46> Defined attribute cn=MS-SMS-Ranged-IP-Low. <10-27-2011 07:31:46> Defined attribute cn=MS-SMS-Ranged-IP-High. <10-27-2011 07:31:46> Defined attribute cn=mS-SMS-Version. <10-27-2011 07:31:46> Defined attribute cn=mS-SMS-Capabilities. <10-27-2011 07:31:47> Defined class cn=MS-SMS-Management-Point. <10-27-2011 07:31:48> Defined class cn=MS-SMS-Server-Locator-Point. <10-27-2011 07:31:48> Defined class cn=MS-SMS-Site. <10-27-2011 07:31:48> Defined class cn=MS-SMS-Roaming-Boundary-Range. <10-27-2011 07:31:48> Successfully extended the Active Directory schema. <10-27-2011 07:31:48> Please refer to the ConfigMgr documentation for instructions on the manual <10-27-2011 07:31:48> configuration of access rights in active directory which may still <10-27-2011 07:31:48> need to be performed. (Although the AD schema has now be extended, <10-27-2011 07:31:48> AD must be configured to allow each ConfigMgr Site security rights to <10-27-2011 07:31:48> publish in each of their domains.)
Step6. OpenTCPport 1433and4022for SQL
replication Note: Performthe followingon the SCCMServeras a DomainAdministrator (SQLAdmin/SMSAdmin) If youare settingup a hierarchy(CAS/Primary/etc)thenon your AD serverdo the following,start GroupPolicyManagementtool andcreatea newGPO,
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 numbers of the instance of the Database Engine, such as 1433, 4022 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 clickNext. 7. In the Name dialog box, type a name and description for this rule, and then click Finish.
Step7. Install .NET3.5.1 andWCFActivation Note: Performthe followingon the SCCM2012serveras SMSadmin In ServerManager select Features, Add Features, Select .NETFramework3.5.1, also select WCF Activationand when prompted answer AddRequiredRoleServicesclick next and next again
Verify the following IIS componentsare installed in addition to the ones preselected by the wizard.
Quote
CommonHTTPFeatures Static Content Default Document Directory Browsing HTTP Errors HTTP Redirection ApplicationDevelopment ASP.NET .NET Extensibility ASP ISAPI Extensions ISAPI Filters HealthandDiagnostics HTTP logging Logging tools Request Monitor Tracing Security Basic Authentication Windows Authentication
URL Authorization Request Filtering IP and Domain Restrictions Performance Static Content Compression ManagementTools IIS Management Console IIS Management Scripts and Tools Management Service IIS 6 Management Compatibilty IIS 6 Metabase Compatibility IIS 6 WMI Compatibility IIS 6 Scripting Tools IIS 6 Management Console
answer yes to any additional prompts, then Click Next and Install and close when done.
Step8. Downloadandinstall .NET4 Note: Performthe followingon the SCCMserveras SMSadmin/SQLAdmin Download .NET 4 from here (webinstall) or here (Standalone). Double click the file, After a while it will complete, Click Finish when done
restart when prompted Note: In some scenarios, such as when IIS is installed or reconfigured after the .NET Framework version 4.0 is installed, you must explicitly enable ASP.NET version 4.0. For example, on a 64-bit computer that runs the .NET Framework version 4.0.30319, run the following command:%windir%\Microsoft.NET\Framework64\v4.0.30319\aspnet_regiis.exe –i –enable
Step9. AddBITSandRemoteDifferentialCompression Note: Performthe followingon the SCCMserveras SMSadmin/SQLAdmin Finally, in ServerManager click on AddFeatures, place a selection mark in BITS and RDC.
Now enable WebDAV Publishing: To enable WebDav > Start > Administrative Tools > Internet Information Services (IIS) Manager > Expand {server name} > Sites > Default Web Site > Double Click on WebDav Authoring Rules.
Select Enable WebDav (On the right hand side).
Select add authoring Rule > All Content > All Users > Permissions > Read > OK.
Select the rule you have just created > WebDav Settings.
Change "Allow Anonymous Properties Queries" to True > Change "Allow Custom Properties" to False > Change "Allow Property Query with Infinite Depth" to True > Change "Allow hidden files to be listed" to True > Apply.
Step10. DownloadandInstall MicrosoftSQLServer2008 R2 Note: Performthe followingon the SCCMserveras SMSadmin/SQLAdmin The supportedversionsof SQLServer2008andSQLServer2008R2 are listedhereon Technet:http://technet.micro...nfigSQLDBconfig The link used above to download the SCCM 2012SP1 will also download some other setups including SQL Server 2008 R2. The link is: http://aka.ms/DLSCSUITE2012 From the SQL install media run setup.exe > Installation > "New Installation or add features to an existing Installation" > OK.
Enter product Key if applicable or you may use the evaluation edition> Next > "I accept..." > Next > Install > Next > Next
You may use the "Default Instance" or the "Named Instance" as per your requirement. I have installed using the "Default Instance". .
Click on Use the same account for all SQL Server Services > Click on Browse > Choose the Service account that we had created earlier (SQLAdmin)> OK > Insert the password of this account that we provided while account creation and then OK
And Click Next > Accept "Windows Authentication" > Add in your SMSADMIN user and SQLADMIN User > Next > Next > Next > Install.
And finally you will see that the SQL Server has been installed successfully. Now Click on Close.
Now we have to configure the SQL Server communication ports with the followings:
Now Open SQL Server Management Studio: Start>All Programs> Choose and expand the installed SQL Server instance and select SQL Server Management Studio
Step12. Install WADK(WindowsAssessmentand DeploymentToolkit) Note: Performthis on SCCMServerPC. We no longer use WAIK, we’re now on WADK for Windows 8. To download the WADK, Please click the following Link. http://www.microsoft.com/en-us/download/details.aspx?id=30652 Onceyoudownloadedthe file just install it as shownin belowscreens.It will ask to Install on the samePC or youmaychoosethe secondoptionso savethe files. Youmayprovidethe pathof the destination folder. In my caseI selectedthe E:\. Oncethis is donefollowthe belowsteps. Install the Windows Assessment and Deployment Kit ( ADK ) for Windows 8. -Run E:\installfiles\adksetup.exe to install the Windows Assessment and Deployment Kit. -When prompted during the setup process, select the following components to install: - User State Migration Tools ( USMT ) - Windows Deployment Tools - Windows PE
Click Yes if you like to join for the customer Experience and you can Click NO and press Next Button to continue the installation.
Click Accept under License Agreement.
Then select the following 3 option as shown in the screen and Click Install button to download the necessary tools for SCCM installation.
Step13. Install ConfigurationManager2012SP1. Note: Performthe followingon the SCCMserveras SMSadmin/SQLAdmin From the product DVD or setup ISO file, if the startup screen does not run automatically, double-click splash.hta.
On the Start page, click Install to proceed the installation.
when the wizard appears, click on Install, click next at the warning and then select Install a ConfigurationManagerPrimarySite
at the EULA click accept
Create a folder on D:\ called RC_Updates and then specify the path to download the updates Tip: If you don't have internet on your SCCM server then you can download the required updates on another computer by doing like so:•
Open a command prompt with administrative permissions
•
Navigate to .\Configuration Manager 2012 Install source\smssetup\bin\X64
•
Run SetupDL.exe target dir (in my example SetupDL.exe D:\RC_Updates)
Click next at the Server Language screen
and at the Client Language Screen
enter your Site and Installation Settings, install the site on D:\ as per below screenshot
select Standaloneas the site type
take note of the warning (ie: if will not be able to join it to an existing site heirarchy later)
review the DatabaseInformation
review the SMSprovidersettings
review the Clientcomputercommunicationsettings, select Configure the Communication method on each site system role
review the site systemroles
click next at the CEIP screen then review the summary
take note of any warnings, if like mine (WSUS and SQL memory, we can fix them later, no problem)
click on BeginInstall now is a good time to look at the C:\ConfigMgrSetup.logwith CMtrace, watch it for errors
after a long install you should see the installer finish, click on Close
reboot the SCCM server and then login again as SMSadmin start the Configmgr console congratulations, you've installed SystemCenter2012ConfigurationManagerReleaseCandidate
Note: This is Part 1 of a seriesof step-by-stepGuidesfor ConfigurationManager2012. To viewthe entire list pleasesee this index. This guideandall guideshere are © windows-noob.com,no reproduction allowedwithoutpreviouswrittenpermission.
