Export (0) Print
Expand All

Sample Plan

This section includes a basic, sample deployment plan for a particular scenario. Although the scenario is fictitious, it is designed to give the reader an idea of how to document the plan at a high level. The rest of this chapter describes in detail the decisions you must make when devising your plan. This sample deployment plan is primarily designed to show you how to create a high level plan for deploying and configuring SMS. It is not designed to replace your customized plan.

This sample deployment plan is for a large organization called Contoso Pharmaceuticals that has 20,000 newly installed client computers in one central location. All of these clients are in one Active Directory site. Contoso's Active Directory infrastructure uses only one Active Directory forest. Contoso has three other locations in different geographic regions. Each location is in its own Active Directory site and is connected to the central location's network by a 1.5 Mbps T1 link.

Contoso's IT department is divided into two administrative areas. One IT group is responsible for supporting computers at headquarters, and the other supports computers at the remote offices. The company is planning for significant future growth, both at its headquarters and in remote locations. Based on this divided management scope, the decision is made to create one administrative SMS site that directly manages all the desktop computers at headquarters, and another SMS site that manages the computers at all remote branch offices.

After thorough planning, Contoso's IT department might create and document a high level SMS site and client deployment plan like the one shown in the following worksheet. Central headquarters has three primary sites: one for the secondary sites to report to, another to assign local Advanced Clients to, and one to be the central site for reporting. The clients at the secondary sites are required to run the Legacy Client. Contoso's IT department creates a document similar to this:

Figure 10.1: Sample high-level SMS 2003 deployment and configuration plan

Figure 10.1: Sample high-level SMS 2003 deployment and configuration plan

High Level SMS Deployment and Configuration Plan at Contoso Pharmaceuticals

  1. Install an SMS primary site server at headquarters. Use site code A01. Use this site for administrative purposes only, like reporting and gathering status. Perform the following tasks at site A01:F

    ____ Remove existing SMS site boundaries to prevent client installations.

    ____ Configure SMS object permissions.

    ____ Configure maintenance tasks, alerts, and status system.

    ____ Lock down and configure Internet Information Services (IIS) for SMS reporting.

    ____ Set up the reporting point.

  2. Using the SMS Administrator console at primary site A01, install secondary sites at each of the three remote offices. Use site codes A02, A03, and A04. Perform the following tasks as each secondary site is installed:

    ____ Configure SMS object permissions.

    ____ Configure maintenance tasks, alerts, and status system.

    ____ Configure site communications (senders and addresses).

    ____ Add a CAP and a distribution point to each secondary site server.

    ____ Configure the secondary site with site boundaries.

    ____ Configure a discovery method at the secondary site.

    ____ Use Client Push Installation to install the SMS Legacy Client on each computer assigned to a secondary site.

  3. Install another SMS primary site server at headquarters. Use site code B01. Perform the same tasks listed in step 1. Then perform the following tasks at this primary site:

    ____ Add a management point and distribution points to the site.

    ____ Configure SMS site boundaries.

    ____ Enable Active Directory System Discovery but not SMS client installation.

  4. Install another SMS primary site server at headquarters. Use site code C01. This will become the central site. Then:

    ____ Perform the same tasks listed in step 1.

    ____ Install a server locator point at site C01.

  5. Complete the hierarchy:

    ____ Configure site communications (senders and addresses) as needed.

    ____ Attach sites A01 and B01 each to their parent central site CO1.

    ____ Create queries in site B01 to divide your clients up into collections.

    ____ Use the Client Push Installation Wizard to install the Advanced Client one collection at a time in site B01.

The final project deployment plan that Contoso creates is much more detailed than the high level plan displayed in this worksheet. The final project plan includes all the details created in the project plans for hierarchy design, security strategy, backup and recovery, site and client deployment, and configuration.

After Contoso administrators have deployed the SMS hierarchy, they enable SMS features, one at a time, at each SMS site. As they enable each feature, they monitor it and test it before enabling another feature.

Contoso is careful to verify the integrity of the SMS hierarchy at each step, even as they are testing their deployment plan in the test lab and pilot project. For example, the site systems for the planned hierarchy are put in place, and the integrity of the SMS hierarchy is confirmed before any site boundaries are configured or clients installed.

For other deployment scenarios, see Chapter 1, "Scenarios and Procedures for Deploying SMS 2003," in the Microsoft Systems Management Server 2003 Operations Guide.

For More Information

Did you find this information useful? Please send your suggestions and comments about the documentation to smsdocs@microsoft.com.

Was this page helpful?
(1500 characters remaining)
Thank you for your feedback
© 2014 Microsoft