Admin Studio Application

Repackaging Guide

TITLE:

Admin Studio Application

Repackaging Guide

CREATION
DATE:

SUBJECT:

Admin Studio Application

Repackaging Guide

REVISION DATE:

AUTHOR:

John Jankowski

REVISED BY #:

TEAM:

SCCM

LAST SAVED BY:

MANAGER:

Contents

1 | Page

CATEGORY:

Dec 11th, 2013

Project

1.Introduction...................................................................................................3
2. Packaging.....................................................................................................3
3. Why Packaging?...........................................................................................3
4. Pre-requisites................................................................................................4
5. Planing for
Packaging
4
6. Installation steps..........................................................................................5
7. Repackaging.................................................................................................8
8. Capturing methods.......................................................................................9
9. Package creation using Repackager (EXE to MSI)......................................11
10. Transforms................................................................................................42
Embedded transforms.................................................................................42
Unembedded transforms.............................................................................43
Secured transforms.....................................................................................43
Unsecured transforms.................................................................................43
11. MST creation using Tuner (MSI to MST)....................................................44
12. Start the "Pre
Validation"
..48
13. Start the "Post
Validation"
54 14. Conclusion.............................................................................56

2 | Page

1.Introduction
Admin Studio provides enterprise IT teams, including the MSI Packager, with the
most advanced software packaging tools to efficiently create reliable application
packages for deployment. AdminStudio provides a complete suite for automating
MSI packaging, customization, testing and management reporting capabilities.
AdminStudio 11.5 includes new features Install Shield 2012 Spring, Virtual Package
Editor, Application Manager, Distribution wizard etc. and enhancements that will
help you use the latest technologies and save time on everyday tasks.

2. Packaging
Application packaging bundles application Files, Registries, Services, Shortcuts into
a single file called a distribution unit (.msi), which makes it easier to deploy and
install them on users computer. Packaging reduces the total cost of ownership for
the customers by enabling them to efficiently install and configure the applications,
advertises features without installing them, installs products on demand, add user
customizations etc.

3. Why Packaging?
The Most common reasons for Re-packaging are as follows

Customized Installation
Reduce Support Costs
Self-Repair
Source Resiliency
Unattended Install

3 | Page

4. Planning for packaging

Considerations before packaging:
1) Check if the vendor application supports repackaging. Eg: Microsoft and Adobe
applications do not support repackaging.
2) If the application is in .exe format and does not contain embedded MSI it should be
packaged to a MSI format.
3) If the application is in MSI format, no changes should be done to the vendor MSI, a
MST (transform) should be generated for the customizations.
Tech review of the Vendor application:
1) Check that the application is installing correctly
2) Check that the application functions correctly
3) Check that the application uninstalls correctly
4) Check if there are any pre-requisites
5) Check for application dependencies
6) Check for any chaining deployments
Locations to check if there is any embedded MSI within the application:
1) Run %Temp% folder
2) Windows/Temp folder
3) Windows/ Installer folder
4) Run Services.msc. Disable Windows Installer service. If the application is not able
to install, it has an embedded MSI.
5) Check in task managerprocesses, if the msiexec.exe process is running, it means
the application uses an embedded MSI.

5. Pre-requisites

32-bit or 64-bit processor at 1 GHz or greater Speed.

1 GB RAM and 4.0 GB Hard Disk
Display
Designed for XGA at 1024 x 768 resolution or higher
Windows 7 Operating System
Microsoft Internet Explorer 7.0 or later
Administrative privileges on the system

6. Installation steps
Double click on AdminStudio11.5.exe from
\\gad\ca\Repository\AppDNA\AdminStudio.

4 | Page

 Click Next.

5 | Page

 Select I Accept the terms in the license agreement.

Click Next.

Click Next.

Click Next

6 | Page

 Choose Typical and proceed with installation.

7. Repackaging
Application Re-packaging is the process of identifying application components and
determining how those components should be installed and configured on client
workstations. This process involves taking commercially or internally developed
setups and creating packages that can easily be deployed to client workstations
without user or administrator intervention. Windows Installer service, which
manages the installation of software, manages the additions and deletions of
software components, monitors file resiliency, and maintains basic system recovery
by using rollbacks. All managed applications will be packaged in an .MSI format to
take advantage of the Windows Installer technology. Managed applications are
defined as applications maintained by system administrators then distributed and
installed for end users via SCCM or Group Policy. Unmanaged applications may be
installed using the .MSI format but are not mandatory. Unmanaged applications are
defined as applications installed by the end user and not distributed via a managed
software distribution method.
Windows Installer is made of up of two key components:
7 | Page

 Windows Installer Service

