CM12R2 Design Arch Partial Sample

Author: James Donnelly

Garth Jones

Issue Date: March 2014

Document Version: 14.0

Document Status: Complete

System Center 2012 R2 Configuration Manager

(CM12R2)

CM12R2 Conceptual Architecture

Before printing think about the environment Avant l'impression, il faut penser à l'environnement

Unclassified

SYSTEM CENTER 2012 R2 CONFIGURATION MANAGER (CM12R2)

March 2014 Page 1

Table of Contents

1 EXECUTIVE SUMMARY ...........................................................................................................................4

1.1 NOTICE TO READER ........................................................................................................................................ 4 1.2 PROJECT BUSINESS CONSIDERATIONS CHARACTERISTICS [NON-TECHNICAL] ............................................................... 4 1.3 BUSINESS DRIVERS & FUNCTIONAL REQUIREMENTS ............................................................................................. 4

2 PROJECT OBJECTIVES ..............................................................................................................................5

2.1 SCOPE AND CONDITIONS ................................................................................................................................. 5 2.2 ASSUMPTIONS .............................................................................................................................................. 6

2.2.1 Replacement of ConfigMgr 2007 ................................................................................................... 6 2.2.2 Networking Environment ............................................................................................................... 6 2.2.3 Application deployment ................................................................................................................. 6 2.2.4 AD / Workstations .......................................................................................................................... 6

2.3 RISKS .......................................................................................................................................................... 7

3 EXISTING ENVIRONMENT .......................................................................................................................8

3.1 SYSTEM MANAGEMENT ENVIRONMENT ............................................................................................................. 8 3.2 NETWORK .................................................................................................................................................... 8 3.3 DISTRIBUTION SERVER SPECS .......................................................................................................................... 8 3.4 SITE PROFILES SORTED BY NUMBER OF USERS ...................................................................................................... 8 3.5 LOGICAL LAYOUT OF CURRENT CLIENT CONFGMGR 2007 SITES THAT HAVE DP ....................................................... 11

4 PROPOSED CM12R2 DESIGN ................................................................................................................ 12

4.1 RECOMMENDATIONS ................................................................................................................................... 12 4.2 BACKUPS ...................................................................................................... ERROR! BOOKMARK NOT DEFINED. 4.3 CONFIGURATIONS ........................................................................................... ERROR! BOOKMARK NOT DEFINED. 4.4 FREE 3RD PARTY TOOLS .................................................................................... ERROR! BOOKMARK NOT DEFINED. 4.5 CLIENT AGENT ............................................................................................... ERROR! BOOKMARK NOT DEFINED.

5 MIGRATION STRATEGY .................................................................... ERROR! BOOKMARK NOT DEFINED.

5.1 CLIENT AGENT INSTALL ..................................................................................... ERROR! BOOKMARK NOT DEFINED. 5.2 HARDWARE SPECIFICATIONS ............................................................................. ERROR! BOOKMARK NOT DEFINED. 5.3 ESTIMATED DISK SPACE ................................................................................... ERROR! BOOKMARK NOT DEFINED. 5.4 VIRTUAL SERVERS ........................................................................................... ERROR! BOOKMARK NOT DEFINED. 5.5 SOFTWARE SPECIFICATIONS .............................................................................. ERROR! BOOKMARK NOT DEFINED. 5.6 SQL SERVER .................................................................................................. ERROR! BOOKMARK NOT DEFINED. 5.7 SITES ............................................................................................................ ERROR! BOOKMARK NOT DEFINED. 5.8 LOGICAL LAYOUT OF PROPOSED CM12R2 DESIGN (WITHOUT NOMAD) .................. ERROR! BOOKMARK NOT DEFINED. 5.9 PROPOSED CM12R2 PROPOSED SITE LIST (WITHOUT NOMAD) .............................. ERROR! BOOKMARK NOT DEFINED. 5.10 LOGICAL LAYOUT OF PROPOSED CM12R2 DESIGN (WITH NOMAD) .................. ERROR! BOOKMARK NOT DEFINED. 5.11 PROPOSED CM12R2 PROPOSED SITE LIST (WITH NOMAD) ............................... ERROR! BOOKMARK NOT DEFINED.

6 CM12R2 IMPLEMENTATION COSTS AND TIMELINE.......................... ERROR! BOOKMARK NOT DEFINED.

6.1 SUGGESTED TRAINING ..................................................................................... ERROR! BOOKMARK NOT DEFINED. 6.1.1 General Training .............................................................................. Error! Bookmark not defined. 6.1.2 Advanced Training ........................................................................... Error! Bookmark not defined.

Unclassified


March 2014 Page 2

7 CM12R2 IMPLEMENTATION COSTS AND TIMELINE INCLUDING 1E NOMAD .... ERROR! BOOKMARK NOT DEFINED.

7.1 SUGGESTED TRAINING ..................................................................................... ERROR! BOOKMARK NOT DEFINED. 7.1.1 General Training .............................................................................. Error! Bookmark not defined. 7.1.2 Advanced Training ........................................................................... Error! Bookmark not defined. 7.1.3 1E Training ....................................................................................... Error! Bookmark not defined.

