1. What is an Installation Package?

An installation package is a program allowing to install an application with specific version, language, configuration…

To create an installation package, the following items are necessary:

AIP document
The Application Installation Procedure is a document detailing step by step the installation and the configuration of the application.
Original Sources
The original sources are all the files (executables, REG, scripts…) needed to install the application using the AIP document.

When the packager delivers an installation package, it must always be provided with a PRN document. The Packaging Release Note is a document detailing all the steps followed to create the package and all the specificities (additional script, custom action, MSI properties…)

2. Infrastructure

2.1 Packaging Repository

The “Packaging Repository” is the working repository of the packaging team.

It must contains at least the following folders:

These folders correspond to the different status of every projects.

The “Production” folder is very useful to check quickly what is the version currently distributed to the machines.

The “Packaging Repository” must also contains the “Packaging Log”, Excel file allowing to follow the history of all the packaging projects in progress, done or even canceled.

2.2 Packaging Log

The “Packaging Log” is a tool allowing to follow up the packaging activity.

2.2.1 Logging

Status

Information

Name of the package
Package Type (Local or Virtual)
Request Reference
Requestor / Application owner
Coordinator: Name of the coordinator of the packaging project
Packager: Name of the packager

History

Date of receipt of the request
Date of receipt of the source
Date of receipt of the AIP (Application Installation Procedure)
Date of the end of the “Assessment” phase
Date of the beginning of the “Testing” phase
Date of the delivery

Additional information can be added:

Location of the package in the distribution environment
Name of the package in the distribution environment
ProductCode
…

2.2.2 Reporting

The “Packaging Log” includes reporting (numbers, percentages…)

It includes also a graphical overview of the delivery.

2.3 SCCM Repository

The “SCCM Repository” is a share where the SCCM packages are stored.

It should contain at least 3 folders:

In the “Dev” folder, all the packages in the “Testing” phase

In the “Production” folder, all the packages currently in production

In the “Archive” folder, all the packages not in production anymore (updated by another package installing a newer version, decommissioned…)

It’s the basic location from where all SCCM distribution points copy the packages.

2.4 Virtual Lab

A lab containing several virtual machines (imaged with the corporate OSD) is needed for the assessment, the packaging and the testing (internal and UAT).

This lab should contain at least 10 virtual machines:

2-3 for the assessment, the packaging and the internal testing
7-8 for the User Acceptance Testing

3. Naming Convention

Let’s define a glossary and the according naming convention.

[PackageName]

The PackageName allows to name each installation package.

This PackageName will be then used for all other naming conventions.

Manufacturer_ApplicationForXXXX_Version_Language_PackageType_PackageVersion

“ApplicationForXXXX” if specific platform/settings or “Application” if generic
“Manufacturer” and “Application” must be without spaces
“Language”: MUI, EN, FR…
“PackageType”: L for Local and V for Virtual
“PackageVersion”: First version is R1, then R2, R3… (R for “Release”)

[ARPName]

The ARPName is the name of the application in Add/Remove Programs after been installed with the installation package. A prefix (for example, IT, the name of the department, the name of the organization…) is used to recognize the application has been installed using a corporate installation package.

IT_[PackageName]

[AIPName]

The Application Installation Procedure is a document detailing step by step the installation and the configuration of the application. The installation package must follow the same behavior as this procedure.

AIP_[PackageName]_v1.0

[PRNName]

The Packaging Release Note is a document detailing all the technical information regarding the creation of the installation package

PRN_[PackageName]_v1.0

4. Packaging Process Model

5. Process

5.1 Request Phase

The application owner, who is the responsible of the application (installation, behavior, technical details, licensing…) create a request to ask the creation of an installation package.

Such a request can be created using a ticketing software, or by email to the Packaging Team coordinator, or using a specific homemade tool…

This request must contains at least:

The Application Installation Procedure (AIP)
The original sources (or a link to download them)
Eventually the scope (specific country, entity…)

Once the request approved by the packaging coordinator, create a new entry in the Packaging Log:

Status: Requested
Package Name (a generic name can be used, it will be formatted correctly during the assessment phase)
Package Type
Request reference (if any)
Requestor (generally the Application Owner)
Coordinator: Person in charge of the packaging project
Request Date

5.2 Assessment Phase

During the “Assessment” phase, an assessment of the packaging request will be done using the AIP and the sources provided.

Modify the Packaging Log:

Status: Assessment
Source: Date when source has been provided (usually the same as the request date)
Application Installation Procedure: Date when AIP has been provided (usually the same as the request date)

In the Packaging Repository:

Create a new folder in “1-Assessment“
Create 3 sub-folders “Documentation“, “Package” and “Source“
Copy the AIP in “Documentation” and the sources in “Source”

On a clean virtual machine:

Install the application using the source and the AIP

Define the [PackageName]

Manufacturer_ApplicationForXXXX_Version_Language_PackageType_PackageVersion

“ApplicationForXXXX” if specific platform/settings or “Application” if generic
“Manufacturer” and “Application” must be without spaces
“Language”: MUI, EN, FR…
“PackageType”: L for Local and V for Virtual
“PackageVersion”: First version is R1, then R2, R3… (R for “Release”)

Back in the Packaging Repository :

Rename the folder: [PackageName]
Rename the AIP: AIP_[PackageName]_v1.0.docx
Create a version 1.1 of the AIP
Apply modification if needed (additional information, clarification…)

5.3 Packaging Phase

Let’s now creating the package.

In the Packaging Repository:

Move the packaging project in “2-Packaging”

Modify the entry in the Packaging Log:

Status: Packaging
Application: [PackageName]
Packager: Name of the packager
Assessment Completed: Current Date

Create the package using the guidelines of the company, for example:

If possible, the package must use a MSI (snapshot capture, MST…), and if not possible a silent install.
Auto-updates must be disabled
No shortcut on desktop by default
Cloud features must be disabled
[ARPName] must be used in Programs and Features control panel

Once created, copy the package in the “Package” folder.

Create a Packaging Release Note with the details of the package (modification applied by the MST, snapshot capture steps, commands, additional scripts…) and copy it in the “Documentation” folder.

5.4 Testing Phase

In the Packaging Repository:

Move the packaging project in “3-Testing”

Modify the entry in the Packaging Log:

Status: Testing
Package Completed: Current Date
SCCM Repository / Source Location: Package location in SCCM repository

The first test to do is an internal test.

On a clean virtual machine:

Test the installation scenario
- Check the log files of the package
- Check the installation according to the AIP
- Appy the test case according to the AIP
- Check if the policy is applied (name in Add/Remove Programs, shortcuts, auto-updates…)
Test the update scenari
Test the uninstallation scenario

In the SCCM Repository: