System Center 2012 Configuration Manager increases IT productivity and efficiency by reducing manual tasks and letting you focus on high-value projects, maximize hardware and software investments, and empower end-user productivity by providing the right software at the right time.
Note: The following section introducing SCCM and Limitations for site systems is copied from Microsoft Technet Site as is and is not written by me , the information is presented as is for the sake of delivering the best Value to the readers, Thank You
Configuration Manager helps you deliver more effective IT services by enabling secure and scalable software deployment, compliance settings management, and comprehensive asset management of servers, desktops, laptops, and mobile devices.
In this article series i am going to show you how to deploy SCCM 2012 R2 server, we are going to prepare our environment for deploying SCCM and we will list the software prerequisites for a successful deployment, and perform essential startup configurations.
Limitations for site systems
Site systems are not supported on Server Core installations for the following operating systems:
- Windows Server 2008 or Windows Server 2008 R2.
- Windows Server 2008 Foundation or Windows Server 2008 R2 Foundation.
- Windows Server 2012 or Windows Server 2012 R2. An exception to this is that beginning with System Center 2012 R2 Configuration Manager, these operating systems support the distribution point site system role, without PXE or multicast support.
- Windows Server 2012 Foundation or Windows Server 2012 R2 Foundation.
After a site system server is installed, it is not supported to change:
- The domain name of the domain where the site system computer is located (also called a domain rename)
- The domain membership of the computer
- The name of the computer
If you must change any of these, you must first remove the site system role from the computer and then reinstall the roles after the change is complete. If this affects the site server computer, you must uninstall the site and then reinstall the site after the change is complete.
Site system roles are not supported on an instance of a Windows Server cluster. The only exception to this is the site database server.
It is not supported to change the startup type or Log on as settings for System Center 2012 Configuration Manager services. Doing so might prevent key services from running correctly.
Well 🙂 having said that let’s begin with Preparing the Environment for the SCCM installation.
Extending the Active Directory Schema for SCCM
In order to make use of all SCCM features and functions and ensure that Configuration Manager clients are able to query Active Directory to locate site resources, you are going to need to extend your Active directory Schema to publish your site information into Active directory. Extending your schema can be done before or after SCCM installation and it requires a user which is a member of the Schema Admins Active directory gorup.
Please note that SCCM Schema extensions for SCCM 2012 R2 are not different from those used by SCCM 2007, which means if you previously extended your schema using SCCM 2007, you no longer need to do this again.
Following am going to show you Four steps that needs to be done to accomplish this, So let’s start with Extending the Active directory Schema with the SCCM extensions “if you need to” 🙂
Extend the Active Directory Schema
The first step would be to Extend the Active Directory Schema, and there are two ways to do this. Using the extadsch.exe utility, Or using the LDIFDE utility to import the schema extension information by using the ConfigMgr_ad_schema.ldf file.
The two ways provide you with the same results , the only difference between them is the results visibility, as using the LDIFDE utility provides greater visibility for the changes made to the schema, besides using the extadsch.exe utility is not supported when being run on Windows 2000 Servers, either ways you need to first take a backup for the system state of the Domain controller that holds the Schema Master FSMO role before proceeding with one of the above methods, then you need to make sure you are logged on with a user with the appropriate permissions, that would be a Schema Admins member.
in this article i will be using the extadsch.exe method. Okay go a head and open an elevated CMD.
Navigate to the SMSSetup\BIN\x64 folder located on the SCCM media and run the extadsch.exe file
Well.. We are done with the First step , let’s move on
Create the System Management Container
So System management container is not created by default when you extend your schema, you are going to need to create it manually on every domain that will has a primary or secondary site server.
Now you can automatically have SCCM to create this management container when it first publishes site information to active directory by assigning Site servers Full control permissions over the Systems Container in Active directory, but as a security practice this is not recommended, so we are going to proceed with creating it manually using ADSIEdit
Open Adsiedit.msc and connect to the Default naming context
Set Security Permissions on the System Management Container
For the site servers to be able to publish site information in active directory System Management container that we have just created, we need to assign Full control permissions to those servers Computer accounts over this container. this can be done from either the Active Directory user and computer console or the ADSIedit console. am just going to go ahead and do it from the Active directory users and computers. You will need to check the Advanced features view in order to see the System Container in AD console.
Enable Active Directory publishing for the Configuration Manager site
This step is done from the SCCM Console after installation and we will get to this later.
Well, now before proceeding with the installation of the SCCM Server, i will prepare my server with all software prerequisites first, i will be installing SCCM 2012 R2 on Windows Server 2012 R2, the SCCM Database will be hosted on a two node Cluster of SQL Server 2012 Sp1. so first things are first …. Let’s begin with installing our prerequisites.
Preparing the Server
Configuration Manager requires Windows Server Update Services (WSUS) of at least version 3.0 SP2 with KB2720211 and KB2734608 installed. If using remote software update points, site server must have WSUS administration console installed.
In Windows Server 2012, WSUS is integrated with the operating system as a server role. for previous OS download and install WSUS from here http://www.microsoft.com/en-eg/download/details.aspx?id=5216
To add WSUS in windows Server 2012 open the Add Roles and Features from the Server Manager and select Windows Server update services to install
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 you will have to install it manually from the Server Manager Features.
Download and Install The User State Migration Tool component of Windows Assessment and Deployment Kit (ADK) for Windows 8.1 from here http://www.microsoft.com/en-us/download/details.aspx?id=39982
Select the required features and click next to download and install.. you need at least to select USMT, Windows PE and Deployment tools.
Open the Server Manager ADD Roles and Features wizard, from the Server Roles page click on IIS 6 WMI Compatibility and on the Features page you will need to install Background intelligent Transfer Service (BITS).
Configuration Manager requires SQL Server to reserve a minimum of 8 gigabytes (GB) of memory for the central administration site and primary site and a minimum of 4 gigabytes (GB) for the secondary site. This memory is reserved by using the Minimum server memory setting under Server Memory Options and is configured by using SQL Server Management Studio. However this will not prevent you from installing SCCM , it will only display a warning on the prerequisites checker..
And that Would be all for Preparing the server for installation, one more thing i would like to mention here is a nice tool for prerequisites check that can be downloaded from here ConfigMgr 2012 R2 Prerequisites Installation Tool 1.3.0 , but this tool would only work on Windows Server 2012 and 2012 R2, you will need to run it as an Administrator from the Windows Powershell.
With all prerequisites done i will leave you with this part of the article, in the next part we will start installing SCCM 2012 R2 and once we are done we are going to startup with some essential configurations. See You .. 🙂