Installing ConfigMgr 2012 RC
Prepare the Windows Environment for Configuration Manager
To allow ConfigMgr clients to query Active Directory Domain Service to locate site resources, three actions are required:
- Extend the Active Directory schema.
- Create the System Management container.
- Set security permissions on the System Management container.
Extend the Active Directory Schema
To extend the schema user account must be member of the Schema Admins Group or who has been delegated with required permissions to modify the schema.
You can extend the Active Directory schema by running the extadsch.exe file located in the SMSSETUP\BIN\X64


Create the System Management Container
Configuration Manager does not automatically create the System Management container in Active Directory Domain Services when the schema is extended. The container must be created one time for each domain that includes a Configuration Manager primary site server or secondary site server that publishes site information to Active Directory Domain Services.
You can grant the site servers computer account Full Control permission to the System container in Active Directory Domain Services, which results in the site server automatically creating the System Management container when site information is first published to Active Directory Domain Services. However, it is more secure to manually create the System Management container.
In this document we are going to grand full control permission to the System container in Active Directory Domain Service.
To manually create the system Management container please check the following link:
http://technet.microsoft.com/en-us/library/gg712264.aspx#BKMK_CreateSMContainer
Remote Differential Compression
- 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.
-
On the Select Features page, select Remote Differential Compression, and then click next.

- Complete the wizard and close Server Manager to complete the configuration.

Internet Information Services (IIS)
-
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.
- On the Select Features page of the Add Features Wizard, install any additional features that are required to support the site system roles you install on this computer. For example, to add BITS Server Extensions:
For Windows Server 2008, select the BITS Server Extensions check box. For Windows Server 2008 R2, select the Background Intelligent Transfer Services (BITS) check box. When prompted, click Add Required Role Services to add the dependent components, including the Web Server (IIS) role, and then click Next.

-
On the Web Server (IIS) page of the Add Features Wizard, click Next.
-
On the Select Role Services page of the Add Features Wizard install any additional role services that are required to support the site system roles you install on this computer. For example, to add ASP.NET and Windows Authentication:
- For Application Development, select the ASP.NET check box and, when prompted, click Add Required Role Services to add the dependent components.
-
For Security, select the Windows Authentication check box.

-
In the Management Tools node, for IIS 6 Management Compatibility, ensure that both the IIS 6 Metabase Compatibility and IIS 6 WMI Compatibility check boxes are selected, and then click Next.
- On the Confirmation page, click Install, complete the wizard, and close Server Manager to complete the configuration
Request Filtering for IIS
By default, IIS blocks several file extensions and folder locations from access by HTTP or HTTPS communication. If your package source files contain extensions that are blocked in IIS, you must configure the requestFiltering section in the applicationHost.config file on distribution point computers.
The following file extensions are used by Configuration Manager for packages and applications. Allow the following file extensions on distribution points:
When you use the default IIS configuration on a distribution point, clients that use BITS fail to download this software deployment from the distribution point. In this scenario, the clients indicate that they are waiting for content. To enable the clients to download this content by using BITS, on each applicable distribution point, edit the requestFiltering section of the applicationHost.config file to allow access to the files and folders in the software deployment.

Install Sites and Create a Hierarchy for Configuration Manager
Setup Downloader
Configuration Manager Setup Downloader is a stand-alone application that verifies and downloads required prerequisite redistributables, language packs, and the latest product updates for Setup.
- On a computer that has Internet access, open Windows Explorer, and browse to <ConfigMgrSourceFiles>\SMSSETUP\BIN\X64.
-
Double-click setupdl.exe. The Setup Downloader opens.

-
Specify the path for the folder that will host the updated installation files, and then click Download.

Prerequisite Checker
The Prerequisite Checker (prereqchk.exe) is a standalone application that verifies server readiness for a site server or specific site system roles. Before site installation, Setup runs the Prerequisite Checker.
System Center 2012 Configuration Manager Setup Wizard
When you run Setup, the local computer is scanned for an existing site server and provides only the options that are applicable, based on the scan results. The System Center 2012 Configuration Manager Setup Wizard provides the following options to install, upgrade, or uninstall a site:
- Install a Configuration Manager primary site server: When you choose to install a new primary site, you can manually configure the site settings in the wizard or allow Setup to configure the site with a default installation path, to use a local installation of SQL Server with the default instance for the site database, to install a management point on the site server, and install a distribution point on the site server.
- Install a Configuration Manager central administration site: The central administration site is used for reporting and to coordinate communication between primary sites in the hierarchy. There is only one central administration site in a System Center 2012 Configuration Manager hierarchy and the central administration site must be the first site installed. .
- Upgrade an existing Configuration Manager installation: Choose this option to upgrade an existing version of System Center 2012 Configuration Manager.
- Uninstall a Configuration Manager site server: When an existing site is detected on the local computer, you have the option to uninstall the site server.
To install a stand-alone primary site:
- On the server where you want to install ConfigMgr 2012, open Windows Explorer and browse to <ConfigMgrSourceFiles>\SMSSETUP\BIN\X64.
- Double click on setup.exe, The ConfigMgr setup wizard will open.

- On the Getting Started page select Install a Configuration Manager primary site and click next.

- On the Microsoft Software License Terms accept license terms and click next.

- On the Updated Prerequisites Components choose Use previously downloaded updates from the following location, and set the path of updates that you download when you run setupdl.exe.

- On the Server Language Selection accept the default setting and click next.

- On the Client Language Selection accept the default setting and click next.

- On the Site and Installation Settings Enter your Site code, Site name and Installation folder path, plus specify if you want to Install the Configuration Manager Console.

- On the Primary Site Installation, You have two options:
- Join the Primary site to an existing hierarchy.
- Install the Primary site as a stand-alone site.
In my scenario I’m going to install Stand-alone site.

If you choose to install Stand-alone Primary site, you will not be able to join this primary site to a hierarchy after this site installation, click Yes to continue.

- On the Database Information, on Server name write database server name (In my scenario SQL installed on the same server).
Note: Leave Instant name blank, if you choose the default instance name during SQL setup.

- On the SMS Provider Settings, Click next.

- On the Client Computer Communication Settings, select Configure the Communication method on each site system role.

- On the Site System Roles, click next.

- On the Customer Experience Improvement Program Configuration, click next.

- On the Settings Summary, click next.

- On prerequisites Check, verify if you have any error or warning and click Begin Install and wait installation until finish.
