System Center
United States (English) Sign in
Home 2012 Previous Versions Library Forums Gallery
175 out of 217 rated this helpful - Rate this topic

Supported Configurations for Configuration Manager

Updated: May 1, 2013

Applies To: System Center 2012 Configuration Manager, System Center 2012 Configuration Manager SP1

noteNote
This topic appears in the Getting Started with System Center 2012 Configuration Manager guide and in the Site Administration for System Center 2012 Configuration Manager guide.

This topic specifies the requirements to implement and maintain Microsoft System Center System Center 2012 Configuration Manager in your environment.

The following sections list products that are supported with System Center 2012 Configuration Manager. No extension of support for these products beyond their current product life-cycles is implied. Products that are beyond their current support life cycle are not supported for use with Configuration Manager. For more information about Microsoft Support Lifecycles, visit the Microsoft Support Lifecycle website at Microsoft Support Lifecycle.

WarningWarning
Microsoft provides support for the current service pack and, in some cases, the immediately previous service pack. For more information about Microsoft support life-cycle policy, go to the Microsoft Support Lifecycle Support Policy FAQ website at Microsoft Support Lifecycle Policy FAQ.

Products that are not listed in this document are not supported with System Center 2012 Configuration Manager unless they are announced on the System Center Configuration Manager Team Blog.

The following sections specify the hardware and software requirements that you must have to implement and maintain Configuration Manager in your environment.

The following table contains information about the support limits at each site type and by each client-facing site system role. This information is based on the recommended hardware for site systems. For information about the recommended hardware for Configuration Manager sites, see Planning for Hardware Configurations for Configuration Manager. For information about the minimum required hardware to run a Configuration Manager site, see Minimum Hardware Requirements for Site Systems, in this topic.

 

Site or site system role More information

Central administration site
  • A central administration site can support up to 25 child primary sites.

  • When you use SQL Server Enterprise or Datacenter for the site database at the central administration site, the shared database and hierarchy supports up to 400,000 clients. The maximum number of supported clients per hierarchy depends on the SQL Server edition in the central administration site, and is independent of the SQL Server edition at primary or secondary sites.

    noteNote
    Configuration Manager supports up to 400,000 clients per hierarchy when you use the default settings for all Configuration Manager features.

  • When you use SQL Server Standard for the site database at the central administration site, the shared database and hierarchy supports up to 50,000 clients. This is because of how the database is partitioned. After you install Configuration Manager, if you then upgrade the edition of SQL Server at the central administration site from Standard to Enterprise or Datacenter, the database does not repartition and this limitation remains.

noteNote
You cannot assign Configuration Manager clients to a central administration site. Support for clients applies to clients that are assigned to child primary sites in the hierarchy.

Primary site
  • Each primary site can support up to 250 secondary sites.

    noteNote
    The number of secondary sites per primary site is based on continuously connected and reliable wide area network (WAN) connections. For locations that have fewer than 500 clients, consider a distribution point instead of a secondary site.

  • A stand-alone primary site always supports up to 100,000 clients.

  • A Configuration Manager SP1 primary site supports up to 10,000 Windows Embedded devices that have File-Based Write Filters (FBWF) enabled when they are configured for the exceptions listed in the Deploying the Configuration Manager Client to Windows Embedded Devices section in the Introduction to Client Deployment in Configuration Manager topic. Otherwise, all other configurations for write filter-enabled embedded devices limit support to 3,000 embedded devices for a primary site. When write filters are not enabled, the standard number of clients are supported.

  • A Configuration Manager SP1 primary site supports up to 50,000 Mac computers.

  • A child primary site that uses SQL Server installed on the same computer as the site server can support up to 50,000 clients. When you use SQL Server that is installed on a computer that is remote from the site server, the child primary site can support up to 100,000 clients.

    noteNote
    In a hierarchy with a central administration site that uses a standard edition SQL Server, the total number of clients supported in the hierarchy is limited to 50,000. In this hierarchy, a child primary site that uses a remote installation of SQL Server cannot support more clients than is supported by the hierarchy. The version of SQL Server that is used by a secondary site does not affect the number of clients that the primary site supports.

  • Unlike a central administration site, the edition of SQL Server you use for the primary site database does not affect the maximum number of clients the primary site supports. This is true for both child primary sites, and stand-alone primary sites.

Secondary site
  • Each secondary site can support communications from up to 5,000 clients when you use a secondary site server that has the recommended hardware and a fast and reliable network connection to its primary parent site. A secondary site could support communications from additional clients when its hardware configuration exceeds the recommended hardware configuration.

    For information about the recommended hardware for Configuration Manager sites, see Planning for Hardware Configurations for Configuration Manager.

Management point

Primary site:

  • Each primary site management point can support up to 25,000 computer clients. To support 100,000 clients you must have at least four management points. Additional restrictions:

    • Mac computer clients: Up to 10,000.

    noteNote
    Do not position management points across a slow link from their primary site server or from the site database server.

  • Each primary site can support up to 10 management points.

    noteNote
    When you have more than four management points in a primary site, you do not increase the supported client count of the primary site beyond 100,000. Instead, any additional management points provide redundancy for communications from clients.

Secondary site:

  • Each secondary site supports a single management point that must be installed on the secondary site server.

  • The secondary site management point supports communications from the same number of clients as supported by the hardware configuration of the secondary site server.

Distribution point

  • Individually, each primary site supports up to 250 distribution points and each distribution point can support up to 4,000 clients.

  • Individually, each secondary site supports up to 250 distribution points and each distribution point can support up to the same number of clients as supported by the hardware configuration of the secondary site server, up to no more than 4,000 clients.

  • Each primary site supports a combined total of up to 5,000 distribution points. This total includes all the distribution points at the primary site and all distribution points that belong to the primary site’s child secondary sites.

  • Each distribution point supports a combined total of up to 10,000 packages and applications.

noteNote
The number of clients that one distribution point can support depends on the speed of the network, the disk performance of the distribution point computer, and the application or package size.

Software update point
  • For Configuration Manager without service pack, each site supports one active software update point for use on the intranet, and optionally, one software update point for use on the Internet. You can configure each of these software update points as a Network Load Balancing (NLB) cluster. You can have up to four software update points in the NLB cluster.

    For Configuration Manager SP1, each site supports multiple software update points for use on the intranet and on the Internet. By default, Configuration Manager SP1 does not support configuring software update points as NLB clusters. However, you can use the Configuration Manager SDK to configure a software update point on a NLB cluster.

  • A software update point that is installed on the site server can support up to 25,000 clients.

  • A software update point that is installed on a computer that is remote from the site server can support up to 100,000 clients.

noteNote
For more information, see Planning for Software Updates in Configuration Manager.

Fallback status point
  • Each fallback status point can support up to 100,000 clients.

Application Catalog website point
  • You can install multiple instances of the Application Catalog website point at primary sites.

  • For improved performance, plan to support up to 50,000 clients per instance.

  • Each instance of this site system role supports up to 400,000 clients, which provides service for the whole hierarchy.

TipTip
As a best practice, install the Application Catalog website point and Application Catalog web service point together on the same site system when they provide service to clients that are on the intranet.

Application Catalog web service point
  • You can install multiple instances of the Application Catalog web service point at primary sites.

  • For improved performance, plan to support up to 50,000 clients per instance.

  • Each instance of this site system role supports up to 400,000 clients, which provides service for the whole hierarchy.

TipTip
As a best practice, install the Application Catalog website point and Application Catalog web service point together on the same site system when they provide service to clients that are on the intranet.

System Health Validator point
  • Each System Health Validator point can support up to 100,000 clients.

Each System Center 2012 Configuration Manager site system server must use a 64-bit operating system. The only exception to this is the distribution point site system role which can be installed on limited 32-bit operating system versions.

Limitations for site systems:

  • Site systems are not supported on Server Core installations for the following operating systems:

    • Windows Server 2008 or Windows Server 2008 R2

    • Windows Server 2008 Foundation or Windows Server 2008 R2 Foundation

    • Windows Server 2012

    • Windows Server 2012 Foundation

  • It is not supported to change the domain membership or computer name of a Configuration Manager site system after it is installed.

  • Site system roles are not supported on an instance of a Windows Server cluster. The only exception to this is the site database server.

The following sections list the hardware requirements and operating system requirements for System Center 2012 Configuration Manager sites, typical site system roles, and function-specific site system roles.

The following table identifies prerequisites that are required by Configuration Manager for each site system role on supported operating systems other than Windows Server 2012. For information about prerequisites for site system roles on Windows Server 2012, see Prerequisites for Site System Roles on Windows Server 2012.

ImportantImportant
Except where specifically noted, prerequisites apply to all versions of System Center 2012 Configuration Manager.

Some prerequisites, such as SQL Server for the site database server, or Windows Server Update Services (WSUS) for the software update point, might require additional prerequisites that are not directly required by the site system role.

For site system roles that require Internet Information Services (IIS), use a version of IIS that the computer supports that runs the site system role. For information, see the following sections, Operating System Requirements for Typical Site System Roles and Operating System Requirements for Function-Specific Site System Roles, in this topic.

 

Site system role .NET Framework version1 Windows Communication Foundation (WCF) activation2 Role services for the web server (IIS) role Additional prerequisites

Site server

Requires both of the following:

  • 3.5 SP1

  • 4.0

Not applicable

Not applicable

Windows feature:

  • Remote Differential Compression

By default, a secondary site installs a management point and a distribution point. Therefore secondary sites must meet the prerequisites for these site system roles.

Database server

Not applicable

Not applicable

Not applicable

A version of SQL Server that Configuration Manager supports must be installed on this computer.

During installation of the Configuration Manager site, the remote registry service must be enabled on the computer that hosts the site database.

When you install SQL Server Express as part of a secondary site installation, the secondary site server computer must meet the requirements for SQL Server Express.

SMS Provider Server

Not applicable

Not applicable

Not applicable

Not applicable

Application Catalog web service point

Requires both of the following:

  • 3.5 SP1

  • 4.0

Requires the following options for WCF activation:

  • HTTP Activation

  • Non-HTTP Activation

Requires the default IIS configuration with the following additions:

  • Application Development:

    • ASP.NET (and automatically selected options)

  • IIS 6 Management Compatibility:

    • IIS 6 Metabase Compatibility