This operating system resident installation service provides a consistent
standard for installing, maintaining and uninstalling applications.

A standard Windows Installer package format

The Windows Installer based packages are saved in an .MSI format. This is a
self-contained database file containing requirements and instructions that the
Windows Installer uses when installing or uninstalling applications.
Typical instructions in Windows Installer packages include:

What application is being installed

What files should be copied or deleted
What shortcuts should be used, and with what, if any, command line
parameters
What changes should be made to the registry
What Windows services should be added
How Windows services should be controlled
What changes should be made to .INI or files

Purpose of Repackaging:
Installations created for the Windows Installer service dramatically differ from
traditional installations, making reusing legacy installations impossible without
using a repackaging tool. Repackager assists you by capturing the data placed on
your system during installation and converting it into a Windows Installer (.msi)
package, which you can then customize and distribute according to your
organizations needs.
Repackaging an installation into a Windows Installer package provides the following
benefits:
Can customize it using Install Shield Editor or Tuner: You can further configure
or customize the Windows Installer package to meet your specific needs by
editing the .msi file in Install Shield Editor or by creating transforms in
InstallShield Editor or Tuner
Can perform conflict analysis and resolution: You can use Conflict Solver to
check the Windows Installer package for conflicts that may exist between it
and other known Windows Installer packages in an Application Catalog
database, ensuring the proper installation and functioning of your
installations.
8 | Page

 Can implement application repair and feature advertising : Finally, once

converted to a Windows Installer package, the installation can take
advantage of Windows Installer functionality such as application repair and
feature advertisement.

Repackaging Wizard Best Practices

To ensure optimal performance of the Repackaging Wizard during repackaging and
when working with Repackager projects, the following best practices is
recommended:

Repackage on a clean System

Launch Repackager Remotely or Install Repackager on the Clean Machine
Use the Repackager Interface to Exclude Unwanted Items
Exit All Other Application
Only Repackage Non-Windows Installer Setups

8. Capturing methods
There are two ways of capturing application using AdminStudio Repackaging wizard
1) Installation Monitoring
2) Snapshot

Installation Monitoring
The Install Monitoring method of repackaging involves monitoring a system for any
processes that is created during the installation. In this way, the repackager can
identify changes being made to the target system. The Installation Monitoring
method has advantages and disadvantages in comparison to the Snapshot method.

Installation Monitoring Advantages

Installation Monitoring is significantly faster than the Snapshot method.

It can detect install "intent." This refers to files or registry entries that were
intended to be installed but were not actually installed because the file or
registry entry already existed on the target machine. However, this will not
detect conditional logic that was present in the installation and was not
actually executed. For example, consider the following two cases:
Case 1: The setup calls CopyFile and overwrites a.dll with a.dll from the
installation. Snapshot will not capture this because the net effect is the same.
However, Installation Monitoring will because the CopyFile function is logged.

9 | Page

Case 2: The legacy installation uses a call to GetVersionEx to conditionally

install the file only if the version to be installed is greater than the installed
version of the file. If the function that copies the file is not called due to this
conditional logic the install intent is not captured.

Installation Monitoring is also less prone to capturing extraneous file and

registry data compared to the Snapshot method .

Installation Monitoring Disadvantages

It is limited to Windows XP, 2000, and NT 4.

It cannot detect changes made by processes already running prior to the

monitoring session or made via DOS.

Installation Monitoring also cannot detect manual changes made in Explorer

without some steps being taken prior to Repackaging.

Snapshot
The Snapshot method of repackaging involves taking a snapshot of a system setup
as a baseline configuration, running an installation, and then taking a second
snapshot of the system after the installation. The information provided by
comparing the two snapshots is stored in .inc file and used to convert the
installation into .msi format.
When using the Snapshot method, it is important to use a clean system for your
initial baseline snapshot. If you do not do so, some system files may already be
present initially and, therefore, will not be captured during repackaging. The
Snapshot method has advantages and disadvantages in comparison to the
Installation Monitoring method.

