myITforum.com : Excerpts from the System Center Configuration Manager 2007 Administrator’s Companion Chapter 11

Chapter 11 – Distributing Software Packages
~Steve Kaczmarek, Content Publishing Manager for the Configuration Manager 2007 Writing Team

Listen to the PodCast on myITforum.com TV

New apps transform you
As spring calls forth pink blossoms:
Software Distribution

One of the primary features of System Center Configuration Manager 2007 is its ability to distribute packages to, and run programs on, Configuration Manager client computers. This process consists of three main elements:

Creating and distributing the package
Advertising a package program to a collection
Receiving the advertisement and executing the program on a client

The package distribution process is the focus of this chapter. First, some terms are defined and just what Configuration Manager does throughout the distribution process is outlined. Then you’ll explore the administrative tasks involved in the creation of packages and advertisements. Finally, you learn how to monitor status messages and log files for the appropriate Configuration Manager components involved and how to test the package and its programs to ensure that they execute properly on the target clients.

Somehow, Configuration Manager administrators and users often misunderstand or mislabel the package distribution process. It’s important to remember that Configuration Manager is fundamentally a package delivery tool. Basically, Configuration Manager is designed to make a package that you create available to a specified target or targets. The key here is that you are responsible for creating the package. You’re also responsible for ensuring that the package will execute as intended when it reaches its target. Configuration Manager will get it there for you, but Configuration Manager won’t correct errors for you—nor should you expect it to.

Look at it this way: suppose you send a bicycle to your nephew. You box up the parts carefully, including instructions on how to assemble it, go to your nearest package delivery service office, fill out the appropriate forms, pay the appropriate fees, and hand over the box. The responsibility of the package delivery service now is to get the box containing the bicycle to your nephew’s house within the time frame you specified and paid for. When the package arrives at your nephew’s house, he opens the package, reads the instructions, and assembles the bicycle. The extent to which your nephew is successful depends on how accurate and easy to understand the instructions are.

Configuration Manager works in much the same way. You, the Configuration Manager administrator, are responsible for creating the package and ensuring that all the appropriate pieces are assembled: source files, scripts, executables, command switches, and so on. You identify where the package must go and who should receive it. Configuration Manager carries out your instructions and even “opens” the package when it arrives at the target. However, the package’s ability to execute—or the user’s ability to use the application, for that matter—isn’t Configuration Manager’s responsibility.

Working with Branch Distribution Points
A new feature of Configuration Manager is the branch distribution point. This site system role is meant to facilitate software distribution to smaller or remote offices. With previous versions of Systems Management Server, the best way to manage bandwidth and connectivity issues related to software distribution to smaller or remote offices where WAN connectivity might have been an issue was to install a secondary site server in that location. You could then take advantage of the bandwidth controls available when communicating between sites to also manage software distribution.

The branch distribution point is a fine alternative to installing a secondary site server if the primary reason you need the secondary site server is to distribute software. For all practical purposes, the branch distribution point functions like a standard distribution point. However, it depends on the availability of a BITS-enabled standard distribution point from which it receives its content—otherwise it will not function. Like the standard distribution point, a branch distribution point can use BITS to manage network bandwidth usage and to provide a local checkpoint restart if the package download is interrupted. Branch distribution points also provide an option that downloads a package from the standard distribution point to the branch distribution point only when requested by a client. This can help manage not only network bandwidth but local storage
on the branch distribution point.

The branch distribution point can be a high-end desktop-class computer, or a server-class computer. The same considerations regarding performance, storage, and network usage apply here as to the standard distribution point. However, local usage is another consideration. If the branch distribution point is a high-end desktop-class computer, then you are subject to the shared connectivity limitations associated with a desktop computer— mainly that you are limited to 10 concurrent shared connections. Also, if that computer doubles as a user’s workstation, that user’s desktop performance will likely be affected by client requests for packages.

Excerpted from "Microsoft® System Center Configuration Manager 2007 Administrator's Companion" by Steven D. Kaczmarek. Reprinted by permission of Microsoft Press. All rights reserved. For more information, go to http://www.microsoft.com/MSPress/books/9554.aspx

Read about the Microsoft® System Center Configuration Manager 2007 Administrator's Companion


		myITforum.com ©2010 \| Legal \| Privacy