What is MS System Center Configuration Manager?
System Center 2012 R2 delivers unified management across on-premises, service provider, and Microsoft Azure environments. System Center 2012 R2 offers exciting new features and enhancements across infrastructure provisioning, infrastructure monitoring, application performance monitoring, automation and self-service, and IT service management.
MS System Cetner 2012 R2 Architecture and Deployments Methods”
1) Central Administration Site – A central administration site can support up to 25 child primary sites. When you install a Central Administration Site and use an Enterprise or Datacenter edition of SQL Server, the hierarchy can support a combined total of up to 400,000 devices. So you must plan for CAS only when an organization has over 1,00,000 clients.
2) Primary Site – Each primary site can support up to 250 secondary sites and up to 1,00,000 clients.
3) Secondary Site – A secondary site supports a maximum of 5,000 clients. For secondary sites SQL Server must be installed on the site server computer and in a location if there are fewer than 500 clients, consider a distribution point instead of a secondary site.
4) Management Point – Each primary site supports up to 10 management points and each primary site management point can support up to 25,000 computer clients. Each secondary site supports a single management point which must be installed on the site server computer.
5) Distribution Point – With System Center 2012 R2 Configuration Manager each primary and secondary site supports up to 250 distribution points and each distribution point supports connections from up to 4,000 clients. Each primary site supports a combined total of up to 5,000 distribution points. This total includes all the distribution points at the primary site and all distribution points that belong to the primary site’s child secondary sites. Each primary and secondary site supports up to 2000 additional distribution points configured as pull-distribution points. For example, a single primary site supports 2250 distribution points when 2000 of those distribution points are configured as pull-distribution points.
6) Software Update Point – A software update point that is installed on the site server can support up to 25,000 clients.
7) Fallback status point – Each fallback status point can support up to 100,000 clients.
2.System Center 2012 R2 Requirements
Ø Disk Space: 50 GB Free Space.
Ø Processor: AMD and Intel -Min 1.4 GHz
- MS Server: 64 Bit version
- Collation: SQL_Latin1_General_CP1_CI_AS
- RAM: 8 G memory in buffer pool per SQL instance, Central Administration Site and Primary Site min-4G of memory. Shared MS SQL or Oracle Database (Will be using MS SQL 2012 Express )
- 2.4 Active Directory Domain Supported: Domain Functional Level- Window 2000, WindowsServer 2003, Windows Server 2008 and 2008 R2, Windows Server 2012 and 2012 R2.
2.5 System Center 2012 R2 Supported Managed Console OS Client List
|Operating Systems||Services Pack||Other Requirements|
|Windows XP Professional||SP3||Net Framework 4|
|Windows 7 Professional, Enterprise and Ultimate||SP1||X86 and 64 bit, Net Framework 4|
|Windows 8, and 81 Pro and Enterprise||SP1||X86 and 64 bit, Net Framework 4|
|Windows 2008 Standard, Enterprise, Datacenter Edition||SP2||X86 and 64 bit, Net Framework 4|
|Windows 2012 R2 Standard, Enterprise and Datacenter||SP1||X86 and 64 bit, Net Framework 4,5|
2.6 SCCM 2012 Prerequisite Checker!! Awesome Tool
SCCM 2012 R2-System Center 2012 R2 Configuration Manager Install Guide
I. SCCM Prerequisites Requirements:
1. Create System Management Container in AD
a. Open ADSI Edit, click on Action, Connect To and click Ok, Double Click on Default Naming Context and the DC=<Domain Controller>
b. Click on the + and scroll down to CN=System.
c. Right Click on CN=System and choose New, Object Choose Container from the options.
d. Click Next and enter System Management as the value.
e. Click Next and Finish.
f. Press F5 to refresh ADSI Edit and you should now see the new System Management Container. Close ADSI Edit.
2. Delegate control to the SCCM site server to the newly created container in AD Users and Computers.
a. Open Active Directory Users and Computers. Click on view, select Advanced Features.
b.Select the System Management Container, and right click it, choose All Tasks and Delegate Control.
c. When the Welcome to Delegation of Control Wizard appears click Next,
d.Click Add. Then Click on Object Types, select Computers.
e. Type in your SCCM server name and click on Check Names, it should resolve.
f.Click Ok, then Next.Choose Create a Custom Task to Delegate, click next,
g. 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.
3.Extend the AD Schema
Extend the Active Directory schema for Configuration Manager Note: Perform the following on the Active Directory Domain Controller as a Domain Administrator
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.
4.Install Site Server roles and features Prerequisites
5.Install Windows Assessment and Deployment Kit (Windows ADK) for Windows 8.1
a.User State Migration Tool (USMT)
b.Windows Deployment Tools
c.Windows PreInstallation Environment (Windows PE)
6.Install SQL Server SQL Server 2012 SP1
i.‘SQL Collation, used for backwards compatibility’
ii.choose SQL_Latin1_General_CP1_CI_AS. Click Ok. Click Next.
b. SQL RAM -SSMS and limit the amount of RAM SQL 50% of total RAM.
Set the value for both max and min.
c. Set SQL Server to run with either a named domain account, network service or local system account.
2.7. System Center 2012 R2 Configuration Manager Installation Steps.
1. Begin the install of SCCM 2012 R2 by running splash.hta. Click Install.
2. Click Next, To Begin.
4.Enter a licence key or evaluate. Click Next.
a.Accept the licence agreement and click Next.
b.Accept pre-req licences and click Next.
5.Create a folder to store install updates and point the SCCM install to that location. Click Next.
6.Updates will download and install.
a. Select any language requirements for the SCCM server and click Next.
b. Select any client language requirements and click Next.
7.Enter a 3 digit site code and description and click Next.
8.Choose whether to run the primary as stand-alone or join to an existing hierarchy. Click Next.
a, In this instance a stand-alone primary is being installed.
Click Yes to accept. Accept the database default configuration and click Next.
9. Specify the path to the SQL database file and log file. In this instance it is the defaults. Click Next.
10. Click Next to set the current server as the SMS Provider
11. Specify the path to the SQL database file and log file. In this instance it is the defaults. Click Next.
12.Set ‘Configure the communication method on each site system role’ as a PKI infrastructure is not being used. Click Next.
13.Install both a MP and a DP onto the site server. Click Next.
14. Choose whether to join the CEIP. Click Next.
15.Click Next at the Summary screen.
16. The following warnings can be ignored at the pre-req check screen. Click Begin Install.
SCCM will begin the installation.
17.Click close when complete.
a. SCCM 2012 R2 Installation Guide.
b.Planning for Discovery in Configuration Manager
2.8 SCCM 2012 R2 -Install SUP and WDS Roles
We’ll need the WSUS role installed as part of the Software Update Point role installation in the next step, so: Start Server Manager and click on Roles > Add Roles. Select Windows Server Update Services and a window will pop up asking to add role services required for Windows Server Update Services (IIS Dynamic Content compression)
Start up the ConfigMgr console, click on Administration in the Wunderbar, click on Site Configuration, and select Servers and Site System Roles, Right click on your server and choose Add Site System Role
2.8 SCCM 2012 -Discery and Boundaries:
Configuring Discovery and Boundaries In Part 1 of this series we got our AD and SCCM servers ready, and then we installed System Center 2012 Configuration Manager as a standalone Primary site. In Part 2 we configured the SCCM server further by adding some Windows Server roles necessary for the following Configuration Manager 2012 functionality, Software Update Point (SUP) and Operating System Deployment. Now we will configure the server further by Enabling some Discovery methods and creating Boundary’s and Boundary Groups. Configuring Discovery Methods:
When you want to discover computers, you can use Active Directory System Discovery or Network Discovery.
As an example, if you want to discover resources that can install the Configuration Manager client before you use client push installation, you might run Active Directory System Discovery. Alternately you could run Network Discovery and use its options to discover the operating system of resources (required to later use client push installation). However, by using Active Directory System Discovery, you not only discover the resource, but discover basic information and can discover extended information about it from Active Directory Domain Services. This information might be useful in building complex queries and collections to use for the assignment of client settings or content deployment. Network Discovery, on the other hand, provides you with information about your network topology that you are not able to acquire with other discovery methods, but Network Discovery does not provide you any information about your Active Directory environment.
It is also possible to use only Heartbeat Discovery to force the discovery of clients that you installed by methods other than client push installation. However, unlike other discovery methods, Heartbeat Discovery cannot discover computers that do not have an active Configuration Manager client, and returns a limited set of information. It is intended to maintain an existing database record and not to be the basis of that record. Information submitted by Heartbeat Discovery might not be sufficient to build complex queries or collections.
If you use Active Directory Group Discovery to discover the membership of a specified group, you can discover limited system or computer information. This does not replace a full discovery of computers but can provide basic information. This basic information is insufficient for client push installation.
When you want to discover information about users, you can use Active Directory User Discovery. Similar to Active Directory System Discovery, this method discovers users from Active Directory and includes basic information in addition to extended Active Directory information. You can use this information to build complex queries and collections similar to those for computers.
Discover Group Information
When you want to discover information about groups and group memberships, use Active Directory Group Discovery. This discovery method creates resource records for security groups.
You can use this method to search a specific Active Directory group to identify the members of that group in addition to any nested groups within that group. You can also use this method to search an Active Directory location for groups, and recursively search each child container of that location in Active Directory Domain Services.
This discovery method can also search the membership of distribution groups. This can identify the group relationships of both users and computers.
When you discover a group, you can also discover limited information about its members. This does not replace Active Directory System or User Discovery and is usually insufficient to build complex queries and collections or serve as the bases of a client push installation.
There are two methods that you can use to discover network infrastructure, Active Directory Forest Discovery and Network Discovery.
You can use Active Directory Forest Discovery to search an Active Directory forest for information about subnets and Active Directory site configurations. These configurations can then be automatically entered into Configuration Manager as boundary locations.
When you want to discover your network topology, use Network Discovery. While other discovery methods return information related to Active Directory Domain Services and can identify the current network location of a client, they do not provide infrastructure information based on the subnets and router topology of your network.
SCCM Config Manager 2012 SP1 Step by Step Guide Boundaries and Discovery [embeddoc url=”http://blog.itsysintegration.net/wp-content/uploads/2014/12/SCCM-Config-Manager-2012-SP1-Step-by-Step-Guide-Boundaries-and-Discovery.pdf” download=”all”]