Not applicable

Application Catalog website point

Requires the following:

  • 4.0

Not applicable

Requires the default IIS configuration with the following additions:

  • Common HTTP Features:

    • Static Content

    • Default Document

  • Application Development:

    • ASP.NET (and automatically selected options)3

  • Security:

    • Windows Authentication

  • IIS 6 Management Compatibility:

    • IIS 6 Metabase Compatibility

Not applicable

Asset Intelligence synchronization point

Requires the following:

  • 4.0

Not applicable

Not applicable

Not applicable

Distribution point4

Not applicable

Not applicable

You can use the default IIS configuration, or a custom configuration.

To use a custom IIS configuration, you must enable the following options for IIS:

  • Application Development:

    • ISAPI Extensions

  • Security:

    • Windows Authentication

  • IIS 6 Management Compatibility:

    • IIS 6 Metabase Compatibility

    • IIS 6 WMI Compatibility

When you use a custom IIS configuration, you can remove options that are not required, such as the following:

  • Common HTTP Features:

    • HTTP Redirection

  • IIS Management Scripts and Tools

Windows feature:

  • Remote Differential Compression

To support PXE or multicast, install and configure the following Windows role:

  • Windows Deployment Services (WDS)

    noteNote
    For Windows Server 2008, Windows Server 2008 R2, WDS is installed and configured automatically when you configure a distribution point to support PXE or Multicast. For Windows Server 2003, you must install and configure WDS manually.

For Configuration Manager with no service pack, to support PXE on a distribution point that is on a computer remote from the site server, you should install the following:

  • Microsoft Visual C++ 2008 Redistributable.

    noteNote
    You can run the Microsoft Visual C++ 2008 Redistributable Setup from the Configuration Manager installation at: <ConfigMgrInstallationFolder>\Client\x64\vcredist_x64.exe

    For Configuration Manager SP1, vcredist_x64.exe is installed automatically when you configure a distribution point to support PXE.

With Configuration Manager SP1, you can use a cloud service in Windows Azure to host a distribution point. For more information, see the section Planning for Distribution Points for Windows Azure in the Planning for Content Management in Configuration Manager topic.

noteNote
With System Center 2012 Configuration Manager, the distribution point site system role does not require Background Intelligent Transfer Service (BITS). When BITS is configured on the distribution point computer, BITS on the distribution point computer is not used to facilitate the download of content by clients that use BITS

Endpoint Protection point

Requires the following:

  • 3.5 SP1

Not applicable

Not applicable

Not applicable

Enrollment point

Requires the following:

  • 3.5 SP1 for Configuration Manager with no service pack

  • 4.0 for Configuration Manager with SP1

Requires the following options for WCF activation:

  • HTTP Activation

  • Non-HTTP Activation

Requires the default IIS configuration with the following additions:

  • Application Development:

    • ASP.NET (and automatically selected options) 3

Not applicable

Enrollment proxy point

Requires the following:

  • 3.5 SP1 for Configuration Manager with no service pack

  • 4.0 for Configuration Manager with SP1

Requires the following options for WCF activation:

  • HTTP Activation

  • Non-HTTP Activation

Requires the default IIS configuration with the following additions:

  • Application Development:

    • ASP.NET (and automatically selected options) 3

Not applicable

Fallback status point

Not applicable

Not applicable

Requires the default IIS configuration with the following additions:

  • IIS 6 Management Compatibility:

    • IIS 6 Metabase Compatibility

Not applicable

Management point

Configuration Manager with no service pack:

  • Management points that support mobile devices require the .NET Framework 3.5 SP15

Configuration Manager with SP1:

  • All management points require the .NET Framework 4

Not applicable

You can use the default IIS configuration, or a custom configuration5.

To use a custom IIS configuration, you must enable the following options for IIS:

  • Application Development:

    • ISAPI Extensions

  • Security:

    • Windows Authentication

  • IIS 6 Management Compatibility:

    • IIS 6 Metabase Compatibility

    • IIS 6 WMI Compatibility

When you use a custom IIS configuration you can remove options that are not required, such as the following:

  • Common HTTP Features:

    • HTTP Redirection

  • IIS Management Scripts and Tools

Windows feature:

  • BITS Server Extensions (and automatically selected options), or Background Intelligent Transfer Services (BITS) (and automatically selected options)

Out of band service point

Requires the following:

  • 4.0

Requires the following options for WCF activation:

  • HTTP Activation

  • Non-HTTP Activation

Not applicable

Not applicable

Reporting services point

Requires the following:

  • 4.0

Not applicable

Not applicable

SQL Server Reporting Services installed and configured to use at least one instance for the reporting services point. The instance you use for SQL Server Reporting Services can be the same instance you use for the site database. Additionally, the instance you use can be shared with other System Center products as long as the other System Center products do not have restrictions for sharing the instance of SQL Server.

Software update point

Requires both of the following:

  • 3.5 SP1

  • 4.0

Not applicable

Requires the default IIS configuration

Windows Server Update Services (WSUS) 3.0 SP2 must be installed on this computer.

State migration point

Not applicable

Not applicable

Requires the default IIS configuration

Not applicable

System Health Validator point

Not applicable

Not applicable

Not applicable

This site system role is supported only on a NAP health policy server.

Windows Intune connector

Requires the following:

  • 4.0

Not applicable

Not applicable

Not applicable

1 Install the full version of the Microsoft.NET Framework before you install the site system roles. For example, see the Microsoft .NET Framework 4 (Stand-Alone Installer).

ImportantImportant
The Microsoft .NET Framework 4 Client Profile is insufficient for this requirement.

2 You can configure WCF activation as part of the .NET Framework Windows feature on the site system server. For example, on Windows Server 2008 R2, run the Add Features Wizard to install additional features on the server. On the Select Features page, expand NET Framework 3.5.1 Features, then expand WCF Activation, and then select the check box for both HTTP Activation and Non-HTTP Activation to enable these options.

3 In some scenarios, such as when IIS is installed or reconfigured after the .NET Framework version 4.0 is installed, you must explicitly enable ASP.NET version 4.0. For example, on a 64-bit computer that runs the .NET Framework version 4.0.30319, run the following command: %windir%\Microsoft.NET\Framework64\v4.0.30319\aspnet_regiis.exe –i –enable

4 You must manually install IIS on computers that run a supported version of Windows Server 2003. Additionally, to install IIS and configure the additional Windows features, the computer might require access to the Windows Server 2003 source media.

5 Each management point that you enable to support mobile devices requires the additional IIS configuration for ASP.NET (and its automatically selected options). With this requirement, review note 3 for applicability to your installation.

For System Center 2012 SP1 only:

The following table identifies prerequisites that are required by Configuration Manager site system roles you install on Windows Server 2012. For information about prerequisites for site system roles on supported operating systems prior to Windows Server 2012, see Prerequisites for Site System Roles.

Some prerequisites, such as SQL Server for the site database server, or Windows Server Update Services (WSUS) for the software update point, might require additional prerequisites that are not directly required by the site system role.

For site system roles that require Internet Information Services (IIS), use a version of IIS that the computer supports that runs the site system role. For information, see the following sections, Operating System Requirements for Typical Site System Roles and Operating System Requirements for Function-Specific Site System Roles, in this topic.

 

Site system role Windows Server Roles and Features Additional prerequisites

Site server

Features:

  • .NET Framework 3.5

  • .NET Framework 4

  • Remote Differential Compression

By default, a secondary site installs a management point and a distribution point. Therefore secondary sites must meet the prerequisites for these site system roles.

Database server

Not applicable

A version of SQL Server that Configuration Manager supports must be installed on this computer.

During installation of the Configuration Manager site, the remote registry service must be enabled on the computer that hosts the site database.

When you install SQL Server Express as part of a secondary site installation, the secondary site server computer must meet the requirements for SQL Server Express.

SMS Provider Server

Not applicable

Not applicable

Application Catalog web service point

Features:

  • .NET Framework 3.5

    • HTTP Activation (and automatically selected options)

  • .NET Framework 4.5

    • ASP.NET 4.5

IIS Configuration:

  • Common HTTP Features:

    • Default Document

  • IIS 6 Management Compatibility:

    • IIS 6 Metabase Compatibility

  • Application Development:

    • ASP.NET 3.5 (and automatically selected options)

    • .NET Extensibility 3.5

Not applicable

Application Catalog website point

Features:

  • .NET Framework 3.5

  • .NET Framework 4.5

    • ASP.NET 4.5

IIS Configuration:

  • Common HTTP Features:

    • Default Document

    • Static Content

  • Application Development:

    • ASP.NET 3.5 (and automatically selected options)

    • ASP.NET 4.5 (and automatically selected options)

    • .NET Extensibility 3.5

    • .NET Extensibility 4.5

  • Security:

    • Windows Authentication

  • IIS 6 Management Compatibility:

    • IIS 6 Metabase Compatibility

Not applicable

Asset Intelligence synchronization point

Features:

  • .NET Framework 4

Not applicable

Distribution point

Features1:

  • Remote Differential Compression

IIS Configuration:

  • Application Development:

    • ISAPI Extensions

  • Security:

    • Windows Authentication

  • IIS 6 Management Compatibility:

    • IIS 6 Metabase Compatibility

    • IIS 6 WMI Compatibility

To support PXE or multicast, install and configure the following Windows role:

  • Windows Deployment Services (WDS)

    noteNote
    WDS installs and configures automatically when you configure a distribution point to support PXE or Multicast on Windows Server 2012.

For Configuration Manager with SP1, to support PXE on a distribution point that is on a computer remote from the site server, install the following:

  • Microsoft Visual C++ 2008 Redistributable.

    noteNote
    For Windows Server 2012, the vcredist_x64.exe is installed automatically when you configure a distribution point to support PXE.

  • PowerShell 3.0 is required on Windows Server 2012 before you install the distribution point.

With Configuration Manager SP1, you can use a cloud service in Windows Azure to host a distribution point. For more information, see the section Planning for Distribution Points for Windows Azure in the Planning for Content Management in Configuration Manager topic.

noteNote
With System Center 2012 Configuration Manager, the distribution point site system role does not require Background Intelligent Transfer Service (BITS). When BITS is configured on the distribution point computer, BITS on the distribution point computer is not used to facilitate the download of content by clients that use BITS

