Using Systems Management Server to Deploy Windows 2000

Distributing the Packages to Sites and Distribution Points

The basic procedure for distributing packages is presented as follows. When you perform this task, note that all distribution points for all sites are listed, so you can select all the intended distribution points at one time. However, make sure that you first distribute the package to a small number of sites so that you can test your SMS infrastructure and procedures. As your confidence increases and capacity allows, you can include additional distribution points at other sites. For more information about this procedure, see "Distributing Software" in the Systems Management Server Administrator's Guide.

To distribute a Windows 2000 Server SMS Package

In the SMS Administrator console, select Packages, select the Windows 2000 package, and then select Distribution Points.
From the Action menu, point to New, and then click Distribution Points.
The New Distribution Points wizard appears.
Click Next to continue past the Welcome page, and select the distribution points you want to use.
If this is a test distribution, select the distribution points that you decided on. Also, if you are using distribution point groups, select them now. Note that all distribution points for all sites are listed, so you can select all the intended distribution points now. However, you might do a limited number of distribution points at one time to better manage network traffic.
Click Finish to start the distribution.

Caution

As soon as you click Finish in step 4, the distribution process begins. You might notice a short delay, due to system processing, package priorities, or sender schedules; however, be prepared for immediate SMS activity.

For more information about the flow of a package after you initiate distribution, see "Software Distribution Flowcharts" in the Microsoft® Systems Management Server 2.0 Resource Guide (part of the Microsoft® BackOffice® 4.5 Resource Kit). The Windows 2000 files are compressed into a single file which is then sent to child sites. At each site, the package might then be sent to other child sites, if they have distribution points for this package.

Testing the Distribution

As the Windows 2000 packages are distributed, verify that they are properly deploying to the distribution points. The section "Monitoring the Distribution," which follows later in this chapter, describes how you can verify that the packages have arrived at all distribution points and how you can quickly identify any problems. However, you also need to test the distributions to ensure that they are complete and that the directory trees are properly laid out. You do not need to test all distribution points at this level, but make sure to spot-check a few distribution points to confirm that the production distribution is working as you intended.

Expanding the Distribution

When the first distribution of the package has been completed successfully, you can distribute the package to additional sites and distribution points. The procedure is exactly the same, except that you might want to send to more distribution points at a greater frequency and with less monitoring. You must be sure to distribute the package to sites before advertising the package to clients at those sites. SMS does not make the advertisement available to the clients until a distribution point is available.

Distributing by Means of the Courier Sender

Network links to some of your sites might be slow or unreliable, or they might already be fully utilized by other traffic. Therefore, sending a large package like Windows 2000 over the network links might not be acceptable. SMS 2.0 includes an alternate sender, called the Courier Sender, that can be used to provide all the benefits of SMS software distribution but without the network overhead normally involved in getting packages to sites.

With the Courier Sender, the SMS package is copied to CD-ROM or similar media and then sent through mail or by courier to your sites. At the sites, someone puts the CD-ROM into the site server and runs a simple program. From this point on, the software distribution carries on as it normally would. The advertisements, status information, and other information will flow over the network at the times you specify; however, this traffic is small relative to the traffic that the package itself would require.