System Center Configuration Manager

From Wikipedia, the free encyclopedia
Jump to: navigation, search
System Center Configuration Manager
Development status Active
Operating system Windows NT
Platform x64
Type Systems management
License Trialware
Website microsoft.com/systemcenter

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[edit]

System Center Configuration Manager has evolved since Microsoft originally released it as "Systems Management Server" in 1994. Significant releases include:

  • Systems Management Server 1.0, released in 1994 along with Windows NT Server 3.5. This initial release targeted the management of MS-DOS, Windows for Workgroups, Windows NT, Macintosh and OS/2 desktops on Windows NT Server, NetWare, LAN Manager and Pathworks networks.
  • Systems Management Server 1.1, released in 1995 to help customers migrate to Windows 95.
  • Systems Management Server 1.2, released in 1996 with new remote-control, SNMP, inventory, and network-monitoring capabilities.[4]
  • Systems Management Server 2.0, released in 1999 to help with Y2K remediation efforts.[5]
  • Systems Management Server 2003, released in 2003 with improved stability, reliability, and software-distribution capabilities.[6]
  • System Center Configuration Manager 2007, released in 2007 with support for Windows Vista and Windows Server 2008.[7]
  • System Center Configuration Manager 2012, released in 2012 with significant changes to application deployment capabilities.[8]
  • System Center Configuration Manager 1511, released in November 2015 to support Windows 10 and new Windows servicing options.[9]
  • System Center Configuration Manager current branch 1602, released March 11, 2016. New features include conditional access for PCs, Office 365 Update Management, greater management of mobile devices and of Windows 10.[10]
  • System Center Configuration Manager current branch 1606, released July 22, 2016. New features include support for managing new Windows 10 features like Windows Information Protection and Windows Defender Advanced Threat Protection, improved integration with the Windows Store for Business supporting online and offline-licensed apps, and more.[11]


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.
  • With the 2.x versions, that site paradigm switched to a group of subnets to be managed together.
  • With SMS 2003 the site could also be defined as one or more Active Directory sites.

The most frequently used feature is inventory management,[citation needed] which provides both hardware and software inventory across a business enterprise.

SMS 2003 saw 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.[12]

Components[edit]

SCCM components include:[13]

  • Policy Infrastructure
  • Service Window Manager
  • CCM Scheduler
  • State System
  • CCM CI SDK
  • DCM Agent
  • DCM Reporting
  • CI Agent
  • MTC
  • CI Store
  • CI Downloader
  • CI Task Manager
  • CI State Store
  • Content In[fra]structure

Requirements[edit]

System Center 2012 Configuration Manager client may require Microsoft Policy Platform (to allow a client to evaluate compliance settings).[14]

See also[edit]

References[edit]

  1. ^ "SCCM is not the Official Acronym for Configuration Manager 2007". Microsoft IT ConfigMgr 2007 Blog. Microsoft. Retrieved 11 February 2016. 
  2. ^ "Migrating from Systems Management Server". microsoft.com. Microsoft. Archived from the original on 2 February 2010. 
  3. ^ http://technet.microsoft.com/en-us/library/gg682077.aspx#BKMK_SupConfigClientOS
  4. ^ Microsoft Announces Availability of Systems Management Server 1.2
  5. ^ [1]
  6. ^ [2]
  7. ^ [3]
  8. ^ [4]
  9. ^ [5]
  10. ^ "Now Available: Update 1602 for System Center Configuration Manager". blogs.technet.microsoft.com. Retrieved 2016-07-19. Some of the features that you can expect to see are: [...] Kiosk mode allows you to lock a managed mobile device to only allow certain apps and features. [...] 
  11. ^ "Now Available: Update 1606 for System Center Configuration Manager". blogs.technet.microsoft.com. Retrieved 2016-07-22. 
  12. ^ Microsoft System Center 2012 | Configuration Manager
  13. ^ Coupland, Martyn (2014). Microsoft System Center Configuration Manager Advanced Deployment. Professional expertise distilled (revised ed.). Packt Publishing Ltd. ISBN 9781782172093. Retrieved 2016-07-19. This diagram lists all of the components within the Configuration Manager client [...] Content Instructure [sic] 
  14. ^ "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[edit]