Endpoint Protection point

Features:

  • .NET Framework 3.5 SP1

Not applicable

Enrollment point

Features:

  • .NET Framework 3.5

    • HTTP Activation

  • .NET Framework 4.5

    • ASP.NET 4.5

  • Common HTTP Features:

    • Default Document

  • Application Development:

    • ASP.NET 3.5

    • .NET Extensibility 3.5

  • IIS 6 Management Compatibility:

    • IIS 6 Metabase Compatibility

Not applicable

Enrollment proxy point

Features:

  • .NET Framework 3.5

  • .NET Framework 4.5

    • ASP.NET 4.5

IIS Configuration:

  • Common HTTP Features:

    • Default Document

    • Static Content

  • Application Development:

    • ASP.NET 3.5 (and automatically selected options)

    • ASP.NET 4.5 (and automatically selected options)

    • .NET Extensibility 3.5

    • .NET Extensibility 4.5

  • Security:

    • Windows Authentication

  • IIS 6 Management Compatibility:

    • IIS 6 Metabase Compatibility

Not applicable

Fallback status point

Requires the default IIS configuration with the following additions:

IIS Configuration:

  • IIS 6 Management Compatibility:

    • IIS 6 Metabase Compatibility

Not applicable

Management point

Features:

  • .NET Framework 4

  • BITS Server Extensions (and automatically selected options), or Background Intelligent Transfer Services (BITS) (and automatically selected options)

IIS Configuration:

  • Application Development:

    • ISAPI Extensions

  • Security:

    • Windows Authentication

  • IIS 6 Management Compatibility:

    • IIS 6 Metabase Compatibility

    • IIS 6 WMI Compatibility

Not applicable

Out of band service point

Features:

  • .NET Framework 4

    • HTTP Activation

    • Non-HTTP Activation

Not applicable

Reporting services point

Features:

  • .NET Framework 4

SQL Server Reporting Services installed and configured to use at least one instance for the reporting services point. The instance you use for SQL Server Reporting Services can be the same instance you use for the site database. Additionally, the instance you use can be shared with other System Center products as long as the other System Center products do not have restrictions for sharing the instance of SQL Server.

Software update point

Features:

  • .NET Framework 3.5 SP1

  • .NET Framework 4

Requires the default IIS configuration

Windows server role:

  • Windows Server Update Services

State migration point

Requires the default IIS configuration

Not applicable

System Health Validator point

Not applicable

This site system role is supported only on a NAP health policy server.

Windows Intune connector

Features:

  • .NET Framework 4

Not applicable

1 With System Center 2012 Configuration Manager, distribution points do not require BITS. When BITS is configured on the distribution point computer, BITS on the distribution point computer is not used to facilitate the download of content by clients that use BITS.

This section identifies the minimum required hardware requirements for Configuration Manager site systems. These requirements are sufficient to support all features of Configuration Manager in an environment with up to 100 clients. This information is suitable for testing environments. For guidance about the recommended hardware for Configuration Manager in full-scale production environments, see Planning for Hardware Configurations for Configuration Manager.

The following minimum requirements apply to all site types (central administration site, primary site, secondary site) when you install all available site system roles on the site server computer.

 

Hardware component Requirement

Processor
  • Minimum: AMD Opteron, AMD Athlon 64, Intel Xeon with Intel EM64T support, Intel Pentium IV with EM64T support

  • Minimum: 1.4 GHz

RAM
  • Minimum: 2 GB

Free disk space
  • Available: 10 GB

  • Total: 50 GB

The following table specifies the operating systems that can support System Center 2012 Configuration Manager site servers, the database server, and the SMS Provider site system role. The table also specifies the Configuration Manager versions that support each operating system.

 

Operating system System architecture Central administration site Primary site Secondary site1 Site database server1, 2 SMS Provider

Windows Server 2008

  • Standard Edition (SP2)

  • Enterprise Edition (SP2)

  • Datacenter Edition (SP2)

x64
  • Configuration Manager with no service pack

  • Configuration Manager with SP1
  • Configuration Manager with no service pack

  • Configuration Manager with SP1
  • Configuration Manager with no service pack

  • Configuration Manager with SP1
  • Configuration Manager with no service pack

  • Configuration Manager with SP1
  • Configuration Manager with no service pack

  • Configuration Manager with SP1

Windows Server 2008 R2

  • Standard Edition with no service pack, or with SP1)

  • Enterprise Edition (with no service pack, or with SP1)

  • Datacenter Edition (with no service pack, or with SP1)

x64
  • Configuration Manager with no service pack

  • Configuration Manager with SP1
  • Configuration Manager with no service pack

  • Configuration Manager with SP1
  • Configuration Manager with no service pack

  • Configuration Manager with SP1
  • Configuration Manager with no service pack

  • Configuration Manager with SP1
  • Configuration Manager with no service pack

  • Configuration Manager with SP1

Windows Server 2012

  • Standard

  • Datacenter

x64
  • Configuration Manager with SP1
  • Configuration Manager with SP1
  • Configuration Manager with SP1
  • Configuration Manager with SP1
  • Configuration Manager with SP1

1 Site database servers are not supported on a read-only domain controller (RODC). For more information, see You may encounter problems when installing SQL Server on a domain controller in the Microsoft Knowledge Base. Additionally, secondary site servers are not supported on any domain controller.
2 For more information about the versions of SQL Server that Configuration Manager supports, see Configurations for the SQL Server Site Database in this topic.

The following table specifies the operating systems that can support multi-function site system roles, and the Configuration Manager versions that support each operating system.

 

Operating system System architecture Distribution point3 Enrollment point and enrollment proxy point Fallback status point Management point Windows Intune connector

Windows Vista

  • Business Edition (SP1)

  • Enterprise Edition (SP1)

  • Ultimate Edition (with no service pack, or with SP1)

x64
  • Configuration Manager with no service pack1, 2

  • Configuration Manager with SP11, 2

Not supported

Not supported

Not supported

Not supported

Windows 7

  • Professional (with no service pack, or with SP1)

  • Enterprise Editions (with no service pack, or with SP1)

  • Ultimate Editions (with no service pack, or with SP1)

x86, x64
  • Configuration Manager with no service pack1, 2

  • Configuration Manager with SP11, 2

Not supported

Not supported

Not supported

Not supported

Windows 8

  • Pro

  • Enterprise

x86, x64
  • Configuration Manager with SP11, 2

Not supported

Not supported

Not supported

Not supported

Windows Server 2003 R2

  • Standard Edition

  • Enterprise Edition

x86, x64
  • Configuration Manager with no service pack2, 4

  • Configuration Manager with SP12, 4

Not supported

Not supported

Not supported

Not supported

Windows Server 2003

  • Standard Edition (SP2)

  • Enterprise Edition (SP2)

  • Datacenter Edition (SP2)

x86, x64
  • Configuration Manager with no service pack2, 4

  • Configuration Manager with SP12, 4

Not supported

Not supported

Not supported

Not supported

Windows Server 2003

  • Web Edition (SP2)

  • Storage Server Edition (SP2)

x86
  • Configuration Manager with no service pack2, 4

  • Configuration Manager with SP12, 4

Not supported

Not supported

Not supported

Not supported

Windows Server 2008

  • Standard Edition (SP2)

  • Enterprise Edition (SP2)

  • Datacenter Edition (SP2)

x86, x64
  • Configuration Manager with no service pack2, 4

  • Configuration Manager with SP12, 4
  • Configuration Manager with no service pack

  • Configuration Manager with SP1
  • Configuration Manager with no service pack

  • Configuration Manager with SP1
  • Configuration Manager with no service pack

  • Configuration Manager with SP1
  • Configuration Manager with SP1

Windows Server 2008 R2

  • Standard Edition (with no service pack, or with SP1)

  • Enterprise Edition (with no service pack, or with SP1)

  • Datacenter Edition (SP1)

x64
  • Configuration Manager with no service pack

  • Configuration Manager with SP1
  • Configuration Manager with no service pack

  • Configuration Manager with SP1
  • Configuration Manager with no service pack

  • Configuration Manager with SP1
  • Configuration Manager with no service pack

  • Configuration Manager with SP1
  • Configuration Manager with SP1

Windows Storage Server 2008 R2

  • Workgroup

  • Standard

  • Enterprise

x64
  • Configuration Manager with no service pack2

  • Configuration Manager with SP12

Not supported

Not supported

Not supported

Not supported

Windows Server 2012

  • Standard

  • Datacenter

x64
  • Configuration Manager with SP1
  • Configuration Manager with SP1
  • Configuration Manager with SP1
  • Configuration Manager with SP1
  • Configuration Manager with SP1

1 Distribution points on this operating system are not supported for PXE.

2 Distribution points on this operating system version do not support Multicast.

3 Unlike other site system roles, distribution points are supported on some 32-bit operating systems. Distribution points also support several different configurations that each have different requirements and in some cases support installation not only on servers, but on client operating systems. For more information about the options available for distribution points, see Prerequisites for Content Management in Configuration Manager in the Deploying Software and Operating Systems in System Center 2012 Configuration Manager guide.

4 Distribution points on this operating system version are supported for PXE, but they do not support network booting of client computers in EFI mode. Client computers with BIOS or with EFI booting in legacy mode are supported.

The following table specifies the operating systems that are supported for use with each feature-specific Configuration Manager site system role, and the Configuration Manager versions that support each operating system.

 

Operating system System architecture Application Catalog web service point and Application Catalog website point Asset Intelligence synchronization point Endpoint Protection point Out of band service point Reporting services point Software update point State migration point System Health Validator point

Windows Server 2008

  • Standard Edition (SP2)

  • Enterprise Edition (SP2)

  • Datacenter Edition (SP2)

x64
  • Configuration Manager with no service pack

  • Configuration Manager with SP1
  • Configuration Manager with no service pack

  • Configuration Manager with SP1
  • Configuration Manager with no service pack

  • Configuration Manager with SP1
  • Configuration Manager with no service pack

  • Configuration Manager with SP1
  • Configuration Manager with no service pack

  • Configuration Manager with SP1
  • Configuration Manager with no service pack

  • Configuration Manager with SP1
  • Configuration Manager with no service pack

  • Configuration Manager with SP1
  • Configuration Manager with no service pack

  • Configuration Manager with SP1

