System Center Configuration Manager
System Center Configuration Manager | |
---|---|
Basic data
|
|
developer | Microsoft |
Publishing year | 2015 |
Current version | Current branch (SCCM 1910) (November 2019) |
Current preliminary version | Technical Preview 1911 |
operating system | Windows , 7, 10, Windows Server Linux, UNIX, Android, iOS |
category | System Center Configuration Manager (ConfigMgr) |
www.microsoft.com/en-us/cloud-platform/system-center |
System Center Configuration Manager ( SCCM ) or, since version 1910, Microsoft Endpoint Configuration Manager ( ECM ) is a software product from Microsoft's System Center Suite . It replaces earlier versions with the name Systems Management Server (SMS).
(IT) systems management is generally understood to mean the centralized management of hardware and software within a company. Systems management is the superset of client management .
The following tasks can be performed automatically by SCCM for a very large number of clients:
- Inventory
-
Software distribution
- System update (patch) management
- remote maintenance
- License monitoring
- Reporting
- Anti-malware management
A Configuration Manager client, which runs as a service on the system, is installed on the device to be managed. This client (also client agent) can be installed automatically on the PCs by means of the so-called "client push installation", so that no manual action is necessary on the PCs even when SCCM is introduced in the company. If the site server cannot establish a connection to the administrative shares on the end device, the client can also be installed manually and assigned to a management point.
In addition to the Configuration Manager Client itself, the “Software Center” component is also installed, which users can use to independently install software that has been provided or uninstall applications that have already been installed.
For each of the above-mentioned tasks there is a so-called client agent, e.g. inventory agent, remote control agent. The principle is that the agents always work independently on the client and then make their results available to the SCCM server. The SCCM server saves the results in the SCCM database and provides the administrator with detailed feedback on all processes running on the client via a status system.
Features
Inventory
A large number of configuration parameters are read out via WMI and other interfaces and transmitted to the server. Both hardware configuration and, for example, installed software and operating system configuration are determined. System files are inventoried with version number and file date. Furthermore, any file types can be inventoried. With the help of software inventory, it is possible to determine on how many end devices a certain software that requires a license is installed.
The inventoried data can then form the basis for evaluations with the "SMS Reporting Services". They also form the database for software distribution. For example, a new version of Office can only be distributed to those clients who have Office installed.
Software distribution
The SMS component software distribution has been greatly enhanced by Microsoft. The software distribution is basically divided into the sections operating system installation, software installation and update installation.
The installation of an operating system can be fully automated without manual intervention by the user. By using task sequences and other methods of automation, the operating system can be adapted very precisely to the requirements of the company , e.g. B. the automatic inclusion in a domain, the installation of standard software such as virus scanners , office packages, etc. With the automated operating system installation , the boot sequence in the BIOS of the terminal device must be set to PXE boot . A previously provided WinPE boot image is then loaded from the WDS server via PXE . The boot image then starts the task sequence.
The software installation enables programs to be distributed to any organizational unit, e.g. B. Virus scanners for every client in the network, graphics programs only in the marketing department. For this purpose, the clients can be grouped into so-called "collections". These collections can be filled both manually (direct membership) and dynamically using SQL queries and inclusion / exclusion rules.
The software to be installed is distributed by the administrator to so-called "Distribution Points", which act as interim storage facilities and thus distribute the network load or B. minimize the traffic with WAN connections .
There are several ways to install software on the client. Essentially, a distinction is made here between the type of provision. SCCM can deliver applications either to users or to devices. A distinction is also made between available and required software. If software is made available to a user, the application is installed on the systems to which the user logs on. If the software is “available”, the user can install the application independently from the software center or the application catalog. If the software is “required”, it is installed without manual intervention. If the application is made available for a device, it is only available on this system (if “available”) via the software center or the application catalog - if “required” it is installed without manual intervention.
Status messages that are transmitted from the client to the server can be used in the Configuration Manager console to track whether and with what status a package was installed on a client.
The software distribution can be controlled via a large number of parameters. Packages can be installed in the background with administrative rights and completely transparently for the user, so that the user's workflow is not interrupted.
Remote control
Remote Control is a tool that makes it possible to connect to a user's PC and provide assistance to the user. In contrast to the remote desktop connection , the session of the logged on user is not disconnected, but the remote control agent forwards the user's screen. Similar products from other manufacturers include pcAnywhere , TeamViewer and VNC . For Windows XP, Microsoft favors the remote assistance integrated in XP, SMS Remote Control is still included in SCCM for reasons of compatibility with Windows 2000 and Windows NT .
Reporting
The SCCM database contains a large number of configuration parameters for all SCCM clients in the company. The aim of reporting is to prepare this data and make it available again in the form of evaluations. The Reporting Services require an Internet Information Server (Web Server) and display the selected report as an ASP page. Additional reports can be easily accessed via hyperlinks within the report, which makes the system very clear and user-friendly. After installing SCCM, a large number of reports are already available. Your own evaluations can also be generated.
License monitoring and software metering
This can be used to monitor the use of applications. The SMS reporting is used to determine which applications are started on how many workstations. This reminds the administrator in good time of license violations.
SCCM installation, configuration and administration
SCCM is suitable for medium to very large companies with up to several hundred thousand jobs. If necessary, large companies are divided into several "sites", which then form a site hierarchy. This consists of a tree, starting with a Central Administration Site (CAS) and subordinate Primary Sites. Other locations can be mapped as secondary sites, remote distribution points or using BranchCache on client PCs, depending on their size and requirements. Every site server needs a Microsoft SQL Server based database to store the information. Certain database information (“global data”) is replicated cyclically between CAS and primary sites. Secondary sites get by with a Microsoft SQL Server Express and deliver file-based data to the higher-level primary site. A parent location can see and manage all of its child locations. A child site shares its data with its parent site. With this system, even very large environments can be administered efficiently and centrally.
With the Configuration Manager console, SCCM is operated from the administrator's computer. There is a wide selection of PowerShell cmdlets for SCCM with which certain actions can be automated.
Microsoft Endpoint Manager
On November 4, 2019, Microsoft announced the Microsoft Endpoint Manager at Microsoft Ignite in Orlando 2019, consisting of a combination of Microsoft System Center Configuration Manager (ConfigMgr) and Microsoft Intune . The new management system should work on the basis of the currently existing ConfigMgr and be continuously expanded with new functions. In addition, Microsoft has announced that it will change the license model. Microsoft Intune licenses should offer the possibility to use the existing ConfigMgr without purchasing new licenses.
As part of Update 1910, released on December 4, 2019 for the ConfigMgr, the client has already been renamed to Microsoft Endpoint Manager .
Various management solutions from Microsoft are currently available as stand-alone software or cloud solutions. According to Microsoft, the ConfigMgr manages around 200 million devices together with Microsoft Intune. Microsoft wants a central program from which the setup, provision, administration and protection of endpoints and applications in the company as well as the co-management is significantly simplified. The management of end devices currently comprises the following products:
- ConfigMgr
- Intune
- Desktop Analytics
- AutoPilot
- Management console for device management
The existing solutions will be managed under the name Microsoft Endpoint Manager from 2020. Constantly new upcoming functions should be implemented over time.
Licensing
By replacing the existing ConfigMgr and Microsoft Intune with the Endpoint Manager, the license model is to be revised and simplified. Different licenses are currently required for both management solutions (ConfigMgr and Intune).
So that existing customers do not suffer a disadvantage under the new license model, Microsoft ConfigMgr licenses can also use Intune to promote co-management. However, this only applies to Windows devices. For operating systems that do not use Windows such as iOS , an Intune, Enterprise Mobility & Security (EMS) or Microsoft 365 E3 or a higher license is required.
Microsoft Endpoint Configuration Manager
Microsoft decided to rename the former ConfigMgr to the Endpoint Configuration Manager (MECM), which was presented at Microsoft Ignite in November 2019. The change is contained in Update 1910, which has been available as an internal console update since December 4, 2019.
Versions
product | Revision | Released | Service pack | Feature pack | Version / Build | comment |
---|---|---|---|---|---|---|
Systems Management Server (SMS) | 1.0 | 1994 | ||||
Systems Management Server (SMS) | 1.1 | 1995 | ||||
Systems Management Server (SMS) | 1.2 | 1996 | ||||
Systems Management Server (SMS) | 2.0 | 1999 | ||||
Systems Management Server (SMS) | 2003 | 2003 | ||||
Systems Management Server (SMS) | 2003 R2 | 2006 | ||||
System Center Configuration Manager (ConfigMgr) | 2007 | 2007 | Beta 1 | 4.00.5135.0000 | ||
System Center Configuration Manager (ConfigMgr) | 2007 | 2007 | RTM | 4.00.5931.0000 | ||
System Center Configuration Manager (ConfigMgr) | 2007 | 2008 (May) | SP1 | 4.00.6221.1000 | ||
System Center Configuration Manager (ConfigMgr) | 2007 | 2010 | SP1 | KB977203 | 4.00.6221.1193 | This update (KB 977203) may be run against SP1 or SP2 clients. |
System Center Configuration Manager (ConfigMgr) | 2007 | 2008 | R2 | no change | The R2 feature add-on requires at least SP1, and can be installed after SP2. | |
System Center Configuration Manager (ConfigMgr) | 2007 | 2009 | SP2 | 4.00.6487.2000 | ||
System Center Configuration Manager (ConfigMgr) | 2007 | 2010 | SP2 | KB977203 | 4.00.6487.2111 | This update (KB 977203) may be run against SP1 or SP2 clients. |
System Center Configuration Manager (ConfigMgr) | 2007 | 2010 | R3 | 4.00.6487.2157 | The R3 update requires SP2 client. | |
System Center 2012 Configuration Manager (ConfigMgr) | 2012 (Formerly "v.Next") |
2010/05/26 | Beta 1 | |||
System Center 2012 Configuration Manager (ConfigMgr) | 2012 | 2011/03/23 | Beta 2 | 5.00.7561.0000 | ||
System Center 2012 Configuration Manager (ConfigMgr) | 2012 | 2011/10/28 | Release Candidate 1 | 5.00.7678.0000 | ||
System Center 2012 Configuration Manager (ConfigMgr) | 2012 | 2012/01/17 | Release Candidate 2 | 5.00.7703.0000 | ||
System Center 2012 Configuration Manager (ConfigMgr) | 2012 | 2012/03/31 | RTM | 5.00.7711.0000 | ||
System Center 2012 Configuration Manager (ConfigMgr) | 2012 | 2012/08/20 | Cumulative Update 1 | 5.00.7703.0200 | ||
System Center 2012 Configuration Manager (ConfigMgr) | 2012 | 2012/09/11 | SP1 beta | 5.00.7782.1000 | ||
System Center 2012 Configuration Manager (ConfigMgr) | 2012 | 2012/12/20 | SP1 | 5.00.7804.1000 | ||
System Center 2012 Configuration Manager (ConfigMgr) | 2012 R2 | 2013/10/18 | R2 | 5.00.7958.1000 | ||
System Center 2012 Configuration Manager (ConfigMgr) | 2012 R2 | 2014/04/01 | Cumulative Update 1 | 5.00.7958.1203 | ||
System Center 2012 Configuration Manager (ConfigMgr) | 2012 R2 | 2014/07/01 | Cumulative Update 2 | 5.00.7958.1303 | ||
System Center 2012 Configuration Manager (ConfigMgr) | 2012 R2 | 2014/09/22 | Cumulative update 3 | 5.00.7958.1401 | ||
System Center 2012 Configuration Manager (ConfigMgr) | 2012 R2 | 2015/02/02 | Cumulative Update 4 | 5.00.7958.1501 | ||
System Center 2012 Configuration Manager (ConfigMgr) | 2012 R2 | 2015/05/06 | Cumulative Update 5 | 5.00.7958.1604 | ||
System Center 2012 Configuration Manager (ConfigMgr) | 2012 SP2 / 2012 R2 SP1 | 2015/05/14 | SP2 / SP1 | 5.00.8239.1000 | ||
System Center 2012 Configuration Manager (ConfigMgr) | 2012 SP2 / 2012 R2 SP1 | 2015/06/26 | Cumulative Update 1 | 5.00.8239.1203 | ||
System Center 2012 Configuration Manager (ConfigMgr) | 2012 SP2 / 2012 R2 SP1 | 2015/11/10 | Cumulative Update 2 | 5.00.8239.1301 | ||
System Center 2012 Configuration Manager (ConfigMgr) | 2012 SP2 / 2012 R2 SP1 | 2016/01/14 | Cumulative update 3 | 5.0.8239.1403 | ||
System Center Configuration Manager (ConfigMgr) | current branch | 2015/12/08 | Build 1511 | 5.0.8325.1000 | ||
System Center Configuration Manager (ConfigMgr) | current branch | 2016/03/11 | Build 1602 | 5.0.8355.1000 | ||
System Center Configuration Manager (ConfigMgr) | current branch | 2016/08/04 | Build 1606 | 5.0.8412.1000 | ||
System Center Configuration Manager (ConfigMgr) | current branch | 2016/11/17 | Build 1610 | 5.0.8458.1000 | ||
System Center Configuration Manager (ConfigMgr) | current branch | 2017/03/23 | Build 1702 | 5.0.8498.1000 | ||
System Center Configuration Manager (ConfigMgr) | current branch | 2017/07/26 | Build 1706 | 5.0.8540.1000 | ||
System Center Configuration Manager (ConfigMgr) | current branch | 2017/11/20 | Build 1710 | 5.0.8577.1000 | What's new | |
System Center Configuration Manager (ConfigMgr) | current branch | 2018/03/22 | Build 1802 | 5.0.8634.1000 | What's new | |
System Center Configuration Manager (ConfigMgr) | current branch | 2018/03/27 | Build 1803 | 5.0.8636.1000 | What's new | |
System Center Configuration Manager (ConfigMgr) | current branch | 2018/04/25 | Build 1804 | 5.0.8648.1000 | What's new | |
System Center Configuration Manager (ConfigMgr) | current branch | 2018/05/21 | Build 1805 | 5.0.8659.1000 | What's new | |
System Center Configuration Manager (ConfigMgr) | current branch | 2018/06/06 | Build 1806 | 5.0.8672.1000 | What's new | |
System Center Configuration Manager (ConfigMgr) | current branch | 2018/06/27 | Build 1806.2 | 5.0.8685.1000 | What's new | |
System Center Configuration Manager (ConfigMgr) | current branch | 2018/07/30 | Build 1807 | 5.0.8700.1000 | What's new | |
System Center Configuration Manager (ConfigMgr) | current branch | 2018/08/18 | Build 1808 | 5.0.8707.1000 | What's new | |
System Center Configuration Manager (ConfigMgr) | current branch | 2018/09/12 | Build 1809 | 5.0.8717.1000 | What's new | |
System Center Configuration Manager (ConfigMgr) | current branch | 2018/10/05 | Build 1810 | What's new | ||
System Center Configuration Manager (ConfigMgr) | current branch | 2018/10/16 | Build 1810.2 | What's new | ||
System Center Configuration Manager (ConfigMgr) | current branch | 2019/03/27 | Build 1902 (baseline) |
Site: 5.0.8790.1000
Console: 5.1902.1085.1500 Client: 5.00.8790.1005 |
What's new | |
System Center Configuration Manager (ConfigMgr) | current branch | 2019/04/18 | Build 1902 hotfix | KB4500232 | Site: 5.0.8790.1000
Console: 5.1902.1085.1600 Client: 5.00.8790.1007 |
Hotfix for SCCM 1902 KB4500232 |
System Center Configuration Manager (ConfigMgr) | current branch | 2019/06/20 | Build 1902 rollup | KB4500571 | Site: 5.0.8790.1000
Console: 5.1902.1085.2600 Client: 5.00.5790.1025 |
Update rollup for SCCM 1902 |
System Center Configuration Manager (ConfigMgr) | current branch | 2019/07/26 | Build 1906 | Site: 5.0.8853.1000
Console: 5.1906.1096.1500 Client: 5.00.8853.1006 |
What's new | |
Microsoft Endpoint Configuration Manager (ECM) | current branch | 2019/11/29 | Build 1910 |
Site: 5.0.8913.1000
Console: 5.1910.1067.1400 Client: 5.00.8913.1008 |
What's new |
Web links
- SCCM homepage at Microsoft Germany
Individual evidence
- ↑ Brad Erson: Use the power of cloud intelligence to simplify and accelerate IT and the move to a modern workplace. In: microsoft.com. November 4, 2019, Retrieved January 20, 2020 (American English).
- ↑ mestew: Innovations in Version 1910 - Configuration Manager. Retrieved January 20, 2020 (German).
- ↑ Microsoft Endpoint Manager: Simplified management and backup of devices - Techwiese. Retrieved January 20, 2020 .
- ↑ Mestew: Innovations in Version 1910 - Configuration Manager. Retrieved January 20, 2020 .
- ↑ Brad Anderson: Use the power of cloud intelligence to simplify and accelerate IT and the move to a modern workplace. Microsoft, accessed January 20, 2020 .
- ↑ olprod: What is co-administration? Retrieved January 20, 2020 (German).
- ↑ Mayunk Jain: Microsoft Intune rolls out an improved, streamlined endpoint management administration experience. Microsoft, accessed January 20, 2020 .
- ↑ mestew: Innovations in Version 1910 - Configuration Manager. Retrieved January 20, 2020 (German).
- ↑ What Exactly Is Microsoft Endpoint Manager? In: Petri. December 3, 2019, accessed February 25, 2020 (American English).
- ↑ a b User state migration is unsuccessful on an ConfigMgr 2007 SP1 or SP 2 client after you install security update 974571 or Windows 7 SP1 . support.microsoft.com
- ↑ Microsoft Messenger Connect, Configuration Manager 2007 R3 no longer in beta . ZDNet
- ↑ Announcing Configuration Manager v. Next official name . ( Memento of the original from October 15, 2012 in the Internet Archive ) Info: The archive link was inserted automatically and has not yet been checked. Please check the original and archive link according to the instructions and then remove this notice. TechNet blogs
- ↑ Microsoft System Center 2012 . microsoft.com
- ↑ Now available: Cumulative Update 1 for System Center 2012 Configuration Manager . blogs.technet.com
- ↑ blogs.technet.com