8 TECHNICAL REFERENCE FOR PORTS USED IN CONFIGURATION MANAGER ..... ERROR! BOOKMARK NOT DEFINED.

9 DMZ SUPPORT .................................................................................. ERROR! BOOKMARK NOT DEFINED.

10 IMAGING DEPOTS ............................................................................ ERROR! BOOKMARK NOT DEFINED.

11 APPENDIX ......................................................................................... ERROR! BOOKMARK NOT DEFINED.

11.1 WINDOWS SOFTWARE UPDATE SERVER ........................................................ ERROR! BOOKMARK NOT DEFINED. 11.2 DETECTION AND REPORTING ........................................................................ ERROR! BOOKMARK NOT DEFINED. 11.3 UPDATE CLASSIFICATIONS ........................................................................... ERROR! BOOKMARK NOT DEFINED. 11.4 PRODUCTS ............................................................................................... ERROR! BOOKMARK NOT DEFINED. 11.5 LANGUAGES ............................................................................................. ERROR! BOOKMARK NOT DEFINED. 11.6 3RD PARTY ................................................................................................ ERROR! BOOKMARK NOT DEFINED. 11.7 DEPLOYMENT OF SOFTWARE UPDATES ........................................................... ERROR! BOOKMARK NOT DEFINED.

12 GLOSSARY ........................................................................................ ERROR! BOOKMARK NOT DEFINED.

Unclassified


March 2014 Page 3

Document Change Log

Version Revision

Date

Summary of Change Change Author

0.01 18-03-14 Initial Draft Garth Jones

James Donnelly

0.14 29-03-14 All subsequent edits and roll-up of all changes for final

version submitted to client

James Donnelly

0.15 13-08-15 Various edits and scrubbing of client names James Donnelly

Garth Jones can be reached at [email protected]

James Donnelly can be reached at [email protected]

mailto:[email protected]


Unclassified


March 2014 Page 4

1 Executive Summary

This document has been scrubbed to replace the client name, names of client teams, servers

and locations with <name removed> in order to keep all that confidential.

The client <name removed> is currently using ConfigMgr 2007 to manage patching and

other imaging tasks within the department. ConfigMgr 2007 will be at end of main stream

support in July 2014 and the client needs to quickly move to CM12R2 to ensure there is no

extended gap in patching capability.

There have been on-going issues with the existing ConfigMgr 2007 environment over

several months, including corruption within the databases. This has led to a decrease in

functionally. As a stop gap measure, a new ConfigMgr 2007 environment is being built to

allow for Software Update Management.

1.1 Notice to Reader

Microsoft System Center Configuration Manager 2012’s official acronym is ConfigMgr.

However, in many circles, the acronyms SCCM and CM12 are used. Since the client will

be deploying System Center Configuration Manager 2012 R2 we will attempt to use

CM12R2 throughout this document.

1.2 Project business considerations characteristics [non-technical]

This section establishes the non-technical characteristics of the CM12R2 deployment project

that are essential in providing guidance to the technical solutions and the project execution

management requirements.

1.3 Business Drivers & Functional Requirements

The report contains conceptual level of detail. The primary focus of this report is infrastructure,

the business, data and application architecture discovery was considered only to drive the

infrastructure requirements.

There are two business requirements for the CM12R2 deployment project

CM12R2 is necessary in order to receive continued main stream vendor support

Re-establish the software patching, management and inventory provided by ConfigMgr

2007.

Unclassified


March 2014 Page 5

2 Project Objectives

The purpose of this project is to replace the current ConfigMgr 2007 with CM12R2.

ConfigMgr 2007 will not receive main stream vendor support as of July 2014.

2.1 Scope and conditions

1. This document discusses high-level designs and approach only. In-depth details will

be described in the engineering and build documents. The decision to implement

CM12R2 has already been made; this guide does not address the business or

technical cases to use CM12R2.

2. The reader has familiarity with the Microsoft infrastructure, AD Directory Services

and ConfigMgr 2007 / CM12R2. This document does not attempt to educate the

reader on the features and capabilities of Microsoft products. The product

documentation covers that information.

3. This document proposes a design of the new CM12R2 environment to address the

following technical requirements:

a. Implement Software Update Deployments

b. Simplify the environment where possible

4. This document will not address administrative roles and responsibilities to be used

by the different support groups. Policies are to be separately defined by the

Business.

Unclassified


March 2014 Page 6

2.2 Assumptions

2.2.1 Replacement of ConfigMgr 2007

The new Software Updates (SU) strategy will use CM12R2 for deployment

Windows Software Update Services (WSUS will be integrated with CM12R2 for

SU)

The implementation of CM12R2 will align with the mandate of the <name

removed> Desktop team standards

Active Directory (AD) schema has already been extended to include the schema

needed by CM12R2

Due to Service Level Agreements of CM12R2, Backup Contingency Plans and

Disaster Recovery Plans are not required