Windows Server 2008 R2

  • Standard Edition (with no service pack, or with SP1)

  • Enterprise Edition (with no service pack, or with SP1)

  • Datacenter Edition (SP1)

x64
  • Configuration Manager with no service pack

  • Configuration Manager with SP1
  • Configuration Manager with no service pack

  • Configuration Manager with SP1
  • Configuration Manager with no service pack

  • Configuration Manager with SP1
  • Configuration Manager with no service pack

  • Configuration Manager with SP1
  • Configuration Manager with no service pack

  • Configuration Manager with SP1
  • Configuration Manager with no service pack

  • Configuration Manager with SP1
  • Configuration Manager with no service pack

  • Configuration Manager with SP1
  • Configuration Manager with no service pack

  • Configuration Manager with SP1

Windows Server 2012

  • Standard

  • Datacenter

x64
  • Configuration Manager with SP1
  • Configuration Manager with SP1
  • Configuration Manager with SP1
  • Configuration Manager with SP1
  • Configuration Manager with SP12
  • Configuration Manager with SP1
  • Configuration Manager with SP1
  • Configuration Manager with SP1

The following sections describe the operating systems and hardware supported for System Center 2012 Configuration Manager computer client installation on Windows-based computers, Mac computers, and servers that run Linux or UNIX. Make sure that you also review Prerequisites for Windows Client Deployment in Configuration Manager for a list of dependencies for the installation of the Configuration Manager client on Windows-based computers and mobile devices.

The following are minimum requirements for Windows-based computers that you manage with Configuration Manager.

 

Requirement Details

Processor and memory

Refer to the processor and RAM requirements for the computers operating system.

noteNote
An exception to this is Windows XP and Windows 2003, which both require a minimum of 256 MB of RAM.

Disk space

500 MB available disk space, with 5 GB recommended for the Configuration Manager client cache.

Less disk space is required if you use customized settings to install the Configuration Manager client:

  • Use the CCMSetup command-line property /skippprereq to avoid installing files that the client does not require. For example, CCMSetup.exe /skipprereq:silverlight.exe if the client will not use the Application Catalog.

  • Use the Client.msi property SMSCACHESIZE to set a cache file that is smaller than the default of 5120 MB. The minimum size is 1 MB. For example, CCMSetup.exe SMSCACHESIZE=2.

For more information about these client installation settings, see About Client Installation Properties in Configuration Manager.

TipTip
Installing the client with minimal disk space is useful for Windows Embedded devices that typically have smaller disk sizes than standard Windows computers.

The following are additional hardware requirements for optional functionality in Configuration Manager.

 

Function Minimum hardware requirements

Operating system deployment

384 MB of RAM

Software Center

500 MHz processor

Remote Control

Pentium 4 Hyper-Threaded 3 GHz (single core) or comparable CPU, with at least a 1 GB RAM for optimal experience.

Out of Band Management

Desktop or portable computers must have the Intel vPro Technology or Intel Centrino Pro and a supported version of Intel AMT.

The following table specifies the operating systems that are supported for Configuration Manager client installation, and the versions of Configuration Manager that support each operating system. For server platforms, client support is independent of any other service that runs on that server unless noted otherwise. For example, the client is supported on domain controllers and servers that run cluster services or terminal services.

 

Operating system System architecture System Center 2012 Configuration Manager version

Windows XP Professional (SP3)

x86
  • Configuration Manager with no service pack

  • Configuration Manager with SP1

Windows XP Professional for 64-bit Systems (SP2)

x64
  • Configuration Manager with no service pack

  • Configuration Manager with SP1

Windows XP Tablet PC (SP3)

x86
  • Configuration Manager with no service pack

  • Configuration Manager with SP1

Windows Vista

  • Business Edition (SP2)

  • Enterprise Edition (SP2)

  • Ultimate Edition (SP2)

x86, x64
  • Configuration Manager with no service pack

  • Configuration Manager with SP1

Windows 7

  • Professional (with no service pack, or with SP1)

  • Enterprise Editions (with no service pack, or with SP1)

  • Ultimate Editions (with no service pack, or with SP1)

x86, x64
  • Configuration Manager with no service pack

  • Configuration Manager with SP1

Windows 8

  • Pro

  • Enterprise

x86, x64
  • Configuration Manager with SP1

Windows Server 2003 Web Edition (SP2)

x86
  • Configuration Manager with no service pack

  • Configuration Manager with SP1

Windows Server 2003

  • Standard Edition (SP2)

  • Enterprise Edition (SP2)

  • Datacenter Edition1 (SP2)

x86, x64
  • Configuration Manager with no service pack

  • Configuration Manager with SP1

Windows Server 2003 R2 SP2

  • Standard Edition

  • Enterprise Edition

  • Datacenter Edition1

x86, x64
  • Configuration Manager with no service pack

  • Configuration Manager with SP1

Windows Storage Server 2003 R2 SP2

x86, x64
  • Configuration Manager with no service pack

  • Configuration Manager with SP1

Windows Server 2008

  • Standard Edition (SP2)

  • Enterprise Edition (SP2)

  • Datacenter Edition (SP2) 1

x86, x64
  • Configuration Manager with no service pack

  • Configuration Manager with SP1

The Server Core installation of Windows Server 2008 (SP2)

x86, x64
  • Configuration Manager with no service pack

  • Configuration Manager with SP1

Windows Storage Server 2008 R2

  • Workgroup

  • Standard

  • Enterprise

x64
  • Configuration Manager with no service pack

  • Configuration Manager with SP1

Windows Server 2008 R2

  • Standard Edition (with no service pack, or with SP1)

  • Enterprise Edition (with no service pack, or with SP1)

  • Datacenter Edition (with no service pack, or with SP1)1

x64
  • Configuration Manager with no service pack

  • Configuration Manager with SP1

The Server Core installation of Windows Server 2008 R2 (with no service pack, or with SP1)

x64
  • Configuration Manager with no service pack

  • Configuration Manager with SP1

Windows Server 2012

  • Standard

  • Datacenter1

x64
  • Configuration Manager with SP1

The Server Core installation of Windows Server 20122

x64
  • Configuration Manager with SP1

1 Datacenter releases are supported but not certified for System Center 2012 Configuration Manager. Hotfix support is not offered for issues specific to Windows Server Datacenter Edition.

2 To support client push installation, the computer that runs Windows Server 2012 Server Core must run the File Server role service for the File and Storage Services server role. You can use the following Windows PowerShell cmdlet to install the File and Storage Services server role, which includes the File Server role service, on a Windows Server 2012 Server Core installation: Install-WindowsFeature FS-FileServer

For more information about installing Windows features on a Server Core computer, see Install Server Roles and Features on a Server Core Server in the Windows Server 2012 TechNet library.

System Center 2012 Configuration Manager and System Center 2012 Endpoint Protection support clients for integration with Windows Embedded. Support limitations for Windows Embedded:

  • All client features are supported natively on supported Windows Embedded systems that do not have write filters enabled. Configuration Manager SP1 clients that use Enhanced Write Filters (EWF) RAM or File Based Write Filters (FBWF) are natively supported for all features except power management. For Configuration Manager with no service pack, Windows Embedded systems that have write filters enabled must use task sequences to deploy to embedded devices, and the task sequences must include steps to disable and then restore the write filters.

  • The Application Catalog is not supported for any Windows Embedded device.

  • Windows Embedded operating systems based on Windows XP are only supported for Endpoint Protection in Configuration Manager SP1.

  • Before you can monitor detected malware on Windows Embedded devices based on Windows XP, you must install the Microsoft Windows WMI scripting package on the embedded device. Use Windows Embedded Target Designer to install this package. The files WBEMDISP.DLL and WBEMDISP.TLB must exist and be registered in the folder %windir%\System32\WBEM on the embedded device to ensure that detected malware is reported.

noteNote
In Configuration Manager SP1, new options are added to control the behavior of Windows Embedded write filters when you install the Endpoint Protection client. For more information, see Introduction to Endpoint Protection in Configuration Manager.

The following table specifies the Windows Embedded versions that are supported with Configuration Manager and Endpoint Protection, and the versions of Configuration Manager and Endpoint Protection that support each Windows Embedded version.

 

Windows Embedded operating system Base operating system System architecture System Center 2012 Configuration Manager version System Center 2012 Endpoint Protection version

Windows Embedded Standard 2009

Windows XP SP3

x86
  • Configuration Manager with no service pack

  • Configuration Manager with SP1
  • Endpoint Protection with SP1

Windows XP Embedded SP3

Windows XP SP3

x86
  • Configuration Manager with no service pack

  • Configuration Manager with SP1
  • Endpoint Protection with SP1

Windows Fundamentals for Legacy PCs (WinFLP)

Windows XP SP3

x86
  • Configuration Manager with no service pack

  • Configuration Manager with SP1
  • Endpoint Protection with SP1

Windows Embedded POSReady 2009

Windows XP SP3

x86
  • Configuration Manager with no service pack

  • Configuration Manager with SP1
  • Endpoint Protection with SP1

WEPOS 1.1 with SP3

Windows XP SP3

x86
  • Configuration Manager with no service pack

  • Configuration Manager with SP1
  • Endpoint Protection with SP1

Windows Embedded Standard 7 with SP1

Windows 7

x86, x64
  • Configuration Manager with no service pack

  • Configuration Manager with SP1
  • Endpoint Protection with no service pack

  • Endpoint Protection with SP1

Windows Embedded POSReady 7

Windows 7

x86, x64
  • Configuration Manager with no service pack

  • Configuration Manager with SP1
  • Endpoint Protection with no service pack

  • Endpoint Protection with SP1

Windows Thin PC

Windows 7

x86, x64
  • Configuration Manager with no service pack

  • Configuration Manager with SP1
  • Endpoint Protection with no service pack

  • Endpoint Protection with SP1

Windows Embedded 8 Standard1

Windows 8

x86, x64
  • Configuration Manager with SP1
  • Endpoint Protection with SP1

Windows Embedded 8 Industry

Windows 8

x86, x64
  • Configuration Manager with SP1
  • Endpoint Protection with SP1

1 This version of Windows Embedded includes the Unified Write Filter (UWF). This write filter type is not supported by System Center 2012 Configuration Manager SP1. Therefore the built-in features for write filter management will not work with UWF.

