SCCM stands for System centre configuration manager, SCCM is a software management suite provided by Microsoft that allow user to manage a large number of windows based computers. SCCM features remote control, patch management, operating system deployment, network protection and other various services.
Note : SCCM was formerly known as System Management server (SMS), originally released in 1994, In november 2004 SMS was renamed to SCCM and is sometimes called configuration manager.
Users of SCCM can integrate with Microsoft InTune, allowing them to manage computers connected to a business, or corporate, network. SCCM allows users to manage computers running the Windows or macOS, servers using the Linux or Unix, and even mobile devices running the Windows, iOS, and Android operating systems.
SCCM is available from Microsoft and can be used on a limited-time trial basis. When the trial period expires, a license needs to be purchased to continue using it.
What’s New In System Center 2012 R2 Configuration Manager
1) System Center 2012 R2 Configuration Manger now supports deployment of Windows 8.1 and Windows server 2012 R2. There is added support for boot images created by using the Windows Automated Installation Kit (Windows AIK) for Windows 7 SP1 and based on Windows PE 3.1.
2) System Center 2012 R2 Configuration Manger is now integrated with Windows Intune and this is named as Unified Modern Device Management. This means you can use System Center 2012 R2 Configuration Manager together with Windows Intune to manage a broad array of PCs and devices covering Windows, Windows RT, Macs, Windows Phone, Apple iOS and Android.
3) You can now select Resultant Client Settings (RSOP) from the Configuration Manager console to view the effective client settings that will be applied to the selected device. This is another great feature.
4) You can now reassign Configuration Manager clients, including managed mobile devices, to another primary site in the hierarchy. Clients can be reassigned individually or can be multi-selected and reassigned in bulk to a new site.
5) Compliance Settings – New mobile device settings and mobile device setting groups have been added.
6) Application Management – Web applications in System Center 2012 R2 Configuration Manager are a new deployment type that allows you to deploy a shortcut to a web-based app on users devices.
7) Collections – A new management option allows you to configure maintenance windows to apply to task sequences only, software updates only, or to all deployments.
System Center 2012 R2 Configuration Manager Design
Before we install the System Center 2012 R2 Configuration Manager it would be better to have an idea on System Center 2012 R2 Configuration Manager Site and System Roles and how are we going to install the roles and their limits. In most of the cases planning for hardware and software requirements for Configuration manager takes more time, so it is very important to understand about the site and system role scalability.
- Central Administration Site (CAS) – 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.
- Primary Site – Each primary site can support up to 250 secondary sites and up to 1,00,000 clients.
- 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.
- 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.
- 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.
- Software Update Point – A software update point that is installed on the site server can support up to 25,000 clients.
- Fallback status point – Each fallback status point can support up to 100,000 clients.