Preparing Site Servers

Wide World Importers’ Midwest Development Center administrators used these procedures to prepare their site servers because some of their clients are using the Macintosh operating system. Their site hierarchy will contain both SMS 2.0 and SMS 1.2, Service Pack 4 site servers when they are finished.

First, the administrators reconfigured SMS 1.2 client settings by using the “To disable automatic component starts and Remote Control in SMS 1.2” procedure described earlier in this chapter. Next, they prepared their site servers by using the same procedure.

Procedure Bullet  To prepare site servers for a mixed SMS 2.0/SMS 1.2 hierarchy in the Midwest Development Center case study

  1. Install and configure one SMS 2.0 site server as a parent site. In the MDC case study, this site server is called MDC. It will be the parent site to the SMS 1.2 site servers that you will maintain in your hierarchy to support the Macintosh clients. This SMS 2.0 site server is configured as the central site.
  2. Install and configure SMS 2.0 site servers to support client computers running Windows 3.x, Windows 95, Windows 98, Windows NT 3.51 or later, and Windows 2000. In the MDC hierarchy, these site servers are called BL_Test, AA_Test, and CL_Test. These sites are all children sites of the SMS 2.0 site server called MDC installed in step 1.
  3. Map your SMS 1.2 domains to your network’s IP subnets or IPX network numbers. Decide which domains to move to each of your SMS 2.0 site servers on the basis of these domain/subnet relationships.

    Review Figures 12.2 and 12.3 to compare the Midwest Development Center SMS 1.2 domains and their mappings to IP subnets and IPX network numbers for each SMS 2.0 site server.

  4. Designate one or more SMS 1.2 site servers to support all clients running the Macintosh operating system. In the case study, the administrators set up two servers to support these clients, MDC_Macs, and AA_Macs. Create new domains that include only those clients. Add the new domains to the SMS 1.2 site servers.

    Important   Because Wide World Importers has a large number of clients using the Macintosh operating system, the Midwest Development Center administrators decided to keep more than one SMS 1.2 site server in their hierarchy. If your situation is similar, you should review the “Client-Side Upgrade Issues” section in Chapter 5, “Migrating SMS 1.2 PGC Applications to SMS 2.0 Shared Applications on Servers,” in the SMS 2.0 Administrator’s Guide and resolve any hierarchy structure issues before proceeding.

  5. Assign the SMS 1.2 clients running all Windows operating systems to the new SMS 2.0 site servers by defining site boundaries for each SMS 2.0 site server. To define site boundaries, navigate to the following location in the SMS Administrator console.
    6. Systems Management Server   Lower levelSite Database (site code-site name)      Lower levelSite Hierarchy          Lower levelsite code - site name

    Right-click the site whose boundaries you want to define, click Properties, and then click the Boundaries tab.

  6. Apply SMS 1.2, Service Pack 4 (or later) to the SMS 1.2 site servers. This will enable those site servers to communicate correctly with the SMS 2.0 site servers in your hierarchy.
  7. Attach the SMS 1.2 site server as a child site to the SMS 2.0 parent site server that you created in step 1. In the case study, MDC_Macs is attached to MDC as a primary child site.
  8. Upgrade all other SMS 1.2 site servers in your hierarchy to SMS 2.0. Configure site boundaries for each upgraded site in the SMS 2.0 Administrator console.
  9. Initiate one or more resource discovery methods if you have not already done so. Also initiate client installation methods on each site server in your hierarchy. For more information, see “Upgrading Clients” earlier in the chapter.

SMS 2.0 will automatically install SMS 2.0 client software on all SMS 1.2 and SMS 2.0 site servers and site systems in the hierarchy.