Monitoring the Distribution

Distributing Windows 2000 in an organization with many sites takes some time to complete. Some sites will take longer than others due to the speed of the wide area network (WAN) links, the reliability of those links, sender scheduling, and so forth. There is also the possibility that, despite good preparations, some sites or distribution points might have inadequate disk space by the time the package arrives. For these reasons, it is important to give the Windows 2000 distribution adequate time to complete. Monitor it closely to determine if there are any issues to resolve and make sure that the distribution is complete at all sites.

System Status Subsystem

SMS 2.0 includes a powerful System Status subsystem for monitoring the distribution. The SMS Administrator console includes a System Status node where you can obtain summary and detailed results from the System Status subsystem. You can also obtain the status of the package distribution from the Package Status subnode.

Note

When you create a package, the definition of that package is immediately distributed to all child sites; however, the actual files for that package, if any, are not distributed at that time. The same package definition is re-sent when the package definition is updated. Status information for the package definition distribution is then available. Therefore, when reviewing package status, make certain you distinguish between the distribution of the package definition and the package files.

Software distribution status is summarized at several levels, as follows.

Package Status for All Packages

When you select Package Status under the System Status, you can see, as shown in Figure 14.6, how many distribution points have been targeted for each package and how many have been installed, are retrying, or have failed. This level is useful to identify how many distribution points, if any, might need intervention. Note the size difference between the original package and the compressed package. The package identification number might also be useful for other purposes, such as troubleshooting.

Enlarge figure

Figure 14.6 The Status of All Packages

At this level there are no status messages to query.

Package Status for a Specific Package

Below the package status for all packages, you can select each package. At this level you can see, as shown in Figure 14.7, which sites should or should not have the package, and which ones might need intervention. You can also verify that all sites have the same package version, as indicated by the Source Version column.

Enlarge figure

Figure 14.7 The Status of the Windows 2000 Package at All Sites

At this level you can select the Action menu and select Show Messages, All to see all the status messages for the package from all sites and distribution points. This can be a lot of messages; and therefore, it is better to review the messages at each site individually.

Package Status at the Sites

Below the package status for a specific package you can select each site. This level of status checking allows you to see, as shown in Figure 14.8, which specific distribution points within a site might be having problems with the distribution.

Enlarge figure

Figure 14.8 The Status of the Windows 2000 Package at a Specific Site

At this level, you can select the Action menu and select Show Messages, All to see all the status messages for the package from this site and all its distribution points. The following sequence of messages is typical (the distribution point-specific messages are listed in the next section):

• or 300001 — package created or modified
• — program created
• 2310, and 2311 — distribution manager preparing package
• — distribution manager initiating schedule and sender to send the package information (not the package files)
• — distribution point assigned
• — preparing to send compressed image of package
• — distribution manager initiated scheduler and sender to send the package files to the sites
• — distribution manager deleted the compressed image of the package

When reviewing status messages, notice that each sequence of Distribution Manager activities ends with the message 2301, which indicates that the sequence was successful. This message appears whenever Distribution Manager completes any activities. Distribution Manager is the SMS component that distributes packages from the site server to the SMS distribution points and that initiates the sending of the package to other sites.

Package Status at a Distribution Point

At the package status at each site, you can select each distribution point. At this level, you can select the Action menu and select Show Messages, All to see all the status messages for the package at this distribution point. The following sequence of messages is typical:

• — distribution manager is refreshing package on distribution point (not seen the first time the package is sent to the distribution point)
• — distribution manager is starting to distribute package to distribution point
• — distribution manager decompressed package to temporary directory (if applicable)
• — distribution manager copied package from temporary directory or package source to distribution point
• — distribution manager successfully distributed package to distribution point

Note

The Systems Management Server Resource Guide includes a chapter, "Status Messages," that lists all status messages and their complete message text.

Reporting Package Distribution Status

You might want to produce a report of the package distribution status, either for easy reference or to address your own specific requirements. You can perform queries of the package distribution status classes and incorporate the responses in the reporting tool of your choice as is done with other SMS reporting tools. Table 14.1 lists the relevant classes and the category of status information that you can find in each.

Table 14.1 Package Distribution Status Classes

© 1985-2000 Microsoft Corporation. All rights reserved.