2.2.2 Networking Environment

The use of IP super-netting is NOT used

The client uses multiple AD sites (shown in point 3.3 below)

There are no overlapping IP boundaries

LAN speeds within a physical site are 100MB or better to the desktop

<NAME REMOVED> MAN sites are a minimum of 100 MB connection.

In the past, there have been no deployments that have caused networking issues

There are no intentions to increase bandwidth to remote site

All network devices can use DNS to resolve Windows servers. For example all

Windows XP PCs and communicate with Windows servers using FQDN

2.2.3 Application deployment

Existing ConfigMgr 2007 Package source is roughly 100GB in size

There are roughly 100 packages in ConfigMgr 2007

It is expected that these packages will be moved to CM12R2

2.2.4 AD / Workstations

If needed, existing Windows XP workstations will be managed by CM12R2

The majority of workstations are Windows 7 SP1

All Windows 7 workstation are within the AD Domains

Unclassified


March 2014 Page 7

2.3 Risks

Delays may be caused to this project due to some of the other projects currently

under way.

For the design phase of the project there is a relatively short time line with a due date

of March 31, 2014

If the existing desktop engineering teams became Microsoft trained and certified on

the existing infrastructure tools being implemented, would be a benefit.

Unclassified


March 2014 Page 8

3 EXISTING ENVIRONMENT

3.1 System Management environment

This section will provide an overview of the existing ConfigMgr 2007 environment. This

will support the proposed architecture as well as provide rationale towards the design

decisions of the current ConfigMgr 2007 environment.

3.2 Network

All network link speeds have been gathered from various sources.

3.3 Distribution Server Specs

There is a mix of servers that are used for distribution point within the client environment.

Below is a highlight of some of the servers that the client is using for DP.

Type CPU Ram

Site Server Dual 1.87GhZ 16GB *VM

DP Type 1 Quad 3Ghz 4GB

DP Type 2 Dual 2.66 GHz 4GB

DP Type 3 Dual 2.4 GHz 12GB

DP Type 4 Single 2.8 GHz 4GB *32bit

3.4 Site profiles sorted by number of users

This table includes number of users, bandwidth and existing distribution points for

ConfigMgr 2007.

Region\City Existing Site Number of PCs

Bandwidth (Mbps) Primary

Distribution Point

<name removed> <name removed> 1896 250 <name removed>



Unclassified


March 2014 Page 9



Distribution Point











<name removed> <name removed> 199 <name removed>















Quebec <name removed> 34 10 <name removed>












Unclassified


March 2014 Page 10



Distribution Point





CMC <name removed> 4 2 <name removed>


CMC <name removed> 2 <name removed>





Unclassified


March 2014 Page 11

3.5 Logical layout of current client ConfgMgr 2007 sites that have DP

<name removed><name removed><name removed>

CNTSCCM-EC-W01

SCCM 2007

Legend

= Fallback Status Point

= Protected Distribution Point

= Configuration Manager DatabaseConfigMgr

DB

= Primary Site Server

= Secondary Site Server

<name removed> <name removed> <name removed><name removed>

<name removed>

<name removed>

<name removed>

<name removed>

<name removed>

<name removed><name removed>

<name removed> <name removed><name removed>

<name removed>

<name removed>

<name removed>

<name removed> <name removed>

<name removed> <name removed>

<name removed>

<name removed>

<name removed>

<name removed>

<name removed>

<name removed>

<name removed>

<name removed>

<name removed>

<name removed>

Unclassified


March 2014 Page 12

4 PROPOSED CM12R2 Design

4.1 Recommendations

The following recommendations are being made following the review of the existing infrastructure:

1. Windows 2012 R2 will be used on all primary and secondary servers. Some of the reasons for this decision are:

a. To leverage the Branch Cache technology.

b. Primary site servers can be difficult to upgrade

2. x64 bit server OS and software will be used where software is possible.

3. SQL 2012 will be used with the primary server and installed locally

a. Better performance

b. Support for SQL Server Reporting Services

4. There will only be one Fallback Status Point (FSP) and it will be hosted on a virtual server.

5. All workstations within the domains and will have the CM12R2 client installed

6. Discovery options

a. AD discovery will be used to select only Windows 7 workstations that have been logged onto within the

last 90 days

b. An existing account called “SCCM push” will be used to install the CM12R2 client on workstations

7. Primary site

a. All class “B” sites will report to the Primary Site

b. All management tasks will take place on the Primary Site

i. Creating applications and deployment

ii. Creating software update packages, SU groups and Deployment

iii. Creating packages, programs and deployment

iv. Create collections, software metering rules, compliance settings

v. Publishing of reports

vi. Asset Intelligent synchronization

vii. Software Update synchronization (WSUS)

c. Host the FSP

8. All class “B” sites will be secondary site servers. Some of the reasons for this decision are:

The rest of this document has been removed in the hopes that you will contact James Donnelly at

[email protected] for the complete document.


CM12R2 Design Arch Partial Sample

Documents

Transcript of CM12R2 Design Arch Partial Sample