Snapshot Advantages

Due to the nature of the Snapshot method, all changes made to the target
system between the snapshots will be recorded. This includes information
Installation Monitoring cannot capture, such as changes made by processes
already running prior to the monitoring session or made via DOS. There are
also no added steps to allow the Snapshot method to record manual changes
made in Explorer.

Snapshot Disadvantages

The Snapshot method will take longer than Installation Monitoring.

It will not capture overwriting files on installation time.

10 | P a g e

9. Package creation using Repackager (EXE

to MSI)
Launch Repackager shortcut from Admin Studio tools
Note: Before running the Repackager do install all the dependencies of the
main application.

11 | P a g e

 Click on the first option Capture and Installation Using Repackaging Wizard.

12 | P a g e

 Tip: As a best practice, Repackager should be run remotely from a network

location or as a standalone installation for best results.
In the Repackaging Wizard, select Snapshot method of capturing and click
Next.

Select Multiple Steps and analyze the initial system Status and Click
Next.

13 | P a g e

The Initial system status is captured. The registry data is read .

After the setup capture is complete, click on Finish.

14 | P a g e

Now, install the application for which the packaging has to be done. Double
click on the setup.exe file.

Select the options on each screen to install the application. Do not open or
install any other files or do any unnecessary clicks as all this will also get
captured as a system change.

15 | P a g e

After the application has been installed, delete the application setup file
placed on desktop (else it will also get captured in the next snapshot) .

16 | P a g e

 Once the installation is completed, do the post configuration settings if

required.

Launch the Repackager from start menu for post capture .

17 | P a g e

 Click on the first option Capture and Installation Using Repackaging Wizard.
Click on Next.

Select Snapshot and click next.

18 | P a g e

Open the Repackager wizard. In the Snapshot Method, this time, Analyze
system status changes will be pre-selected. Click on Next to proceed .

Enter the Product information.

Tip:

Capture the product information beforehand so that it can be entered here

promptly.
The product name should follow the below structure:
Vendor
name(max
8
characters)_application
name(max
characters)_version number (max 8 characters including . )

19 | P a g e

15

 Click on Next.

20 | P a g e

 In the set Target Project Information and Capture settings screen, leave the
project path as default C:/Packages. Click Start.

Click Yes on the dialog box to create a new folder Packages.

21 | P a g e

 System changes are captured.

Click Finish to complete the setup.

22 | P a g e

 The Repackager files are stored in C:/Packages folder.

Open the .irp file from the project folder with Repackager .

Editing IRP file

Open the .irp file to make the changes. This file contains the captured differences
between the initial system setup and the system setup after the application was
installed.

23 | P a g e

 Click on Files and folders on the right had pane you will see the files and
folders that are part of the package, only keep our application related files
and exclude the rest by right clicking on the unnecessary file and selecting
Exclude/Exclude all
Click on Registry entries on the right had pane you will see the registry
entries that are part of the package, only keep our application related entries
and exclude the rest by right clicking on the unnecessary entries and
selecting Exclude/Exclude all.
By selecting Exclude only the current folder and the files in it are excluded.

24 | P a g e

 The excluded files show in Red. These files can be again included by
clicking Include or Include all after a right click on the folder.

By selecting Exclude all the current folder and the subfolders in it are
excluded.

25 | P a g e

The excluded files show in Red. These files can be again included by
clicking Include or Include all after a right click on the folder .

Since the following folders were excluded from the package, these can also
be deleted from the C:/Packages folder.

26 | P a g e

The Registry Entries section contains all the registries that got captured.
Not all the registries captured during the snapshot are a part of the
application. Such registries can be excluded from the package by a doing a
right-click on the package and selecting exclude or exclude all .
Only retain the registries that are for the application for which the setup
capture is run.

27 | P a g e

 The Shortcuts section contains all the shortcuts that got captured. You can
exclude the shortcuts that you do not want in the package.
Packaging tip:
[WindowsVolume] folder should always be excluded as it pertains to the
current users environment.
Exclude any shortcut to the uninstall exe as you do not want the user to
uninstall the application.
Exclude any documentation or readme shortcuts and Desktop shortcuts.

