[Previous] [Next]

Lesson 1: Overview of Software Distribution

Almost any software or data can be distributed by SMS and shipped to client computers. The first step in SMS software distribution is creating a package and a program. A package contains the data or software that needs to be distributed and installation instructions. A program contains an installation instruction contained in the package. Next, an advertisement is used to send the package and program to a collection. A collection contains at least one client computer and, optionally, subcollections. A subcollection is simply a collection included within another collection. Finally, the Advertised Programs Client Agent receives the package and runs the program included in the advertisement on the client computer. Installation instructions can be created for packages using the SMS Installer application.

After this lesson, you will be able to: Estimated Completion Time: 15 minutes

What Can Be Distributed?

With the software distribution feature, single files or entire applications can be distributed, as packages, to distribution points in a Systems Management Server (SMS) hierarchy. If instructions without files must be sent, the software distribution feature can be used to distribute instructions-only packages to client computers. In this case, distribution points are not used to distribute the package. An instruction-only package can be used to run regularly scheduled maintenance tasks such as disk defragmentation. If a package contains files, distribution points are specified during package creation. For all packages, advertisements send package instructions to CAPs.

The client access point (CAP) is a site system whose role is to provide a set of shared directories and files that create a common communications point between the site server and the client computers.

The Advertised Programs Client Agent running on the client computer installs the application or simply runs a command using an instruction sent to the CAP. Advertisements and packages are intentionally separated in SMS so that multiple advertisements can be created to execute any instruction in a previously distributed package.

The software distribution process typically includes:

Commands are run on the client computer by the Advertised Programs Client Agent. It uses a package that is the combination of the application's files and a program (the actual command to run the application).

A program that cannot be run at a client computer is ignored. The Advertised Programs Client Agent on a Windows 16-bit client computer, for example, will ignore packages intended for Windows 32-bit client computers.

Supported Client Computers

Any client computer that has the Advertised Programs Client Agent installed and is a member of a collection is considered a package target. The following client operating systems are supported directly by SMS 2.0:

To support client computers running MS-DOS 5.0 or later, Macintosh System 7.x, OS/2 2.x, and OS/2 Warp with Windows, maintain an SMS 1.2 site server in the SMS 2.0 site hierarchy. Packages can be created on the SMS 2.0 site server or created on the SMS 1.2 site server. Packages will then run as SMS 1.2 Run Command on Workstation jobs. If Windows 16-bit or Windows 32-bit client computers are managed by an SMS 1.2 site server, then Share Package on Server jobs are also supported from the site servers.

Configuring Software Distribution

A package is configured at the site server, made available on distribution points if necessary, and run on the client computer using instructions from the CAP. Figure 4-1 shows the entire software distribution process.

Click to view at full size

Figure 4-1. An overview of the software distribution process.

The process of distributing software or commands to client computers is described in the sections that follow.

Procedures Completed on the Site Server

The Distribution Process

A GUID is globally unique across computers and networks because it is created from a time stamp and a code based on the network address hardwired on the host computer.