Setup:

SCCM 2007 Capacity planning

http://blogs.technet.com/b/deploymentguys/archive/2008/05/20/sccm-for-deployment-rough-sizing-
guidelines.aspx

Step1 - The environment

 A working domain

Site Server machine which will host SCCM server roles and most of the site systems roles

SQL server machine

Client machines

SQL server Requirements for sccm 2012

 When installing ConfigMgr 2012 it's important to fulfill all SQL Server requirements. The
following must be configured during installation:

 The instance of SQL Server in use at each site must use the following collation:
SQL_Latin1_General_CP1_CI_AS;

 Only the Database Engine Services feature is required for each site server (Configuration
Manager database replication does not require the SQL Server replication feature);

 Configuration Manager requires Windows authentication to validate connections to the

database;

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

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

 Configuration Manager requires SQL Server to reserve a minimum of 8 gigabytes (GB) of

memory in the buffer pool used by an instance of SQL Server for the central administration site
and primary site and a minimum of 4 gigabytes (GB) for the secondary site;
You must use a dedicated instance of SQL Server for each site, in other words, you
cannot host two Database from two different Site Servers in the same SQL instance, it
could be in the same server though, but in separated instances

SCCM server requirements for 2012

The following table describes Site and Site Role scalability maximums

SCCM 2012 OS requirement

Windows Server 2008 (x64) SP2: SCCM 2012 + SCCM 2012 Sp1

Windows Server 2008 R2 (x64) SP2: SCCM 2012 + SCCM 2012 Sp1

Windows Server 2012 (x64) SP2: SCCM 2012 Sp1

Site/Site Role Item Maximum Value

CAS Total combined clients, when running SQL 400K

Enterprise or Datacenter Edition

Total combined clients, when running SQL 50K

Standard

Primary Maximum Primary Sites per CAS 25

Maximum clients supported per Primary Site 100K

Secondary Site Maximum Secondary Sites per Primary Site 250

Maximum clients supported per Secondary Site 5000

Management Maximum desktop clients supported per MP 25K

Point
Distribution Point – you can have up to 100 DP’s per site. Each DP is capable of supporting 4,000
clients.

CAS/Standalone Primary Site (up to 50,000 clients) w/co-located SQL Serve

· 2 x Quad-Core (Intel Xeon E5504 or comparable)

· 32GB of RAM
· 350GB - 950GB total hard disk space* (OS, ConfigMgr, SiteDB, TempDB)

Primary Site in a hierarchy (up to 25,000 clients) w/co-located SQL

· 2 x Dual-Core (Intel Xeon 5140 or comparable)

· 16GB of RAM
· 450GB - 1050GB total hard disk space* (OS, ConfigMgr, SiteDB, DistDB, TempDB)
Primary Site in a hierarchy (up to 50,000 clients) w/remote SQL Server:
· 2 x Dual-Core (Intel Xeon 5140 or comparable)
· 8GB of RAM
· 50GB total hard disk space* (OS, ConfigMgr)
Remote SQL Server (to support above Primary Site):
· 2 x Quad-Core (Intel Xeon E5504 or comparable)
· 32GB of RAM
· 425GB - 1225GB total hard disk space (OS, SiteDB, DistDB, TempDB)

Management Point:
· 2 x Dual-Core (Intel Xeon 5140 or comparable)
· 8GB of RAM
· 50GB total hard disk space (OS, ConfigMgr)
Distribution Point:
· 1 x Dual-Core (Intel Xeon 5140 or comparable)
· 8GB of RAM
· Disk space at your discretion (OS, Content)
Application Catalog (web service and web site co-located):
· 2 x Dual-Core (Intel Xeon 5140 or comparable)
· 16GB of RAM
· 50GB total hard disk space (OS, ConfigMgr)

Client OS: Windows XP SP3 or higher ( can have sccm 2012 to sccm 2012 sp1 clients)

But Clients running windows 8 or windows server 2012 can have sccm 2012 SP1 client only

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.

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

SQL server versions supported for SCCM 2012

SQL Server 2008

SQL Server 2008 R2

SQL Server 2012

SQL Server Express 2008 R2

SQL Server 2012 Express

===============================

SQL Server ports

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

Management point, SMS Provider computer, Reporting Services point ‘Site server roles uses the default
SQL ports

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

User accounts in SCCM

Network access account: To access resources on the network

Client push account

SQL service account

Domain join account

Step2 - Extend Active Directory Schema

Step3 - System Container creation and Permissions Assignment