28 | P a g e

 Uncheck the create a windows Installer package (.msi) after creating the
Editor project.
Tip:

A customized template containing the organizational standards can be

created. That template can be used by selecting Use a customized
template option.

29 | P a g e

Check the package information. Make sure the package name follows the
standards.

In Software Identification Tag settings, leave the default settings .

A software identification tag is a small XML-based file that contains

descriptive information about the software, such as the product name,

product edition, product version, and publisher. Software asset management
tools collect the data in the tags to provide accurate application
identification for software that is installed in an enterprise

30 | P a g e

Uncheck the options according to the below screenshot .

Note:

If the application contains services, then check Map NT Service events to the
Service Control table.

31 | P a g e

Click the build button to generate the ISM file .

Now in C:/Packages/MSI_Package folder, The .context file can be deleted as it

is not required.

32 | P a g e

Customizing the ISM file

Right click on .ism file and edit with Install Shield.

The following is the snap shot of Installation Designer. Various details

provided can be edited to modify and customize the ISM as per requirements .

General Information:

Under this segment we can provide and modify the information about the
installation package. While providing the required details well follow various
standard naming conventions or best practices.
Under Install information ->General Information->Summary information-> change
the Summary title and subject to MSI name, update the package code, Author and
keywords. Use the following naming convention for MSI title and subject :
Title/Subject = VendorName_ProductName_Version, where

Vendor Name should not contain more than 8 characters,

Product Name should not contain more than 15 characters,
Version should not contain more than 8 characters .

33 | P a g e

Under Add or Remove Programs Tab, Disable the change button and Remove
Button. Also select the suitable Display icon .

In Organization View Feature name, Feature Display Name and Description -Should
be same as the MSI name. For ex: remove the New Feature string from both
Display Name and Description.

34 | P a g e

 The best practices can be applied to .ism to create quality MSI Database.

Click on Property Manager tab, select the NEW button then we enter the
standard Properties.

We have to add below mention Properties.

35 | P a g e

 To convert .ism to .msi go to build and click on Release wizard.

Click on next.

On the Product Configuration window, keep the default. You can change the
product Configuration name here. Click Next

36 | P a g e

 On the Specify a Release window, keep the default. You can change the
New Release Name here. Click Next

On the Filtering Settings window, keep the default. Click Next

37 | P a g e

 On the Setup Languages window, keep the default. Click Next

On the Media Type window, keep the default. Click Next

38 | P a g e

 There are 3 selections as shown below since we want to create a selfextracting MSI we select the first option. Click Next on the screen below.

The Create installation launcher (Setup.exe) option is checked by default.

Keep this option checked if you want to create a single Setup.exe. Since we
want to create a MSI this option has been unchecked. Click Next on the
screen below.

39 | P a g e

 On the Digital Signature window, keep the default. Click Next

On the Advanced Settings window, keep the default. Click Next

40 | P a g e

 On the Summary window, keep the default. Click Finish

The build process will start.

41 | P a g e

 The conversion has been completed and msi will be created inside release
folder.

Final MSI will be created in the following location:

C:\Packages\MSI_Package\Software
1\DiskImages\Disk1

42 | P a g e

Name\Product

Configuration

1\Release

 Below mentioned files are important files in admin studio packaging.

.IRP-Install Shield Project File
.ISM-Install Shield Module
.MSI-Microsoft Windows Installer

10. Transforms
The MSI format lets you easily modify or customize the software install by creating a
transform. An MSI transform is a file (.mst) that describes how WIS (Windows
Installer Service) should install an MSI package. The four types of Windows Installer
transforms are embedded, unembedded, secured, and unsecured

Embedded transforms
Embedded transforms are stored inside the .msi file of the package. This guarantees
to users that the transform is always available when the installation package is
available.
If the installation source is read-only, such as a CD or a network share to which the
person creating the transform has read-only access, this is not an option because
you must be able to write to the source to embed the transform in the *.msi file.
To add an embedded transform to the transforms list, add a colon (:) prefix to the
file name. Embedded transforms are not cached separately on the client computer,
because Windows Installer can always obtain the transform from the .msi file.
.Embedded transforms might be used in combination with secured or unsecured
transforms.

43 | P a g e

