Content deleted Content added
Inventory was the main feature long time ago; main reason for using SCCM is (in most cases) OS en software deployment. |
|||
Line 38:
| access-date= 2016-07-22
}}</ref>
* System Center Configuration Manager branch 1610,released in November 2016 <ref>{{Cite web | url= https://blogs.technet.microsoft.com/enterprisemobility/2016/11/18/now-available-update-1610-for-system-center-configuration-manager/ | title= Now Available: Update 1610 for System Center Configuration Manager | website= blogs.technet.microsoft.com | access-date= 2017-04-05 }}</ref>
* System Center Configuration Manager branch 1702 <ref name=":0">{{Cite web|url=https://blogs.technet.microsoft.com/enterprisemobility/2017/07/28/now-available-update-1706-for-system-center-configuration-manager/|title=Now Available: Update 1706 for System Center Configuration Manager|last=|first=|date=|website=blogs.technet.microsoft.com|archive-url=|archive-date=|dead-url=|access-date=2017-04-05}}</ref>
* System Center Configuration Manager branch 1706 <ref name=":0" />
Line 51:
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 [[Wide area network|WAN]].
== ==
== Components ==
| |||