Site and Site System Role Scalability
Hi Guys,
Today i will talk about Site and Site System Scalability .Both are very important factors in Configuration Manager.
Site
A site consists of a site server, site system roles, clients, and resources. A site always requires access to a Microsoft SQL Server database. There are several types of SCCM sites. A SCCM site uses boundaries to determine the clients belonging to the site. Multiple sites can be configured into site hierarchies and connected such that you can manage bandwidth utilization between sites. A SCCM site is identified by the three-character code and the friendly site name configured during Setup
Site
Server: The site server is the computer on which you install
Configuration Manager 2007 or 2012, and it hosts services required for
Configuration Manager.
Site
system: A site
system is any
computer running a supported version of Microsoft Windows or a shared folder
that hosts one or more site
system roles.
Site
system Role: A site
system role is a function required to be able to use Configuration Manager or to use a feature of Configuration Manager.
The following table contains information about the support limits
at each site type and by each client-facing site system role. This information
is based on the recommended hardware for site systems.
For more information read on TechNet
Site or site system
role
|
More information
|
Central
administration site
|
·
A central administration site can support up
to 25 child primary sites.
·
When using SQL Server Enterprise or
Datacenter for the site database at the central administration site, the
shared database and hierarchy supports up to 400,000 clients. The maximum
number of supported clients per hierarchy depends on the SQL Server edition
in the central administration site, and is independent of the SQL Server
edition at primary or secondary sites.
·
When you use SQL Server Standard for the
site database at the central administration site, the shared database and
hierarchy supports up to 50,000 clients. This is because of how the database
is partitioned. After you install Configuration Manager, if you then upgrade
the edition of SQL Server at the central administration site from Standard to
Enterprise or Datacenter, the database does not repartition and this
limitation remains.
|
Primary
site
|
·
Each primary site can support up to 250
secondary sites.
·
A stand-alone primary site always supports up
to 100,000 clients.
·
A Configuration Manager SP1 primary site
supports up to 10,000 Windows Embedded devices that have File-Based Write
Filters (FBWF) enabled when they are configured for the exceptions listed in
the Deploying the Configuration Manager Client to Windows Embedded
Devices section
in the Introduction to Client Deployment in Configuration Manager topic. Otherwise, all other configurations for
write filter-enabled embedded devices limit support to 3,000 embedded devices
for a primary site. When write filters are not enabled, the standard number
of clients are supported.
·
A Configuration Manager SP1 primary site
supports up to 50,000 Mac computers.
·
A child primary site that uses SQL Server
installed on the same computer as the site server can support up to 50,000
clients. When you use SQL Server that is installed on a computer that is
remote from the site server, the child primary site can support up to 100,000
clients.
·
Unlike a central administration site, the
edition of SQL Server you use for the primary site database does not
affect the maximum number of clients the primary site supports. This is true
for both child primary sites, and stand-alone primary sites.
|
Secondary
site
|
·
Each secondary site can support communications
from up to 5,000 clients when you use a secondary site server computer with
the recommended hardware and that has a fast and reliable network connection
to its primary parent site. A secondary site might be able to support
communications from additional clients when its hardware configuration
exceeds the recommended hardware configuration.
For information about the recommended hardware for Configuration Manager sites, see Planning for Hardware Configurations for Configuration Manager. |
Comments
Post a Comment