Step4 - Site Server Prerequisites

Step5 - SQL Server considerations

Step6 - SCCM 2012 intallation

Client Migration

Client GUID and advertisement history is preserved

Rest of the data will be regenerated like inventory information

Client migration methods

Client push

GPO

Windows Update

Logon Scripts

Manual installation

Migrate clients in batches. One client generates about 4.7 MB of data traffic to sync itself with the CM12

Disabled all advertisements and TS during migration as this will ensure that no user is deploying
anything while migration.

Site to Site communication

Data type Examples Replication Where is data found?

 type

Global Collection rules, SQL Central administration

data package metadata, site, all primary sites,
software update secondary sites (a subset
metadata, of global data is
Deployments replicated here)

Site data Collection SQL Central administration

members, HINV, site, originating primary
alert messages site

Content Software package File-based Primary sites, secondary

installation bits, sites, distribution points
software updates,
boot images

The two types of data that take advantage of the SQL Server Service Broker are:

1. Global data – any data generated by the administrator (e.g. data entered manually from the
administration console)
2. Site data – any data that is generated by the system

Migration

DRS
Important links

http://wibier.me/sccm-2012-sp1-and-sql-server/

http://anoopcnair.com/2012/06/20/sccm-configmgr-2012-site-to-site-replication-sql-data-replication-
service-replication-configuration-management-sql-service-broker-replication-groups-and-manual-sync/

http://technet.microsoft.com/en-us/library/gg712701.aspx#database_replication

http://www.sqlteam.com/article/how-to-troubleshoot-service-broker-problems

http://www.techrepublic.com/blog/datacenter/making-sense-of-microsoft-system-center-licensing/
3047 ( SCCM licensing procedure)

http://blogs.technet.com/b/meacoex/archive/2013/02/19/migrate-windows-xp-to-windows-7-using-
sccm-2012.aspx ( Migrate windows XP to windows 7)

http://www.simple-tech.info/you-receive-an-access-is-denied-error-when-you-want-to-connect-a-
remote-computer-or-server-with-wmi-and-use-specific-user-credentials-number-0x80070005-access-is-
denied.aspx ( Fix WMI on the clients and servers)

http://schadda.blogspot.in/2012/02/sccm-2012-deploy-multiple-applications.html

Deploy multiple applications in SCCM 2012

====================================================

SCCM design consideration

ConfigMgr 2012 / SCCM 2012 Design Considerations

Back to ConfigMgr 2012 menu
Central Administration Site

 A central administration site can support up to 25 child primary sites

 When you use SQL Server Enterprise or Datacenter for the site database at the central
administration site, the shared database and hierarchy supports up to 400,000 clients
 In most cases a CAS is not required. You only need a CAS if:
o you REQUIRE more than one Primary Site
o you have over 100,000 clients

Primary Site

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

 Each primary site management point can support up to 25,000 computer clients. To
support 100,000 clients you must have at least four management points. Each primary
site can support up to 10 management points
 Each primary site can support up to 250 secondary sites

Primary Site Server (local or remote SQL)

 Microsoft support both scenarios and do not care where SQL is installed. However most
ConfigMgr consultants will tell you to install SQL locally. You have more control and your
solution will be less problematic.
 Also the ConfigMgr Primary Site Server computer account must be local administrator
and Sysadmin for the SQL instance. This is a hard sell for most DBAs in a shared SQL
environment.

Secondary Site
  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
 Each secondary site supports a single management point that must be installed on the
secondary site server.
 Maximum number of clients in 5,000

Distribution Point

 Individually, each primary site supports up to 250 distribution points and each distribution
point can support up to 4,000 clients.
 Individually, each secondary site supports up to 250 distribution points and each
distribution point can support up to the same number of clients as supported by the
hardware configuration of the secondary site server, up to no more than 4,000 clients.
 Each primary site supports a combined total of up to 5,000 distribution points. This total
includes all the distribution points at the primary site and all distribution points that
belong to the primary site’s child secondary sites.
 Each distribution point supports a combined total of up to 10,000 packages and
applications.

Boundaries
Best practice is to use IP Ranges

High Availability

 ConfigMgr is not a real-time service like Exchange or SharePoint. It has not been
designed to be "highly available" (even though you can introduce a certain amount of
redundancy by deploying additional management points). It is more useful that you
implement a backup strategy (with regular test restores) so that you can recover a failed
site in an acceptable time-frame.
 Note that ConfigMgr 2012 supports full recovery via SQL backup alone.