Unembedded transforms
Unembedded transforms are stored separate from the .msi file of the original
package. Unembedded transforms are cached separately on the client computer.
You can use unembedded transforms in combination with secured or unsecured
transforms.

Secured transforms
Secured transforms are recommended for security reasons. If an application is
installed at an elevated level, either per-user or per-computer, a user with low rights
can modify an unsecured transform and use it to make changes to the computers
that have elevated privileges.
Secured transforms are stored locally on the client computer in a location where, on
a secure file system such as NTFS, the user does not have write access. Such
transforms are cached in this location during the installation or advertisement of the
package. During subsequent installation-on-demand or maintenance installations of
the package, Windows Installer uses the cached transforms.
To specify secured transform storage, set the Transforms Secure policy, or set the
TRANSFORMSSECURE property, or pass the @ or | symbol in the transforms list .

Important: You cannot combine unsecured transforms and secured transforms in

the same TRANSFORMS list.
If a user removes the product, Windows Installer removes all secured transforms for
that product from that user's computer. If Windows Installer finds that a secured
transform is not locally available, it then attempts to restore the transform cache
from a source. Secure transforms can be secure-at-source or secure-full-path .

Secure-At-Source transforms that are missing from the local transform cache are
restored from the root of the source of the .msi file .
Secure-Full-Path transforms that are missing from the local transform cache are
restored from the original full path specified by the transform list .
Unsecured transforms
Unsecured transforms have not been secured as described in Secured Transforms in
the preceding list. When a package is installed or advertised as a per-user
installation, and the package has unsecured transforms, Windows Installer saves the
unsecured transforms in the Application Data folder in the user's profile. This
enables a user to maintain a customization of a product while roaming from
computer to computer.

44 | P a g e

When the package is installed or advertised as a per-computer installation, and the

package uses unsecured transforms, Windows Installer saves the unsecured
transforms in the %windir%\Installer folder.
If the cached copy of the transform becomes unavailable, Windows Installer can
restore the transform cache using a source listed in the SOURCELIST property.
Windows Installer uses the same method to search for a transform source as it uses
to search for an .msi file.
To apply unsecured transforms when installing a package, pass the transform file
names in the TRANSFORMS property or in the command-line string, and do not
begin the string with the @ or | characters. Do not set the Transforms Secure policy
or the TRANSFORMSSECURE property.

11. MST creation using Tuner (MSI to MST)

Launch Tuner shortcut from AdminStudio tools

Click Create New Transform

45 | P a g e

 Click Browse

Select the .MSI File and Click Open

46 | P a g e

 Click Create

47 | P a g e

48 | P a g e

12. Start the Prevalidation

Select the Prevalidation Tab
Click Start

49 | P a g e

 We will get the below Warnings and Errors.

Click on save button to save the transform file.

50 | P a g e

 .MST File will be opened

Edit the MST file as per requirement.

General Information:

Under this segment we can provide and modify the information about the
installation package. While providing the required details well follow various
standard naming conventions or best practices.

51 | P a g e

Under Install information ->General Information->Summary information-> change

the Summary title and subject to MSI name, update the package code, Author and
keywords. Use the following naming convention for MSI title and subject :
Title/Subject = VendorName_ProductName_Version, where

Vendor Name should not contain more than 8 characters,

Product Name should not contain more than 15 characters,
Version should not contain more than 8 characters .

Under Add or Remove Programs Tab, Disable the change button and Remove
Button. Also select the suitable Display icon .

Click on the Shortcut tab ans any Desktop shortcut is presented Right click
on the shortcut and delete as below screen shot .

52 | P a g e

 Click on Property Manager tab, select the NEW button and then we enter the
standard Properties.

53 | P a g e

 We have to add below mention Properties.

Click on save button to save the transform file.

54 | P a g e

13. Start the Post validation

Click on Build button and select Validate option then select Full MSI Validation
Suite.

55 | P a g e

 We will get the below Warnings and Errors.

If you want to resolve any ICE Errors go through the below mentioned link.
http://msdn.microsoft.com/en-us/library/aa368934(v=vs.85).aspx

56 | P a g e

 Find the .MST file created.

14. Conclusion
The AdminStudio Client tool is installed and ready to use for package the
applications.

57 | P a g e