The following sections specify the hardware and
software requirements that you must have to implement and maintain
Configuration Manager in your environment.
Use the following information to determine how many
clients (devices) are supported by Configuration Manager sites and
hierarchies.
The following table identifies logical groups that
combine different types of supported devices into one of three
client groups. These client groups are then referenced in this
topic to identify how many devices are supported by each type of
Configuration Manager site, and as a combined total of devices for
a hierarchy of Configuration Manager sites.
Logical groups |
Details |
Client group 1
|
This client group includes computers that run a client for
Configuration Manager and includes Windows Server,
Windows Client, and Windows Embedded operating systems.
It also includes the Configuration Manager client for Linux and
UNIX.
For more information, see the following sections of this
topic:
|
Client group 2
|
This client group includes devices that are managed using
Windows Intune with Configuration Manager, and devices
supported by using the Exchange Server connector.
For more information, see the following sections of this
topic:
Note |
Prior to Configuration Manager SP1, only mobile devices
supported by using the Exchange Server connector are supported
by Configuration Manager. |
|
Client group 3
|
This client group includes devices that are enrolled by
Configuration Manager, devices supported by the mobile device
legacy client, and computers that run the client for Mac.
For more information, see the following sections of this
topic:
|
Clients per Hierarchy
This section contains information about the number of
clients (devices) that are supported by a Configuration Manager
hierarchy.
The following table lists the maximum number of devices
supported by different hierarchy designs and configurations, and is
followed by supplemental details about the different designs and
the maximum number of devices each design supports:
Note |
Configuration Manager supports up to the listed number of
devices from each client group for each listed hierarchy design
when you use the default settings for all Configuration Manager
features. |
Hierarchy design |
Client group 1 |
Client group 2 |
Client group 3 |
Stand-alone primary site
|
100,000
|
50,000 1
|
25,000
|
Central administration site with a site database created on a
Datacenter or Enterprise edition of SQL Server
|
400,000
|
300,000
|
25,000
|
Central administration site with a site database created on a
Standard edition of SQL Server
|
50,000
|
300,000
|
25,000
|
1 When a stand-alone primary site supports
only devices from client group 2, the site can support up to
100,000 devices.
Stand-alone primary: For a hierarchy that has a
stand-alone primary site as the top-level site, Configuration
Manager supports up to 100,000 devices from client group 1.
Additional devices from client group 2 and client group 3
are also supported. Unlike a central administration site, the
edition of SQL Server that you use at a primary site does not
affect the maximum number of clients that the hierarchy can
support.
Central administration site: For a hierarchy
that has a central administration site as the top-level site, the
combined number of clients from client group 1 that the
hierarchy can support depends on the edition of SQL Server
that you use to host the site database at the central
administration site. Regardless of the edition of SQL Server
that you use, the number of devices from client group 2 and
from client group 3 that a hierarchy supports does not
change.
If you expand a stand-alone primary site into a
hierarchy by installing a new central administration site, the
edition of SQL Server in use at the primary site does not
place limits on the number of devices that the hierarchy can
support. Instead, it is the edition of SQL Server in use at
the new central administration site that determines the maximum
number of devices that the new hierarchy can support.
- When you install a central administration
site and use an Enterprise or Datacenter edition of
SQL Server, the hierarchy can support a combined total of up
to 400,000 devices from client group 1. Additional devices
from client group 2 and client group 3 are also
supported. In this configuration, the number of devices that each
child primary site can support remains limited by the configuration
of that primary site. For more information, see the Clients per Site section in
this topic.
- When you install a central administration
site and use a Standard edition of SQL Server, the hierarchy
can support a total of up to 50,000 devices from client
group 1. This total of devices is combined from all child
primary sites in the hierarchy. This limitation exists because of
how the database is partitioned when it’s created by using a
Standard edition of SQL Server at the central administration
site. Additional devices from client group 2 and client
group 3 are also supported. After you install a central
administration site, if you then upgrade the edition of
SQL Server at the central administration site from Standard to
an Enterprise or Datacenter edition, the database does not
repartition and the 50,000 device limitation remains in place.
Clients per Site
The maximum number of clients (devices) that a site can
support depends on the site type, and the version of Configuration
Manager that you use. Although you can only assign a device to a
primary site, secondary sites support communications from
devices.
To help identify the supported number of devices,
devices are divided into three logical client groups. A site is not
limited to supporting devices from a single client group. A primary
site can support a separate number of devices from each of the
three client groups. For example, a stand-alone primary site that
runs Configuration Manager SP1 can support up to 100,000
devices from client group 1, up to 50,000 devices from client
group 2, and up to 25,000 devices from client group 3;
for a total of 175,000 devices. However, Configuration Manager does
not support replacing any number of devices from one client group
with devices from another client group. For example, you have a
stand-alone primary site that has 100,000 assigned devices from
client group 1 and you do not assign any devices from client
group 2 or client group 3. In this scenario, the site
cannot support additional devices from client group 1 even
though it is not supporting additional clients from the additional
client groups.
The following table identifies the maximum number of
devices per client group that are supported at primary and
secondary sites:
Tip |
The maximum number of clients that a primary or secondary site
can support is not affected by the edition of SQL Server you
use at that site. However, a child primary site that uses a local
site database (installed on the site server) is limited to 50,000
clients from client group 1. |
Site type |
Configuration Manager version |
Client group 1 |
Client group 2 |
Client group 3 |
Stand-alone primary site, with a local site database, or a
remote site database
|
System Center 2012 Configuration Manager with no
service pack 1
|
100,000
|
50,000 4
|
25,000
|
System Center 2012 Configuration Manager with
SP1
|
100,000 2
|
50,000 4
|
25,000
|
System Center 2012 R2 Configuration Manager
|
100,000 2
|
50,000 4
|
25,000
|
Child primary site with a local site database
|
System Center 2012 Configuration Manager with no
service pack 1
|
50,000
|
50,000 4
|
25,000
|
System Center 2012 Configuration Manager with
SP1
|
50,000 2
|
50,000 4
|
25,000
|
System Center 2012 R2 Configuration Manager
|
50,000 2
|
50,000 4
|
25,000
|
Child primary site with a remote site database
|
System Center 2012 Configuration Manager with no
service pack 1
|
100,000
|
50,000 4
|
25,000
|
System Center 2012 Configuration Manager with
SP1
|
100,000 2, 3
|
50,000 4
|
25,000
|
System Center 2012 R2 Configuration Manager
|
100,000 2, 3
|
50,000 4
|
25,000
|
Secondary site
|
Any version 1
|
5,000 5
|
1 System Center 2012
Configuration Manager with no service pack does not support
the cilent for Linux and UNIX (client group 1) and does not support
the client for Mac (client group 3). Additioanlly, client
group 2 includes only mobile devices supported by using the
Exchange Server connector. Support for the additional device
types in this client group is introduced with
System Center 2012
Configuration Manager SP1.
2 Beginning with
System Center 2012 Configuration Manager SP1,
primary sites support Windows Embedded devices that have
File-Based Write Filters (FBWF) enabled. When embedded devices do
not have write filters enabled, a primary site can support a number
of embedded devices up to the allowed number of devices for that
site (50,000 or 100,000). Of the total number of devices that a
primary site supports, a maximum of 10,000 of these can be Windows
Embedded devices when those devices 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. A primary site
supports only 3,000 Windows Embedded devices that have FBWF
enabled and that are not configured for the exceptions.
3 In a hierarchy that has a central
administration site that uses a Standard edition of
SQL Server, child primary sites are limited to 50,000 devices
from client group 1 because this is the maximum number of
devices that are supported by that hierarchy configuration.
4 When a site supports only devices from
client group 2, the site can support up to 100,000 devices.
With this configuration, there is no change to the total number of
devices that are supported in the hierarchy.
5 Each secondary site can support
communications from up to 5,000 devices when you use a secondary
site server that has the recommended hardware and a fast and
reliable network connection to its primary parent site. This number
includes a mix of devices from any of the three client groups. A
secondary site could support communications from additional devices
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.
Clients per Management Point
The number of devices that a management point supports
depends on the type of site where the management point is located,
and the type and numbers of clients that might use the management
point. To help you understand the following details, you should be
familiar with the three logical client groups which define
different types of clients. For information about the client
groups, see Client Support
Numbers for Sites and Hierarchies, in this topic.
Site type |
Client group 1 |
Client group 2 |
Client group 3 |
Primary site:
- Each primary site supports up to 10
management points
|
- Allocate at least one management point for
every 25,000 clients
For example, if you have a stand-alone primary site that can
support up to 100,000 clients from client group 1, and you have
100,000 active clients from client group 1, you must have at least
four management points. It is a best practice to provide additional
management points.
Note |
When you use more than four management points in a primary
site, you do not increase the number of clients that site can
support beyond the documented limits. Instead, any additional
management points provide redundancy for communications from
clients. |
|
Not applicable. Clients in client group 2 do not require
the use of a management point.
|
- Allocate at least one management point that
is enabled for mobile devices for every 25,000 devices that run the
mobile device legacy client in addition to any management points
you use to manage devices that run the client for Mac.
- Allocate at least one management point that
is enabled for mobile devices for every 10,000 devices that run the
client for Mac, in addition to any management points you use for
devices that run the mobile device legacy client.
|
Secondary site:
- Each secondary site supports a single
management point which must be installed on the site server
computer.
|
The management point at a secondary site always supports
communications from the same number of clients as supported by the
secondary site server. For information about the number of clients
supported by a secondary site, see, Clients per Site, in this
topic.
|
For example, you have a site that supports the
following devices:
- 35,000 clients that include a mix of Windows
client and server operating systems, Linux, and Windows Embedded
devices (group 1)
- 15,000 devices that run the client for Mac,
(group 3)
- 10,000 devices that run the mobile device
legacy client (group 3)
To support this distribution of devices, you deploy
five management points:
- Two management points to support the various
devices from group 1
- Two management points enabled for mobile
devices to support the clients for Mac
- One additional management point enable for
mobile devices to support the devices that run the mobile device
legacy client
Note |
In most scenarios you cannot control the specific management
point that is used by a client that runs the mobile device legacy
client or the Mac client. Therefore, it is a best practice to plan
for extra capacity, providing additional management points per
device. |
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 or Windows
Server 2012 R2. An exception to this is that beginning
with System Center 2012 R2 Configuration Manager, these operating
systems support the distribution point site system role, without
PXE or multicast support.
- Windows Server 2012 Foundation or
Windows Server 2012 R2 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.
Prerequisites for Site System Roles
The following table identifies prerequisites that are
required by Configuration Manager for each site system role on
supported operating systems prior to Windows Server 2012. For
information about prerequisites for site system roles on Windows
Server 2012 and Windows Server 2012 R2, see Prerequisites for Site System
Roles on Windows Server 2012.
Important |
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:
|
Not applicable
|
Not applicable
|
Windows feature:
- Remote Differential Compression
The computer where you install a central administration site or
a primary site must have the required version of Windows AIK
or Windows ADK installed before you install Configuration
Manager. Similarly, when you upgrade a Configuration Manager site,
you must install the version of the Windows ADK that the new
version of Configuration Manager requires before you can upgrade
the site. For more information about this requirement, see Operating System Deployment in this
topic.
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
|
The computer where you install an instance of the
SMS Provider must have the required version of
Windows AIK or Windows ADK installed before you install
the SMS Provider. Similarly, when you upgrade a Configuration
Manager site, on each computer that runs an instance of the
SMS Provider you must install the version of the
Windows ADK that the new version of Configuration Manager
requires. For more information about this requirement, see Operating System Deploymentin this
topic.
|
Application Catalog web service point
|
Requires both of the following:
|
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:
|
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:
- IIS 6 Management Compatibility:
- IIS 6 Metabase Compatibility
|
Not applicable
|
Asset Intelligence synchronization point
|
Requires the following:
|
Not applicable
|
Not applicable
|
Not applicable
|
Certificate registration point
|
Requires the following:
|
Requires the following options for WCF activation:
|
Requires the default IIS configuration with the following
additions:
- IIS 6 Management Compatibility:
- IIS 6 Metabase Compatibility
- IIS 6 WMI Compatibility
|
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:
- Security:
- 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:
- 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)
Note |
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 System Center 2012 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.
Note |
You can run the Microsoft Visual C++ 2008 Redistributable
Setup from the Configuration Manager installation at:
<ConfigMgrInstallationFolder>\Client\x64\vcredist_x64.exeFor
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.
Note |
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:
|
Not applicable
|
Not applicable
|
Not applicable
|
Enrollment point
|
Requires the following:
- 3.5 SP1 for System Center 2012
Configuration Manager with no service pack
- 4.0 for System Center 2012
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 System Center 2012
Configuration Manager with no service pack
- 4.0 for System Center 2012
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
|
System Center 2012 Configuration Manager with no
service pack:
- Management points that support mobile devices
require the .NET Framework 3.5 SP15
System Center 2012 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:
- Security:
- 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:
- 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:
|
Requires the following options for WCF activation:
- HTTP Activation
- Non-HTTP Activation
|
Not applicable
|
Not applicable
|
Reporting services point
|
Requires the following:
|
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:
|
Not applicable
|
Requires the default IIS configuration
|
Windows Server Update Services (WSUS) 3.0 SP2 must be installed
on this computer.
For more information, see the Planning
for Software Update Point Installation section in the Planning for Software
Updates in Configuration Manager topic.
|
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:
|
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).
Important |
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.
Prerequisites for Site System Roles on
Windows Server 2012
For System Center 2012
Configuration Manager SP1 and
System Center 2012 R2 Configuration Manager
only:
The following table identifies prerequisites that are
required by Configuration Manager site system roles you install on
Windows Server 2012 or Windows Server 2012 R2. 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.5
- Remote Differential Compression
|
The computer where you install a central administration site or
a primary site must have the required version of Windows AIK
or Windows ADK installed before you install Configuration
Manager. Similarly, when you upgrade a Configuration Manager site,
you must install the version of the Windows ADK that the new
version of Configuration Manager requires before you can upgrade
the site. For more information about this requirement, see Operating System Deployment in this
topic.
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
|
The computer where you install an instance of the
SMS Provider must have the required version of
Windows AIK or Windows ADK installed before you install
the SMS Provider. Similarly, when you upgrade a Configuration
Manager site, on each computer that runs an instance of the
SMS Provider you must install the version of the
Windows ADK that the new version of Configuration Manager
requires. For more information about this requirement, see Operating System Deploymentin this
topic.
|
Application Catalog web service point
|
Features:
- .NET Framework 3.5
- HTTP Activation (and automatically selected
options)
- .NET Framework 4.5
IIS Configuration:
- Common HTTP Features:
- 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
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:
- IIS 6 Management Compatibility:
- IIS 6 Metabase Compatibility
|
Not applicable
|
Asset Intelligence synchronization point
|
Features:
|
Not applicable
|
Certificate registration point
|
Features:
IIS Configuration:
- Application Development:
- ASP.NET 3.5 (and automatically selected
options)
- ASP.NET 4.5 (and automatically selected
options)
- IIS 6 Management Compatibility:
- IIS 6 Metabase Compatibility
- IIS 6 WMI Compatibility
|
Not applicable
|
Distribution point
|
Features1:
- Remote Differential Compression
IIS Configuration:
- Application Development:
- Security:
- 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)
Note |
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.
Note |
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.
Note |
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:
|
Not applicable
|
Enrollment point
|
Features:
- .NET Framework 3.5
- .NET Framework 4.5
- Common HTTP Features:
- 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
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:
- 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.5
- BITS Server Extensions (and automatically
selected options), or Background Intelligent Transfer Services
(BITS) (and automatically selected options)
IIS Configuration:
- Application Development:
- Security:
- IIS 6 Management Compatibility:
- IIS 6 Metabase Compatibility
- IIS 6 WMI Compatibility
|
Not applicable
|
Out of band service point
|
Features:
- .NET Framework 4.5
- HTTP Activation
- Non-HTTP Activation
|
Not applicable
|
Reporting services point
|
Features:
|
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.5
Requires the default IIS configuration
|
Windows server role:
- Windows Server Update Services
For more information, see the Planning
for Software Update Point Installation section in the Planning for Software
Updates in Configuration Manager topic.
|
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:
|
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.
Minimum Hardware Requirements for Site
Systems
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
|
|
Free disk space
|
- Available: 10 GB
- Total: 50 GB
|
Operating System Requirements for Site
Servers, Database Servers, and the SMS Provider
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
|
- System Center 2012 Configuration Manager with no
service pack
- System Center 2012 Configuration Manager with
SP1
- System Center 2012 R2 Configuration Manager
|
- System Center 2012 Configuration Manager with no
service pack
- System Center 2012 Configuration Manager with
SP1
- System Center 2012 R2 Configuration Manager
|
- System Center 2012 Configuration Manager with no
service pack
- System Center 2012 Configuration Manager with
SP1
- System Center 2012 R2 Configuration Manager
|
- System Center 2012 Configuration Manager with no
service pack
- System Center 2012 Configuration Manager with
SP1
- System Center 2012 R2 Configuration Manager
|
- System Center 2012 Configuration Manager with no
service pack
- System Center 2012 Configuration Manager with
SP1
- System Center 2012 R2 Configuration Manager
|
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
|
- System Center 2012 Configuration Manager with no
service pack
- System Center 2012 Configuration Manager with
SP1
- System Center 2012 R2 Configuration Manager
|
- System Center 2012 Configuration Manager with no
service pack
- System Center 2012 Configuration Manager with
SP1
- System Center 2012 R2 Configuration Manager
|
- System Center 2012 Configuration Manager with no
service pack
- System Center 2012 Configuration Manager with
SP1
- System Center 2012 R2 Configuration Manager
|
- System Center 2012 Configuration Manager with no
service pack
- System Center 2012 Configuration Manager with
SP1
- System Center 2012 R2 Configuration Manager
|
- System Center 2012 Configuration Manager with no
service pack
- System Center 2012 Configuration Manager with
SP1
- System Center 2012 R2 Configuration Manager
|
Windows Server 2012
|
x64
|
- System Center 2012 Configuration Manager with
SP1
- System Center 2012 R2 Configuration Manager
|
- System Center 2012 Configuration Manager with
SP1
- System Center 2012 R2 Configuration Manager
|
- System Center 2012 Configuration Manager with
SP1
- System Center 2012 R2 Configuration Manager
|
- System Center 2012 Configuration Manager with
SP1
- System Center 2012 R2 Configuration Manager
|
- System Center 2012 Configuration Manager with
SP1
- System Center 2012 R2 Configuration Manager
|
Windows Server 2012 R2
|
x64
|
- System Center 2012 R2 Configuration
Manager
|
- System Center 2012 R2 Configuration
Manager
|
- System Center 2012 R2 Configuration
Manager
|
- System Center 2012
Configuration Manager with SP13
- System Center 2012 R2 Configuration
Manager
|
- System Center 2012 R2 Configuration
Manager
|
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.
3 To support this operating system as a
database server for System Center 2012
Configuration Manager with SP1, you must install cumulative
update 3 for System Center 2012
Configuration Manager SP1. For more information see Description of Cumulative Update 3 for
System Center 2012 Configuration Manager Service Pack 1.
Note |
Windows Server 2012 R2 does not support the Windows
Assessment and Deployment Kit 8.0 (Windows ADK). For Configuration
Manager SP1, the Windows ADK is a prerequisite for a computer
that is a site server or that hosts an instance of the
SMS Provider. Therefore, Windows Server 2012 R2 remains
unsupported for use as a site server or as a host for the SMS
Provider for Configuration Manager SP1 even when cumulative
update 3 is installed. |
Operating System Requirements for Typical
Site System Roles
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
|
- System Center 2012 Configuration Manager with no
service pack1, 2
- System Center 2012 Configuration Manager with
SP11, 2
- System Center 2012 R2 Configuration Manager 1, 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
|
- System Center 2012 Configuration Manager with no
service pack1, 2
- System Center 2012 Configuration Manager with
SP11, 2
- System Center 2012 R2 Configuration Manager 1, 2
|
Not supported
|
Not supported
|
Not supported
|
Not supported
|
Windows 8
|
x86, x64
|
- System Center 2012 Configuration Manager with
SP11, 2
- System Center 2012 R2 Configuration Manager 1, 2
|
Not supported
|
Not supported
|
Not supported
|
Not supported
|
Windows 8.1
|
x86, x64
|
- System Center 2012 Configuration Manager with
SP12, 4, 7
- System Center 2012 R2 Configuration Manager 1, 2
|
Not supported
|
Not supported
|
Not supported
|
Not supported
|
Windows Server 2003
- Standard Edition (SP2)
- Enterprise Edition (SP2)
- Datacenter Edition (SP2)
|
x86, x64
|
- System Center 2012 Configuration Manager with no
service pack2, 4
- System Center 2012 Configuration Manager with
SP12, 4
- System Center 2012 R2 Configuration Manager 2, 4
|
Not supported
|
Not supported
|
Not supported
|
Not supported
|
Windows Server 2003
- Web Edition (SP2)
- Storage Server Edition (SP2)
|
x86
|
- System Center 2012 Configuration Manager with no
service pack2, 4
- System Center 2012 Configuration Manager with
SP12, 4
- System Center 2012 R2 Configuration Manager 2, 4
|
Not supported
|
Not supported
|
Not supported
|
Not supported
|
Windows Server 2003 R2
- Standard Edition
- Enterprise Edition
|
x86, x64
|
- System Center 2012 Configuration Manager with no
service pack2, 4
- System Center 2012 Configuration Manager with
SP12, 4
- System Center 2012 R2 Configuration Manager 2, 4
|
Not supported
|
Not supported
|
Not supported
|
Not supported
|
Windows Server 2008
- Standard Edition (SP2)
- Enterprise Edition (SP2)
- Datacenter Edition (SP2)
|
x86, x64
|
- System Center 2012 Configuration Manager with no
service pack2, 4
- System Center 2012 Configuration Manager with
SP12, 4
- System Center 2012 R2 Configuration Manager 2, 4
|
- System Center 2012 Configuration Manager with no
service pack
- System Center 2012 Configuration Manager with
SP1
- System Center 2012 R2 Configuration Manager
|
- System Center 2012 Configuration Manager with no
service pack
- System Center 2012 Configuration Manager with
SP1
- System Center 2012 R2 Configuration Manager
|
- System Center 2012 Configuration Manager with no
service pack
- System Center 2012 Configuration Manager with
SP1
- System Center 2012 R2 Configuration Manager
|
- System Center 2012 Configuration Manager with
SP1
- System Center 2012 R2 Configuration Manager
|
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
|
- System Center 2012 Configuration Manager with no
service pack4
- System Center 2012 Configuration Manager with
SP15
- System Center 2012 R2 Configuration Manager 5
|
- System Center 2012 Configuration Manager with no
service pack
- System Center 2012 Configuration Manager with
SP1
- System Center 2012 R2 Configuration Manager
|
- System Center 2012 Configuration Manager with no
service pack
- System Center 2012 Configuration Manager with
SP1
- System Center 2012 R2 Configuration Manager
|
- System Center 2012 Configuration Manager with no
service pack
- System Center 2012 Configuration Manager with
SP1
- System Center 2012 R2 Configuration Manager
|
- System Center 2012 Configuration Manager with
SP1
- System Center 2012 R2 Configuration Manager
|
Windows Storage Server 2008 R2
- Workgroup
- Standard
- Enterprise
|
x64
|
- System Center 2012 Configuration Manager with no
service pack2, 4
- System Center 2012 Configuration Manager with
SP12, 5
- System Center 2012 R2 Configuration Manager 2, 5
|
Not supported
|
Not supported
|
Not supported
|
Not supported
|
Windows Server 2012
|
x64
|
- System Center 2012 Configuration Manager with
SP1
- System Center 2012 R2 Configuration Manager 6
|
- System Center 2012 Configuration Manager with
SP1
- System Center 2012 R2 Configuration Manager
|
- System Center 2012 Configuration Manager with
SP1
- System Center 2012 R2 Configuration Manager
|
- System Center 2012 Configuration Manager with
SP1
- System Center 2012 R2 Configuration Manager
|
- System Center 2012 Configuration Manager with
SP1
- System Center 2012 R2 Configuration Manager
|
The Server Core installation of Windows Server 2012
|
x64
|
- System Center 2012 R2 Configuration Manager 1, 2
|
Not supported
|
Not supported
|
Not supported
|
Not supported
|
Windows Server 2012 R2
|
x64
|
- System Center 2012 Configuration Manager with
SP17
- System Center 2012 R2 Configuration Manager 6
|
- System Center 2012 Configuration Manager with
SP17
- System Center 2012 R2 Configuration Manager
|
- System Center 2012 Configuration Manager with
SP17
- System Center 2012 R2 Configuration Manager
|
- System Center 2012 Configuration Manager with
SP17
- System Center 2012 R2 Configuration Manager
|
- System Center 2012 Configuration Manager with
SP17
- System Center 2012 R2 Configuration Manager
|
The Server Core installation of Windows
Server 2012 R2
|
x64
|
- System Center 2012 R2 Configuration Manager 1, 2
|
Not supported
|
Not supported
|
Not supported
|
Not supported
|
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.
5 Distribution points on this operating
system version are supported for PXE boot of x64 UEFI computers but
do not support PXE boot of IA32 UEFI computers.
6 Distribution points on this operating
system version are supported for PXE boot of both x64 and IA32 UEFI
computers.
7 To support this operating system as a site
system server for System Center 2012
Configuration Manager with SP1, you must install cumulative
update 3 for System Center 2012
Configuration Manager SP1. For more information see Description of Cumulative Update 3 for
System Center 2012 Configuration Manager Service Pack 1.
Operating System Requirements for
Function-Specific Site System Roles
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 |
Certificate registration 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
|
- System Center 2012 Configuration Manager with no
service pack
- System Center 2012 Configuration Manager with
SP1
- System Center 2012 R2 Configuration Manager
|
- System Center 2012 Configuration Manager with no
service pack
- System Center 2012 Configuration Manager with
SP1
- System Center 2012 R2 Configuration Manager
|
Not supported
|
- System Center 2012 Configuration Manager with no
service pack
- System Center 2012 Configuration Manager with
SP1
- System Center 2012 R2 Configuration Manager
|
- System Center 2012 Configuration Manager with no
service pack
- System Center 2012 Configuration Manager with
SP1
- System Center 2012 R2 Configuration Manager
|
- System Center 2012 Configuration Manager with no
service pack
- System Center 2012 Configuration Manager with
SP1
- System Center 2012 R2 Configuration Manager
|
- System Center 2012 Configuration Manager with no
service pack
- System Center 2012 Configuration Manager with
SP1
- System Center 2012 R2 Configuration Manager
|
- System Center 2012 Configuration Manager with no
service packSystem Center 2012 Configuration Manager
with SP1System Center 2012 R2 Configuration Manager
|
- System Center 2012 Configuration Manager with no
service pack
- System Center 2012 Configuration Manager with
SP1
- System Center 2012 R2 Configuration Manager
|
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
|
- System Center 2012 Configuration Manager with no
service pack
- System Center 2012 Configuration Manager with
SP1
- System Center 2012 R2 Configuration Manager
|
- System Center 2012 Configuration Manager with no
service pack
- System Center 2012 Configuration Manager with
SP1
- System Center 2012 R2 Configuration Manager
|
- System Center 2012 R2 Configuration
Manager
|
- System Center 2012 Configuration Manager with no
service pack
- System Center 2012 Configuration Manager with
SP1
- System Center 2012 R2 Configuration Manager
|
- System Center 2012 Configuration Manager with no
service pack
- System Center 2012 Configuration Manager with
SP1
- System Center 2012 R2 Configuration Manager
|
- System Center 2012 Configuration Manager with no
service pack
- System Center 2012 Configuration Manager with
SP1
- System Center 2012 R2 Configuration Manager
|
- System Center 2012 Configuration Manager with no
service pack
- System Center 2012 Configuration Manager with
SP1
- System Center 2012 R2 Configuration Manager
|
- System Center 2012 Configuration Manager with no
service packSystem Center 2012 Configuration Manager
with SP1System Center 2012 R2 Configuration Manager
|
- System Center 2012 Configuration Manager with no
service pack
- System Center 2012 Configuration Manager with
SP1
- System Center 2012 R2 Configuration Manager
|
Windows Server 2012
|
x64
|
- System Center 2012 Configuration Manager with
SP1
- System Center 2012 R2 Configuration Manager
|
- System Center 2012 Configuration Manager with
SP1
- System Center 2012 R2 Configuration Manager
|
- System Center 2012 R2 Configuration
Manager
|
- System Center 2012 Configuration Manager with
SP1
- System Center 2012 R2 Configuration Manager
|
- System Center 2012 Configuration Manager with
SP1
- System Center 2012 R2 Configuration Manager
|
- System Center 2012 Configuration Manager with
SP12
- System Center 2012 R2 Configuration Manager
|
- System Center 2012 Configuration Manager with
SP1
- System Center 2012 R2 Configuration Manager
|
- System Center 2012 Configuration Manager with
SP1System Center 2012 R2 Configuration Manager
|
- System Center 2012 Configuration Manager with
SP1
- System Center 2012 R2 Configuration Manager
|
Windows Server 2012 R2
|
x64
|
- System Center 2012 Configuration Manager with
SP11
- System Center 2012 R2 Configuration Manager
|
- System Center 2012 Configuration Manager with
SP11
- System Center 2012 R2 Configuration Manager
|
- System Center 2012 R2 Configuration
Manager
|
- System Center 2012 Configuration Manager with
SP11
- System Center 2012 R2 Configuration Manager
|
- System Center 2012 Configuration Manager with
SP11
- System Center 2012 R2 Configuration Manager
|
- System Center 2012 Configuration Manager with
SP11
- System Center 2012 R2 Configuration Manager
|
- System Center 2012 Configuration Manager with
SP11
- System Center 2012 R2 Configuration Manager
|
- System Center 2012 Configuration Manager with
SP11
- System Center 2012 R2 Configuration Manager
|
- System Center 2012 Configuration Manager with
SP11
- System Center 2012 R2 Configuration Manager
|
1 To support this operating system as a site
system server for System Center 2012
Configuration Manager with SP1, you must install cumulative
update 3 for System Center 2012
Configuration Manager SP1. For more information see Description of Cumulative Update 3 for
System Center 2012 Configuration Manager Service Pack 1.
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.
Computer Client Hardware
Requirements
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.
Note |
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
creates a cache that is 2 MB in size.
For more information about these client installation settings,
see About Client
Installation Properties in Configuration Manager.
Tip |
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.
|
Operating System Requirements for
Configuration Manager Client Installation
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 |
Configuration Manager version |
Windows XP Professional (SP3)
|
x86
|
- System Center 2012 Configuration Manager with no
service pack
- System Center 2012 Configuration Manager with
SP1
- System Center 2012 R2 Configuration Manager
|
Windows XP Professional for 64-bit Systems (SP2)
|
x64
|
- System Center 2012 Configuration Manager with no
service pack
- System Center 2012 Configuration Manager with
SP1
- System Center 2012 R2 Configuration Manager
|
Windows XP Tablet PC (SP3)
|
x86
|
- System Center 2012 Configuration Manager with no
service pack
- System Center 2012 Configuration Manager with
SP1
- System Center 2012 R2 Configuration Manager
|
Windows Vista
- Business Edition (SP2)
- Enterprise Edition (SP2)
- Ultimate Edition (SP2)
|
x86, x64
|
- System Center 2012 Configuration Manager with no
service pack
- System Center 2012 Configuration Manager with
SP1
- System Center 2012 R2 Configuration Manager
|
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
|
- System Center 2012 Configuration Manager with no
service pack
- System Center 2012 Configuration Manager with
SP1
- System Center 2012 R2 Configuration Manager
|
Windows 8
|
x86, x64
|
- System Center 2012 Configuration Manager with
SP1
- System Center 2012 R2 Configuration Manager
|
Windows 8.1
|
x86, x64
|
- System Center 2012 Configuration Manager with
SP13
- System Center 2012 R2 Configuration Manager
|
Windows Server 2003 Web Edition (SP2)
|
x86
|
- System Center 2012 Configuration Manager with no
service pack
- System Center 2012 Configuration Manager with
SP1
- System Center 2012 R2 Configuration Manager
|
Windows Server 2003
- Standard Edition (SP2)
- Enterprise Edition (SP2)
- Datacenter Edition1 (SP2)
|
x86, x64
|
- System Center 2012 Configuration Manager with no
service pack
- System Center 2012 Configuration Manager with
SP1
- System Center 2012 R2 Configuration Manager
|
Windows Server 2003 R2 SP2
- Standard Edition
- Enterprise Edition
- Datacenter Edition1
|
x86, x64
|
- System Center 2012 Configuration Manager with no
service pack
- System Center 2012 Configuration Manager with
SP1
- System Center 2012 R2 Configuration Manager
|
Windows Storage Server 2003 R2 SP2
|
x86, x64
|
- System Center 2012 Configuration Manager with no
service pack
- System Center 2012 Configuration Manager with
SP1
- System Center 2012 R2 Configuration Manager
|
Windows Server 2008
- Standard Edition (SP2)
- Enterprise Edition (SP2)
- Datacenter Edition (SP2) 1
|
x86, x64
|
- System Center 2012 Configuration Manager with no
service pack
- System Center 2012 Configuration Manager with
SP1
- System Center 2012 R2 Configuration Manager
|
The Server Core installation of Windows Server 2008
(SP2)
|
x86, x64
|
- System Center 2012 Configuration Manager with no
service pack
- System Center 2012 Configuration Manager with
SP1
|
Windows Storage Server 2008 R2
- Workgroup
- Standard
- Enterprise
|
x64
|
- System Center 2012 Configuration Manager with no
service pack
- System Center 2012 Configuration Manager with
SP1
- System Center 2012 R2 Configuration Manager
|
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
|
- System Center 2012 Configuration Manager with no
service pack
- System Center 2012 Configuration Manager with
SP1
- System Center 2012 R2 Configuration Manager
|
The Server Core installation of Windows
Server 2008 R2 (with no service pack, or with SP1)
|
x64
|
- System Center 2012 Configuration Manager with no
service pack
- System Center 2012 Configuration Manager with
SP1
- System Center 2012 R2 Configuration Manager
|
Windows Server 2012
|
x64
|
- System Center 2012 Configuration Manager with
SP1
- System Center 2012 R2 Configuration Manager
|
The Server Core installation of Windows
Server 20122
|
x64
|
- System Center 2012 Configuration Manager with
SP1
- System Center 2012 R2 Configuration Manager
|
Windows Server 2012 R2
|
x64
|
- System Center 2012 Configuration Manager with
SP13
- System Center 2012 R2 Configuration Manager
|
Windows Storage Server 2012 R2
|
x64
|
- System Center 2012 Configuration Manager with
SP13
- System Center 2012 R2 Configuration Manager
|
The Server Core installation of Windows
Server 2012 R22
|
x64
|
- System Center 2012 R2 Configuration Manager
|
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 this operating system version must run the File
Server role service for the File and Storage Services server
role.
3 To support this operating system as a
client with System Center 2012 Configuration Manager
with SP1, you must first install cumulative update 3 for
System Center 2012 Configuration Manager SP1. For
more information see Description of Cumulative Update 3 for
System Center 2012 Configuration Manager Service Pack 1.
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.
Embedded Operating System Requirements
for Configuration Manager Clients
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.
- For System Center 2012
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.
- Beginning with System Center 2012
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.
- Beginning with System Center 2012 R2
Configuration Manager, clients that use Unified Write Filters (UWF)
are natively supported for all features except power
management.
- 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.
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 |
Configuration Manager version |
System Center 2012 Endpoint Protection version |
Windows Embedded Standard 2009
|
Windows XP SP3
|
x86
|
- System Center 2012 Configuration Manager with no
service pack
- System Center 2012 Configuration Manager with
SP1
- System Center 2012 R2 Configuration Manager
|
- System Center 2012
Endpoint Protection with SP1
|
Windows XP Embedded SP3
|
Windows XP SP3
|
x86
|
- System Center 2012 Configuration Manager with no
service pack
- System Center 2012 Configuration Manager with
SP1
- System Center 2012 R2 Configuration Manager
|
- System Center 2012
Endpoint Protection with SP1
|
Windows Fundamentals for Legacy PCs (WinFLP)
|
Windows XP SP3
|
x86
|
- System Center 2012 Configuration Manager with no
service pack
- System Center 2012 Configuration Manager with
SP1
- System Center 2012 R2 Configuration Manager
|
- System Center 2012
Endpoint Protection with SP1
|
Windows Embedded POSReady 2009
|
Windows XP SP3
|
x86
|
- System Center 2012 Configuration Manager with no
service pack
- System Center 2012 Configuration Manager with
SP1
- System Center 2012 R2 Configuration Manager
|
- System Center 2012
Endpoint Protection with SP1
|
WEPOS 1.1 with SP3
|
Windows XP SP3
|
x86
|
- System Center 2012 Configuration Manager with no
service pack
- System Center 2012 Configuration Manager with
SP1
- System Center 2012 R2 Configuration Manager
|
- System Center 2012
Endpoint Protection with SP1
|
Windows Embedded Standard 7 with SP1
|
Windows 7
|
x86, x64
|
- System Center 2012 Configuration Manager with no
service pack
- System Center 2012 Configuration Manager with
SP1
- System Center 2012 R2 Configuration Manager
|
- System Center 2012
Endpoint Protection with no service pack
- System Center 2012
Endpoint Protection with SP1
|
Windows Embedded POSReady 7
|
Windows 7
|
x86, x64
|
- System Center 2012 Configuration Manager with no
service pack
- System Center 2012 Configuration Manager with
SP1
- System Center 2012 R2 Configuration Manager
|
- System Center 2012
Endpoint Protection with no service pack
- System Center 2012
Endpoint Protection with SP1
|
Windows Thin PC
|
Windows 7
|
x86, x64
|
- System Center 2012 Configuration Manager with no
service pack
- System Center 2012 Configuration Manager with
SP1
- System Center 2012 R2 Configuration Manager
|
- System Center 2012
Endpoint Protection with no service pack
- System Center 2012
Endpoint Protection with SP1
|
Windows Embedded 8 Pro
|
Windows 8
|
x86, x64
|
- System Center 2012 Configuration Manager with
SP11
- System Center 2012 R2 Configuration Manager
|
- System Center 2012
Endpoint Protection with SP1
|
Windows Embedded 8 Standard
|
Windows 8
|
x86, x64
|
- System Center 2012 Configuration Manager with
SP11
|
- System Center 2012
Endpoint Protection with SP1
|
Windows Embedded 8 Industry
|
Windows 8
|
x86, x64
|
- System Center 2012 Configuration Manager with
SP11
- System Center 2012 R2 Configuration Manager
|
- System Center 2012
Endpoint Protection with SP1
|
Windows Embedded 8.1 Industry
|
Windows 8.1
|
x86, x64
|
- System Center 2012 R2 Configuration Manager
|
- System Center 2012 R2 Endpoint Protection
|
1 The Unified Write Filter (UWF) that is
included with this version of Windows Embedded is not supported by
System Center 2012 Configuration Manager SP1.
Therefore, with System Center 2012
Configuration Manager SP1, the built-in features for
write filter management will not work with UWF.
Client Requirements for Mac
Computers
Note |
For System Center 2012
Configuration Manager SP1 and
System Center 2012 R2 Configuration Manager
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:
Operating system |
Configuration Manager version |
Mac OS X 10.6 (Snow Leopard)
|
- System Center 2012
Configuration Manager with SP1
- System Center 2012 R2 Configuration
Manager
|
Mac OS X 10.7 (Lion)
|
- System Center 2012
Configuration Manager with SP1
- System Center 2012 R2 Configuration
Manager
|
Mac OS X 10.8 (Mountain Lion)
|
- System Center 2012
Configuration Manager with SP1 cumulative update 1
- System Center 2012 R2 Configuration
Manager
|
For more information about computers that run Mac OS X,
see How to
Install Clients on Mac Computers in Configuration Manager.
Client Requirements for Linux and UNIX
Servers
Note |
For System Center 2012
Configuration Manager SP1 and
System Center 2012 R2 Configuration Manager
only: |
Use the information in the following sections to
identify the supported distributions of Linux and UNIX and the
hardware requirements to run a 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.
Supported Distributions of Linux and
UNIX
The following table lists the different releases of the
client for Linux and UNIX that you can use with each version of
Configuration Manager:
Configuration Manager version |
Version of the client for Linux and UNIX |
System Center 2012 Configuration Manager with no service
pack
|
Not supported
|
System Center 2012 Configuration Manager with SP1
|
- System Center 2012 Configuration
Manager SP1 Client for Linux and UNIX
- Cumulative Update 1 for System
Center 2012 Configuration Manager SP1 Client for Linux
and UNIX
|
System Center 2012 R2 Configuration Manager
|
- System Center 2012 R2 Configuration Manager
Agent for Linux and UNIX
|
The following table identifies the operating systems,
platforms, and client installation packages that are supported for
each release of the client for Linux and UNIX:
Important |
Only the most recent update for the System Center 2012
Configuration Manager SP1 Client for Linux and UNIX or the
System Center 2012 R2 Configuration Manager Agent for Linux and
UNIX is available for download. You can download clients for
additional operating systems, and view the Release History
including the client build versions online at the Microsoft
Download Center:
|
Operating system |
Version |
System Center 2012 Configuration Manager SP1 Client
for Linux and UNIX |
Cumulative Update 1 for System Center 2012
Configuration Manager SP1 Client for Linux and UNIX |
System Center 2012 R2 Configuration Manager Agent for Linux and
UNIX |
Red Hat Enterprise Linux (RHEL)
|
Version 4 x86
|
ccm-RHEL4x86.<build>.tar
|
ccm-RHEL4x86.<build>.tar
|
ccm-RHEL4x86.<build>.tar
|
Version 4 x64
|
ccm-RHEL4x64.<build>.tar
|
ccm-RHEL4x64.<build>.tar
|
ccm-RHEL4x64.<build>.tar
|
Version 5 x86
|
ccm-RHEL5x86.<build>.tar
|
ccm-Universalx86.<build>.tar
|
ccm-Universalx86.<build>.tar
|
Version 5 x64
|
ccm-RHEL5x64.<build>.tar
|
ccm-Universalx64.<build>.tar
|
ccm-Universalx64.<build>.tar
|
Version 6 x86
|
ccm-RHEL6x86.<build>.tar
|
ccm-Universalx86.<build>.tar
|
ccm-Universalx86.<build>.tar
|
Version 6 x64
|
ccm-RHEL6x64.<build>.tar
|
ccm-Universalx64.<build>.tar
|
ccm-Universalx64.<build>.tar
|
Solaris
|
Version 9 SPARC
|
ccm-Sol9sparc.<build>.tar
|
ccm-Sol9sparc.<build>.tar
|
ccm-Sol9sparc.<build>.tar
|
Version 10 x86
|
ccm-Sol10x86.<build>.tar
|
ccm-Sol10x86.<build>.tar
|
ccm-Sol10x86.<build>.tar
|
Version 10 SPARC
|
ccm-Sol10sparc.<build>.tar
|
ccm-Sol10sparc.<build>.tar
|
ccm-Sol10sparc.<build>.tar
|
Version 11 x86
|
No support
|
ccm-Sol11x86.<build>.tar
|
ccm-Sol11x86.<build>.tar
|
Version 11 SPARC
|
No support
|
ccm-Sol11sparc.<build>.tar
|
ccm-Sol11sparc.<build>.tar
|
SUSE Linux Enterprise Server (SLES)
|
Version 9 x86
|
ccm-SLES9x86.<build>.tar
|
ccm-SLES9x86.<build>.tar
|
ccm-SLES9x86.<build>.tar
|
Version 10 SP1 x86
|
ccm-SLES10x86.<build>.tar
|
ccm-Universalx86.<build>.tar
|
ccm-Universalx86.<build>.tar
|
Version 10 SP1 x64
|
ccm-SLES10x64.<build>.tar
|
ccm-Universalx64.<build>.tar
|
ccm-Universalx64.<build>.tar
|
Version 11 SP1 x86
|
ccm-SLES11x86.<build>.tar
|
ccm-Universalx86.<build>.tar
|
ccm-Universalx86.<build>.tar
|
Version 11 SP1 x64
|
ccm-SLES11x64.<build>.tar
|
ccm-Universalx64.<build>.tar
|
ccm-Universalx64.<build>.tar
|
CentOS
|
Version 5 x86
|
No support
|
ccm-Universalx86.<build>.tar
|
ccm-Universalx86.<build>.tar
|
Version 5 x64
|
No support
|
ccm-Universalx64.<build>.tar
|
ccm-Universalx64.<build>.tar
|
Version 6 x86
|
No support
|
ccm-Universalx86.<build>.tar
|
ccm-Universalx86.<build>.tar
|
Version 6 x64
|
No support
|
ccm-Universalx64.<build>.tar
|
ccm-Universalx64.<build>.tar
|
Debian
|
Version 5 x86
|
No support
|
ccm-Universalx86.<build>.tar
|
ccm-Universalx86.<build>.tar
|
Version 5 x64
|
No support
|
ccm-Universalx64.<build>.tar
|
ccm-Universalx64.<build>.tar
|
Version 6 x86
|
No support
|
ccm-Universalx86.<build>.tar
|
ccm-Universalx86.<build>.tar
|
Version 6 x64
|
No support
|
ccm-Universalx64.<build>.tar
|
ccm-Universalx64.<build>.tar
|
Version 7 x86
|
No support
|
No support
|
ccm-Universalx86.<build>.tar
|
Version 7 x64
|
No support
|
No support
|
ccm-Universalx64.<build>.tar
|
Ubuntu
|
Version 10.4 LTS x86
|
No support
|
ccm-Universalx86.<build>.tar
|
ccm-Universalx86.<build>.tar
|
Version 10.4 LTS x64
|
No support
|
ccm-Universalx64.<build>.tar
|
ccm-Universalx64.<build>.tar
|
Version 12.4 LTS x86
|
No support
|
ccm-Universalx86.<build>.tar
|
ccm-Universalx86.<build>.tar
|
Version 12.4 LTS x64
|
No support
|
ccm-Universalx64.<build>.tar
|
ccm-Universalx64.<build>.tar
|
Oracle Linux
|
Version 5 x86
|
No support
|
ccm-Universalx86.<build>.tar
|
ccm-Universalx86.<build>.tar
|
Version 5 x64
|
No support
|
ccm-Universalx64.<build>.tar
|
ccm-Universalx64.<build>.tar
|
Version 6 x86
|
No support
|
ccm-Universalx86.<build>.tar
|
ccm-Universalx86.<build>.tar
|
Version 6 x64
|
No support
|
ccm-Universalx64.<build>.tar
|
ccm-Universalx64.<build>.tar
|
HP-UX
|
Version 11iv2 IA64
|
No support
|
ccm-HpuxB.11.23i64.<build>.tar
|
ccm-HpuxB.11.23i64.<build>.tar
|
Version 11iv2 PA-RISC
|
No support
|
ccm-HpuxB.11.23PA.<build>.tar
|
ccm-HpuxB.11.23PA.<build>.tar
|
Version 11iv3 IA64
|
No support
|
ccm-HpuxB.11.31i64.<build>.tar
|
ccm-HpuxB.11.31i64.<build>.tar
|
Version 11iv3 PA-RISC
|
No support
|
ccm-HpuxB.11.31PA.<build>.tar
|
ccm-HpuxB.11.31PA.<build>.tar
|
AIX
|
Version 5.3 (Power)
|
No support
|
ccm-Aix53ppc.<build>.tar
|
ccm-Aix53ppc.<build>.tar
|
Version 6.1 (Power)
|
No support
|
ccm-Aix61ppc.<build>.tar
|
ccm-Aix61ppc.<build>.tar
|
Version 7.1 (Power)
|
No support
|
ccm-Aix71ppc.<build>.tar
|
ccm-Aix71ppc.<build>.tar
|
Note |
For the clients for Linux and UNIX, the listed version includes
all subsequent minor versions. For example, where the table
indicates support for CentOS version 6, this also includes any
subsequent minor version of CentOS 6, such as CentOS 6.3.
Similarly, where the table indicates support for an operating
system that uses service packs, such as SUSE Linux Enterprise
Server 11 SP1, support includes subsequent service packs for that
operating system. |
For information about client installation packages and
the Universal Agent, see How to Install Clients
on Linux and UNIX Computers in Configuration Manager.
Hardware and Disk Space Requirements
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.
Note |
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
|
Mobile Devices Enrolled by 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 |
Configuration Manager version |
Supported languages |
Windows Mobile 6.1
|
- System Center 2012 Configuration Manager with no
service pack
- System Center 2012 Configuration Manager with
SP1
- System Center 2012 R2 Configuration Manager
|
- Chinese (Simplified)
- Chinese (Traditional)
- English (US)
- French (France)
- German
- Italian
- Japanese
- Korean
- Portuguese (Brazil)
- Russian
- Spanish (Spain)
|
Windows Mobile 6.5
|
- System Center 2012 Configuration Manager with no
service pack
- System Center 2012 Configuration Manager with
SP1
- System Center 2012 R2 Configuration Manager
|
- Chinese (Simplified)
- Chinese (Traditional)
- English (US)
- French (France)
- German
- Italian
- Japanese
- Korean
- Portuguese (Brazil)
- Russian
- Spanish (Spain)
|
Nokia Symbian Belle
|
- System Center 2012 Configuration Manager with no
service pack
- System Center 2012 Configuration Manager with
SP1
- System Center 2012 R2 Configuration Manager
|
- 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
|
Mobile Devices Enrolled by Windows
Intune
For System Center 2012
Configuration Manager SP1 and
System Center 2012 R2 Configuration Manager
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.
Important |
You must have a subscription to Windows Intune to manage the
following operating systems. |
Operating system |
Operating system version |
Configuration Manager version |
Company portal supported languages |
Windows Phone 8
|
Not applicable
|
- System Center 2012
Configuration Manager with SP1
- System Center 2012 R2 Configuration
Manager
|
- 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 8 RT
|
Not applicable
|
- System Center 2012
Configuration Manager with SP1
- System Center 2012 R2 Configuration
Manager
|
Windows 8.1 RT
|
Not applicable
|
- System Center 2012 R2 Configuration
Manager
|
Windows 8.1
|
Not applicable
|
- System Center 2012 R2 Configuration
Manager
|
iOS
|
|
- System Center 2012
Configuration Manager with SP1
- System Center 2012 R2 Configuration
Manager
|
|
- System Center 2012 R2 Configuration
Manager
|
Android 1
|
|
- System Center 2012
Configuration Manager with SP1
- System Center 2012 R2 Configuration
Manager
|
1 Support for devices that run Android
begins with Android 2.3, and includes all subsequent releases
of Android. However, when you use System Center 2012
Configuration Manager SP1, or when you use System Center
2012 R2 Configuration Manager with a version of Android that is
prior to 4.0, a limited set of functionality is available.
Beginning with System Center 2012 R2 Configuration Manager, when
you use the Company Portal app, Configuration Manager supports
additional capabilities for devices that run Android 4.0 or
later.
For more information, see the How to Manage Mobile
Devices by Using Configuration Manager and Windows Intune topic
in the Deploying
Clients for System Center 2012 Configuration Manager guide.
Mobile Device Support by Using the
Exchange Server Connector
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 |
Configuration Manager version |
Exchange Server 2010 SP1
|
- System Center 2012 Configuration Manager with no
service pack
- System Center 2012 Configuration Manager with
SP1
- System Center 2012 R2 Configuration Manager
|
Exchange Server 2010 SP2
|
- System Center 2012 Configuration Manager with
SP1
- System Center 2012 R2 Configuration Manager
|
Exchange Server 2013
|
- System Center 2012
Configuration Manager with SP1
- System Center 2012 R2 Configuration
Manager
|
Exchange Online (Office 365) 1
|
- System Center 2012 Configuration Manager with no
service pack
- System Center 2012 Configuration Manager with
SP1
- System Center 2012 R2 Configuration Manager
|
1 Includes Business Productivity Online
Standard Suite.
Mobile Device Legacy Client
The following sections list the hardware and operating
systems that are supported for the mobile device legacy client in
System Center 2012 Configuration Manager.
Mobile Device Legacy Client Hardware
Requirements
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.
Mobile Device Legacy Client
Operating System Requirements
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 |
Configuration Manager version |
Supported languages |
Windows CE 5.0 (Arm and x86 processors)
|
- System Center 2012 Configuration Manager with no
service pack
- System Center 2012 Configuration Manager with
SP1
- System Center 2012 R2 Configuration Manager
|
- 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)
|
- System Center 2012 Configuration Manager with no
service pack
- System Center 2012 Configuration Manager with
SP1
- System Center 2012 R2 Configuration Manager
|
- 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)
|
- System Center 2012 Configuration Manager with no
service pack
- System Center 2012 Configuration Manager with
SP1
- System Center 2012 R2 Configuration Manager
|
- Chinese (Simplified)
- Chinese (Traditional)
- English (US)
- French (France)
- German
- Italian
- Japanese
- Korean
- Portuguese (Brazil)
- Russian
- Spanish (Spain)
|
Windows Mobile 6.0
|
- System Center 2012 Configuration Manager with no
service pack
- System Center 2012 Configuration Manager with
SP1
- System Center 2012 R2 Configuration Manager
|
- 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, the minimum
version of the Microsoft .NET Framework they require, and the
versions of the Configuration Manager console that support each
operating system.
Operating system |
System architecture |
Minimum .NET Framework version |
Configuration Manager version |
Windows XP Professional (SP3)
|
x86
|
.NET Framework 4 1
|
- System Center 2012 Configuration Manager with no
service pack
- System Center 2012 Configuration Manager with
SP1
- System Center 2012 R2 Configuration Manager
|
Windows Vista
- Business Edition (SP2)
- Enterprise Edition (SP2)
- Ultimate Edition (SP2)
|
x86, x64
|
.NET Framework 4 1
|
- System Center 2012 Configuration Manager with no
service pack
- System Center 2012 Configuration Manager with
SP1
- System Center 2012 R2 Configuration Manager
|
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
|
.NET Framework 4 1
|
- System Center 2012 Configuration Manager with no
service pack
- System Center 2012 Configuration Manager with
SP1
- System Center 2012 R2 Configuration Manager
|
Windows 8
|
x86, x64
|
.NET Framework 4.5
|
- System Center 2012 Configuration Manager with
SP1
- System Center 2012 R2 Configuration Manager
|
Windows 8.1
|
x86, x64
|
.NET Framework 4.5
|
- System Center 2012 R2 Configuration
Manager
|
Windows Server 2008
- Standard Edition (SP2)
- Enterprise Edition (SP2)
- Datacenter Edition (SP2)
|
x86, x64
|
.NET Framework 4 1
|
- System Center 2012 Configuration Manager with no
service pack
- System Center 2012 Configuration Manager with
SP1
- System Center 2012 R2 Configuration Manager
|
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
|
.NET Framework 4 1
|
- System Center 2012 Configuration Manager with no
service pack
- System Center 2012 Configuration Manager with
SP1
- System Center 2012 R2 Configuration Manager
|
Windows Server 2012
- Standard Edition
- Datacenter Edition
|
x64
|
.NET Framework 4.5
|
- System Center 2012 Configuration Manager with
SP1
- System Center 2012 R2 Configuration Manager
|
Windows Server 2012 R2
- Standard Edition
- Datacenter Edition
|
x64
|
.NET Framework 4.5
|
- System Center 2012 R2 Configuration Manager
|
1 The Configuration Manager console requires
the full version of the .NET Framework 4 and is not
supported with the .NET Framework Client Profile.
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)
|
DPI setting
|
Minimum resolution
|
96 / 100%
|
1024x768
|
120 /125%
|
1280x960
|
144 / 150%
|
1600x1200
|
196 / 200%
|
2500x1600
|
|
For System Center 2012
Configuration Manager SP1 and
System Center 2012 R2 Configuration Manager
only: Beginning 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
|
- System Center 2012
Configuration Manager SP1
- System Center 2012 R2 Configuration
Manager
|
For information about using a Configuration Manager
console in an environment with multiple versions of Configuration
Manager, see the Interoperability
for the Configuration Manager Console section in the Interoperability between
Different Versions of Configuration Manager topic.