noteNote
For Configuration Manager SP1 only:

The client for Mac is supported only on Mac computers that use an Intel 64-bit chipset.

The following operating systems are supported for the Configuration Manager client for Mac computers:

  • Mac OS X 10.6 (Snow Leopard)

  • Mac OS X 10.7 (Lion)

For more information about computers that run Mac OS X, see How to Install Clients on Mac Computers in Configuration Manager.

noteNote
For Configuration Manager SP1 only:

Use the information in the following sections to identify the supported distributions of Linux and UNIX and the hardware requirements to run the Configuration Manager client for Linux and UNIX. For information about the operating system file dependencies for the client for Linux and UNIX, see Prerequisites for Client Deployment to Linux and UNIX Servers in the Planning for Client Deployment for Linux and UNIX Servers topic. For an overview of the management capabilities supported for computers that run Linux or UNIX, see the Deploying the Configuration Manager Client to Linux and UNIX Servers section in the Introduction to Client Deployment in Configuration Manager topic.

The following table identifies the operating systems that are supported for the Configuration Manager client for Linux and UNIX:

 

Operating System Version

Red Hat Enterprise Linux (RHEL)
  • Version 4 (x86 and x64)

  • Version 5 (x86 and x64)

  • Version 6 (x86 and x64)

Solaris
  • Version 9 (SPARC)

  • Version 10 (x86 and SPARC)

SUSE Linux Enterprise Server (SLES)
  • Version 9 (x86)

  • Version 10 SP1 (x86 and x64)

  • Version 11 (x86 and x64)

The following are minimum hardware requirements for computers that you manage with the Configuration Manager client for Linux and UNIX.

 

Requirement Details

Processor and memory

Refer to the processor and RAM requirements for the computer’s operating system.

Disk space

500 MB available disk space, with 5 GB recommended for the Configuration Manager client cache.

Network connectivity

Configuration Manager client computers must have network connectivity to Configuration Manager site systems to enable management.

The following sections describe the hardware and operating systems that are supported for managing mobile devices in System Center 2012 Configuration Manager.

noteNote
The following mobile device clients are not supported in the Configuration Manager hierarchy:

  • Device management clients from System Management Server 2003 and Configuration Manager 2007

  • Windows CE Platform Builder device management client (any version)

  • System Center Mobile Device Manager VPN connection

The following sections describe the hardware and operating systems that are supported for the mobile devices enrolled by System Center 2012 Configuration Manager.

The following table lists the platforms and languages that support Configuration Manager enrollment and the versions of Configuration Manager that support each platform.

 

Operating system System Center 2012 Configuration Manager version Supported languages

Windows Mobile 6.1
  • Configuration Manager with no service pack

  • Configuration Manager with SP1
  • Chinese (Simplified)

  • Chinese (Traditional)

  • English (US)

  • French (France)

  • German

  • Italian

  • Japanese

  • Korean

  • Portuguese (Brazil)

  • Russian

  • Spanish (Spain)

Windows Mobile 6.5
  • Configuration Manager with no service pack

  • Configuration Manager with SP1
  • Chinese (Simplified)

  • Chinese (Traditional)

  • English (US)

  • French (France)

  • German

  • Italian

  • Japanese

  • Korean

  • Portuguese (Brazil)

  • Russian

  • Spanish (Spain)

Nokia Symbian Belle
  • Configuration Manager with no service pack

  • Configuration Manager with SP1
  • Arabic

  • Basque (Basque)

  • Bulgarian

  • Catalan

  • Chinese (Hong Kong SAR)

  • Chinese (Simplified)

  • Chinese (Traditional)

  • Croatian

  • Czech

  • Danish

  • Dutch

  • English (UK)

  • English (US)

  • Estonian

  • Farsi

  • Finnish

  • French (Canada)

  • French (France)

  • Galician

  • German

  • Greek

  • Hebrew

  • Hungarian

  • Icelandic

  • Indonesian

  • Italian

  • Kazakh

  • Korean

  • Latvian

  • Lithuanian

  • Malay

  • Norwegian

  • Polish

  • Portuguese (Brazil)

  • Portuguese (Portugal)

  • Romanian

  • Russian

  • Serbian (Latin/Cyrillic)

  • Slovak

  • Slovenian

  • Spanish (Latin America)

  • Spanish (Spain)

  • Swedish

  • Tagalog (Filipino)

  • Thai

  • Turkish

  • Ukrainian

  • Urdu

  • Vietnamese

For System Center 2012 SP1 only: The following table lists the platforms and languages that are supported for mobile devices that are enrolled by Windows Intune and you use the Windows Intune connector in Configuration Manager.

ImportantImportant
You must have a subscription to Windows Intune to manage the following operating systems.

 

Operating system System Center 2012 Configuration Manager version Company portal supported languages

Windows Phone 8
  • Configuration Manager with SP1
  • Chinese (Simplified)

  • Chinese (Traditional)

  • Czech

  • Danish

  • Dutch

  • English (US)

  • Finnish

  • French (France)

  • German

  • Greek

  • Hungarian

  • Italian

  • Japanese

  • Korean

  • Norwegian

  • Polish

  • Portuguese (Brazil)

  • Romanian

  • Russian

  • Spanish (Spain)

  • Swedish

  • Turkish

Windows RT
  • Configuration Manager with SP1
  • Chinese (Simplified)

  • Chinese (Traditional)

  • Czech

  • Danish

  • Dutch

  • English (US)

  • Finnish

  • French (France)

  • German

  • Greek

  • Hungarian

  • Italian

  • Japanese

  • Korean

  • Norwegian

  • Polish

  • Portuguese (Brazil)

  • Romanian

  • Russian

  • Spanish (Spain)

  • Swedish

  • Turkish

iOS
  • Configuration Manager with SP1
  • Chinese (Simplified)

  • Chinese (Traditional)

  • Czech

  • Danish

  • Dutch

  • English (US)

  • Finnish

  • French (France)

  • German

  • Greek

  • Hungarian

  • Italian

  • Japanese

  • Korean

  • Norwegian

  • Polish

  • Portuguese (Brazil)

  • Romanian

  • Russian

  • Spanish (Spain)

  • Swedish

  • Turkish

Android
  • Configuration Manager with SP1
  • Chinese (Simplified)

  • Chinese (Traditional)

  • Czech

  • Danish

  • Dutch

  • English (US)

  • Finnish

  • French (France)

  • German

  • Greek

  • Hungarian

  • Italian

  • Japanese

  • Korean

  • Norwegian

  • Polish

  • Portuguese (Brazil)

  • Romanian

  • Russian

  • Spanish (Spain)

  • Swedish

  • Turkish

System Center 2012 Configuration Manager offers limited management for mobile devices when you use the Exchange Server connector for Exchange Active Sync (EAS) capable devices that connect to a server running Exchange Server or Exchange Online. For more information about which management functions Configuration Manager supports for mobile devices that the Exchange Server connector manages, see Determine How to Manage Mobile Devices in Configuration Manager.

The following table lists the platforms that support the Exchange Server connector and which versions of Configuration Manager support each platform.

 

Version of Exchange Server System Center 2012 Configuration Manager version

Exchange Server 2010 SP1

  • Configuration Manager with no service pack

  • Configuration Manager with SP1

Exchange Server 2010 SP2
  • Configuration Manager with SP1

Exchange Server 2013
  • Configuration Manager with SP1

Exchange Online (Office 365) 1
  • Configuration Manager with no service pack

  • Configuration Manager with SP1

1 Includes Business Productivity Online Standard Suite.

The following sections list the hardware and operating systems that are supported for the mobile device legacy client in System Center 2012 Configuration Manager.

The mobile device client requires 0.78 MB of storage space to install. In addition, logging on the mobile device can require up to 256 KB of storage space.

System Center 2012 Configuration Manager supports management for Windows Phone, Windows Mobile, and Windows CE when you install the Configuration Manager mobile device legacy client. Features for these mobile devices vary by platform and client type. For more information about which management functions Configuration Manager supports for the mobile device legacy client, see Determine How to Manage Mobile Devices in Configuration Manager.

The following table lists the mobile device platforms that are supported with the mobile device legacy client for Configuration Manager, and the versions of Configuration Manager that support each platform.

 

Operating system System Center 2012 Configuration Manager version Supported languages

Windows CE 5.0 (Arm and x86 processors)

  • Configuration Manager with no service pack

  • Configuration Manager with SP1
  • Chinese (Simplified)

  • Chinese (Traditional)

  • English (US)

  • French (France)

  • German

  • Italian

  • Japanese

  • Korean

  • Portuguese (Brazil)

  • Russian

  • Spanish (Spain)

Windows CE 6.0 (Arm and x86 processors)

  • Configuration Manager with no service pack

  • Configuration Manager with SP1
  • Chinese (Simplified)

  • Chinese (Traditional)

  • English (US)

  • French (France)

  • German

  • Italian

  • Japanese

  • Korean

  • Portuguese (Brazil)

  • Russian

  • Spanish (Spain)

Windows CE 7.0 (Arm and x86 processors)

  • Configuration Manager with no service pack

  • Configuration Manager with SP1
  • Chinese (Simplified)

  • Chinese (Traditional)

  • English (US)

  • French (France)

  • German

  • Italian

  • Japanese

  • Korean

  • Portuguese (Brazil)

  • Russian

  • Spanish (Spain)

Windows Mobile 6.0

  • Configuration Manager with no service pack

  • Configuration Manager with SP1
  • Chinese (Simplified)

  • Chinese (Traditional)

  • English (US)

  • French (France)

  • German

  • Italian

  • Japanese

  • Korean

  • Portuguese (Brazil)

  • Russian

  • Spanish (Spain)

The following table lists the operating systems that are supported to run the Configuration Manager console, and the versions of the Configuration Manager console that support each operating system. Each computer that installs the Configuration Manager console requires the Microsoft .NET Framework 4.

 

Operating system System architecture System Center 2012 Configuration Manager version

Windows XP Professional (SP3)

x86
  • Configuration Manager with no service pack

  • Configuration Manager with SP1

Windows Vista

  • Business Edition (SP2)

  • Enterprise Edition (SP2)

  • Ultimate Edition (SP2)

x86, x64
  • Configuration Manager with no service pack

  • Configuration Manager with SP1

