‘A’ to ‘W’ of Repackaging


This Article is about some of the generic terms the packagers will use in their day to day work.Hope this will help more for the newbies in packaging to understand more about these terms.


The process of verifying whether the software is necessary and achieving a plan of deployment.

Application Source

The unedited and unpackaged data for applications—what the packaging process starts with.

Assigned Applications

An application that is available for users but not installed at user sign on. It is installed when a user clicks the application icon.

Baseline Test Computer

A test computer that is built on a clean computer and has had service packs and any required patches applied and user accounts, Group Policies, and any other existing applications installed that you are likely to see in the end-user environment.

Change Management

A process to prevent conflicts in deployments.

Change Management Coordinator

A central contact that provides coordination in the change management process and ensures that the processes are followed.

Clean Test Computer

A test computer that has the core OS installed, all drivers installed, and any required general network settings configured.

Conflict Resolution

The process to resolve problems identified during a review process.

Conformance Testing

Testing to verify that software applications function with existing software.

Deployment Method

How an application is distributed.

Deployment Source

Location that contains the edited and deployment-ready package.


The delivery, maintenance, and reporting of software packages.

Distribution Documentation

A document to detail the deployment method and source location of the application.

Distribution Endpoints

Your commercial application distribution software generally likes to have a place to find the software-modified source or your custom deployment solution has locations from which the files can be installed.

DLL Hell

An annoying residual effect of installing multiple applications—a situation in which each application installs its own DLL files. Version conflicts, overwrites, and unforeseen modifications can result. Deployment software in recent years is focusing more and more on controlling this problem.

Elevated Privileges

When applications are installed on a client system, the installer may require privileges to the computer at a higher level than the user context (such as getting edit access to the registry). Windows Installer has a method for elevating the privileges of the application.

If the deployment method relies on an installed service, the service can be installed with a userid (or system access) that has elevated privileges.

Email Deployment Method

Aside from the obvious use for sending information, email deployment can send links or executables to users.


A generic term that describes a business unit, company, division, or departmental division.

Explicit Linking

An executable will attempt to load any needed libraries when the application calls for the file.


Generally, a snapshot of the computer operating system.

Image Inclusion Deployments

A deployment method that packages applications into an image snapshot. The application is deployed by the act of imaging a workstation.

Implicit Linking

The list of libraries an executable needs is located within the header of the executable.

Installation Point

Location where the application was originally installed.

Mass Deployments

The process of distributing applications to all end points in one deployment.

Package Documentation

A form that contains data needed by the deployment group to get an application out; it

should be customized for your particular environment. Some suggested headings:

Overview, Contact, Prerequisites, Detailed Steps, Post Steps, Troubleshooting, Process Overview, Known Issues and Optional Items. Its primary focus is the application, not the distribution.

Peer Review

A good practice to catch errors prior to a deployment. After the product or application or deployment method is completed, a technically knowledgeable person that was not involved in the process reviews all aspects, looking for errors or conflicts. Having another set of eyes (and a different viewpoint) can find overlooked areas.

Phased Rollouts

A process of sending applications out in small sections.


Process, Procedure, and Documentation.

Published Application

An application that is available to the user but not installed at user sign on.

Pull Technology

A distribution technology that primarily relies on client end points triggering the deployment event.

Push Technology

A distribution technology that primarily relies on servers (distribution points) triggering the deployment event.


Libraries that are needed and not included in the original operating system—the libraries are contained within the software application.

Remote Users

Users not physically located in the same location as the deployment starting point.


The process of getting a software application prepared for deploying to your environment.

Resource Kit

A collection of utilities focused on a particular product.


The overall process of getting an application distributed.

Rollout Team

The group of people involved in the creation of the deployment application.

Shared Resources

Basically anything an application will need to function, including (but is not limited to) file extensions, user document workspace, ActiveX controls, Open Database Connectivity (ODBC) databases, drivers, fonts, shortcuts, DLLs, and so on.


Service level agreement, which is a document that describes the relationship between the owner of the application or process and the support organization. Although the document’s content is very flexible, the agreement normally details the acceptable outage durations, who to contact on both sides, when dark windows are allowed, critical times for the application to be online and any processes needed to resolve issues. Documenting the backup process and what it takes to restore the data is also a good inclusion item. By detailing the information ahead of time, conflicts are prevented or at least more easily resolved.

Snapshot Software

Software used to take a status image of an application or operating system.


A deployment method that describes the manual method of deployment.

Software Metering

Process to control and monitor software licenses.


The starting point; where the data is located.

Standardization (or Standards)

A set of criteria that all applications abide by to ensure compatibility and mutual functionality.

Target Systems

The distribution end-point computers.

Test Computer

Computer used for testing.

Web Deployment

A deployment method that provides a Web page with links. Users click the link and the application is installed.

Windows File Protection

WFP is a process in Windows 2000 and later that ensures the core operating system files aren’t inadvertently overwritten.

Windows Installer Transforms

A method to modify Windows Installer files.

Working Test Computer

A test computer that has the software application installed and functioning properly. It is the final and desired state of the testing process.


1 Response to “‘A’ to ‘W’ of Repackaging”

  1. 1 gowri January 28, 2010 at 6:55 pm

    Excellent writeup which gives a gist about the terms used by packagers…
    Your writeups are eye opener for a newbiew…I am yet to read many of your post…But on a spree and will read and learn things through your post..
    Keep blogging 🙂

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out /  Change )

Google+ photo

You are commenting using your Google+ account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )


Connecting to %s

%d bloggers like this: