IPD - Configuration Manager 2007

8/7/2019 IPD - Configuration Manager 2007

1/19

Microsoft System Center ConfigurationManager 2007 SP1 with R2

Infrastructure Planning and Design Series


2/19

What Is IPD?

Planning and design guidance that aims to clarify andstreamline the planning and design process for Microsoft

infrastructure technologies

IPD:

Defines decision flow Describes decisions to be made Relates decisions and options for the business Frames additional questions for business understanding

Page 2 |


3/19

MICROSOFT SYSTEM CENTER CONFIGURATION MANAGER 2007 SP1 WITH R2

G etting Started

Page 3 |


4/19

Purpose and Agenda

PurposeTo assist in the decision process to plan a successfulMicrosoft System Center Configuration Manager SP1with R2 implementation

AgendaDefine the project scopeDetermine which roles will be deployedDetermine the number of sites required

Design the sitesDetermine the number of hierarchies requiredDesign each hierarchy

Page 4 |


5/19

What Is Microsoft System Center

Configuration Manager 2007 SP1 with R2?Microsoft System Center Configuration Manager (ConfigMgr) 2007 SP1 with R2 is a configurationmanagement solution that:

Contributes to a more effective IT department by enablingsecure and scalable operating system and applicationdeployment and desired configuration management.

Provides comprehensive asset management of servers,desktops, and mobile devices.

Page 5 |


6/19

Applicable ScenariosThe guide addresses the needs of:

Organizations with no configuration management solution that want to useConfigMgr.

Organizations that presently use another configuration managementsolution and are planning to move to ConfigMgr.

Organizations with multi-forest environments where ConfigMgr will beemployed to manage systems that span Active Directory forest

boundaries.

Organizations that have distributed environments with systems separatedby wide area network (WAN) links.

Organizations with mobile devices, such as smartphones, that operatebeyond firewalls but must be managed centrally.

Page 6 |


7/19

Ex ample of ConfigMgr Architecture

Page 7 |


8/19

ConfigMgr Design Flow

Page 8 |


9/19

Step 1. Define Project Scope

Answer the following questions to align goals with business

motivation:

Will project encompass entire enterprise? Which features will project address? What is the client population to be managed? What are the organizations service e x pectations?

Page 9 |

1 2 3 4 5 6


10/19

Step 2. Determine Which Roles Will Be

Deployed

Page 10 |

E stablishing which site roles are required and where they are

located determines site design and sizing, network sizing, and

if the ConfigMgr client will be deployed.

1 2 3 4 5 6


11/19

Step 3. Determine the Number of Sites

RequiredStart with one site, and then add more as required by the following: Scale Privacy concerns Internet-connected clients Active Directory forests Network location International languages Organization

Page 11 |

1 2 3 4 5 6


12/19

Step 4. Design the Sites

Task 1: Plan the roles that are always required Task 2: Plan the roles that are optional Task 3: Plan the roles that are feature-specific Task 4: Determine where to place hierarchy roles Task 5: Determine where to place primary and secondary

sites and branch distribution points

Task 6: Determine if native mode is required the twooptions are native mode and mi x ed mode

Page 12 |

1 2 3 4 5 6


13/19

Step 4, Task 6. Option 1: Native Mode

Page 13 |

B enefits:

Higher level of security by integrating with a public key infrastructure (PKI)

to help protect client-to-server communication.

E nables the management of clients that are connected to the Internet, such

as laptops used by mobile workers, computers used from an employees

home, and smartphones.

Challenges:

PKI infrastructure is required.

E stimated native mode site operations are 10-15 percent slower in overall

performance compared to sites configured to operate in mi x ed mode due to

added load of encryption and signing.

Cannot interoperate with SMS 2003.

All parent locations up to and including the central site must be in native

mode.1 2 3 4 5 6


14/19

Step 4. Task 6. Option 2: Mi x ed Mode

Page 14 |

B enefit:

E nables integration with SMS 2003.

Challenge:

Additional design may be required to ensure the security of connections beyond the organizations firewalls.

1 2 3 4 5 6


15/19

Step 4. Design the Sites - continued

Task 7: Assign Clients to Sites

Task 8: Design boundaries of protected distribution point systems

Task 9: Design the site systems

Task 10: Determine the Fault-Tolerance Approach

Page 15 |

1 2 3 4 5 6


16/19

Step 5. Determine Number of Hierarchies

RequiredStart with one hierarchy and add more, if required.

Some possible scenarios requiring additional hierarchy are:

Size Central site is mi x ed mode and native mode is required Isolated networks Politics Regulatory requirements

Page 16 |

1 2 3 4 5 6


17/19

Step 6. Design E ach Hierarchy Task 1: Determine where to place central site Task 2: Plan the site hierarchy

Page 17 |

1 2 3 4 5 6


18/19

Summary and ConclusionThe guide summarized the critical design decisions, activities,

and tasks required to enable a successful design of ConfigMgr.

It focused on decisions involving:

Which ConfigMgr roles will be required The server roles, role placement, databases, and

connectivity of the ConfigMgr infrastructure

The number of ConfigMgr hierarchies required, and howmany sites are required within each hierarchy

Provide feedback to [email protected]

Page 18 |


19/19

Date post:	08-Apr-2018
Category:	Documents
Upload:	orbati6290
View:	225 times
Download:	0 times

IPD - Configuration Manager 2007

Documents