Configuration Manager 2012 Implementation and Administration
- Sample Organization
- Configuring Installation Prerequisites
- Implementing the Central Administration Site
- Deploying the Primary Sites
- Deploying the Secondary Sites
- Configuring the Hierarchy
- Configuring Sites
- Configuring Client Settings
- Implementing Internet-Based Client Management
- Summary
- Best Practices
This chapter is from the book
This chapter is from the book
This chapter is from the book
System Center Configuration Manager (ConfigMgr) 2012 helps reduce the cost of managing the Windows infrastructure by providing scalable, secure, end-to-end administration and reporting functionality for the enterprise. It is important to fully understand the architectural design before Configuration Manager 2012 infrastructure servers and roles are deployed.
This chapter walks through the steps necessary to deploy, configure, and administer key Configuration Manager 2012 functionality. This functionality includes deploying and administering the roles and features needed to enable operating system deployment, systems configuration management, patch management, software provisioning, asset management, and reporting.
Sample Organization
To illustrate the implementation and administration of Configuration Manager 2012, a multilocation sample organization named Company XYZ will be used. This will provide a backdrop of reality against which the Configuration Manager 2012 design can be developed.
Existing Environment
Company XYZ is headquartered in San Francisco with offices in Paris, London, Tokyo, and New York City. The company has over 3,000 employees distributed primarily between San Francisco and Paris. London and Tokyo are medium-sized branch offices. Finally, the New York office is a very small office with only a handful of employees.
There is a network connection between the San Francisco and Paris offices. London and Tokyo connect to the Paris office. New York is connected to the separate San Francisco office. Figure 3.1shows the corporate wide area network (WAN) topology.
)
Figure 3.1 Company XYZ WAN topology.
The company has a single Active Directory forest and domain. The domain name is companyxyz.com and has a domain controller DC1. Each office has its own Active Directory site in the Active Directory site topology. Table 3.1 summaries the location information.
Table 3.1 Company XYZ Location Information
|
Location |
AD Site |
Network |
Users |
|
San Francisco |
SFO |
10.1.x.x |
2,000 |
|
Paris |
PAR |
10.4.x.x |
1,000 |
|
London |
LON |
10.2.x.x |
100 |
|
Tokyo |
TOK |
10.5.x.x |
100 |
|
New York |
NYC |
10.3.x.x |
5 |
The San Francisco office has the central IT organization that covers the entire Company XYZ organization, but the Paris office also has a smaller IT organization that covers the Paris, London, and Tokyo locations. The Paris office has significant autonomy and needs administrative control over its infrastructure due to regulatory concerns.
This information will be used to inform the Configuration Manager 2012 design.
Developing a Configuration Manager 2012 Design
Based on the Company XYZ existing environment, the recommendation would be to have a Primary Site Server in San Francisco and a Primary Site Server in Paris based on the local IT presence and the requirement for local administrative control. The recommendation would be to place Secondary Site Servers in London and Tokyo based on the size of the offices. Given the small size of the New York office with only five users, no servers will be placed there.
Table 3.2 summarizes the locations, server roles, and server names needed for the infrastructure.
Table 3.2 Company XYZ Configuration Manager 2012 Design
|
Location |
SCCM Site |
Site Code |
Server Name |
|
San Francisco |
Central Administration Site |
XYZ |
CM1 |
|
Primary Site |
SFO |
CM2 |
|
|
Paris |
Primary Site |
PAR |
CM3 |
|
London |
Secondary Site |
LON |
CM4 |
|
Tokyo |
Secondary Site |
TOK |
CM5 |
|
New York |
NYC |
Figure 3.2 shows a diagram of the recommended Configuration Manager 2012 infrastructure.
)
Figure 3.2 The Company XYZ ConfigMgr 2012 design.
The balance of this chapter implements and configures the Configuration Manager 2012 design for Company XYZ.