Windows 7

  • Professional Edition (with no service pack, or with SP1)

  • Enterprise Edition (with no service pack, or with SP1)

  • Ultimate Edition (with no service pack, or with SP1)

x86, x64
  • Configuration Manager with no service pack

  • Configuration Manager with SP1

Windows 8

  • Pro

  • Enterprise

x86, x64
  • Configuration Manager with SP1

Windows Server 2008

  • Standard Edition (SP2)

  • Enterprise Edition (SP2)

  • Datacenter Edition (SP2)

x86, x64
  • Configuration Manager with no service pack

  • Configuration Manager with SP1

Windows Server 2008 R2

  • Standard Edition (with no service pack, or with SP1)

  • Enterprise Edition (with no service pack, or with SP1)

  • Datacenter Edition (with no service pack, or with SP1)

x64
  • Configuration Manager with no service pack

  • Configuration Manager with SP1

Windows Server 2012

  • Standard Edition

  • Datacenter Edition

x64
  • Configuration Manager with SP1

Installing both the System Center 2012 Configuration Manager console and the Configuration Manager 2007 console on the same computer is supported. However, both the console and the site it connects to must both run the same version of Configuration Manager. For example, you cannot use the System Center 2012 Configuration Manager console to manage Configuration Manager 2007 sites. Also, you cannot use a console from System Center 2012 Configuration Manager with SP1 to manage a site that runs System Center 2012 Configuration Manager with no service pack, and vice versa. When a hierarchy contains sites that run System Center 2012 Configuration Manager with no service pack and sites that run System Center 2012 Configuration Manager with SP1, some features that are available in System Center 2012 Configuration Manager with SP1 are not available in the console until all sites in the hierarchy upgrade to SP1.

The requirements in the following table apply to each computer that runs Configuration Manager console.

 

Minimum hardware configuration Screen resolution

  • 1 x Pentium 4 Hyper-Threaded 3 GHz (Intel Pentium 4 HT 630 or comparable CPU)

  • 2 GB of RAM

  • 2 GB of disk space.

 

DPI setting

Minimum resolution

96 / 100%

1024x768

120 /125%

1280x960

144 / 150%

1600x1200

196 / 200%

2500x1600

For Configuration Manager SP1 only: With Configuration Manager SP1, the Configuration Manager console supports PowerShell. When you install support for PowerShell on a computer that runs the Configuration Manager console, you can run PowerShell cmdlets on that computer to manage Configuration Manager. You can install a supported version of PowerShell before or after the Configuration Manager console installs. The following table lists the minimum required version of PowerShell for each version of Configuration Manager.

 

PowerShell version System architecture Configuration Manager version

PowerShell 3.0

x86
  • Configuration Manager SP1

Each System Center 2012 Configuration Manager site database can be installed on either the default instance or a named instance of a SQL Server installation. The SQL Server instance can be co-located with the site system server, or on a remote computer.

When you use a remote SQL Server, the instance of SQL Server used to host the site database can also be configured as a SQL Server failover cluster in a single instance cluster, or a multiple instance configuration. SQL Server cluster configurations that have multiple active nodes are supported for hosting the site database. The site database site system role is the only System Center 2012 Configuration Manager site system role supported on an instance of a Windows Server cluster. If you use a SQL Server cluster for the site database, you must add the computer account of the site server to the Local Administrators group of each Windows Server cluster node computer.

noteNote
A SQL Server cluster in a Network Load Balancing (NLB) cluster configuration is not supported. Additionally, SQL Server database mirroring technology and peer-to-peer replication are not supported.

When you install a secondary site, you can use an existing instance of SQL Server or allow Setup to install and use an instance of SQL Server Express. Whichever option that you choose, SQL Server must be located on the secondary site server. The version of SQL Server Express that Setup installs depends on the version of Configuration Manager that you use:

  • Configuration Manager without a service pack: SQL Server 2008 Express

  • Configuration Manager with SP1: SQL Server 2012 Express

The following table lists the SQL Server versions that are supported by System Center 2012 Configuration Manager.

 

SQL Server version SQL Server service pack Minimum required SQL Server cumulative update Configuration Manager version Configuration Manager site type

SQL Server 2008

  • Standard1

  • Enterprise

  • Datacenter

SP2

Minimum of cumulative update 9
  • Configuration Manager with no service pack

  • Configuration Manager with SP1
  • Central administration site

  • Primary site

  • Secondary site

SP3

Minimum of cumulative update 4
  • Configuration Manager with no service pack

  • Configuration Manager with SP1
  • Central administration site

  • Primary site

  • Secondary site

SQL Server 2008 R2

  • Standard1

  • Enterprise

  • Datacenter

SP1

Minimum of cumulative update 6
  • Configuration Manager with no service pack2

  • Configuration Manager with SP1
  • Central administration site

  • Primary site

  • Secondary site

SP2

No minimum cumulative update
  • Configuration Manager with no service pack2

  • Configuration Manager with SP1
  • Central administration site

  • Primary site

  • Secondary site

SQL Server 2012

  • Standard1

  • Enterprise

No service pack

Minimum of cumulative update 2
  • Configuration Manager with SP1
  • Central administration site

  • Primary site

  • Secondary site

SP1

No minimum cumulative update
  • Configuration Manager with SP1
  • Central administration site

  • Primary site

  • Secondary site

SQL Server Express 2008 R2

SP1

Minimum of cumulative update 6
  • Configuration Manager with no service pack

  • Configuration Manager with SP1
  • Secondary site

SP2

No minimum cumulative update
  • Configuration Manager with no service pack

  • Configuration Manager with SP1
  • Secondary site

SQL Server 2012 Express

No service pack

Minimum of cumulative update 2
  • Configuration Manager with SP1
  • Secondary site

SP1

No minimum cumulative update
  • Configuration Manager with SP1
  • Secondary site

1 When you use SQL Server Standard for the database at the central administration site, the hierarchy can only support up to 50,000 clients. For more information, see Site and Site System Role Scalability.

2 Configuration Manager with no service pack does not support the site database on any version of a SQL Server 2008 R2 cluster. This includes any service pack version or cumulative update version of SQL Server 2008 R2. With Configuration Manager SP1, the site database is supported on a SQL Server 2008 R2 cluster.

The following are required configurations for each database server with a full SQL Server installation, and on each SQL Server Express installation that you manually configure for secondary sites. You do not have to configure SQL Server Express for a secondary site if SQL Server Express is installed by Configuration Manager.

 

Configuration More information

SQL Server version

Configuration Manager requires a 64-bit version of SQL Server to host the site database.

Database collation

At each site, both the instance of SQL Server that is used for the site database and the site database must use the following collation: SQL_Latin1_General_CP1_CI_AS.

noteNote
Configuration Manager supports two exceptions to this collation to meet standards that are defined in GB18030 for use in China. For more information, see Technical Reference for International Support in Configuration Manager.

SQL Server features

Only the Database Engine Services feature is required for each site server.

noteNote
Configuration Manager database replication does not require the SQL Server replication feature.

Windows Authentication

Configuration Manager requires Windows authentication to validate connections to the database.

SQL Server instance

You must use a dedicated instance of SQL Server for each site.

SQL Server memory

When you use a database server that is co-located with the site server, limit the memory for SQL Server to 50 to 80 percent of the available addressable system memory.

When you use a dedicated SQL Server, limit the memory for SQL Server to 80 to 90 percent of the available addressable system memory.

Configuration Manager requires SQL Server to reserve a minimum of 8 gigabytes (GB) of memory in the buffer pool used by an instance of SQL Server for the central administration site and primary site and a minimum of 4 gigabytes (GB) for the secondary site. This memory is reserved by using the Minimum server memory setting under Server Memory Options and is configured by using SQL Server Management Studio. For more information about how to set a fixed amount of memory, see How to: Set a Fixed Amount of Memory (SQL Server Management Studio).

Optional SQL Server Configurations

The following configurations either support multiple choices or are optional on each database server with a full SQL Server installation.

 

Configuration More information

SQL Server service

On each database server, you can configure the SQL Server service to run by using a domain local account or the local system account of the computer that is running SQL Server.

  • Use a domain user account as a SQL Server best practice. This kind of account can be more secure than the local system account but might require you to manually register the Service Principle Name (SPN) for the account.

  • Use the local system account of the computer that is running SQL Server to simplify the configuration process. When you use the local system account, Configuration Manager automatically registers the SPN for the SQL Server service. Be aware that using the local system account for the SQL Server service is not a SQL Server best practice.

For information about SQL Server best practices, see the product documentation for the version of Microsoft SQL Server that you are using. For information about SPN configurations for Configuration Manager, see How to Manage the SPN for SQL Server Site Database Servers. For information about how to change the account that is used by the SQL Service, see How to: Change the Service Startup Account for SQL Server (SQL Server Configuration Manager).

SQL Server Reporting Services

Required to install a reporting services point that lets you run reports.

SQL Server ports

For communication to the SQL Server database engine, and for intersite replication, you can use the default SQL Server port configurations or specify custom ports:

  • Intersite communications use the SQL Server Service Broker, which by default uses port TCP 4022.

  • Intrasite communication between the SQL Server database engine and various Configuration Manager site system roles by default use port TCP 1433. The following site system roles communicate directly with the SQL Server database:

    • Management point

    • SMS Provider computer

    • Reporting Services point

    • Site server

When a SQL Server hosts a database from more than one site, each database must use a separate instance of SQL Server, and each instance must be configured to use a unique set of ports.

WarningWarning
Configuration Manager does not support dynamic ports. Because SQL Server named instances by default use dynamic ports for connections to the database engine, when you use a named instance, you must manually configure the static port that you want to use for intrasite communication.

If you have a firewall enabled on the computer that is running SQL Server, make sure that it is configured to allow the ports that are being used by your deployment and at any locations on the network between computers that communicate with the SQL Server.

For an example of how to configure SQL Server to use a specific port, see How to: Configure a Server to Listen on a Specific TCP Port (SQL Server Configuration Manager) in the SQL Server TechNet library.

The following sections identify function-specific requirements for Configuration Manager.

For devices that run the Windows Mobile operating system, Configuration Manager only supports the Uninstall action for applications on Windows Mobile 6.1.4 or later versions.

Configuration Manager requires several prerequisites to support deploying operating systems. The following prerequisites are required on the site server of each central administration site or primary site before you can install the site, even when you do not plan to use operating system deployments:

  • For Configuration Manager with no service pack: Automated Installation Kit (Windows AIK)

  • For Configuration Manager with service pack 1: Windows Assessment and Deployment Kit (Windows ADK)

For more information about prerequisites for operating system deployment, see the Prerequisites For Deploying Operating Systems in Configuration Manager topic in the Deploying Software and Operating Systems in System Center 2012 Configuration Manager guide.

System Center 2012 Configuration Manager supports out of band management for computers that have the following Intel vPro chip sets and Intel Active Management Technology (Intel AMT) firmware versions:

  • Intel AMT version 3.2 with a minimum revision of 3.2.1

  • Intel AMT version 4.0, version 4.1, and version 4.2

  • Intel AMT version 5.0 and version 5.2 with a minimum revision of 5.2.10

  • Intel AMT version 6.0 and version 6.1

The following limitations apply:

  • AMT provisioning is not supported on AMT-based computers that are running any version of Windows Server, Windows XP with SP2, or Windows XP Tablet PC Edition.

  • Out of band communication is not supported to an AMT-based computer that is running the Routing and Remote Access service in the client operating system. This service runs when Internet Connection Sharing is enabled, and the service might be enabled by line of business applications.

  • The out of band management console is not supported on workstations running Windows XP on versions earlier than Service Pack 3.

For more information about out of band management in Configuration Manager, see Introduction to Out of Band Management in Configuration Manager.

The Configuration Manager remote control viewer is not supported on Windows Server 2003 or Windows Server 2008 operating systems.

The minimal screen resolution supported for client computers to run Software Center and the Application Catalog is 1024 by 768.

The following web browsers are supported for use with the Software Center and Application Catalog:

  • Internet Explorer 7

  • Internet Explorer 8

  • Internet Explorer 9

  • Internet Explorer 10

  • Firefox 15

noteNote
The Software Center and Application Catalog do not support web browsers that connect from computers that run Windows Server Core 2008.

All System Center 2012 Configuration Manager site systems must be members of a Windows Active Directory domain. The following table identifies the Windows Active directory domain functional level that is supported with each version of System Center 2012 Configuration Manager:

 

Active Directory domain functional level Configuration Manager version

Windows 2000
  • Configuration Manager with no service pack

  • Configuration Manager with SP1

Windows Server 2003
  • Configuration Manager with no service pack

  • Configuration Manager with SP1

Windows Server 2008
  • Configuration Manager with no service pack

  • Configuration Manager with SP1

Windows Server 2008 R2
  • Configuration Manager with no service pack

  • Configuration Manager with SP1

Windows Server 2012
  • Configuration Manager with SP1
noteNote
If you configure discovery to filter and remove stale computer records, the Active Directory domain functional level must be a minimum of Windows Server 2003.

This requirement includes site systems that support Internet-based client management in a perimeter network (also known as DMZ, demilitarized zone, and screened subnet).

The following are limitations for site systems:

  • Configuration Manager does not support the change of domain membership, domain name, or computer name of a Configuration Manager site system after the site system is installed.

Configuration Manager client computers can be domain members, or workgroup members.

The following sections contain additional information about domain structures and requirements for Configuration Manager.

Configuration Manager Active Directory schema extensions provide benefits for Configuration Manager sites. However, they are not required for all Configuration Manager functions. For more information about Active Directory schema extension considerations, see Determine Whether to Extend the Active Directory Schema for Configuration Manager.

If you have extended your Active Directory schema for Configuration Manager 2007, you do not have to update your schema for System Center 2012 Configuration Manager. You can update the Active Directory schema before or after you install Configuration Manager. Schema updates do not interfere with an existing Configuration Manager 2007 sites or clients. For more information about how to extend the Active Directory schema for System Center 2012 Configuration Manager, see the Prepare Active Directory for Configuration Manager section in the Prepare the Windows Environment for Configuration Manager topic.

Except for out of band management, Configuration Manager supports installing site systems and clients in a domain that has a disjoint namespace.

noteNote
For more information about namespace limitations for when you manage AMT-based computers out of band, see Prerequisites for Out of Band Management in Configuration Manager.

A disjoint namespace scenario is one in which the primary Domain Name System (DNS) suffix of a computer does not match the Active Directory DNS domain name where that computer resides. The computer that uses the primary DNS suffix that does not match is said to be disjoint. Another disjoint namespace scenario occurs if the NetBIOS domain name of a domain controller does not match the Active Directory DNS domain name.

The following table identifies the supported scenarios for a disjoint namespace.

 

Scenario More information

Scenario 1:

The primary DNS suffix of the domain controller differs from the Active Directory DNS domain name. Computers that are members of the domain can be either disjoint or not disjoint.

In this scenario, the primary DNS suffix of the domain controller differs from the Active Directory DNS domain name. The domain controller is disjoint in this scenario. Computers that are members of the domain, such as site servers and computers, can have a primary DNS suffix that either matches the primary DNS suffix of the domain controller or matches the Active Directory DNS domain name.

Scenario 2:

A member computer in an Active Directory domain is disjoint, even though the domain controller is not disjoint.

In this scenario, the primary DNS suffix of a member computer on which a site system is installed differs from the Active Directory DNS domain name, even though the primary DNS suffix of the domain controller is the same as the Active Directory DNS domain name. In this scenario, you have a domain controller that is not disjoint and a member computer that is disjoint. Member computers that are running the Configuration Manager client can have a primary DNS suffix that either matches the primary DNS suffix of the disjoint site system server or matches the Active Directory DNS domain name.

To allow a computer to access domain controllers that are disjoint, you must change the msDS-AllowedDNSSuffixes Active Directory attribute on the domain object container. You must add both of the DNS suffixes to the attribute.

In addition, to make sure that the DNS suffix search list contains all DNS namespaces that are deployed within the organization, you must configure the search list for each computer in the domain that is disjoint. Include in the list of namespaces the primary DNS suffix of the domain controller, the DNS domain name, and any additional namespaces for other servers with which Configuration Manager might interoperate. You can use the Group Policy Management console to configure the Domain Name System (DNS) suffix search list.

ImportantImportant
When you reference a computer in Configuration Manager, enter the computer by using its Primary DNS suffix. This suffix should match the Fully Qualified Domain Name registered as the dnsHostName attribute in the Active Directory domain and the Service Principal Name associated with the system.

Except for out of band management, Configuration Manager supports site systems and clients in a single label domain when the following criteria are met:

  • The single label domain in Active Directory Domain Services must be configured with a disjoint DNS namespace that has a valid top level domain.

    For example: The single label domain of Contoso is configured to have a disjoint namespace in DNS of contoso.com. Therefore, when you specify the DNS suffix in Configuration Manager for a computer in the Contoso domain, you specify Contoso.com and not Contoso.

  • DCOM connections between site servers in the system context must be successful by using Kerberos authentication.

noteNote
For more information about namespace limitations for when you manage AMT-based computers out of band, see Prerequisites for Out of Band Management in Configuration Manager.

The following sections contain general support configuration information for System Center 2012 Configuration Manager.

Configuration Manager supports Internet Protocol version 6 (IPv6) in addition to Internet Protocol version 4 (IPv4). The following table lists the exceptions.

 

Function Exception to IPv6 support

Network Discovery

IPv4 is required when you configure a DHCP server to search in Network Discovery.

Out of band management

IPv4 is required to support out of band management.

Windows CE

IPv4 is required to support the Configuration Manager client on Windows CE devices.

Mobile devices that are enrolled by Windows Intune and the Windows Intune connector

IPv4 is required to support mobile devices that are enrolled by Windows Intune and the Windows Intune connector.

Cloud-based distribution points

IPv4 is required to support Windows Azure and cloud-based distribution points.

Wake-up proxy communication

IPv4 is required to support the client wake-up proxy packets.

Configuration Manager works with any hardware that is certified on the Windows Hardware Compatibility List for the version of the operating system that the Configuration Manager component is installed on. Site Server roles require NTFS file systems so that directory and file permissions can be set. Because Configuration Manager assumes that it has complete ownership of a logical drive, site systems that run on separate computers cannot share a logical partition on any storage technology. However, each computer can use a separate logical partition on the same physical partition of a shared storage device.

Support considerations for the listed storage technologies:

  • Storage Area Network: A Storage Area Network (SAN) is supported when a supported Windows-based server is attached directly to the volume that is hosted by the SAN.

  • Single Instance Storage: Configuration Manager does not support configuration of distribution point package and signature folders on a Single Instance Storage (SIS)-enabled volume.

    Additionally, the cache of a Configuration Manager client is not supported on a SIS-enabled volume.

    noteNote
    Single Instance Storage (SIS) is a feature of the Windows Storage Server 2003 R2 operating system.

  • Removable Disk Drive: Configuration Manager does not support install of Configuration Manager site system or clients on a removable disk drive.

System Center 2012 Configuration Manager provides support for clients in workgroups. Configuration Manager supports moving a client from a workgroup to a domain or from a domain to a workgroup. For more information, see How to Install Configuration Manager Clients on Workgroup Computers

All System Center 2012 Configuration Manager site systems must be members of a supported Active Directory domain. This requirement includes site systems that support Internet-based client management in a perimeter network (also known as DMZ, demilitarized zone, and screened subnet).

Configuration Manager supports client installation and all site server roles in the following virtualization environments:

 

Virtualization environment Configuration Manager version

Windows Server 2008
  • Configuration Manager with no service pack

  • Configuration Manager with SP1

Microsoft Hyper-V Server 2008
  • Configuration Manager with no service pack

  • Configuration Manager with SP1

Windows Server 2008 R2
  • Configuration Manager with no service pack

  • Configuration Manager with SP1

Microsoft Hyper-V Server 2008 R2
  • Configuration Manager with no service pack

  • Configuration Manager with SP1

Windows Server 2008
  • Configuration Manager with no service pack

  • Configuration Manager with SP1

Microsoft Hyper-V Server 2008
  • Configuration Manager with no service pack

  • Configuration Manager with SP1

Windows Server 2012
  • Configuration Manager with SP1

Microsoft Hyper-V Server 2012
  • Configuration Manager with SP1

Each virtual computer that you use must meet or exceed the same hardware and software configuration that you would use for a physical Configuration Manager computer.

