Size and scale numbers for System Center Configuration Manager

Applies to: System Center Configuration Manager (Current Branch)

Each System Center Configuration Manager deployment will have a maximum number of sites, site system roles, and devices that it can support. These numbers vary depending on your hierarchy structure (what types and numbers of sites you use) and the site system roles that you deploy. The information in the following areas can help you identify the number of site system roles and sites that you'll need to support the devices you expect to manage with your environment.

Use the information in this topic in conjunction with the information in the following articles:

The following support numbers are based on using the recommended hardware for Configuration Manager and the default settings for all available Configuration Manager features. When you do not use the recommended hardware, or use more aggressive custom settings (like running hardware or software inventory more frequently than the defaults of once every seven days), the performance of site systems can be degraded and might not meet the stated levels of support.

Site types

Central administration site:

  • A central administration site supports up to 25 child primary sites.

Primary site:

  • Each primary site supports up to 250 secondary sites.

  • 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.

    For information about the number of clients and devices that a primary site can support, see Client numbers for sites and hierarchies in this topic.

Secondary site:

  • Secondary sites don't support child sites.

Site system roles

Application Catalog web service point:

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

    Tip

    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.

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

    • Each instance of this site system role supports the maximum number of clients that are supported by the hierarchy.

Application Catalog website point:

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

    Tip

    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.

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

    • Each instance of this site system role supports the maximum number of clients that are supported by the hierarchy.

Distribution point:

  • Distribution points per site:

    • Each primary and secondary site supports up to 250 distribution points.

    • Each primary and secondary site supports up to 2000 additional distribution points that are configured as pull-distribution points. For example, a single primary site supports 2250 distribution points when 2000 of those distribution points are configured as pull-distribution points.

    • Each distribution point supports connections from up to 4,000 clients.

    • A pull-distribution point acts like a client when it accesses content from a source distribution point.

  • 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 the 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.

Warning

The actual number of clients that one distribution point can support depends on the speed of the network and the hardware configuration of the distribution point computer.

The number of pull-distribution points that one source distribution point can support similarly depends on the speed of the network and the hardware configuration of the source distribution point computer. But this number is also affected by the amount of content that you've deployed. This is because, unlike clients that typically access content at different times during a deployment, all pull-distribution points request content at the same time—and can request all available content, not just the content that is applicable to them, as a client would. When too much of a processing load is placed on a source distribution point, there can be unexpected delays in distributing the content to the expected distribution points in your environment.

Fallback status point:

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

Management point:

  • Each primary site supports up to 15 management points.

    Tip

    Don't install management points on servers that are across a slow link from the primary site server or from the site database server.

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

    For information about the number of clients and devices that a management point can support, see the Management points section in this topic.

Software update point:

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

  • A software update point that is remote from the site server can support up to 150,000 clients when the remote computer meets the Windows Server Update Services (WSUS) requirements to support this number of clients.

  • By default, Configuration Manager doesn't support configuring software update points as Network Load Balancing (NLB) clusters. However, you can use the Configuration Manager SDK to configure up to four software update points on an NLB cluster.

Client numbers for sites and hierarchies

Use the following information to determine how many clients and which types of clients you can support at a site or in a hierarchy.

Hierarchy with a central administration site

A central administration site supports a total number of devices that includes up to the number of devices listed for the following three groups:

  • 700,000 desktops (computers that run Windows, Linux, and UNIX). Also see, support for embedded devices.

  • 25,000 devices that run Mac and Windows CE 7.0

  • One of the following, depending on how your deployment supports mobile device management (MDM):

    • 100,000 devices that you manage by using on-premises MDM

    • 300,000 cloud-based devices

    For example, in a hierarchy, you can support 700,000 desktops, up to 25,000 Mac and Windows CE 7.0, and up to 300,000 cloud-based devices when you integrate Microsoft Intune—for a total of 1,025,000 devices. If you support devices that are managed by on-premises MDM, the total for the hierarchy is 825,000 devices.

Important

In a hierarchy where the central administration site uses a Standard edition of SQL Server, the hierarchy supports a maximum of 50,000 desktops and devices. The edition of SQL Server that is in use at a stand-alone primary site doesn't limit that site's capacity to support up to the stated number of clients.

Child primary site

Each child primary site in a hierarchy with a central administration site supports the following:

  • 150,000 total clients and devices that aren't limited to a specific group or type, as long as support doesn't exceed the number that is supported for the hierarchy. Also see, support for embedded devices.

For example, a primary site that supports 25,000 computers that run Mac and Windows CE 7.0 (because that is the limit for a hierarchy) can then support an additional 125,000 desktop computers. This brings the total number of supported devices up to the child primary site's supported maximum limit of 150,000.

Stand-alone primary site

A stand-alone primary site supports the following number of devices:

  • 175,000 total clients and devices, not to exceed:

    • 150,000 desktops (computers that run Windows, Linux, and UNIX). Also see, support for embedded devices.

    • 25,000 devices that run Mac and Windows CE 7.0

    • One of the following, depending on how your deployment supports mobile device management:

      • 50,000 devices that you manage by using on-premises MDM

      • 150,000 cloud-based devices

For example, a stand-alone primary site that supports 150,000 desktops and 10,000 Mac or Windows CE 7.0 can support only an additional 15,000 devices. Those devices can be either cloud-based or managed by using on-premises MDM.

Primary sites and Windows Embedded devices

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. 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 important note found in the Planning for client deployment to Windows Embedded devices. A primary site supports only 3,000 Windows Embedded devices that have EWF enabled and that are not configured for the exceptions.

Secondary sites

Secondary sites support the following:

  • 15,000 desktops (computers that run Windows, Linux, and UNIX)

Management points

Each management point can support the following number of devices:

  • 25,000 total clients and devices, not to exceed:

    • 25,000 desktops (computers that run Windows, Linux, and UNIX)

    • One of the following (not both):

      • 10,000 devices that are managed by using on-premises MDM

      • 10,000 devices that run Mac and Windows CE 7.0 clients