通过

Configuration Manager 1511, 1602, 1606 (Current Branch) Supported Configurations

  • 项目

One problem with dropping the year from our product name (it’s System Center Configuration Manager now) is that it can be tricky to search for documentation!

One page I visit almost weekly is the Supported Configurations page.

Here is the landing page for the ConfigMgr Current Branch (CB) Supported Configurations

https://technet.microsoft.com/en-us/library/mt589499.aspx

Here is the page outlining supported client counts (how many Intune devices do we support?) and site system scale (how many MP’s do you need?)

https://technet.microsoft.com/en-us/library/mt589738.aspx

Here is the page describing the SQL requirements (CU requirements, collation requirements, etc)

https://technet.microsoft.com/en-us/library/mt589592.aspx

And finally, the page listing recommended hardware specs for ConfigMgr

https://technet.microsoft.com/en-us/library/mt589500.aspx

Comments

  • Anonymous
    February 18, 2016
    And after 4 years of SC devs getting "we should start switching to the Windows collations to minimize these issues from happening" from SQL Server guys as stated in the following post, the obsolete SQL Collation is still required and the only one available. Nice one!https://blogs.technet.microsoft.com/servicemanager/2012/05/24/clarification-on-sql-server-collation-requirements-for-system-center-2012/
  • Anonymous
    March 07, 2016
    The previous version documentation (https://technet.microsoft.com/en-us/library/gg682085.aspx) included a link http://go.microsoft.com/fwlink/?LinkId=209762 for a specific search using technet metadata which I always found very useful. I used the article in http://blogs.inkeysolutions.com/2011/03/search-msdn-or-technet-on-bing.html to create a query (hopefully correct) for the new version:("Configuration Manager") site:technet.microsoft.com meta:search.MSCategory(mt613151)
  • Anonymous
    May 22, 2016
    The SQL page does not list SQL 2008 R2 Express as supported for a Secondary Site.. Can anyone confirm whether that is an oversight or in fact 2008 R2 is not supported?