BDD Scenarios: Automating Application Deployment

Introduction

Published: March 8, 2005

In order for a newly deployed computer to be immediately useful, it is necessary to install the application packages that the users of the computer require to do their day-to-day work. These applications, if used by the majority of users, can be included in the operating system image itself. But in many cases, the needs of different groups of clients, or even of individual clients, are different, requiring a different list of applications for each computer.

It also may be necessary to install hardware-specific applications (for example, DVD players, CD-ROM burning software, or OEM management agents) since including such applications in the image itself could result in a very large image that would be difficult to deploy and keep up-to-date.

The SMS 2003 OS Deployment Feature Pack supports the installation of applications as part of the deployment process, but does not provide a way to dynamically build this list. Using only the OS Deployment Feature Pack, it would be necessary to define a different program, collection, and advertisement for each unique combination, which would quickly become unmanageable. As an alternative, standard SMS 2003 software distribution, based on inventory-driven collections, could be used, but this would introduce delays ranging from minutes to hours before these applications would be installed.

To work around these limitations, the Solution Accelerator for Business Desktop Deployment Enterprise Edition includes the ability to install a dynamically generated list of applications. This is described in the Zero Touch Installation Deployment Feature Team Guide.

The following scenarios are described in the sections below:

Role-based application installation. Each computer can be assigned a role, which is used to select the packages that should be installed on the computer.

Location-based application installation. Based on the computer's location on the computer network, location-based packages can be selected.

Hardware-specific application installation. Packages can be installed based on the make and model of the computer.

Computer-specific application installation. Packages are installed based on a specific computer attribute such as computer name or MAC address.

All of these scenarios assume that the application package list is manually specified, either through a configuration file (CustomSettings.ini) or database queries. This places the burden on IT administrators to determine which applications should be installed. To remove this burden, three additional scenarios are described:

Dynamic computer-specific application installation. Using the SMS 2003 inventory for the original operating system, a list of packages to be installed on the new operating system can be constructed, substituting the appropriate package if newer versions of the package are now available.

User self-provisioned hardware-specific application installation. Using Zero Touch Provisioning, users or appropriate surrogates can build the application list prior to the operating system deployment.

Customized dynamic computer-specific application installation. This is a variation on the dynamic computer-specific application installation scenario described above. It allows users or appropriate surrogates to customize using Zero Touch Provisioning the list of applications determined using SMS 2003 inventory; applications can be added to (if additional applications are needed) or removed from (if some applications are no longer used) the list as necessary.


**
In This Article
**