You can validate that your virtualization environment is supported for Configuration Manager by using the Server Virtualization Validation Program and its online Virtualization Program Support Policy Wizard. For more information about the Server Virtualization Validation Program, see Windows Server Virtualization Validation Program.

noteNote
Configuration Manager does not support Virtual PC or Virtual Server guest operating systems that run on a Mac.

Configuration Manager cannot manage virtual machines unless they are online. An offline virtual machine image cannot be updated nor can inventory be collected by using the Configuration Manager client on the host computer.

No special consideration is given to virtual machines. For example, Configuration Manager might not determine whether an update has to be re-applied to a virtual machine image if the virtual machine is stopped and restarted without saving the state of the virtual machine to which the update was applied.

Network Address Translation (NAT) is not supported in Configuration Manager, unless the site supports clients that are on the Internet and the client detects that it is connected to the Internet. For more information about Internet-based client management, see the Planning for Internet-Based Client Management section in the Planning for Communications in Configuration Manager topic.

Configuration Manager supports the DirectAccess feature in Windows Server 2008 R2 for communication between site system servers and clients. When all the requirements for DirectAccess are met, by using this feature, Configuration Manager clients on the Internet can communicate with their assigned site as if they were on the intranet.

For server-initiated actions, such as remote control and client push installation, the initiating computer (such as the site server) must be running IPv6, and this protocol must be supported on all intervening networking devices.

Configuration Manager does not support the following over DirectAccess:

  • Deploying operating systems

  • Communication between Configuration Manager sites

  • Communication between Configuration Manager site system servers within a site

Windows BranchCache is integrated in System Center 2012 Configuration Manager. You can configure the BranchCache settings on a deployment type for applications, on the deployment for a package, and for task sequences.

When all the requirements for BranchCache are met, this feature enables clients at remote locations to obtain content from local clients that have a current cache of the content. For example, when the first BranchCache-enabled client computer requests content from a distribution point that is configured as a BranchCache server, the client computer downloads and caches the content. This content is then made available for clients on the same subnet that request this same content, and these clients also cache the content. In this manner, successive clients on the same subnet do not have to download content from the distribution point, and the content is distributed across multiple clients for future transfers.

To support BranchCache with Configuration Manager, add the Windows BranchCache feature to the site system server that is configured as a distribution point. System Center 2012 Configuration Manager distribution points on servers configured to support BranchCache require no additional configuration.

noteNote
With Configuration Manager SP1, cloud-based distribution points support the download of content by clients that are configured for Windows BranchCache.

To use BranchCache, the clients that can support BranchCache must be configured for BranchCache distributed mode, and the operating system setting for BITS client settings must be enabled to support BranchCache.

The following table lists the Configuration Manager client operating systems that are supported with Windows BranchCache and identifies for each operating system if BranchCache distributed mode is supported natively by the operating system, or if the operating system requires the addition of the BITS 4.0 release.

 

Operating system Support details

Windows Vista with SP21

Requires BITS 4.0

Windows 7 with SP1

Supported by default

Windows 8

Supported by default

Windows Server 2008 with SP21

Requires BITS 4.0

Windows Server 2008 R2 with no service pack, with SP1, or with SP2

Supported by default

Windows Server 2012

Supported by default

1 On this operating system, the BranchCache client functionality is not supported for software distribution that is run from the network or for SMB file transfers. Additionally, this operating system cannot use BranchCache functionality with cloud-based distribution points.

You can install the BITS 4.0 release on Configuration Manager clients by using software updates or software distribution. For more information about the BITS 4.0 release, see Windows Management Framework.

For more information about BranchCache, see BranchCache for Windows in the Windows Server documentation.

Fast User Switching, available in Windows XP in workgroup computers, is not supported in System Center 2012 Configuration Manager. Fast User Switching is supported for computers that are running Windows Vista or later versions.

System Center 2012 Configuration Manager cannot manage more than one operating system on a single computer. If there is more than one operating system on a computer that must be managed, adjust the discovery and installation methods that are used to ensure that the Configuration Manager client is installed only on the operating system that has to be managed.

The following sections identify the upgrade options for System Center 2012 Configuration Manager, the operating system version of site servers and clients, and the SQL Server version of database servers.

The following table lists the versions of System Center 2012 Configuration Manager, and the supported upgrade paths between versions.

 

Configuration Manager version Release options Supported Upgrade Paths More information

System Center 2012 Configuration Manager

  • An evaluation release that expires 180 days after installation.

  • A complete release, to perform a new installation.
  • System Center 2012 Configuration Manager evaluation release

You can install System Center 2012 Configuration Manager as either a full installation, or as a trial installation. If you install Configuration Manager as a trial installation, after 180 days, you can only connect a read-only Configuration Manager console and Configuration Manager functionality is limited. At any time before or after the 180 day period, you have the option to upgrade the trial installation to a full installation.

System Center 2012 Configuration Manager supports migration of your Configuration Manager 2007 infrastructure but does not support an in–place upgrade of sites from Configuration Manager 2007.

However, migration supports the upgrade of a Configuration Manager 2007 distribution point, or secondary site that is co-located with a distribution point, to a System Center 2012 Configuration Manager distribution point.

System Center 2012 Configuration Manager SP1
  • An evaluation release that expires 180 days after installation.

  • A complete release, to perform a new installation.

  • An upgrade from System Center 2012 Configuration Manager.
  • System Center 2012 Configuration Manager SP1 evaluation release

  • System Center 2012 Configuration Manager with no service pack

You can install System Center 2012 Configuration Manager SP1 as a trial installation, a full install, or as an upgrade to existing infrastructure that runs System Center 2012 Configuration Manager with no service pack. However, an upgrade Configuration Manager 2007 to System Center 2012 Configuration Manager SP1 is not supported.

If you install Configuration Manager as a trial installation, after 180 days you can only connect a read-only Configuration Manager console and Configuration Manager functionality is limited. At any time before or after the 180 day period, you have the option to upgrade the trial installation to a full installation.

System Center 2012 Configuration Manager SP1 supports migration from Configuration Manager 2007 and System Center 2012 Configuration Manager SP1.

For information about how to upgrade an evaluation release of Configuration Manager to a full installation, see the Upgrade an Evaluation Installation to a Full Installation section in the Install Sites and Create a Hierarchy for Configuration Manager topic.

For more information about migration, see Migrating Hierarchies in System Center 2012 Configuration Manager.

In addition to upgrading the version of System Center 2012 Configuration Manager you use for sites, Configuration Manager clients and Configuration Manager consoles, you can upgrade the operating systems that run Configuration Manager site servers, database servers, site system servers, and clients. The information in the following sections can help you upgrade the infrastructure for Configuration Manager.

Configuration Manager supports an in-place upgrade of the operating system of the site server in the following situations:

  • In-place upgrade to a higher Windows Server service pack as long as the resulting service pack level remains supported by Configuration Manager.

Configuration Manager does not support the following Windows Server upgrade scenarios.

  • Any version of Windows Server 2008 to any version of Windows Server 2008 R2.

  • Any version of Windows Server 2008 to any version of Windows Server 2012.

  • Any version of Windows Server 2008 R2 to any version of Windows Server 2012.

When a direct operating system upgrade is not supported, perform one of the following procedures after you have installed the new operating system:

  • Install System Center 2012 Configuration Manager with the service pack level that you want, and configure the site according to your requirements.

  • Install System Center 2012 Configuration Manager with the service pack level that you want and perform a site recovery. This scenario requires you to have a site backup that was created by using the Backup Site Server maintenance task on the original Configuration Manager site, and that you use the same installation settings for the new System Center 2012 Configuration Manager site.

Configuration Manager supports an in-place upgrade of the operating system for Configuration Manager clients in the following situations:

  • In-place upgrade to a higher Windows Server service pack as long as the resulting service pack level remains supported by Configuration Manager.

Configuration Manager supports an in-place upgrade of SQL Server from a supported version of SQL on the site database server. The following sections provide information about the different upgrade scenarios supported by Configuration Manager and any requirements for each scenario.

Configuration Manager supports the in-place upgrade of SQL Server to a higher service pack as long as the resulting SQL Server service pack level remains supported by Configuration Manager.

When you have multiple Configuration Manager sites in a hierarchy, each site can run a different service pack version of SQL Server, and there is no limitation to the order in which sites upgrade the service pack version of SQL Server that is used for the site database.

Configuration Manager supports the in-place upgrade of SQL Server from SQL Server 2008 to SQL Server 2008 R2.

When you have multiple Configuration Manager sites in a hierarchy, each site can run a different version of SQL Server, and there is no limitation to the order in which sites upgrade the version of SQL Server in use for the site database.

For Configuration Manager SP1 only: Configuration Manager with SP1 supports the in-place upgrade of SQL Server 2008 or SQL Server 2008 R2 to SQL Server 2012 with the following limitations:

  • Each Configuration Manager site must run service pack 1 before you can upgrade the version of SQL Server to SQL Server 2012 at any site.

  • When you upgrade the version of SQL Server that hosts the site database at each site to SQL Server 2012, you must upgrade the SQL Server version that is used at sites in the following order:

    • Upgrade SQL Server at the central administration site first.

    • Upgrade secondary sites before you upgrade a secondary sites parent primary site.

    • Upgrade parent primary sites last. This includes both child primary sites that report to a central administration site, and stand-alone primary sites that are the top-level site of a hierarchy.

    ImportantImportant
    Although you upgrade the service pack version of a Configuration Manager site by upgrading the top-tier site first and then upgrading down the hierarchy, when you upgrade SQL Server to SQL Server 2012, you must use the previous sequence, upgrading the primary sites last. This does not apply to upgrades of SQL Server 2008 to SQL Server 2008 R2.

  1. Stop all Configuration Manager services at the site.

  2. Upgrade SQL Server to a supported version.

  3. Restart the Configuration Manager services.

See Also

-----
For additional resources, see Information and Support for Configuration Manager.

Tip: Use this query to find online documentation in the TechNet Library for System Center 2012 Configuration Manager. For instructions and examples, see Search the Configuration Manager Documentation Library.
-----
Did you find this helpful?
(1500 characters remaining)
© 2013 Microsoft
|
Site Feedback
© 2013 Microsoft. All rights reserved.