Before
start writing up a design document for a proposed System Center Current Branch
deployment, review the changes in current Branch from its successors. Get the
numbers correct for the devices that needs to be managed, network tropology
along with geographical locations of the organization specially if you are part
of multi tired global organization.
A quick
summary of the System Center Current Branch (1511) and supported client and
site numbers;
Hierarchy - Supported Client numbers:
Hierarchy with CAS:
•700,000 desktops
(computers that run Windows, Linux and UNIX)
Child primary site attached to the CAS;
Each child primary site in
a hierarchy with a central administration site supports 150,000 total clients
and devices, not limited to a specific group or type, so as long as support
does not exceed the number supported for the hierarchy
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)
◦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 you manage with On-Premises MDM
◾ 150,000 cloud-based devices
Secondary sites:
Secondary sites support
15,000 desktops (computers that run Windows, Linux and UNIX)
Management points:
Each management 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 managed using On-Premises MDM
◾ 10,000 devices that run Mac and Windows CE 7.0
Hierarchy – Supported site
numbers:
CAS:
·
Supports up to 25 child primary sites
Primary site:
·
Supports up to 250 secondary sites
Secondary Site:
·
Secondary sites do not support child sites
Based on
the requirements, determine the hierarchy design and configuration. A quick
summary of various site system roles, best practices and limitations;
Application Catalog website
point:
·
You can install multiple instances of the Application Catalog website
point at primary sites
·
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 supported by the hierarchy
Application Catalog web
service point:
·
You can install multiple instances of the Application Catalog web
service point at primary sites
·
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 supported by the hierarchy
Asset Intelligence
synchronization point:
- A site system role that
connects to Microsoft to download information for the Asset Intelligence
- A hierarchy supports only
a single instance of Asset Intelligence synchronization point
- Asset Intelligence
synchronization point must be at the top-tier site of your hierarchy (A central
administration site or the stand-alone primary site).
Distribution points per
site:
- Each primary and secondary site supports up
to 250 distribution points.
- Each distribution point supports connections
from up to 4,000 clients.
·
By default, distribution point
role installs on the site server computer of new primary and secondary sites
·
Each primary site supports a combined total of up to 5,000 distribution
points. This total includes all the distribution points at the primary site and
all distribution points that belong to the primary site’s child secondary
sites.
·
Each distribution point supports a combined total of up to 10,000
packages and applications.
Endpoint Protection point:
- A hierarchy supports only
a single instance of this role
- must be at the top-tier
site of your hierarchy
- must be licensed to use
Endpoint Protection to manage clients
Enrollment point:
- Role manages PKI certificates for
Configuration Manager to enroll mobile devices and Mac computers
- Can install multiple
instances of Enrollment Point role at a site, or at multiple sites in the same
hierarchy
Fallback status point:
- Each Fallback status
point can support up to 100,000 clients
·
Can be installed multiple instances of this role at a site
Management point
- Each primary site supports up to 15 management points
·
Do not 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
Service connection point:
- A hierarchy supports only a
single instance of this role
·
Must be installed at the top-tier site of the hierarchy
·
Integrates with MS Intune
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 WSUS requirements to support this number of clients
·
By default, Configuration Manager does not support configuring software
update points as NLB clusters. However, you can use the Configuration Manager
SDK to configure up to four software update points on a NLB cluster
Click here
for complete SCCM 1511 Current Branch step by step guide, step by step migration
guide, step by step monitoring and health check guide and step by step SCCM
current branch servicing guide
No comments:
Post a Comment