System Center Configuration Manager
| Development status | Active |
|---|---|
| Operating system | Windows NT |
| Platform | x64 |
| Type | Systems management |
| License | Trialware |
| Website |
microsoft |
System Center Configuration Manager (SCCM, also known as ConfigMgr),[1] formerly Systems Management Server (SMS)[2] is a systems management software product developed by Microsoft for managing large groups of computers running Windows NT, Windows Embedded, OS X, Linux or UNIX, as well as Windows Phone, Symbian, iOS and Android mobile operating systems.[3] Configuration Manager provides remote control, patch management, software distribution, operating system deployment, network access protection and hardware and software inventory.
History
SMS went through three major iterations:
- The 1.x versions of the product defined the scope of control of the management server (the site) in terms of the NT domain being managed.
- Since the 2.x versions, that site paradigm has switched to a group of subnets that will be managed together.
- Since SMS, 2003, the site could also be defined as one or more Active Directory sites.
The most frequently used feature is inventory management, which provides both hardware and software inventory across a business enterprise.
The major difference between the 2.x product and SMS 2003 is the introduction of the Advanced Client. The Advanced Client communicates with a more scalable management infrastructure, namely the Management Point. A Management Point (MP) can manage up to 25000 Advanced Clients.
Microsoft introduced the Advanced Client to provide a solution to the problem where a managed laptop might connect to a corporate network from multiple locations and thus should not always download content from the same place within the enterprise (though it should always receive policy from its own site). When an Advanced Client is within another location (SMS Site), it may use a local distribution point to download or run a program which can conserve bandwidth across a WAN.
Microsoft released the current generation of the product, System Center 2012 Configuration Manager, in March 2012.[4]
Requirements
System Center 2012 Configuration Manager client may require Microsoft Policy Platform (to allow a client to evaluate compliance settings).[5]
See also
- Microsoft Servers
- Microsoft System Center
- Configuration management
- Windows Server Update Services
- SYDI
References
- ↑ "SCCM is not the Official Acronym for Configuration Manager 2007". Microsoft IT ConfigMgr 2007 Blog. Microsoft. Retrieved 11 February 2016.
- ↑ "Migrating from Systems Management Server". microsoft.com. Microsoft. Archived from the original on 2 February 2010.
- ↑ http://technet.microsoft.com/en-us/library/gg682077.aspx#BKMK_SupConfigClientOS
- ↑ Microsoft System Center 2012 | Configuration Manager
- ↑ "Prerequisites for Windows Client Deployment in Configuration Manager". Technet. Microsoft. Retrieved 2015-03-15.
Microsoft Policy Platform 1.2.3514.0[: ] Required to allow clients to evaluate compliance settings.
External links
| ||||||||||||||