Re Packager User Guide

Repackager
User Guide
Version 8.0
Repackager 8.0 User Guide
Part Number: RPK-0800-UG00
Product Release Date: 29 November 2006
Copyright Notice
Copyright © 2001–2006 Macrovision Corporation and/or Macrovision Europe Ltd. All Rights Reserved.
This product contains proprietary and confidential technology provided by and owned by Macrovision Europe Ltd., UK, and Macrovision Corporation of
Santa Clara, California, U.S.A. Any use, copying, publication, distribution, display, modification, or transmission of such technology in whole or in part in
any form or by any means without the prior express written permission of Macrovision Europe Ltd. and Macrovision Corporation is strictly prohibited.
Except where expressly provided by Macrovision Europe Ltd. and Macrovision Corporation in writing, possession of this technology shall not be construed
to confer any license or rights under any of Macrovision Europe Ltd. and Macrovision Corporation’s intellectual property rights, whether by estoppel,
implication, or otherwise.
ALL COPIES OF THE TECHNOLOGY and RELATED INFORMATION, IF ALLOWED BY MACROVISION CORPORATION, MUST DISPLAY THIS NOTICE OF
COPYRIGHT AND OWNERSHIP IN FULL.
Trademarks
Macrovision, AdminStudio, InstallShield, FLEXenabled, FLEXlm, FLEXnet, and FLEXnet Manager are registered trademarks or trademarks of Macrovision
Corporation, or other Macrovision companies, in the United States of America and/or other countries. All other brand and product names mentioned
herein are the trademarks and registered trademarks of their respective owners.
Restricted Rights Legend

The software and documentation are “commercial items,” as that term is defined at 48 C.F.R. §2.101, consisting of “commercial computer software” and
“commercial computer software documentation,” as such terms are used in 48 C.F.R. §12.212 or 48 C.F.R. §227.2702, as applicable. Consistent with
48 C.F.R. §12.212 or 48 C.F.R. §227.2702-1 through 227.7202-4, as applicable, the commercial computer software and commercial computer
software documentation are being licensed to U.S. government end users (A) only as commercial items and (B) with only those rights as are granted to all
other end users pursuant to the terms and conditions set forth in the Macrovision Corporation standard commercial agreement for this software.
June 2006
Contents
1 Repackager 8.0 User Guide . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7

Using Help . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8
Help Conventions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8
2 Welcome to Macrovision . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11
Technical Support Resources . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14
Contacting Macrovision Corporation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15
3 Repackaging Legacy Installations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19

About Repackaging. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21
Purpose of Repackaging Applications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21
Repackaging Options Comparison. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22
Repackager Best Practices . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23
About Repackaging on Clean Systems. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24
Alternate-Language Repackaging on Clean Machines . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25
Including the InstallScript Engine With a Windows Installer Package . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25
Launching the Repackager Interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25
Setting Repackager Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26
Selecting Data Display Colors . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26
Specifying Additional Merge Module Directories . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26
Controlling the Display of ICE Validation Warnings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28
Isolating Windows Installer Packages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29
About Application Isolation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29
Isolating Windows Installer Packages Using Application Isolation Wizard . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30
About Assemblies . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30
About Manifests. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31
About Digital Certificates . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32
Repackager 8.0 User Guide RPK-0800-UG00 3

Contents
Setting Isolation Options. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33

Specifying Manifest Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33
Setting Digital Signature Options for Shared Assemblies . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35
Building an Isolated Windows Installer Package . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36
Repackaging Methods. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37
Installation Monitoring Method. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37
Snapshot Method. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38
InstallShield Professional Logging Method . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38
Creating Repackager Projects. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40
Repackaging Legacy Installations Using the Repackaging Wizard. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41
Repackaging Using the Installation Monitoring Method. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42
Repackaging Using the Snapshot Method. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52
Repackaging Using the InstallScript Professional Logging Method . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 71
Repackaging an InstallScript MSI Setup to a Basic MSI Setup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 75
Running the Repackaging Wizard Remotely . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 77
Running the Repackaging Wizard from the Command Line. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 79
Converting Legacy Installations Using the Repackager Interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 80
Converting Repackager 3.x Output Files. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 81
Converting Microsoft SMS Projects . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 81
Converting Novell ZENworks Projects . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 82
Converting WinINSTALL Projects . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 85
Converting Wise Installation Projects . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 85
Converting InstallShield Professional Log Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 86
Chaining Multiple Windows Installer Packages Together . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 86
Configuring Exclusions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 87
Configuring Exclusions Using Repackager . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 87
Excluding Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 88
Excluding All Files in a Directory . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 88
Excluding Directories and Subdirectories . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 88
Excluding Registry Keys . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 89
Excluding Registry Values . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 89
Excluding .ini Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 89
Excluding .ini File Sections . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 90
Excluding Shortcuts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 90
Excluding All Shortcuts in a Directory. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 90
Excluding Shortcuts from Subdirectories . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 91
Specifying the External Configuration File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 91
Modifying External Configuration Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 92
Configuring Exclusions Using the Exclusions Editor. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 93
Exclusions and Repackager . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 93
Exclusions and the OS Snapshot Wizard. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 93
Launching Exclusions Editor . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 94
Excluding Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 96
Excluding Files with Specific Extensions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 97
4 RPK-0800-UG00 Repackager 8.0 User Guide

Contents
Excluding Directories . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 98
Editing Existing File Exclusions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 99
Removing File Exclusions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 99
Excluding .ini Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 100
Excluding Sections from .ini Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 101
Editing Existing .ini File Exclusions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 102
Removing .ini File Exclusions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 103
Excluding Registry Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 104
Editing Existing Registry Exclusions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 105
Removing Registry Exclusions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 106
Working With Repackager Projects . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 106
Building an InstallShield Editor Project . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 107
Building a Windows Installer Package . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 110
Configuring Advanced Conversion Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 114
Viewing Repackager Project Properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 115
Using the Setup Intent Wizard to Detect File Dependencies in a Repackager Project . . . . . . . . . . . . . . . . . . . . . . . . . . . . 116
Creating a Setup Capture Report for a Project . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 117
Saving Repackager Projects . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 118
Opening InstallShield Editor from Repackager . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 119
Scanning InstallShield Professional Setups for Additional Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 119
Creating an InstallShield Editor Template to Use Within Repackager . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 121
Repackager Reference . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 125
Repackager Interface. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 126
Welcome to Repackager Page . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 127
Menus and Toolbar. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 128
Dialog Boxes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 130
Views . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 139
Repackaging Wizard . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 154
Welcome Panel . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 155
Method Selection Panel . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 155
Snapshot Method Panel . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 157
Collect Product Information Panel . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 159
InstallScript MSI Identified Panel . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 161
InstallShield Professional Setup Panel . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 162
Set Target Project Information and Capture Settings Panel . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 163
InstallScript MSI Conversion Output Panel . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 164
Repackaging Panel. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 165
Summary Panel . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 166
Additional Repackaging Wizard Dialog Boxes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 167
Repackaging Wizard Command-Line Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 170
Reboot Handling in the Repackaging Wizard . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 172

Contents
SmartScan Wizard . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 172

Welcome to the SmartScan Wizard Panel . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 174
Original InstallShield Professional Setup Panel . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 175
Scanning Panel . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 176
Setup Feature Tree Panel . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 176
Scanning Media Panel. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 177
Setup Intent Wizard . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 177
Welcome Panel . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 178
Scanning Project Panel . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 178
Results Panel . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 179
VMware Repackaging Wizard . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 180
Welcome Panel . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 180
VMware Virtual Machines Panel . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 180
Exclusions Editor Interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 181
Menus . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 182
Files Tab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 183
.ini Files Tab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 184
Registry Tab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 185
File Exclusion Information Dialog Box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 186
INI File Exclusion Information Dialog Box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 186
Choose Registry Key Dialog Box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 187
Edit Registry Key Dialog Box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 188
About Exclusions Editor Dialog Box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 188
Options.ini File. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 189
Files Associated with Repackager . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 194
Repack.ini File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 196
Troubleshooting. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 196
Troubleshooting Guidelines for WinINSTALL Conversion . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 196
Troubleshooting Guidelines for SMS Conversion . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 197
Resolving an “Error Building Table File” Error . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 198
Index . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 199

1
Repackager 8.0 User Guide
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 organization’s
needs.
Documentation regarding repackaging is presented in the following sections:
Table 1-1: Repackager Help Library
Section Description
About Repackaging Introduces you to repackaging, explains various repackaging methods, lists
Repackaging Best Practices, explains how to include the InstallScript Engine
with a Windows installer package, and reviews Repackager options.
Isolating Windows Installer Isolation reduces versioning conflicts by modifying an application so it always
Packages loads the versions of components—such as DLLs—with which it was
originally developed and tested. This section reviews isolation concepts and
options, and explains how to build an isolated Windows Installer package.
Repackaging Methods Describes the methods of repackaging that Repackager supports.
Creating Repackager Projects Explains how to repackage legacy installations using the Repackaging Wizard
and the Repackager interface. Repackaging produces a Repackager project
file (.irp), which can then be built into an InstallShield Editor project (.ism) or a
Windows Installer package (.msi).
Configuring Exclusions Explains how to use Repackager and the Exclusions Editor to configure the
exclusions used when repackaging a legacy installation.
Working With Repackager Projects Explains how to build an InstallShield Editor project and Windows Installer
package from a Repackager project.
Scanning InstallShield Professional Explains how to scan InstallShield Professional setups for possible additional
Setups for Additional Data files.

Chapter 1: Repackager 8.0 User Guide
Using Help
Table 1-1: Repackager Help Library (cont.)
Section Description
Creating an InstallShield Editor Explains how to create an InstallShield Editor template to use to speed up the
Template to Use Within Repackager Repackaging process.
Repackager Reference Describes Repackager wizards, views, and dialog boxes.
Using Help
Repackager online help can be opened from within the Repackager interface and also from Macrovision
HelpNet Web site.
Repackager Help Library

Help is available both from the Repackager interface Help menu and directly from certain individual
interface elements.
When you have questions about your Macrovision product, first consult the Repackager Help Library.
The Help Library is the complete user’s guide for using Repackager.
Web-Based Online Help

Web-based online help is available to you 24 hours a day, seven days a week, on our Web site at http://
helpnet.macrovision.com.
Help Conventions
In this documentation, reader alert and style conventions are used to bring your attention to specific
information or help you identify information.
Reader Alert Conventions

Reader alerts are used throughout this documentation to notify you of both supplementary and essential
information. The following table explains the meaning of each alert.
Table 1-2: Reader Alert Conventions
Image Alert Name Description
Note Notes are used to draw attention to pieces of information that should stand out.
Important Note Important notes are used for information that is essential for users to read.
Caution Cautions indicate that this information is critical to the success of the desired
feature or product functionality.

Help Conventions
Table 1-2: Reader Alert Conventions (cont.)
Image Alert Name Description
Tip Tips are used to indicate helpful information that could assist you in better utilizing
the desired function or feature.
Best Practices Best Practices alerts instruct you on the best way to accomplish a task.
Edition-Specific Note Edition-specific notes indicate that the information applies to a specific edition of a
product (such as Standard, Professional, or Enterprise edition).
Windows Logo Windows Logo Guideline alerts accompany Microsoft logo compliance
Guideline requirements and recommendations.
Security Security alerts identify security issues.
Procedure The Procedure graphic indicates that procedural instructions follow.
External Web Site Graphic

When this documentation includes a link to an external Web site, that link opens in a new browser
window and is identified by the following graphic:
For more information, see Microsoft MSDN Library .
Style Conventions
The following style conventions are used throughout this documentation.
Table 1-3: Style Conventions
Style Example Description
User Interface On the File menu, click Open. User interface elements appear in bold when
Elements referenced in tasks.
Variables fileName Variables appear in italics.
Code #define HWND_BROADCAST 0xffff Code snippets appear in a monospace

typeface.
User Inputted Type $D(install). Text that is to be entered as a literal value is

Text displayed in a monospace typeface, in bold,
and in blue.
File Name and My files are located in the File names and directory paths are presented
Directory Paths C:\MyDocuments\SampleCode directory. in a monospace typeface.

Help Conventions
Table 1-3: Style Conventions (cont.)
Style Example Description
.INI File Text Insert the line LimitedUI=Y into the file to display Text in .INI files is presented in a monospace
only the Welcome dialog box when the Windows typeface.
Installer package is run.
Command-Line To run the installation silently, enter: Command-line statements and parameters
Statements are presented in a monospace typeface.
Setup.exe /s /v/qn
Environment Set the value of the windir environment variable to Environment variables are presented in a
Variables your monospace typeface.
Examples Create two groups, one called Admins and the Examples are presented in bold.
other called General.
Functions FeatureAddItem adds a new feature to a script- Functions are presented in presented in bold.
created feature set.
Properties In the Name property, enter a name for this custom Properties are presented in bold.
control that is unique among all of the controls in
your project.
Screen Output If you type an incorrect parameter, the message Screen output (from a log file or from the
The system cannot find the path console) is displayed in a monospace
specified. is displayed. typeface, and in blue.
Links Obtain the latest modules, white papers, project Links appear in blue. For external links that
samples, and more from: open in a new window, a New Window graphic
( ) follows the link.
http://www.macrovision.com/downloads

2
Welcome to Macrovision
Macrovision Corporation is the market leader in electronic licensing, installation, and digital rights
management (DRM) technologies. Over 50,000 software vendors and virtually all of the Fortune 1,000
companies use Macrovision’s technologies to maximize the value of their software.
Software Value Management solutions bridge the gap between pricing and packaging software on the
development side, and purchasing and managing that software on the enterprise side. Macrovision
markets the FLEXnet Software Value Management platform, which includes the InstallShield suite of
software installation, repackaging, and update solutions; these solutions are deployed on more than 500
million desktops worldwide. Macrovision holds more than 910 software licensing, DRM, and content
protection patents worldwide. Macrovision is headquartered in Santa Clara, California, and has offices
worldwide.

Chapter 2: Welcome to Macrovision
Macrovision Solutions
Macrovision Solutions
Maximize the Value of Your Software
Software Value Management is a set of best practices that enables software vendors and their enterprise
customers to maximize the value of the software applications they create, use, and maintain.
After an application is developed by the engineering department, publishers use Software Value
Management tools to maximize the application’s revenue potential. These tools include installers and
licensing tools that help publishers flexibly package, price, and protect their products. Their enterprise
customers use Software Value Management tools to maximize the productivity that they get from the
software they purchase. These tools enable corporate IT staff to repackage applications, resolve potential
conflicts, optimize license purchases, and manage updates.
Table 2-1: Macrovision Software Value Management Solutions
Industries & Activities FLEXnet Software Value Management Solutions
Software Vendors: • InstallShield and InstallAnywhere—Tools for authoring installations and

• Market Software software management for any operating system.
• Sell Software • FLEXnet Publisher—Price, package, protect your product, and manage
software licenses throughout the product’s lifecycle to better meet market
• Distribute Software
needs and maximize revenue.
• Service Software
• Renew Software
Enterprise IS and IT: • InstallShield and InstallAnywhere—Tools for authoring installations and
• Buy Software software management for any operating system.
• Prepare & Deploy Software

• FLEXnet Publisher—Price, package, protect your product, and manage
software licenses throughout the product’s lifecycle to better meet market
• Maintain Software needs and maximize revenue.
• Renew Software • AdminStudio—Application packaging, customization, testing, and workflow
management for the enterprise.
• FLEXnet Manager—Maximize the value of your software assets through
accurate usage reporting and centralized license management.
Try a Macrovision Solution Today!

Evaluation copies of Macrovision solutions are available from the Macrovision Web site or from our
sales staff. Visit us online at http://www.macrovision.com, or call today at (800) 809-5659 (North
America) or (44) (117) 903 0650 (Europe, Middle East, and Africa).

Macrovision Professional Services
Macrovision Professional Services

Macrovision offers more than industry-leading software. We also provide training, technical support,
and consulting services that solve all your software installation, updating, and enterprise application
management needs.
Expert Training Services

Whether you’re a novice or an experienced user wishing to refine your skill set, Macrovision’s training
courses are the answer.
Macrovision’s professional trainers are authorities on installation engineering, updating, enterprise
software packaging, software licensing, and license management. They will teach you the skills you need
to become an expert.
• Only Macrovision offers classes run by Macrovision-certified trainers.
• Every class features hands-on training for solving real-world issues.
• Private, on-site courses customized to your company’s needs are also available.
Visit http://www.macrovision.com/services/education/index.shtml today to learn more or fill out our
online form.
Product Support Services

Whenever you need assistance, Macrovision’s technical support staff can answer any question that you
have and help you overcome any issue that you face.
Besides the many award-winning support resources on the Macrovision Web site, Macrovision offers a
number of annually renewable maintenance plans to meet your specific needs.
• Choose the maintenance plan that best fits your needs and budget.
• Get personalized assistance from Macrovision’s senior engineers and support technicians.
Visit http://www.macrovision.com/support/index.shtml to learn more.
Expert Consulting Services

Macrovision is the premier source for installation engineering, updating, enterprise software packaging,
software licensing, and license management services worldwide. Macrovision offers professional
consulting services that enable you to accelerate and increase the value you receive from your
investments in Content and Software Value Management solutions.
• Get the additional expertise you need to complete your projects on time and on budget.
• Achieve professional results without tying up your company’s internal resources.
• Work alongside our experts to learn invaluable techniques and best practices.
Visit http://www.macrovision.com/services/consulting/index.shtml to learn more or fill out our online
form.

Technical Support Resources
Additional Contact Information

Below is contact information for Macrovision Professional Services across the world.
Table 2-2: Additional Contact Information for Macrovision Professional Services
Location Telephone Number
The Americas, Australia, New Zealand (847) 466-6000
Europe, Middle East, Africa (44) (117) 903 0650
Asia-Pacific (81) (3) 5774 6253
Technical Support Resources

Macrovision’s Product Support Services team offers a set of comprehensive resources to help you find
the answers you need. Comprehensive user documentation for your Macrovision product can be found
in the product help library. Also, online resources such as our Knowledge Base provide quick access to
years of experience at no cost, while maintenance plans give you more robust support with our expert
engineers. Take a look at your options below and see which solution is right for you.
Knowledge Base
The Knowledge Base is accessible from the Support section of the Macrovision Web site at http://
www.macrovision.com/support/index.shtml. It contains answers to many commonly asked questions
and includes new information about Repackager that may not appear in the documentation. Click
Repackager on this page to open the Repackager-specific knowledge base. You can use the Knowledge
Base search engine to search articles by phrases, numbers, platforms, and version.
Support Site
In addition to enabling you to search the Knowledge Base, the Macrovision Support site at http://
www.macrovision.com/support/index.shtml helps you:
• Obtain Repackager updates.
• Submit Repackager feedback.
• View webinars.
• Perform Repackager registration.
• Obtain Repackager white papers, case studies, marketing materials, and training materials.
• Obtain object libraries and sample projects.
Online Communities
The online communities are another excellent resource when you have questions about using
Repackager. In these communities, users like you share tips and ideas and help each other get the most
out of Repackager. Visit the communities in the Support section of our Web site, available at http://
community.macrovision.com.

Contacting Macrovision Corporation
Contacting Macrovision Technical Support

Macrovision offers a variety of maintenance plans to fit the individual needs of all of our customers.
Please visit http://www.macrovision.com/support/maintenance.shtml to find the plan that suits you
best.

You may contact us from anywhere in the world by visiting the Macrovision Web site at http://
www.macrovision.com.
United States
Table 2-3: United States Contact Information
Office Address Telephone
Macrovision Corporate Headquarters Macrovision Corporation Tel: (408) 562-8400

Santa Clara Office 2830 De La Cruz Blvd.
Fax: (408) 567-1800
• Video and Music Technologies Santa Clara, CA 95050
Email: corpinfo@ macrovision.com
• FLEXnet Publisher
Macrovision Chicago Office Macrovision Corporation Tel: (847) 466-4000

• Licensing Technologies 900 National Pkwy., Suite 125
Toll Free (800) 374-4353
Schaumburg, IL 60173
• InstallShield Sales: (847) 466-6000
• InstallAnywhere Sales Toll Free: (800) 809-5659
• AdminStudio
Order Fax: (847) 619-0788
• FLEXnet Manager
Macrovision San Francisco Office Macrovision Corporation Tel: (415) 255-3060

• Games Technologies 795 Folsom Street
Fax: (415) 255-0910
2nd Floor - Suite 200
San Francisco, CA 94107 Email: gamesales@macrovision.com
Macrovision New York Office Macrovision Corporation Tel: (212) 219-4400

• Information Commerce Group, 81 Franklin Street, Suite 500
Toll Free: (800) 804-0103
New York, NY 10013
• eMeta Fax: (212) 219-4401
• eRights Suite
• RightAccess
• RightCommerce
• eRightsWEB

Europe, Middle East, and Africa Region
Table 2-4: Europe, Middle East, and Africa Contact Information
Macrovision UK Macrovision UK Ltd. Tel: (44) (870) 871 1111

Maidenhead Office Malvern House
Fax: (44) (870) 871 1161
14-18 Bell Street
Maidenhead
Berkshire, SL6 1BR
United Kingdom
Macrovision UK/Europe Macrovision Corporation Tel: (44) (870) 873 6300

Cheshire Office Vision House, Priory Court
Fax: (44) (192) 870 6329
• FLEXnet Publisher Preston Brook,
Cheshire, WA7 3FR
• FLEXnet Manager United Kingdom
Macrovision UK/Europe Macrovision Corporation Tel: (44) (117) 903 0650

Cheshire Office Vision House, Priory Court
German: (44) (192) 870 6315
• InstallShield Preston Brook,
Cheshire, WA7 3FR French: (44) (192) 870 6314
• InstallAnywhere United Kingdom Spanish: (44) (192) 870 6311
• Update Service
Fax: (44) (192) 870 6329
• AdminStudio
Macrovision France Macrovision Corporation Tel: (33) 1 44 43 53 44

• FLEXnet Manager 33 rue de Galillée
Fax: (33) 1 44 43 53 91
75016 Paris
France For all InstallShield and AdminStudio
inquiries, please call (44) (192) 870-
6314
Macrovision Netherlands Macrovision Corporation Tel: (31) (0) 20 403 7673

• FLEXnet Publisher Busitel 1, Orlyplein 85
Fax: (31) (0) 20 403 7676
1043 DS Amsterdam
• AdminStudio The Netherlands
• FLEXnet Manager
Macrovision Alicante Office Macrovision Corporation Tel: (34) 956 107 771
• Games Technologies Av. Jaime I El Conquistador
Email: gamesales@macrovision.com
1-3 Bajo El Campello
Alicante 03560
Spain

Asia Region
Table 2-5: Macrovision Asia Region Contact Information
Macrovision Corporation Macrovision Corporation Tel: (852) 2868 5131

Greater China Office Unit 301B, 3/F
Fax: (852) 2850 6690
Malaysia Building
50 Gloucester Road, Hong Kong Email: Sales-China@macrovision.com
Macrovision Japan and Asia K.K. Macrovision Corporation Tel: (81) (3) 5774 6253
Japan Office Aoyama Diamond Building 3F
Fax: (81) (3) 5774 6269
1-1-8, Shibuya, Shibuya-ku
Tokyo 150-0002 Japan Email: Sales-Japan@macrovision.com
Macrovision Korea Macrovision Corporation Tel: (82) (2) 6241 5700

Korea Office Suite 417
Fax: (82) (2) 6241 5701
Korea City Air Terminal B/D
159-6 Samsung-dong, Kangnam-ku, Mobile: (82) (11) 779 0445
Seoul 135-728 Korea Email: Sales-Korea@macrovision.com
Macrovision Corporation Macrovision Corporation Tel: (886) (2) 2999 7979

Taiwan Office 6F-13, No. 12, Lane 609, Sec. 5
Fax: (886) (2) 2999 7575
Chung-Hsin Rd., San-Chung
Taipei, Taiwan 241 Email: Sales-Taiwan@macrovision.com


3
Repackaging Legacy Installations
needs.
Documentation regarding repackaging is presented in the following sections:
Table 3-1: Repackager Help Library
Section Description
About Repackaging Introduces you to repackaging, explains various repackaging methods, lists Repackaging
Best Practices, explains how to include the InstallScript Engine with a Windows installer
package, and reviews Repackager options.
Isolating Windows Isolation reduces versioning conflicts by modifying an application so it always loads the
Installer Packages versions of components—such as DLLs—with which it was originally developed and tested.
This section reviews isolation concepts and options, and explains how to build an isolated
Windows Installer package.
Repackaging Methods Describes the methods of repackaging that Repackager supports.
Creating Repackager Explains how to repackage legacy installations using the Repackaging Wizard and the
Projects Repackager interface. Repackaging produces a Repackager project file (.irp), which can
then be built into an InstallShield Editor project (.ism) or a Windows Installer package (.msi).
• Repackaging Legacy Installations Using the Repackaging Wizard
• Converting Legacy Installations Using the Repackager Interface
• Chaining Multiple Windows Installer Packages Together
Configuring Exclusions Explains how to use Repackager and the Exclusions Editor to configure the exclusions used
when repackaging a legacy installation.

Chapter 3: Repackaging Legacy Installations
Table 3-1: Repackager Help Library (cont.)
Section Description
Working With Explains how to build an InstallShield Editor project and Windows Installer package from a
Repackager Projects Repackager project. The topics in this section include:
• Building an InstallShield Editor Project
• Building a Windows Installer Package
• Viewing Repackager Project Properties
• Using the Setup Intent Wizard to Detect File Dependencies in a Repackager Project
• Creating a Setup Capture Report for a Project
• Saving Repackager Projects
• Opening InstallShield Editor from Repackager
Scanning InstallShield Explains how to scan InstallShield Professional setups for possible additional files.
Professional Setups for
Additional Data
Creating an Explains how to create an InstallShield Editor template to use to speed up the Repackaging
InstallShield Editor process.
Template to Use Within
Repackager
Repackager Reference Describes Repackager wizards, views, and dialog boxes.

About Repackaging
About Repackaging
This section introduces you to repackaging, lists Repackaging Best Practices, and explains how to set
Repackager options.
• Purpose of Repackaging Applications
• Repackaging Options Comparison
• Repackager Best Practices
• About Repackaging on Clean Systems
• Including the InstallScript Engine With a Windows Installer Package
• Launching the Repackager Interface
• Setting Repackager Options
Purpose of Repackaging Applications

needs.
Repackaging an installation into a Windows Installer package provides the following benefits:
• Can customize it using InstallShield Editor or Tuner—You can further configure or customize the
Windows Installer package to meet your specific needs by editing the .msi file in InstallShield Editor
or by creating transforms in InstallShield Editor or Tuner.
• Can perform conflict analysis and resolution—You can use ConflictSolver 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.
• 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.

About Repackaging
Repackaging Options Comparison

The following table details the different options available to you when using Repackager, based upon
source type, product and version:
Table 3-2: Repackaging Options Comparison Chart
Source Product / Version Repackaging Method Result
Media IS Professional 1.x to 5.1.x Repackaging Wizard Repackager project with no feature
delineation
Installation Monitoring or Snapshot
IS Professional 5.5 to 7.x Repackaging Wizard Repackager project with feature

delineation, including registry entries
Installation Monitoring or Snapshot
and shortcuts
and SmartScan Wizard
IS InstallScript MSI Repackaging Wizard Repackager project with feature

Installation Monitoring or Single Step
and shortcuts
Snapshot
IS Editor InstallScript Repackaging Wizard Repackager project with feature

IS DevStudio 9.x InstallScript InstallShield Professional Logging
and shortcuts. Also captures path
Method
variables and converts them into
properties (using text substitution
rather than hard-coded path names).
Project Repackager 3.x output (.inc) Repackager Interface Repackager project with no feature
delineation
Microsoft SMS projects (.ipf) Select Open on the File menu to have
Repackager automatically convert file
Novell ZENworks 3.0, 3.1, or 4.0
to a Repackager project
projects (.axt/.aot)
WinINSTALL projects (.txt) (6.0, 6.5,
7.x)
Wise installation projects (.wse)
InstallShield Pro log files (.isl) Repackager Interface Repackager project with feature
delineation
Select Open on the File menu to have
Repackager automatically convert file
to a Repackager project
Once you have created a Repackager project, you can visually examine the files, .ini files, shortcuts, and
registry data from the installation, and exclude any non-essential items. Then, you can build the
Repackager project into an InstallShield Editor project (.ism) for further editing, or create a Windows
Installer package (.msi).

About Repackaging
Repackager Best Practices

When using Repackager, please implement the following Best Practices:
To ensure optimal performance of Repackager during repackaging and when working with Repackager
projects, we recommend that you incorporate the following best practices:
• Capture Everything using the Repackaging Wizard and Exclude Using the Repackager Interface
• Repackage on a Clean System
• Exit All Other Applications
• Run Repackager Over the Network
• Only Repackage Non-Windows Installer Setups
Capture Everything using the Repackaging Wizard and Exclude Using the
Repackager Interface
You should repackage using the provided exclusions and then use the Repackager Interface to visually
remove unwanted items from the capture.
Because this occurs post-capture, you do not need to recapture the legacy setup if you inadvertently
exclude items from the Windows Installer package you are building.
Note: Since Windows Installer does not support packaging device drivers, you would need to create Custom Actions to
install device drivers. See Using Custom Actions in the Windows Installer help section for more information.
Repackage on a Clean System

It is essential that you repackage applications on a “clean” system to ensure you capture all changes
made by the installation, especially when using the Snapshot repackaging method. See About
Repackaging on Clean Systems.
Exit All Other Applications

Other applications may lock files or directories, and may hinder the performance of the setup and
repackaging. Therefore, exit all applications prior to repackaging.
Run Repackager Over the Network

It is essential that you repackage applications on a “clean” system to ensure you capture all changes
made by the installation, especially when using the Snapshot repackaging method. Repackaging on a
clean system provides the following benefits:
• Prevents you from capturing Repackager files—By repackaging on a clean system, you are ensuring
that you do not inadvertently capture Repackager files during repackaging.
• Ensures that you capture all of the necessary setup files—If you do not repackage on a clean system,
you may not capture all of the necessary files for the setup because the files may already be installed
on the system.

About Repackaging
To ensure your machine is completely clean, run Repackager remotely over the network and store
output files to a network drive. For instructions on how to run Repackager over the network, see
Running the Repackaging Wizard Remotely
Tip: The clean system should have a baseline configuration for your target environment, and can be either a physical
computer or a virtual clean system created by a program such as VMware.
Only Repackage Non-Windows Installer Setups

Windows Installer setups should not be repackaged. They should either be edited in InstallShield Editor,
or, as Microsoft recommends, by creating a transform. This can be done using InstallShield Editor or
Tuner.
You should not repackage Windows Installer (.msi) packages for the following reasons:
• Repackaging a Windows Installer package is against Microsoft Best Practices.
• If you make changes to a Windows Installer package, vendors will no longer provide support for that
product.
• If you repackage a Windows Installer package, the component codes within the package are not
retained and hence future patching or upgrades will not work.
• Traditionally, repackaging tools will ignore the Windows Installer-specific data in the Registry. This
will result in an incomplete package.
About Repackaging on Clean Systems

For optimal results when using Repackager or OS Snapshot, you should perform these processes on a
clean system. A clean system typically consists of a computer with only the operating system and
necessary service packs installed on it. It is the baseline system that the computer requires to run.
Although it may be tempting to consider basic software, such as Microsoft Office, as part of the clean
system, this can result in poor snapshots and repackaged setups. Each application you install on the
baseline system adds to the DLLs, changes versions of files, makes new registry entries, etc. This may
cause Repackager or the OS Snapshot Wizard to miss these during capture, which ultimately may lead to
missing files or registry entries in repackaged setups, or unexpected conflicts between the operating
system and Windows Installer packages.
Note: To download a standalone setup for Repackager, go to the following URL:

http://support.installshield.com/kb/view.asp?pcode=ALL&articleid=Q108601
You can copy this to a clean system and install it to run Repackager standalone, instead of with the entire AdminStudio
suite. When installation is complete, the Repackager executable will be located in the following directory:
AdminStudio Installation Directory\Repackager\islc.exe

About Repackaging
Alternate-Language Repackaging on Clean Machines

The standalone Repackager setup for clean machines does not install any language resources other than
US English. Therefore, if you are Repackaging a setup on a clean system in a language other than in US
English, you need to ensure you point to the correct template in the Repackaged Output View.
This can be on a mapped network drive, or you can copy the language-populated template (for example,
ISProjBlankTpl.ism) to your clean system from the AdminStudio Installation
Directory\Editor\Support directory.
Language-specific templates are available when you purchase InstallShield Editor Language Packs.
Including the InstallScript Engine With a Windows Installer

Package
Should you need to include the InstallScript engine with your setup, all the major releases of the
InstallScript engine are available in the InstallScript_Engines folder on the AdminStudio installation
CD. For more information, see the Update to the Latest InstallShield Installation Engines Knowledge
Base article at:
http://consumer.installshield.com/kb.asp?id=Q108322
Launching the Repackager Interface

Repackager can be launched from within the AdminStudio interface. Additionally, if you install
Repackager on a network, use Windows Explorer to browse to the islc.exe executable on the shared
drive.
Task To launch Repackager from the AdminStudio interface:
1. Launch AdminStudio.
2. Click the Tools tab.
3. From the Tools Gallery, click the Repackager icon on the left side.
The Welcome to Repackager Page opens and you can begin the repackaging process.
Note: You can also launch Repackager directly from the Windows Start menu by pointing to All Programs,
Macrovision, Repackager 8.0 Tools, and clicking Repackager.

About Repackaging
Setting Repackager Options

On the Options Dialog Box, which is opened by selecting Options from the Tools menu, you can
specify the following Repackager options:
• Selecting Data Display Colors
• Specifying Additional Merge Module Directories
• Controlling the Display of ICE Validation Warnings
Selecting Data Display Colors

On the Colors tab of the Repackager Options dialog box, you can configure the color of scanned items
and deleted items in Repackager’s exclusion views (Files, .ini Files, Registry Data, and Shortcuts).
Task To change the way excluded and included data is displayed in Repackager:
1. Open the Repackager interface.

2. From the Tools menu, select Options. The Colors tab of the Options dialog box opens.
3. Configure the display colors for Excluded, SmartScan, and Setup Intent items.
4. Click OK.
Specifying Additional Merge Module Directories

If you have custom merge modules that should be used when building a Windows Installer package, you
need to specify the directories that contain those custom merge modules on the Merge Modules tab of
the Options dialog box.
Task To specify directories of additional Merge Modules:

2. From the Tools menu, select Options. The Colors tab of the Options dialog box opens.
3. Open the Merge Modules tab.

About Repackaging
4. Enter the directory paths to the custom merge modules. To specify multiple directories, separate the
folder paths with commas.
Note: You can click Browse and navigate to a directory, but if you browse to a second directory, its directory path
will replace the one you initially selected. Therefore, if you want to specify multiple directories separated by commas,
you need to manually enter the directory paths.
5. Click OK.

About Repackaging
Controlling the Display of ICE Validation Warnings

On the Build Options tab of the Options Dialog Box, you can specify whether or not you want to list
ICE validation warnings in the Repackager output window during the Build process.
Task To set the display of ICE validation warnings during builds:
1. From the Repackager interface, select Options from the Tools menu. The Options dialog box
opens.
2. Open the Build Options tab.
3. To display any ICE validation warnings that occur during the Repackager Build process, select the
Display ICE validation warnings option. By default, this option is not selected.

Isolating Windows Installer Packages

Application isolation is one solution to component versioning conflicts. Isolation reduces versioning
conflicts by modifying an application so it always loads the versions of components—such as DLLs—with
which it was originally developed and tested.
When building a Windows Installer package from your Repackager project, you can also choose to create
an isolated version of that package by selecting an option on the Repackaged Output View.
Information about application isolation is presented in the following topics:
• About Application Isolation
• About Assemblies
• About Manifests
• About Digital Certificates
• Setting Isolation Options
• Building an Isolated Windows Installer Package
About Application Isolation

Application isolation, which is a technique used to minimize the dependencies of an application on
system components or dynamic elements, is one solution to component versioning conflicts. Isolation
reduces versioning conflicts by modifying an application so it always loads the versions of components
and dynamic elements with which it was originally developed and tested.
Isolation is accomplished by:
• Providing DLLs and other shared components for specific applications, and
• Placing information traditionally stored in the Registry into other files that specify the locations of
these isolated components.
Application isolation provides increased stability and reliability for applications because they are
unaffected by changes caused by installation and ongoing maintenance of other applications on the
system.
Depending on the isolation options chosen, you can partially or totally isolate an application. When
using assemblies and manifests to isolate applications for Windows XP systems, the assemblies can be
updated following deployment without necessitating application reinstallation.
Reasons to Isolate Applications

You would want to isolate an application if:
• You want to resolve incompatibilities between different versions of shared components.
• You want to reduce the complexity of the installation by storing COM activation data in a manifest
instead of the registry.
• You want to insulate the application from changes to shared components.

Reasons Not to Isolate an Application

You would not want to isolate an application if, following application isolation, you discover that the
application no longer works because of an internal dependency on a component that has been moved
during the isolation process.
Tip: Following isolation, you can use the Dynamic Dependency Scanner in InstallShield Editor to verify isolated files are
loaded from a different directory.
Isolating Windows Installer Packages Using Application Isolation Wizard

In addition to being able to generate an isolated version of a repackaged setup immediately after the
build step in Repackager, you can also use Application Isolation Wizard to isolate a Windows Installer
package.
Application Isolation Wizard is a stand-alone tool which accepts a Windows Installer package as input
and outputs a new, isolated Windows Installer package.
The Application Isolation Wizard provides a user interface experience that allows the user to extend the
initial “dependency scanning” process for identifying file isolation candidates, while in Repackager you
specify your assembly and digital signing isolation options on the Isolation Options dialog box, and then
those selections are applied to all isolated packages created by Repackager.
About Assemblies
Assemblies are DLLs or other portable executable files that applications require to function. Under
Windows XP, these can be either shared or private. Private assemblies are typically stored in the same
directory as the application they support. Shared assemblies are stored in the WinSxS directory, and are
digitally signed.
By creating manifests for assemblies, Repackager allows you to create self-contained applications that
can use different versions of the same DLL or other portable executable, without any version conflicts.
Shared Assemblies
Shared assemblies are assemblies available to multiple applications on a computer. Applications that
require these assemblies specify their dependence within a manifest. Multiple versions of shared
assemblies can be used by different applications running simultaneously.
These assemblies are stored in the WinSxS directory, and must be digitally signed for authenticity. After
deployment, the version of shared assemblies can be changed, allowing for changes in dependencies.
Private Assemblies
Private assemblies are assemblies created for exclusive use by an application. They are accompanied by
an assembly manifest, which contains information normally stored in the registry. Private assemblies
allow you to totally isolate an application, eliminating the possibility that dependent files may be
overwritten by other applications.
These assemblies are always stored in the same location as their associated executable.

About Manifests
Manifests, which are used during isolation, are XML files that describe an application. Repackager can
create two types of manifests: application manifests and assembly manifest.
Application Manifests Describe an Isolated Application

Application manifests are XML files that describe an isolated application. This descriptive information
includes the relationship between the application and its dependent files.
Typically, the naming convention for a manifest is:
ApplicationName.Extension.manifest
For example, if the application was HelloWorld.exe, the manifest file is called:
HelloWorld.exe.manifest
Assembly Manifests Describe an Application’s Assemblies

Assembly manifests are XML files that describe an application’s assemblies. This includes components
such as DLLs.
Information stored in the assembly manifest, such as COM registration information, ProgIDs, etc., is
usually stored in the Registry. However, by making it independent from the Registry, only that
application can use the dependent files described in the manifest. This enables you to have multiple
versions of the same DLL or other portable executable file on a system without generating compatibility
conflicts.
Typically, the naming convention for a manifest is:
AssemblyName.Extension.manifest
For example, if the component was Goodbye.dll, the manifest file is called:
Goodbye.dll.manifest
Manifests as New Components

When you create manifests, Repackager supports putting them into new components. If you do not
select the Create new component for each assembly option on the Manifest Options tab of the
Isolation Options dialog box, the manifest will be added to the same component as the assembly.

About Digital Certificates

Digital certificates identify you and/or your company to end users to assure them the assembly they are
about to use has not been altered. They are issued by a certification authority such as VeriSign, or
created using a combination of software publishing credentials (.spc) and a private key (.pvk), both also
issued by a certification authority. The certificate includes the public cryptograph key, and, when used in
combination with a private key, can be used by end users to verify the authenticity of the signor.
The following digital certificate concepts are defined in this topic:
• Private Keys
• Software Publishing Credentials
• Using a Certificate Store
• Creating a Certificate File
Private Keys
A private key (a file with the extension .pvk) is granted by a certification authority. Repackager uses the
private key you enter in the Digital Signature tab of the Isolation Options dialog box to digitally sign
your shared assembly and ensure end users of its content's authenticity.
The .spc (Software Publishing Credentials) file and .pvk file you enter in the Digital Signature tab
compose the digital certificate for shared assemblies.
Contact a certification authority such as VeriSign for more information on the specifics of software
publishing credentials.
Software Publishing Credentials

You must supply a certification authority with specific information about your company and software to
obtain software publishing credentials in the form of an .spc file. Your software publishing credentials
are used to generate a digital signature for your assembly.
The .spc file and .pvk (private key) file you enter as in the Digital Signature tab of the Advanced Options
dialog box compose the digital certificate for shared assemblies.
Contact a certification authority such as VeriSign for more information on the specifics of software
publishing credentials.
Using a Certificate Store

To perform code signing, both private key and software publishing credential information must be
supplied. This must occur each time a package is signed. Most server operating systems store a
certificate locally on the computer that the user used to request the credential information.
Instead of having to store credential files on each of the user computers, you can create a Certificate
Store, a storage location which will have numerous certificates, which enables all users or computers
with adequate permissions to retrieve the certificate as needed.
Using a Certificate Store allows you to associate the same credentials and private key files with multiple
packages. This simplification is particularly useful when isolating applications, as typically the code
signing information will be identical for all shared assemblies. Ultimately, the Certificate Store removes
the burden of managing private key and software publishing credential information.

Creating a Certificate File

You can create a certificate file from the constituent PVK and SPC files and import it into the Certificate
Store using the PVK Digital Certificate Files Importer. You can then export the certificate (.cer) file for
use outside of the Certificate Store.
Caution: Certificate files must be 2048-bit or higher. For more information, see the article: Assembly Signing Example on
the Microsoft Developer Network Web site.
Setting Isolation Options

Application isolation is one solution to component versioning conflicts. Isolation reduces versioning
conflicts by modifying an application so it always loads the versions of components—such as DLLs—with
which it was originally developed and tested.
On the Isolation Options Dialog Box, which is opened by selecting Isolation Options from the Tools
menu, you can specify the following Repackager isolation options:
• Assembly Options—Specify the type of assemblies Repackager will create: private side-by-side
assemblies in the application folder or shared side-by-side assemblies in the WinSxS folder. You can
also specify the assembly naming conventions. See Specifying Manifest Options
• Digital Signature Options—You can configure the certificate information required when using shared
assemblies. This required digital signature provides an extra layer of protection, allowing you to
obtain information about the company who created a global assembly. See Setting Digital Signature
Options for Shared Assemblies.
Specifying Manifest Options

On the Manifest Options tab of the Isolation Options Dialog Box, which is opened by selecting
Isolation Options from the Tools menu, you can specify the following options:
• Selecting the Assembly Type
• Specifying the Assembly Naming Conventions
Note: For more information on assemblies and manifests, see About Assemblies and About Manifests.

Selecting the Assembly Type

Isolation Options from the Tools menu, you can specify the type of assemblies Repackager will
create: private side-by-side assemblies in the application folder or shared side-by-side assemblies in the
WinSxS folder.
Task To select the assembly type:

2. From the Tools menu, select Isolation Options. The Manifest Options tab of the Isolation
Options dialog box opens.
3. Select one of the following Assembly Type options:
• Create private side-by-side assemblies in the application folder
• Create shared side-by-side assemblies in WinSxS directory.
Note: Manifests for shared assemblies must be digitally signed. See Setting Digital Signature Options for Shared
Assemblies.
Note: The modifications you make on the Isolation Options dialog box will be recorded in the isolationconfig.ini
file, which is stored in the AdminStudio Shared directory.

Specifying the Assembly Naming Conventions

Isolation Options from the Tools menu, you can specify the type of naming conventions Repackager
will use when creating assemblies.
Task To set the default naming convention for assemblies:

3. In the Assembly Naming Conventions area, Enter your Company name and Division. These
two fields create the default assembly naming convention (in the form Company.Division.Assembly
followed by a number).
4. If you want to create a new component for each assembly, select the Create new component for
each assembly option.
Assemblies created during application isolation will follow the naming convention as specified.
Note: The modifications you make on the Isolation Options dialog box will be recorded in the isolationconfig.ini file,
which is stored in the AdminStudio Shared directory.
Setting Digital Signature Options for Shared Assemblies

You can configure the certificate information required when using shared assemblies on the Digital
Signature tab of the Isolation Options dialog box.This required digital signature provides an extra layer
of protection, allowing you to obtain information about the company who created a global assembly.
Note: The modifications you make on the Isolation Options dialog box will be recorded in the isolationconfig.ini file,
which is stored in the AdminStudio Shared directory.
Note: For more information, see About Digital Certificates.
Task To set digital signature options:

3. Open the Digital Signatures tab.

4. Click the Browse ( ) button next to the Certificate File field and navigate to the certificate file
you are using to sign assemblies.
A digital certificate identifies you and/or your company to end users and assures them the data they
are about to receive has not been altered.
5. In the Code Signing Technology area, select the type of code signing technology you want to use
for the digital signature. You can use one of the following technologies:
Technology Description
Credentials Select this option to use credential files as the code signing technology. If you select
this option, you must supply the name and location of both your software publishing
credential files:
• SPC File—Specify the name and location of your software publishing credentials
file (.spc).
• PVK—Specify the name and location of your private key file (.pvk).
In order to receive a software publishing credentials and a private key, you must
supply a certification authority, such as such as VeriSign, with specific information
about your company and software.
Certificate Name in the Select this option to use the name of an existing certificate file in the Certificate Store
store as the code signing technology. The Certificate Store is a central repository for
certificate files. Using a Certificate Store allows you to reuse the certificate files for
different purposes as necessary.
As an alternative to providing .spc and .pvk files, you can specify the certificate
name as it appears in the certificate store.
Building an Isolated Windows Installer Package

To reduce versioning conflicts by modifying an application so it always loads the versions of
components—such as DLLs—with which it was originally developed and tested, select the Create an
isolated version of the Windows Installer package. An additional Windows Installer package
will be created in the same directory as the .ism file and the other .msi file, with the naming convention
of:
appname.isolated.msi
For more information on how Repackager isolates applications and the available isolation options, see
Isolating Windows Installer Packages.

Repackaging Methods
Repackaging Methods
Repackager supports three methods of repackaging:
Table 3-3: Repackaging Methods
Repackaging Method Description
Installation Monitoring Repackager monitors system changes as an application is installed, and that data can be
Method converted into a Windows Installer package. Installation Monitoring is the default method.
Snapshot Method Repackager compares a system snapshot before and after an installation, determines the
changes that were made, and that data can be converted to a Windows Installer package.
InstallShield Repackager reads logged output of InstallShield Editor and DevStudio 9.x InstallScript
Professional Logging installations to obtain additional information that would not be captured by repackaging,
Method such as path variables and a feature tree.
Installation Monitoring Method

When using the Installation Monitoring method, the Repackaging Wizard monitors a system for any
processes that are created during an installation. The Installation Monitoring method determines the
dynamic interdependencies between files.
By monitoring these processes in the background, the Repackaging Wizard can identify files, shell links,
and registry entries that are added, modified, or removed by the installation. The resulting files and
Repackager output file can be converted into a Windows Installer package.
Installation Monitoring Method Considerations

Consider the following about Installation Monitoring when selecting a repackaging method:
• Faster than Snapshot—Installation Monitoring is significantly faster than the Snapshot repackaging
method.
• Clean system not required—Although it is still a good practice to repackage on a clean system, it is not
as important when using Installation Monitoring technology as it is when you use the Snapshot
method.
• Can exclude processes from the project—When using the Installation Monitoring method, you can
specify the processes that you want to exclude from the Installation Monitoring.

Repackaging Methods
Snapshot Method
When using the Snapshot method, the Repackaging Wizard takes a reference snapshot of a system as a
baseline configuration, performs the installation, and then takes a second snapshot.
The difference between the two snapshots is stored in a directory you specify, along with the Repackager
output file (.inc). This file can then be converted into a Windows Installer package (.msi) using
Repackager.
Snapshot Method Considerations

Consider the following about Snapshot technology when selecting a repackaging method:
• Slower than Installation Monitoring—The Snapshot method is significantly slower than the Installation
Monitoring repackaging method.
• Clean system is required—When repackaging using Snapshot technology, you should use a clean
system, with a baseline configuration for your target environment. If you do not repackage on a
clean system, you may not capture all of the necessary files for the setup because the files may
already be installed on the system.
InstallShield Professional Logging Method
Note: The InstallShield Professional Logging Method is supported for InstallShield Editor and DevStudio 9.x InstallScript
installations.
Using the InstallShield Professional Logging Method, Repackager can read logged output of
InstallShield Editor and DevStudio 9.x InstallScript installations. This enables Repackager to capture
additional information from those installations that would not be captured by the Installation
Monitoring or Snapshot methods: path variables and the feature tree.
Path Variables
When using the InstallShield Professional Logging Method, path variables are captured and converted
into properties (using text substitution rather than hard-coded path names).
For example, if you were using a standard repackaging method, the path name of the application’s
executable file would be captured as follows:
C:\Program Files\CompanyName\ApplicationName\ProgramName.exe
When using the InstallShield Professional Logging Method, the executable path name would be
captured using a path variable instead of a hard-coded path name:

Repackaging Methods
[INSTALLDIR]\ProgramName.exe
Feature Tree
The InstallShield Professional Logging Method is able to group files, shortcuts and registry entries into
features corresponding to InstallShield Professional components. Any items (files, folders, shortcuts, or
registry entries) that are attached to a component directly or indirectly (through File Groups), are
attached to corresponding features.
If you do not use the InstallShield Professional Logging Method to repackage a InstallShield Editor or
DevStudio 9.x InstallScript installation, all files, shortcuts and registry entries would be installed
together as one feature.
Selecting the InstallShield Professional Logging Method

You access the InstallShield Professional Logging Method through the Repackaging Wizard, but
InstallShield Professional Logging Method is not offered as a choice on the Method Selection
Panel of the Repackaging Wizard. Only Installation Monitoring and Snapshot are listed:
When you are repackaging a InstallShield Editor or DevStudio 9.x InstallScript installation and want to
use the InstallShield Professional Logging Method, you can select either Installation Monitoring or
Snapshot on the Method Selection Panel. However, if you select the Snapshot method, you must
select Single Step on the Snapshot Method Panel (which would open next).
Caution: If you select the Snapshot / Multiple Steps repackaging method, Repackager will not recognize the setup as an
InstallShield Editor or DevStudio 9.x InstallScript installation and the InstallShield Professional Setup Panel will not open.

Creating Repackager Projects
After you select the Installation Monitoring or Snapshot method, and then specify an InstallShield
Editor or DevStudio 9.x InstallScript installation on the Repackaging Wizard’s Collect Product
Information Panel, Repackager will automatically detect the InstallScript installation and will display
the InstallShield Professional Setup Panel. On this panel, you can choose to use the InstallShield
Professional Logging Method instead of the repackaging method you chose on the Method
Selection Panel.
For instructions on how to use the InstallShield Professional Logging Method when repackaging
InstallShield Editor or DevStudio 9.x InstallScript installations, see Repackaging Using the InstallScript
Professional Logging Method and InstallShield Professional Setup Panel.

Repackager projects (.irp) allow you to visually analyze the files, .ini files, shortcuts, and registry
entries captured or changed during the conversion of a legacy setup into a Windows Installer package.
You can also exclude files, shortcuts, registry entries, and .ini files from the resulting Windows Installer
package, without affecting the original setup data.
There are two methods of creating Repackager projects:
Table 3-4: Methods of Creating Repackager Projects
Method Installation Source
Repackaging You can use the Repackaging Wizard to convert the following installations:
Wizard
• InstallShield Professional 1.x to 5.1.x
• InstallShield Professional 5.5 to 7.x
• InstallShield InstallScript MSI
• InstallShield DevStudio 9.x InstallScript
• InstallShield Editor InstallScript
See Repackaging Legacy Installations Using the Repackaging Wizard.
Repackager You can use the Repackager interface to convert the following installations:
Interface
• Repackager 3.x output (.inc)
• Microsoft SMS projects (.ipf)
• Novell ZENworks 3.0, 3.1, or 4.0 projects (.axt/.aot)
• WinINSTALL projects (.txt) (6.0, 6.5, 7.x)
• Wise installation projects (.wse)
• InstallShield Professional log files (.isl)
See Converting Legacy Installations Using the Repackager Interface.

Repackaging Legacy Installations Using the Repackaging

Wizard
One frequently used method of creating a Repackager project is to repackage a legacy setup.
Fundamentally, this involves monitoring the execution of a non-Windows Installer setup and converting
changes made by the setup into a Windows Installer file.
Repackager provides the Repackaging Wizard for accomplishing this task. Using this Wizard, you can
select the repackaging method (either Snapshot or Installation Monitoring), specify the setup(s) you
want to repackage, and run the setup(s). When the Repackaging Wizard has finished its analysis,
Repackager automatically creates a Repackager project (.irp) file, which can be modified in Repackager.
You can then convert this file to an InstallShield Editor project (.ism) for further editing, or convert it
directly to a Windows Installer package (.msi).
Note: For InstallShield Editor or DevStudio 9.x InstallScript installations, you can choose to use the InstallShield
Professional Logging Method instead of the Snapshot or Installation Monitoring methods.
When using the Repackaging Wizard to repackage a legacy setup, you can use any of the following
methods:
Table 3-5: Repackaging Methods
Repackaging Method Description
Installation Repackager monitors system changes as an application is installed, and that data can be
Monitoring Method converted into a Windows Installer package. Installation Monitoring is the default method.
See Repackaging Using the Installation Monitoring Method.
Snapshot Method Repackager compares a system snapshot before and after an installation, determines the
changes that were made, and that data can be converted to a Windows Installer package.
This is the default method.
See Repackaging Using the Snapshot Method.
InstallShield Repackager reads logged output of InstallShield Editor and DevStudio 9.x InstallScript
Professional Logging installations, allowing you to get additional information that would not be captured by standard
Method repackaging.
See Repackaging Using the InstallScript Professional Logging Method.
Using InstallScript You can use the Repackaging Wizard and InstallScript Scan to convert an InstallScript MSI
Scan installation to a Basic MSI package with InstallScript support. InstallScript Scan preserves the
original components and much of the InstallScript installation logic, architecture, and
maintainability of the original installation package.
See Repackaging an InstallScript MSI Setup to a Basic MSI Setup

Repackaging Using the Installation Monitoring Method

When you choose the Installation Monitoring method of repackaging, Repackager monitors system
changes as an application is installed, and then you can convert that data into a Windows Installer
package. Installation Monitoring is the default method.
To repackage an installation using the Installation Monitoring method, perform the following steps:
• Step 1: Selecting the Repackaging Method.
• Step 2: Excluding Processes (Optional)
• Step 3: Collecting Product Information
• Step 4: Adding Additional Setup Programs (Optional)
• Step 5: Set Target Project Information
• Step 6: Set Capture Settings (Optional)
• Step 7: Beginning the Repackaging Process
Step 1: Selecting the Repackaging Method

In this step, you launch the Repackaging Wizard and select the Installation Monitoring repackaging
method.
Task To select a repackaging method:
1. From the Repackager interface, launch the Repackaging Wizard by clicking on the link or by
selecting Repackaging Wizard from the Tools menu. The Welcome Panel opens.

2. Click Next. The Method Selection Panel opens.
3. Select Installation Monitoring.
Note: The InstallShield Professional Logging Method, which should be used to repackage InstallShield Editor and
DevStudio 9.x InstallScript installations, is not offered as a choice on the Method Selection panel. See Repackaging
Using the InstallScript Professional Logging Method for more information on using that method.
4. Continue with Step 2: Excluding Processes (Optional).

Step 2: Excluding Processes (Optional)

During Installation Monitoring, Repackager captures all of the activity of each service or process
running on the machine, and then processes this collected data. However, many services running on a
machine may have nothing to do with the installation being repackaged.
• If you want to modify the default excluded processes list, perform the following steps.
• If you do not want to modify the default excluded processes list, continue with Step 3: Collecting
Product Information.
Tip: If you know that the installation that you are capturing is from a self-extracting .exe file and if you want to use the
Installation Monitoring method, you should add the name of that .exe file to the excluded processes list.
Task To exclude processes from Installation Monitoring:
1. On the Method Selection Panel, click the Advanced Settings link. The Excluded Processes dialog
box opens, listing a default set of processes.
2. To add a process to this list, click the New ( ) button to add a new blank line to this list, and enter
the name of the process that you want to exclude.
3. To delete a process from this list, select the process and click the Delete ( ) button.
Note: The changes you make to the excluded processes list are persisted for future Repackaging sessions.
Therefore, once you have entered an appropriate set of processes to exclude for your machine, you can skip this
optional step.
4. Click OK to return to the Method Selection Panel.

5. Continue with Step 3: Collecting Product Information.

Step 3: Collecting Product Information

In this step, you will specify the installation you want to repackage and enter any command-line
arguments to be used when the installation is run.
Task To enter product information:
1. On the Method Selection Panel, click Next. The Collect Product Information Panel opens.
2. Click the Browse ( ) button next to the Program File field and select the installation program
that you are repackaging.
3. In the Command-line Argument(s) field, enter any command-line arguments to be used when
the installation is run.
4. In the Product Information area, modify the Product Name, Version, and Company Name,
as necessary.
5. If you want to associate Web sites with this installation, click the More link to open the Additional
Product Information dialog box, enter the Product URL and Support URL for the application
you are repackaging, and click OK.
6. Continue with Step 4: Adding Additional Setup Programs (Optional).

Step 4: Adding Additional Setup Programs (Optional)

You can specify additional setup programs to repackage together with this installation. Additional setup
programs share the same product name, version number, and company name in the repackaged
installation. However, as you locate each additional setup program to repackage, you can specify
command-line parameters pertaining only to that setup. You can also specify the order in which the
setups are run, should it be necessary.
• If you want to add additional setup programs, perform the following steps.
• If you do not want to add additional setup programs, continue with Step 5: Set Target Project
Information.
Task To add additional setup programs, perform the following steps:
1. On the Collect Product Information Panel, click the Edit Setup List link. The Additional Setup
Programs dialog box opens.
2. If you want to add a setup program, perform the following steps:

a. Click New. The Setup Information dialog box opens.
b. Click the Browse ( ) button next to the Program File field and select the setup program that
you want to add.
c. In the Command-line Argument(s) field, enter any command-line arguments to be used
when this setup is run.

d. Click OK to return to the Additional Setup Programs dialog box.

e. If necessary, click the Up and Down buttons to change the order in which the setups are run.
3. If you want to edit an existing setup program, perform the following steps:
a. On the Additional Setup Programs dialog box, select the program that you want to edit and click
Edit. The Setup Information dialog box opens.
b. Modify the Program File and Command-line Argument(s) fields.

c. Click OK to return to the Additional Setup Programs dialog box.
4. If you want to delete a listed setup program, perform the following steps:
a. Select the program that you want to delete and click Delete. A dialog box opens prompting you
to confirm the deletion.
b. Click OK to confirm the deletion and return to the Additional Setup Programs dialog box, where
the deleted program is no longer listed.
5. Click OK to return to the Collect Product Information panel.
6. Continue with Step 5: Set Target Project Information.

Step 5: Set Target Project Information

In this step, you identify the location where you want files created by Repackager to be stored. For the
Installation Monitoring repackaging method, it is recommended that this location not be located on
your clean machine, but rather on the same machine as the Repackager executable (most likely on your
administrator machine).
Task To set target project information and capture settings:
1. On the Collect Product Information Panel, click Next. The Set Target Project Information and
Capture Settings Panel opens.
Note: If you specified an InstallShield Editor or DevStudio 9.x InstallScript installation in the Program File field of the
Collect Product Information Panel, the InstallShield Professional Setup Panel appears instead of the Set Target Project
Information and Capture Settings Panel. See Repackaging Using the InstallScript Professional Logging Method.
2. Click the Browse ( ) button next to the Project path to store files field and select the directory
where you want the Repackaging Wizard to place its output, including the Repackager project file
(.irp), the Repackaging Wizard output files, and source files.
You can also enter the name of a new folder in the Project path to store files field, and you will be
prompted to create it when you exit this panel.
3. Continue with Step 6: Set Capture Settings (Optional).

Step 6: Set Capture Settings (Optional)

From the Set Target Project Information and Capture Settings Panel, you can specify the following
capture types for the repackaging session:
• Files and deleted files
• .ini files and .ini files with non-.ini extensions
• Shortcuts
• Registry data and deleted registry data

Options set in this dialog box apply to the current and subsequent repackaging sessions.
• If you want to set capture settings, perform the following steps.
• If you do not want to set capture settings, continue with Step 7: Beginning the Repackaging Process.
Task To set capture settings:
1. On the Set Target Project Information and Capture Settings Panel, click Edit. The Analysis Options
dialog box opens.
Note: Options set in this dialog box apply to the current and subsequent repackaging sessions.

2. Select the capture types that you want to use for this repackaging session:
• Files
• Deleted files
• INI files
• (INI files with) Non-.ini extensions
• Shortcuts
• Registry data
• Deleted registry data

3. Click OK to return to the Set Target Project Information and Capture Settings Panel.
4. Continue with Step 7: Beginning the Repackaging Process.
Step 7: Beginning the Repackaging Process

In this step you will begin the repackaging process.
Task To begin the repackaging process:
1. To begin the repackaging process, click Start on the Set Target Project Information and Capture
Settings Panel. The Repackaging Panel opens and the Repackaging Wizard captures the initial
system status. Then, the selected setup program will be launched.
2. Follow the prompts until the installation has completed. When the installation is complete, you are
prompted to make any additional changes to the system (such as deleting files and shortcuts) that
you want to be recorded in this repackaged installation.

3. When you are ready to complete the repackaging process, click Process. The Repackaging Wizard
then analyzes the system and setup data that it collected.
Following repackaging, the Summary Panel is displayed, providing confirmation that the
repackaging was successful.
4. Click Finish. Repackager launches and opens the Repackager project file (*.irp) that you just
created.
5. Continue with the instructions in Working With Repackager Projects.

Repackaging Using the Snapshot Method

When using the Snapshot method of repackaging, the Repackaging Wizard takes a reference snapshot
of a system as a baseline configuration, performs the installation, and then takes a second snapshot.
The difference between the two snapshots is stored in a directory you specify, including the Repackager
project file (.irp), the Repackaging Wizard output files, and the source files. The Repackager project file
can then be converted into a Windows Installer package (.msi).
Types of Snapshot Repackaging

There are two types of Snapshot repackaging:
Single Step
When Repackaging in a single step:
• You specify at least one setup program to repackage.
• Repackager first takes an initial system snapshot.
• Repackager then runs the setup program(s) you selected.
• Then Repackager takes a second snapshot to create the script file that can be converted into a
You also have the option of requiring the Repackager to prompt you before running the setup
program(s), allowing you the opportunity to make changes to your system that you want included in the
final package.
See Performing Single Step Snapshot Repackaging.
Multiple Step
When repackaging in multiple steps:
• You to run the Repackager to obtain an initial system snapshot, after which the Repackager exits.
• You can then perform any modifications to the system, such as changing configurations, running
installations, and so forth.
• After making the necessary modifications, you would then run the Repackager again to analyze
system status changes.
The difference between the second Repackager execution and the first results in the script file that
ultimately can be converted into a Windows Installer package.
See Performing Multiple Step Snapshot Repackaging.

Performing Multiple Step Snapshot Repackaging

To repackage an installation using the Multiple Step Snapshot method, perform the following steps:
• Step 2: Initial Analysis
• Step 3: Install Setup and Make Manual System Changes
• Step 4: Entering Product Information

In this step, you launch the Repackaging Wizard and select the Snapshot repackaging method.

DevStudio 9.x InstallScript installations, is not offered as a choice on the Method Selection panel. See Repackaging
Using the InstallScript Professional Logging Method for more information on using that method.
3. Select Snapshot and click Next. The Snapshot Method panel opens.
4. On the Snapshot Method panel, select Multiple Steps. The Analyze the initial system status
option is enabled.
5. Select the Analyze the initial system status option.
6. Continue with Step 2: Initial Analysis.

Step 2: Initial Analysis

In this step, the Repackaging Wizard takes an initial snapshot of your system.
Task To perform initial analysis:
1. On the Snapshot Method panel, click Next. The Repackaging Panel of the Repackaging Wizard
opens, displaying the progress of the initial system status capture.
When Repackager finishes capturing the initial system status, the Summary panel opens,
prompting you to install the application you are repackaging.

2. Click Finish to close the Repackaging Wizard.

3. Continue with Step 3: Install Setup and Make Manual System Changes.
Step 3: Install Setup and Make Manual System Changes

In this step, you will manually launch the installation of the application you are repackaging, and then
you will make any manual changes to the system that you want captured in the Windows Installer
package.
Task To install setup and make manual system changes:
1. Launch the installation program of the application you are repackaging.

2. Follow the prompts until the installation has completed.
3. When the installation is complete, make any additional changes to the system (such as deleting files
and shortcuts) that you want to be recorded in this repackaged installation.
4. Launch the Repackaging Wizard again. The Welcome Panel opens.
6. Select Snapshot and click Next. The Snapshot Method Panel opens with Multiple Steps
already selected, and the Analyze system status changes option now enabled and selected.
7. Continue with Step 4: Entering Product Information.

Step 4: Entering Product Information

In this step, you will enter product information for the application that you just installed.
1. On the Snapshot Method Panel, click Next. The Collect Product Information Panel opens.
Because you are now performing the second step of a multiple-step Snapshot, the Setup
Programs area is disabled (because you have already installed the application you are
repackaging).
as necessary.
3. If you want to associate Web sites with this installation package, perform the following steps:
a. Click the More link. The Additional Product Information dialog box opens.
b. Enter the Product URL and Support URL for the application you are repackaging.
c. Click OK.
4. Continue with Step 5: Set Target Project Information.


In this step, you identify the location where you want files created by Repackager to be stored.
Task To set target project information and capture settings:
1. On the Collect Product Information Panel, click Next. The Set Target Project
Information and Capture Settings Panel opens.

From the Set Target Project Information and Capture Settings Panel, you can specify capture
types for the repackaging session such as files, .ini files, shortcuts, and Registry data. You can also
restrict directory analysis to specific directories, which can significantly improve repackaging
performance.
• If you want to modify the default capture settings, perform the following steps.
• If you do not want to modify the default capture settings, click Next and continue with Step 7:
Beginning the Repackaging Process.

Task To modify capture settings:
1. On the Set Target Project Information and Capture Settings Panel, click Edit. The
Analysis Options dialog box opens.
• Files
• Deleted files
• INI files
• Shortcuts
• Registry data

3. If you want to restrict directory analysis to specific directories, click New. The Choose Directory
dialog box opens.
4. Select a directory and click OK. The selected directory is now listed on the Analysis Option dialog
box.
5. If you want to modify an existing restriction, or delete a restriction, select the directory and click
Edit or Delete.


Settings Panel. The Repackaging Panel opens and the Repackaging Wizard captures the system
state changes.
When the Repackaging Wizard has finished analyzing the system state changes and creating the
Repackager project, the Summary Panel opens, providing confirmation that the repackaging was
successful and listing the location of your new Repackager project.

created.
Performing Single Step Snapshot Repackaging

To repackage an installation using the Single Step Snapshot method, perform the following steps:
• Step 2: Collecting Product Information


In this step, you launch the Repackaging Wizard and select the Snapshot repackaging method.

DevStudio 9.x InstallScript setups, is not offered as a choice on the Method Selection panel. See Repackaging Using
the InstallScript Professional Logging Method for more information on using that method.
3. Select Snapshot and click Next. The Snapshot Method panel opens.
4. On the Snapshot Method panel, select Single Step.

5. If you want to be prompted before the selected setup program is launched, select the Prompt
before running the setup program(s) option. If you do not select this option, the setup
program will automatically be launched as soon as the Repackaging Wizard has finished analyzing
the system status.
6. Continue with Step 2: Collecting Product Information.

Step 2: Collecting Product Information

In this step, you will specify the installation you want to repackage and enter any command-line
arguments to be used when the installation is run.
1. On the Snapshot Method panel, click Next. The Collect Product Information Panel opens with the
Setup Programs and Product Information areas enabled.
2. Click the Browse ( ) button next to the Program File field and select the installation program
that you are repackaging.
as necessary.

c. Click OK.
6. Continue with Step 3: Set Target Project Information .

In this step, you identify the location where you want files created by Repackager to be stored.
Task To set target project information:
1. On the Collect Product Information Panel, click Next. The Set Target Project Information and
Capture Settings Panel opens.


From the Set Target Project Information and Capture Settings Panel, you can specify capture
types for the repackaging session such as files, .ini files, shortcuts, and Registry data. You can also
restrict directory analysis to specific directories, which can significantly improve repackaging
performance.
• If you want to modify the default capture settings, perform the following steps.
• If you do not want to modify the default capture settings, click Next and continue with Step 7:
Beginning the Repackaging Process.
Task To modify capture settings:
1. On the Set Target Project Information and Capture Settings Panel, click Edit. The
Analysis Options dialog box opens.
• Files
• Deleted files
• INI files
• Shortcuts
• Registry data

3. If you want to restrict directory analysis to specific directories, click New. The Choose Directory
dialog box opens.
4. Select a directory and click OK. The selected directory is now listed on the Analysis Option dialog
box.
5. If you want to modify an existing restriction, or delete a restriction, select the directory and click
Edit or Delete.


1. To begin the repackaging process, click Start on the Set Target Project Information and
Capture Settings Panel. The Repackaging Panel opens and the Repackaging Wizard captures
the initial system status.
Depending upon whether you chose the Prompt before running the setup program(s) option
on the Snapshot Method Panel, either the installation that you selected will start or you will be
prompted to start it.
2. Install the application by following the prompts until the installation has completed.
3. When the installation is complete, you are prompted to make any additional changes to the system
(such as deleting files and shortcuts) that you want to be recorded in this repackaged installation.

4. When you are ready to complete the repackaging process, click Process. The Repackaging Wizard
then analyzes the system and setup data that it collected.
Following repackaging, the Summary Panel is displayed, providing confirmation that the
repackaging was successful and listing the location of the Repackager project that was just created.
created.

Repackaging Using the InstallScript Professional Logging Method

If you are repackaging an InstallShield Editor or DevStudio 9.x InstallScript installation, you can use the
InstallShield Professional Logging Method to read logged output of those setups to obtain additional
information that would not be captured by the Installation Monitoring or Snapshot methods: Path
Variables and the Feature Tree.
See InstallShield Professional Logging Method for more information.
Using the InstallScript Professional Logging Method

To repackage an InstallShield Editor or DevStudio 9.x installation using the InstallScript Professional
Logging Method, perform the following steps:
Task To repackage using the InstallScript Professional Logging Method:
1. Launch the Repackaging Wizard from Repackager. The Welcome Panel opens.

3. Select the Installation Monitoring method.

The InstallShield Professional Logging Method is not offered as a choice on this panel, but
when you select an InstallShield Editor or DevStudio 9.x InstallScript installation on the Collect
Product Information Panel (the next panel in the Repackaging Wizard), Repackager will
automatically detect the InstallScript installation and will display the InstallShield Professional
Setup Panel. On this panel you can choose to use the InstallShield Professional Logging
Method instead of the method you chose on the Method Selection Panel.
Caution: When you are attempting to repackage a setup using the InstallScript Professional Logging Method, you are
permitted to select either Installation Monitoring or Snapshot on the Method Selection Panel, but it is
recommended that you select Installation Monitoring.
If you were to select the Snapshot method, an additional panel opens, entitled Snapshot Method. On this panel, if you
select Multiple Steps instead of Single Step, Repackager will not recognize the setup as an InstallShield Editor or
DevStudio 9.x InstallScript installation and the InstallShield Professional Setup Panel will not open. You can avoid
this extra and possibly troublesome step by selecting Installation Monitoring on the Method Selection Panel.

4. On the Method Selection Panel, click Next. The Collect Product Information Panel opens.
Caution: Do not use the Edit Setup List link to add an additional setup program to this project. If you do,
Repackager will not recognize the specified installation as an InstallShield Editor or DevStudio 9.x InstallScript
installation and the InstallShield Professional Setup Panel will not open.
5. Click the Browse ( ) button next to the Program File field and select the InstallShield Editor or
DevStudio 9.x InstallScript installation that you are repackaging.
as necessary.
c. Click OK.

9. Click Next. Because you specified an InstallShield Editor or DevStudio 9.x InstallScript installation
in the Program File field, the InstallShield Professional Setup Panel opens.
10. Select the Use InstallShield Professional logging instead of repackaging option.
11. Click Next. The Set Target Project Information and Capture Settings Panel opens.
Settings Panel. The selected InstallShield Editor or DevStudio 9.x installation is launched.

14. Follow the prompts until the installation has completed.
Repackager then launches and opens the Repackager project file (*.irp) that you just created.
Repackaging an InstallScript MSI Setup to a Basic MSI Setup

InstallScript MSI installations use a Windows Installer database for storage of all file/registry
information, but the actual user interface, and much of the installation logic is driven by the InstallScript
engine via a setup.exe file. This type of installation architecture can cause difficulties during
deployment, such as:
• inability to customize or transform the application
• inability to conflict detect
• inability to suppress the user interface
• difficulty patching or upgrading the application

Also, if an InstallScript MSI installation is repackaged using traditional methods (OS Snapshot or
Installation Monitoring), significant platform-specific or custom installation, maintenance, and
uninstallation logic, and user interface information is lost because those methods only record the
installation activities for the specific platform used during repackaging.
Therefore, it is recommended that you use InstallScript Scan to convert an InstallScript MSI installation
to a Basic MSI package with InstallScript support. InstallScript Scan preserves the original components
and much of the InstallScript installation logic, architecture, and maintainability of the original
installation package.
Note: If you want to convert an InstallScript MSI package to a Basic MSI that preserves the InstallScript installation logic,
and you are using the Snapshot method, you must select Single Step rather than Multiple Steps. If you select Multiple
Steps, the InstallScript installation logic will not be preserved.
Task To convert an InstallScript MSI Setup to a Basic MSI Setup with InstallScript support:
1. Launch the Repackaging Wizard from Repackager. The Welcome Panel opens.
3. Select a repackaging method: Installation Monitoring or Snapshot.
4. Click Next. If you selected Snapshot on the Method Selection Panel, the Snapshot Method
Panel appears. (If you selected Installation Monitoring, skip to Step 6.)
5. Select Single Step and click Next. The Collect Product Information Panel opens.
Caution: Because you are converting an InstallScript MSI package to a Basic MSI package with InstallScript support,
you must select the Single Step Snapshot method (or use the Installation Monitoring method). If you select Multiple
Step Snapshot, the InstallScript installation logic will not be preserved.

6. On the Collect Product Information Panel, select the InstallScript MSI setup file and enter
other product information.
Caution: While it is possible to click the Edit Setup List button and select additional setups, because you are
converting an InstallScript MSI package, do not select additional setups.
7. Click Next. Repackager will automatically determine if this is an InstallScript-based setup. If it is an

InstallScript-based setup, the InstallScript MSI Identified Panel opens, informing you that the
Repackaging Wizard has identified this setup as being an InstallScript MSI setup and prompting you
to use InstallScript Scan to convert this setup.
8. Select Yes and click Next. The InstallScript MSI Conversion Output Panel opens.
9. In the Project Path to store files field, specify the location where you want the Repackaging Wizard
to store files created during InstallScript Scan Analysis and where it will save the converted MSI
package.
Note: To specify capture types for the repackaging session, click the Edit button to access the Analysis Options
dialog box.
10. Click Next. The Repackaging Panel appears, displaying the progress of the repackaging
operation.
11. Following repackaging, the Summary Panel is displayed, providing confirmation that the
repackaging was successful.
12. Click Finish to launch the Repackager to edit and build your project. See Working With Repackager
Projects.

Running the Repackaging Wizard Remotely

For optimal performance and repackaging integrity, you should only repackage on a clean system, and
you should run Repackager remotely from a mapped drive. This minimizes unwanted data capture
during repackaging.
Configuring Repackager to Run from a Network Location

To map the network location of Repackager, perform the following steps.
Task To configure Repackager to run from a network location:
1. On a production machine that does not contain AdminStudio, download and install the standalone
version of Repackager 8.0. (You will not repackage legacy setups on this machine.) To download the
Repackager installation setup, go to the following URL:
When installation is complete, the Repackager executable will be located in the following directory:
2. Share the Repackager directory on the production machine so it can be accessed from the network.
This can be done by right-clicking the directory in Windows Explorer and selecting Sharing from the
context menu.
3. Configure sharing rights as necessary. Click OK to close the dialog box.
4. From your clean system where you will repackage legacy setups, launch Windows Explorer and
select Map Network Drive from the Tools menu.
5. Specify the drive letter you want use to represent the shared location.
6. Click Browse and locate the directory you shared from the production machine. Click OK once you
select the folder.
7. Click Finish to exit the Map Network Drive Wizard.

Using Windows Explorer to Access Repackager

After you have mapped the network location, you can access Repackager using Windows Explorer.
Task To launch Repackager remotely:
1. Launch Windows Explorer.

2. Navigate to the drive mapped to the shared Repackager directory on your production machine.
3. Navigate to the Repackager folder and double-click on islc.exe to launch Repackager remotely.
4. Run the Repackaging Wizard to begin repackaging your legacy setup.
Note: Set the Repackaging Wizard output location to a shared directory on the production machine to ensure output files
are written to the network rather than to the clean system.
Remote Repackaging on Windows NT4

When repackaging remotely from a Windows NT4 system, you may encounter an error if MSCVRT.dll is
not installed. To install the MSCVRT.dll, install a standalone version of Repackager. The Repackager
installation setup can be downloaded at the following URL:
Run this installation setup on a clean Windows NT system. When installation is complete, the
Repackager executable will be located in the following directory:
Tip: This will create shortcuts for Repackager and the Repackaging Wizard on the clean system. You can use them to
launch Repackager or the Repackaging Wizard for subsequent repackaging needs.

Running the Repackaging Wizard from the Command Line
Task To run the Repackaging Wizard from the command line:
1. Open a command-line prompt.

2. Type Repack.exe followed by any command-line options you want to pass. See Repackaging Wizard
Command-Line Options.
3. Press Enter.
An example of a typical command line is as follows:
Repack.exe -app Setup.exe -o C:\MyRepackagedApps\Output
-pp SomeApp -cs Custom -cf MyOptions.ini -sb
In the above example, the following options are used:
Table 3-6: Repackager Command-Line Options used in Example
Option Description
-app Specifies the name of the setup.
-o Specifies the location of the output directory
-pp Specifies the name of the product (and the name of the Repackager output file).
-cs Specifies to use a custom analysis options file to use.
-cf Name of the analysis options file to use.
-sb Allows you to run Repackager silently, with no user interaction.

Converting Legacy Installations Using the Repackager

Interface
In addition to repackaging a legacy installation using the Repackaging Wizard, you can also convert
many setup types directly to Repackager projects (.irp)—and ultimately to InstallShield Editor projects
(.ism) and Windows Installer packages (.msi). Repackager can directly convert the following setup
types:
• Converting Repackager 3.x Output Files
• Converting Microsoft SMS Projects
• Converting Novell ZENworks Projects
• Converting WinINSTALL Projects
• Converting Wise Installation Projects
• Converting InstallShield Professional Log Files
• Repackaging an InstallScript MSI Setup to a Basic MSI Setup

Converting Repackager 3.x Output Files

To convert a Repackager 3.x output file to a Repackager project, perform the following steps.
Task To convert a Repackager 3.x output file (.inc) to a Repackager project (which can subsequently be built into a
Windows Installer package):
1. Launch Repackager.
2. On the File menu, click Open. The Open dialog box opens.
3. Change the Files of type filter to Legacy Repackager Files (*.inc).
4. Browse to locate the Repackager 3.x output file you want to convert.
5. Select the file and click OK.
The Repackager 3.x project is updated to the Repackager project (.irp) format. Files, .ini files,
shortcuts, and registry entries within the project are visible through the appropriate views in the
Repackager Interface.
Converting Microsoft SMS Projects

To convert a Microsoft SMS project to a Repackager project, perform the following steps.
Task To convert a Microsoft SMS project (.ipf) to a Repackager project (which can subsequently be built into a
2. From the File menu, select Open.
3. In the Open dialog box, change the Files of type filter to SMS Installer (*.ipf).
4. Browse to locate the SMS project you want to convert.
5. Select the project, and click OK.
The legacy project is converted to a Repackager project. Files, .ini files, shortcuts, and registry entries
within the project are visible through the appropriate views in the Repackager Interface.

Converting Novell ZENworks Projects

You can convert Novell ZENworks 3.0, 3.1, or 4.0 projects (.axt/.aot) to Windows Installer packages
(.msi) one at a time or in bulk:
• Repackager Interface—You can convert a ZENworks project to a Windows Installer package using
the Repackager interface. See Converting a Novell ZENworks Project Using the Repackager
Interface.
• Command Line—You can use the Command Line to bulk convert multiple ZENworks projects to
Windows Installer packages. See Converting Multiple Novell ZENworks Projects Using the
Command Line.
Note: In order to convert an .aot file, the ZENworks Desktop Management Agent 6.5 or later (zenlite.dll) must be installed
on the workstation where Repackager is installed. If this agent is not installed, Repackager can only convert ZENworks
.axt files. See About .axt and .aot Application Object Template Files for more information.
Converting a Novell ZENworks Project Using the Repackager Interface

Using Repackager, you can convert Novell ZENworks 3.0, 3.1 or 4.0 projects (.axt/.aot) to Windows
Installer packages (.msi).
About .axt and .aot Application Object Template Files

In ZENworks Desktop Management, the snAppShot utility generates application object template files—
with either an .axt or .aot extension—that contain the details that are required for the Application
Launcher to be able to distribute an application to a workstation:
• registry entries to be added
• files to be copied
• changes to be made in the .ini files and system text files (autoexec.bat and config.sys)
Because an .axt file is a text file that can be edited with a text editor in order to modify it after it has been
created, it can be opened and converted by Repackager.
However, in order to convert a .aot file (which is not a text file), the ZENworks Desktop Management
Agent 6.5 or later (zenlite.dll) must be installed on the workstation where Repackager is installed. If
this agent is not installed, Repackager can only convert ZENworks .axt files.
Note: For information on installing the ZENworks Desktop Management agent (version 6.5 or later) to a workstation, see
one of the following:
• Novell ZENworks 6.5 Desktop Management Installation Guide
http://www.novell.com/documentation/zenworks65/dminstall/data/front.html
• Novell ZENworks 7 Desktop Management Installation Guide
http://www.novell.com/documentation/zenworks7/index.html?page=/documentation/zenworks7/dm7install/data/
front.html

Task To convert a Novell ZENworks project (.axt/.aot) to a Repackager project (which can subsequently be built
into a Windows Installer package):
2. On the File menu, click Open.
3. In the Open dialog, change the Files of type filter to either Novell ZENworks (*.axt) or Novell
ZENworks (*.axt/*.aot).
Note: If the ZENworks Desktop Management Agent 6.5 or later (zenlite.dll) is installed on the workstation where
Repackager is installed, the Files of type filter will be Novell ZENworks (*.axt/*.aot). If this agent is not installed, the
Files of type filter will be Novell ZENworks (*.axt) and you will be unable to select .aot files as the legacy setup
source. See About .axt and .aot Application Object Template Files for more information.
4. Browse to locate the ZENworks project you want to convert.

The legacy project is converted to a Repackager project. Files, .ini files, shortcuts, and registry entries
Converting Multiple Novell ZENworks Projects Using the Command Line

To perform a bulk conversion of ZENworks 3.0, 3.1, or 4.0 projects to Windows Installer packages, you
use the -Z command line switch.
Task To convert multiple Novell ZENworks projects (.axt/.aot) to a Windows Installer package, a Repackager
project, or an InstallShield Editor project:
1. Create an .ini file using the following format:

[General]
OutputFormat=MSI|INC|ISM
[AXT]
C:\myData\Project1.axt
[AOT]
C:\myData\Project1.aot

The following table describes the elements of this file:
Section Description
[General] Controls the output format of the entire conversion process. Select one of the following to identify
the output format:
• MSI—Windows Installer package
• INC—Repackager output file
• ISM—InstallShield Editor project file
[AXT] List the names and locations of the legacy ZENworks projects (.axt) you want to convert. Include
the paths (absolute or relative) to the .axt files.
[AOT] List the names and locations of the ZENworks .aot projects you want to convert. Include the paths
(absolute or relative) to the .aot files.
2. Run the repackaging process from the command line using the -Z parameter:
ISLC.exe -Z"YourFileName.ini"
Repackager loads the loads the .ini file and begins the conversion process. A dialog box opens to
display progress messages.
To limit the volume of messages listed, clear the Verbose check box.
3. When the repackaging process is complete, the Cancel button changes to a Close button. Click
Close to close this dialog box.
You will find the converted files in the location specified in the .ini file as the location of the .aot/
.axt input files.

Converting WinINSTALL Projects
Task To convert a WinINSTALL 6.0, 6.5, or 7.x project (.txt) to a Repackager project (which can subsequently be
built into a Windows Installer package):
3. In the Open dialog box, change the Files of type filter to WinINSTALL (*.txt).
4. Browse to locate the WinINSTALL project you want to convert.
6. If the WinINSTALL Conversion dialog box opens, fill in the WinINSTALL-specific variables and
click OK.
The legacy project is converted to a Repackager project. Files, .ini files, shortcuts, and registry
entries within the project are visible through the appropriate views in the Repackager Interface.
Note: WinINSTALL projects must be converted to .txt files prior to conversion to Repackager projects.
Converting Wise Installation Projects
Task To convert a Wise Installation project (.wse) to a Repackager project (which can subsequently be built into a
3. In the Open dialog box, change the Files of type filter to Wise Projects (*.wse).
4. Browse to locate the Wise Installer project you want to convert.
The legacy project is converted to a Repackager project. Files, .ini files, shortcuts, and registry
entries within the project are visible through the appropriate views in the Repackager Interface.

Converting InstallShield Professional Log Files

You can convert an InstallShield Professional log file (.isl) to a Repackager project if you have access to
the original setup media. When you open the log file, following the steps below, Repackager will try to
find the original setup media automatically (in the location specified in the log file), but if it cannot, it
will allow you to browse to it before continuing. If you do not have access to the original setup media, the
conversion will fail.
Task To convert an InstallShield Professional Log File (.isl) to a Repackager project (which can subsequently be
built into a Windows Installer package):
3. In the Open dialog box, change the Files of type filter to InstallShield Pro Log Files (*.isl).
4. Browse to locate the InstallShield Professional log file you want to convert.
5. Select the file, and click OK.
The log file is converted to a Repackager project. Files, .ini files, shortcuts, and registry entries
Chaining Multiple Windows Installer Packages Together

If your application includes more than one Windows Installer (*.msi) package, you can use InstallShield
Editor to chain them together using a nested MSI Custom Action. This enables you to run multiple MSI
files within a single setup process.
To do this, you open the InstallShield Editor Custom Actions View and use the Custom Action
Wizard.
Task To add a Nested MSI Custom Action:
1. Launch InstallShield Editor.

2. Open your Windows Installer package in Direct Edit Mode.
3. In the Installation Designer, expand the Behavior and Logic tree and select the Custom
Actions node. The Custom Actions View opens.
4. In the middle pane, click Custom Actions and select Custom Action Wizard from the context
menu.
5. Follow the Nested

Installations procedure in the InstallShield Editor user
documentation to create a nested MSI Custom Action.

Configuring Exclusions
Repackaging exclusions refer to exclusions made during repackage time using the Repackaging Wizard.
Any files, registry entries, .ini files, or shortcuts excluded at this point are not included in the Repackager
project.
There are two methods of configuring exclusions:
• Configuring Exclusions Using Repackager
• Configuring Exclusions Using the Exclusions Editor
Configuring Exclusions Using Repackager

There are three types of exclusions used when repackaging a legacy installation:
Table 3-7: Repackager Exclusion Types
Exclusion Type Description
Repackaging Repackaging exclusions refer to exclusions made during repackage time using the Repackaging
Exclusions Wizard. Any files, registry entries, .ini files, or shortcuts excluded at this point are not included in
the Repackager project. Therefore, if you exclude a directory you later need, you need to
repackage the legacy setup again.
The Repackager best practice is to capture everything using the Repackaging Wizard, and then
exclude visually in the Repackager Interface. This way, you avoid having to run the Repackaging
Wizard again if you accidentally exclude necessary files.
In some cases, you may want to avoid capturing specific data types during repackaging. For
example, your organization may never want to capture shortcuts. You can disable capture of
shortcuts during repackage time, thereby eliminating the need to exclude them later. In Snapshot
mode, you may want to limit the analysis to a certain directory to reduce the time it takes to
capture the initial and final snapshot.
Project Exclusions Each Repackager project can use a project exclusion list which marks files, registry entries,
shortcuts, and .ini files as excluded in the Repackager project. If your process dictates that you
capture everything and only exclude items in the Repackager Interface, then you should set up
commonly captured but unnecessary items from the project by default. Because all the data from
the original capture is intact, if you accidentally exclude necessary files, you can always reinclude
them from the Repackager Interface and quickly rebuild your Windows Installer package.
Individual Project Because each project is different, and may require you to make decisions as to whether certain
Exclusions captured data is necessary, you can also selectively exclude or reinclude items on a per-package
basis. These individual project exclusions allow you a fine-level of control as you prepare to build
your Windows Installer package from the Repackager project.

Excluding Files
To exclude a captured file from the InstallShield Editor project and Windows Installer package, perform
the following steps.
Task To exclude a captured file from the InstallShield Editor project and Windows Installer package:
1. Select Files and Folders from the View List. The Files and Folders View opens.
2. Expand the directory tree and select the directory containing the file you want to exclude.
3. In the file list, right-click on the file and select Exclude.
Excluding All Files in a Directory

To exclude all captured files in a directory from the InstallShield Editor project and Windows Installer
package, perform the following steps.
Task To exclude all captured files in a directory from the InstallShield Editor project and Windows Installer
package:
2. Expand the directory tree and select the directory containing the files you want to exclude.
3. Right-click on the directory and select Exclude.
Excluding Directories and Subdirectories

To exclude all captured files and subdirectories within a directory from the InstallShield Editor project
and Windows Installer package, perform the following steps.
Task To exclude all captured files and subdirectories within a directory from the InstallShield Editor project and
Windows Installer package:
2. Expand the directory tree to display the directory containing the files and subdirectories you want to
exclude.
3. Right-click on the directory and select Exclude All.

Excluding Registry Keys

To exclude a registry key from the InstallShield Editor project and Windows Installer package, perform
the following steps.
Task To exclude a registry key from the InstallShield Editor project and Windows Installer package:
1. Select Registry Entries from the View List. The Registry Entries View opens.
2. Expand the Registry tree to display the registry key you want to exclude.
3. Right-click on the registry key and select Exclude.
Excluding Registry Values

To exclude a captured registry value from the InstallShield Editor project and Windows Installer
Task To exclude a captured registry value from the InstallShield Editor project and Windows Installer package:
1. Select Registry Entries from the View List. The Registry Entries View opens.
2. Expand the Registry tree and select the registry key containing the value you want to exclude.
3. In the Registry Value list, right-click on the value and select Exclude.
Excluding .ini Files

To exclude a captured .ini file from the InstallShield Editor project and Windows Installer package,
perform the following steps.
Task To exclude a captured .ini file from the InstallShield Editor project and Windows Installer package:
1. Select INI Files from the View List. The INI Files View opens.
2. Expand the INI Files tree to display the .ini file you want to exclude.
3. Right-click on the .ini file and select Exclude.

Excluding .ini File Sections

To exclude a section in a captured .ini file from the InstallShield Editor project and Windows Installer
Task To exclude a section in a captured .ini file from the InstallShield Editor project and Windows Installer package:
1. Select INI Files from the View List. The INI Files View opens.
2. Expand the INI Files tree to display the .ini file containing the section you want to exclude.
3. Right-click on the section and select Exclude.
Excluding Shortcuts
To exclude a captured shortcut from the InstallShield Editor project and Windows Installer package,
Task To exclude a captured shortcut from the InstallShield Editor project and Windows Installer package:
1. Select Shortcuts from the View List. The Shortcuts View opens.
2. Expand the Shortcuts tree to display the shortcut you want to exclude.
3. Right-click on the shortcut and select Exclude.
Excluding All Shortcuts in a Directory

To exclude all captured shortcuts in a directory from the InstallShield Editor project and Windows
Installer package, perform the following steps.
Task To exclude all captured shortcuts in a directory from the InstallShield Editor project and Windows Installer
package:
2. Expand the Shortcuts tree to display the directory containing the shortcuts you want to exclude.
3. Right-click on the directory and select Exclude.

Excluding Shortcuts from Subdirectories

To exclude all captured shortcuts within a directory or its subdirectories from the InstallShield Editor
project and Windows Installer package, perform the following steps.
Task To exclude all captured shortcuts within a directory or its subdirectories from the InstallShield Editor project
and Windows Installer package:
2. Expand the Shortcuts tree to display the directory containing the shortcuts and/or subdirectories
containing shortcuts you want to exclude.
3. Right-click on the directory and select Exclude All.
Specifying the External Configuration File

To specify an external configuration file which you want to use as a filter when converting legacy setups,
Task To specify an external configuration file which you want to use as a filter when converting legacy setups:
1. From the Repackager Project menu, select Properties. The General tab of the Project
Properties dialog box opens.
2. Open the Exclusions tab.
3. Select the Use settings from the shared location or the Use settings from a custom file
option. The Browse button for that option is activated.

4. Click Browse and select the configuration file you want to use.
Tip: After you select a configuration file, the Edit button is activated, enabling you to open the file in the Exclusions
Editor.
5. Click OK.
When you apply a configuration file, Repackager automatically updates all views to reflect the
configuration file’s exclusions. However, if you have already excluded items using Repackager, item
states are retained.
Modifying External Configuration Files

To configure an external configuration file, perform the following steps.
Task To configure an external configuration file:
1. From Repackager's Project menu, click Properties. The General tab of the Project Properties
dialog box opens.
2. Select the Exclusions tab.
3. Select the file you want to modify in either the Use settings from the shared location option or
Use settings from a custom file options.
4. Click Edit. The Exclusions Editor opens.
5. Make necessary modifications using the Exclusions Editor.
6. When you finish editing the configuration file, click OK.
7. Click OK to close the Project Properties dialog box.
When you apply a configuration file, Repackager automatically updates all views to reflect the
configuration file's exclusions. However, if you have already excluded items using Repackager, item
states are retained.

Configuring Exclusions Using the Exclusions Editor

The Exclusions Editor allows you to configure three types of exclusions: Repackaging, Project, and OS
Snapshot.
Repackaging Exclusions
Repackaging exclusions refer to exclusions made during repackage time using the Repackaging Wizard.
Any files, registry entries, .ini files, or shortcuts excluded at this point are not included in the
Repackager project. Therefore, if you exclude a directory you later need, you need to repackage the
legacy setup again.
The Repackager best practice is to capture everything using the Repackaging Wizard, and then exclude
visually in the Repackager Interface. This way, you avoid having to run the Repackaging Wizard again if
you accidentally exclude necessary files.
In some cases, you may want to avoid capturing specific data types during repackaging. For example,
your organization may never want to capture shortcuts. You can disable capture of shortcuts during
repackage time, thereby eliminating the need to exclude them later. In Snapshot mode, you may want to
limit the analysis to a certain directory to reduce the time it takes to capture the initial and final
snapshot.
Project Exclusions
Each Repackager project can use a project exclusion list which marks files, registry entries, shortcuts,
and .ini files as excluded in the Repackager project. If your process dictates that you capture everything
and only exclude items in the Repackager Interface, then you should set up commonly captured but
unnecessary items from the project by default. Because all the data from the original capture is intact, if
you accidentally exclude necessary files, you can always reinclude them from the Repackager Interface
and quickly rebuild your Windows Installer package.
OS Snapshot Exclusions
Like pre-capture repackaging exclusions, you can use the Exclusions Editor to configure exclusions to
apply during the capture of OS snapshots. However, to maximize the usefulness of OS snapshots, you
should avoid editing the default snapshot exclusion list (ISSnapshot.ini).
Exclusions and Repackager

Exclusions in Repackager refer to files, registry entries, shortcuts, and .ini files that are marked as
excluded in the Repackager Interface by default when you open a Repackager project or if you change
your exclusions file. The captured data is only marked as excluded and not ignored or discarded during
capture. You can create a exclusion file in the Exclusions Editor, and link it to Repackager from the
Exclusions Tab of the Project Properties dialog box in Repackager.
Exclusions and the OS Snapshot Wizard

When using the Exclusions Editor to configure analysis options for capturing OS snapshots, you are
creating an exclusion list for files, directories, .ini files, .ini file sections, and registry data. Items in the
exclusion list are not captured during the OS snapshot process, and will not be included in the OS
snapshot file which is created.

Launching Exclusions Editor

The Exclusions Editor can be launched either within the Repackager interface or outside of Repackager.
You can edit the default exclusions file, isrepackager.ini, using either interface.
However, if you want to create a new, custom exclusions file, you must launch the Exclusions Editor
outside of Repackager.
• Launching Exclusions Editor Outside of Repackager
• Launching Exclusions Editor Within Repackager
Launching Exclusions Editor Outside of Repackager

To launch the Exclusions Editor outside of the Repackager interface, perform the following steps.
Task To add a file to the exclusion list:
1. Launch the Exclusions Editor by locating and executing the following file:
AdminStudio Installation Directory\Repackager\AnalysisOptions.exe
The Files tab of the Exclusions Editor opens.

2. Perform one of the following to open an exclusions file:
• Shared Exclusions—To edit the shared exclusions file, on the Files menu, point to Open and
click Shared Exclusions. The exclusions in the shared exclusions file are now listed on the
Files tab.
• Custom Exclusions—To create a new custom exclusions file, on the Files menu, click New. A
default set of exclusions is listed.
3. Make edits to the file.
4. Save the file by selecting Save on the File menu.
5. If you were creating a custom exclusions file, specify a name and location for this exclusions file and
click Save.

Launching Exclusions Editor Within Repackager

To add a file to the exclusion list, perform the following steps.
1. Launch Repackager and open a project.

2. On the Project menu, click Properties. The Project Properties dialog box opens.
3. On the Exclusions tab, do one of the following:
• To edit the default exclusions file, select Use settings from the shared location and click
Edit.
• To edit a custom exclusions file, select Use settings from a custom file, browse to the file
you want to open (if it is not listed), and click Edit.
The Files tab of the Exclusions Editor opens, with the appropriate exclusions file open.
4. Make edits to the file.
5. Save the file and close the Exclusions Editor by clicking OK.
Note: Note that when opening the Exclusions Editor from within Repackager, there is no File menu displayed,
meaning that you can only edit an existing exclusions file; you cannot create a new exclusions file.

Excluding Files
You use the Exclusions Editor to create an exclusion list for files so that those files are not captured
during the OS snapshot process, and will not be included in the OS snapshot file.
1. Launch the Exclusions Editor and open an exclusions file by performing the steps listed in
Launching Exclusions Editor:
2. On the Files tab, click New. The File Exclusion Information dialog box opens.
3. Enter or browse to the directory Path containing the file you want to exclude.
4. Enter the name of the file you want to exclude, or browse to it by clicking the Browse ( ) button to
the right of the Excluded Files field. If you want to exclude multiple files from the same directory,
separate them with semicolons (|). If you want to exclude all files in a directory, enter an asterisk (*).
5. Click OK to close the File Exclusion Information dialog box. The new exclusion appears in the
Files tab.
6. Save the exclusions file as described in Launching Exclusions Editor:
Note: When configuring file exclusions for Repackager, you are only configuring Repackager to automatically mark the file
as excluded; this can be changed from within Repackager on a file-by-file basis. However, when configuring file exclusions
for the OS Snapshot Wizard, files in the exclusion list are not captured in the OS snapshot file.

Excluding Files with Specific Extensions

To exclude files with specific extensions from the exclusion list, perform the following steps.
Task To exclude files with specific extensions from the exclusion list:
3. In the File Exclusion Information dialog box, enter or browse to the directory containing the
files you want to exclude. If you want to exclude files with a certain extension from all directories,
enter an asterisk (*) for the Path value.
4. Enter an asterisk followed by the extension you want excluded in the Excluded Files field. For
example, if you want to exclude all .bak files, enter *.bak. If you want to exclude multiple file types
from the same directory (or from all directories), separate each exclusion with a pipe (|).
Files tab.

Excluding Directories
To add a directory to the exclusion list, perform the following steps.
Task To add a directory to the exclusion list:
3. In the File Exclusion Information dialog box, enter or browse to the directory Path containing
the files you want to exclude.
4. Enter an asterisk (*) in the Excluded Files field.
Files tab.

Editing Existing File Exclusions

To edit an existing file exclusion, perform the following steps.
Task To edit an existing file exclusion:
2. Select the appropriate exclusion and click Edit. The File Exclusion Information dialog box
opens.
3. In the File Exclusion Information dialog box, modify the Path and Excluded Files
information.
4. Click OK to close the File Exclusion Information dialog box. The edited exclusion is listed in the
Files tab.
Removing File Exclusions

To remove an existing file exclusion, perform the following steps.
Task To remove an existing file exclusion:
2. Select the appropriate exclusion and click Delete.
3. Confirm the exclusion by clicking OK. The deleted exclusion is removed from the list.

Excluding .ini Files

To add an .ini file to the exclusion list, perform the following steps.
Task To add an .ini file to the exclusion list:
2. Open the INI Files tab.
3. Click New. The INI File Exclusion Information dialog box opens.
4. Enter or browse to the .ini file you want to exclude.
5. If there are specific sections you want to exclude from the .ini file, put the section names in brackets
([]) and separate them with pipes (|) in the Excluded Sections field. If you want to exclude all
sections, put an asterisk (*) in the Excluded Sections field.
6. Click OK to close the INI File Exclusion Information dialog box. The new exclusion appears in
the list on the INI Files tab.
7. Save the exclusions file as described in Launching Exclusions Editor.
Note: When configuring .ini file exclusions for Repackager, you are only configuring Repackager to automatically mark the
.ini file and/or sections as excluded; this can be changed from within Repackager on an .ini file by .ini file basis. However,
when configuring .ini file exclusions for the OS Snapshot Wizard, .ini files in the exclusion list are not captured in the OS
snapshot file.

Excluding Sections from .ini Files

To add a specific .ini file section to the exclusion list, perform the following steps.
Task To add a specific .ini file section to the exclusion list:
3. Click New. The INI File Exclusion Information dialog box opens.
4. Enter or browse to the .ini file containing the section you want to exclude.
5. To exclude a specific .ini file section, enter the section name in brackets ([]) in the Excluded
Sections field. If there are multiple sections, separate them with pipes (|).
the INI Files and Sections Excluded During Analysis dialog box.
the list on the INI Files tab.
snapshot file.

Editing Existing .ini File Exclusions

To edit an existing .ini file exclusion, perform the following steps.
Task To edit an existing .ini file exclusion:
Launching Exclusions Editor.
3. Select the appropriate exclusion and click Edit. The INI File Exclusion Information dialog box
opens.
4. In the File Exclusion Information dialog box, modify the INI File and Excluded Sections
information.
5. Click OK to close the INI File Exclusion Information dialog box. The edited exclusion appears
in the list on the INI Files tab.
snapshot file.

Removing .ini File Exclusions

To delete an existing .ini file exclusion, perform the following steps.
Task To delete an existing .ini file exclusion:
3. Select the appropriate exclusion and click Delete.
4. Confirm the exclusion by clicking OK. The deleted exclusion is removed from the list.
snapshot file.

Excluding Registry Data

To add registry data to the exclusion list, perform the following steps.
Task To add registry data to the exclusion list:
2. Open the Registry tab.
3. Click New. The Choose Registry Key dialog box opens.
4. Enter or browse to the registry key you want to exclude and click OK. The key is added to the list on
the Registry tab.
5. If you want to exclude a certain value in the key, select it from the list and click Edit. The Edit
Registry Key dialog box opens.
6. Provide the Value Name you want to exclude, and click OK to close the dialog box. The exclusion
information is reflected in the list on the Registry tab.
Note: When configuring registry exclusions for Repackager, you are only configuring Repackager to automatically mark
the registry entry and/or values as excluded; this can be changed from within Repackager on an registry key by registry
key basis. However, when configuring registry exclusions for the OS Snapshot Wizard, registry data in the exclusion list is
not captured in the OS snapshot file.

Editing Existing Registry Exclusions

To edit existing registry exclusions, perform the following steps.
Task To edit an existing registry exclusion:
3. Select the registry key that you want to edit and click Edit. The Edit Registry Key dialog box
opens.
4. Modify the exclusion as necessary and click OK. The edited information is reflected in the list on the
Registry tab.

Working With Repackager Projects
Removing Registry Exclusions

To delete an existing registry exclusion, perform the following steps.
Task To delete an existing registry exclusion:
3. Select the registry key that you want to delete and click Delete.
4. Confirm the deletion by clicking OK. The deleted exclusion is removed from the list.

After creating a Repackager project—by Repackaging Legacy Installations Using the Repackaging
Wizard or by Converting Legacy Installations Using the Repackager Interface—you can perform the
following tasks:
• Building an InstallShield Editor Project
• Building a Windows Installer Package
• Viewing Repackager Project Properties
• Using the Setup Intent Wizard to Detect File Dependencies in a Repackager Project
• Creating a Setup Capture Report for a Project
• Saving Repackager Projects
• Opening InstallShield Editor from Repackager

Building an InstallShield Editor Project

You can build an InstallShield Editor project (.ism) and Windows Installer package (.msi) from your
Repackager project (.irp) simultaneously. You can also choose to build just an InstallShield Editor
project, so that you can open it in InstallShield Editor and make some modifications prior to building
the Windows Installer package.
Task To build a InstallShield Editor project (.ism):
1. In the Repackager interface, open the Repackager project that you want to convert to an
InstallShield Editor project.
2. Select Repackaged Output from the View List. The Repackaged Output View opens.
3. In the Editor Project field, enter the name and location of the InstallShield Editor Project file you
want to create.
4. If you do not want to Create a Windows Installer package (.msi) after creating the Editor
project, clear this option. If you want to create a Windows Installer Package, see Building a
Windows Installer Package.

5. A project template contains all of the default settings and design elements that you want to use as a
starting point when you create an installation project. In the Repackaged Output Options area,
select the InstallShield Editor Project Template you want to use when creating the project:
• Use the default Editor template—Select this option to use the default InstallShield Editor Project
Template.
• Use a customized template—Select this option to use a customized InstallShield Editor Project
Template.
For example, if you wanted all of your InstallShield Editor projects to have a special custom
dialog, a set of required redistributables, and a particular SQL script, you could create a project
template that has all of those settings. Then, any time that you wanted to create a new project,
you could base it off of your custom template. This enables you to avoid re-creating the custom
dialog, re-adding the redistributables, and re-adding the SQL script every time that you create a
new InstallShield Editor Project.
6. Select Package Information from the View List. The Package Information View opens.
7. Select Package Information from the View List. The Package Information View opens, where you
can specify information for the Windows Installer package that you build from the Repackager
project. Much of this information may be prepopulated based on settings used in the Repackaging
Wizard.
8. Enter the following information:

a. Company Name—The name of the company that developed the product you are repackaging.
b. Product Name—The name of the product you are repackaging.
c. Version—The product’s version number.
d. Product URL—The URL for product information. This appears in Add/Remove Programs in
the Control Panel.

e. Support URL—A URL for support information. This also appears in Add/Remove Programs
in the Control Panel, and is often changed during repackaging to provide an internal support
URL.
9. Select Advanced Settings from the View List. The Advanced Settings View opens.
10. Select the options that you want to use, as described in Configuring Advanced Conversion Options.
11. Select Repackaged Output on the View List. The Repackaged Output View opens.
12. Click the Build button. The build process begins, and its progress is reported in the output window.
When the build process is complete, a Conversion completed message appears in the output window,
and a link to the build log file is provided.

Building a Windows Installer Package

You can simultaneously build an InstallShield Editor project (.ism) and Windows Installer package
(.msi) from your Repackager project (.irp). However, before you do so, you must configure options in
your Repackager project necessary for the build.
Task To build a InstallShield Editor project (.ism) and Windows Installer package (.msi):
1. In the Repackager interface, open the Repackager project that you want to convert to an
InstallShield Editor project and build a Windows Installer package.
2. Select Repackaged Output from the View List. The Repackaged Output View opens.
3. In the Editor Project field, enter the name and location of the InstallShield Editor Project file you
want to create.

4. Select the Create a Windows Installer package (.msi) after creating the Editor project
option, and select the following additional options:
a. The compression option that you select for this package depends upon the size of your
application’s installation and your delivery method.
Neither Setup.exe nor your .msi file can be spanned across multiple disks. So, if the source files
associated with your Windows Installer package cannot fit on the same disk as the setup.exe
and .msi file, you will need to include them in .cab files on other disks. But if you are performing
a network installation and have unlimited space, there is no need to compress files or include
additional files in .cab files.
From the list, select one of the following options:
Option Description
Create single compressed .msi Select this option if you want to compress all necessary files inside the
file .msi package, as opposed to storing them outside of the .msi database.
Create single compressed Select this option if you want to compress all files inside a setup.exe file,
setup.exe file including the .msi file and all other necessary files.
Create .msi file + external Select this option if you want to create an .msi file and want to compress
compressed .cab file the rest of the necessary files in an external .cab file.
For example, you might have an installation that contains three features—
each containing a 1.5 MB file, Setup.exe, and the installation files for
Windows NT—and you want to create a custom media type that is 2 MB
in size. The build will span multiple disks.
• Disk one will contain Setup.exe, InstMsiW.exe (which contains the
logic to install the Windows Installer service on Windows NT
machines), Setup.ini (which is required for installations that include
Setup.exe), and your .msi file.
• The remaining disks will contain .cab files that store compressed
copies of all your source files.
Create .msi file + external Select this option if you want to create an .msi file and a setup.exe file,
compressed .cab file + and want to compress all the rest of the necessary files in an external
setup.exe .cab file.
Create uncompressed .msi file Select this option if you want to create an uncompressed .msi file. All of
the rest of the necessary files, in uncompressed format, would be
shipped with the .msi file.
Create uncompressed .msi file Select this option if you want to create an uncompressed .msi file along
and setup.exe with a setup.exe file. All of the rest of the necessary files, in
uncompressed format, would be shipped with the .msi and setup.exe
files.
b. To reduce versioning conflicts by modifying an application so it always loads the versions of

components—such as DLLs—with which it was originally developed and tested, select the
Create an isolated version of the Windows Installer package. An additional Windows
Installer package will be created in the same directory as the .ism file and the other .msi file,
with the naming convention of:

For more information on how Repackager isolates applications and the available isolation
options, see Isolating Windows Installer Packages.
c. Select the Run automated tests against the Windows installer package option to
automatically run PackageExpert tests against the newly built Windows Installer package to
determine if it is built according to Windows Installer standards, and if it is in compliance with
the installation requirements of the Windows Vista operating system. All of the tests that are
currently selected on the PackageExpert Configuration View are run, and those selected tests
that are automatically resolvable, will be resolved.
Note: For more information on PackageExpert, see Using PackageExpert to Identify and Resolve Package
Errors.
5. A project template contains all of the default settings and design elements that you want to use as a
starting point when you create an installation project. In the Repackaged Output Options area,
select the InstallShield Editor Project Template you want to use when creating the project:
• Use the default Editor template—Select this option to use the default InstallShield Editor Project
Template.
• Use a customized template—Select this option to use a customized InstallShield Editor Project
Template.
For example, if you wanted all of your InstallShield Editor projects to have a special custom
dialog, a set of required redistributables, and a particular SQL script, you could create a project
template that has all of those settings. Then, any time that you wanted to create a new project,
you could base it off of your custom template. This enables you to avoid re-creating the custom
dialog, re-adding the redistributables, and re-adding the SQL script every time that you create a
new InstallShield Editor Project.

6. Select Package Information from the View List. The Package Information View opens,
where you can specify information for the Windows Installer package that you build from the
Repackager project. Much of this information may be prepopulated based on settings used in the
Repackaging Wizard.
7. Enter the following information:

a. Company Name—The name of the company that developed the product you are repackaging.
b. Product Name—The name of the product you are repackaging.
c. Version—The product’s version number.
d. Product URL—The URL for product information. This appears in Add/Remove Programs in
the Control Panel.
e. Support URL—A URL for support information. This also appears in Add/Remove Programs
in the Control Panel, and is often changed during repackaging to provide an internal support
URL.

9. Select the options that you want to use, as described in Configuring Advanced Conversion Options.
10. Select Repackaged Output on the View List. The Repackaged Output View opens.
11. Click the Build button. The build process begins, and its progress is reported in the output window.
When the build process is complete, a Conversion completed message appears in the output window,
a link to the build log file is provided, and the location of the .msi file is listed. For example:
Output file: C:\1516261\WinZip.msi
Configuring Advanced Conversion Options
Task To configure advanced conversion options:
2. In the Advanced Settings View, select the options you want to use during conversion, as
described in Advanced Settings View.

Viewing Repackager Project Properties

You can view the properties of the currently open Repackager project by opening the Project Properties
dialog box.
Task To view properties for the current Repackager project:
1. Open a project in the Repackager interface.

2. From the Project menu, select Properties. The General tab of the Project Properties dialog
box opens.
The following properties are listed:
• Project Location—The full path of the directory where the current Repackager project file (.irp)
is located.
• Project File —The name of the current Repackager project file.
• Captured Data File—The name and location of the captured data file (.inc), which was either
created by the Repackaging Wizard or during conversion of a Novell ZENworks project,
Microsoft SMS project, or WinINSTALL project. The path is relative to the current Repackager
project file.
• Registry Data File—The name and location of the file containing captured registry data. The path
is relative to the current Repackager project file.
• Conversion Options File—The name and location of the Options.ini file, which contains an
exhaustive list of all options you can use during conversion of the Repackager project to an
InstallShield Editor project and Windows Installer package.

• Editor Project File—The name and location of the InstallShield Editor project file as set in the
Product View (MSI Package). The path is relative to the current Repackager project file.
• Windows Installer Package—The name and location of the Windows Installer package. The path is
relative to the current Repackager project file.
3. When finished viewing properties in the General tab, click OK.
Using the Setup Intent Wizard to Detect File Dependencies in

a Repackager Project
To detect file dependencies that may not be included in your Repackager project (.irp):
Task To detect file dependencies:
1. From the Project menu, select Setup Intent Wizard. The Welcome Panel opens.
2. From the Welcome panel, click Next. The Scanning Project Panel opens.
3. Once scanning is finished, the Results Panel opens, listing new files that your setup requires.
4. From the Results Panel, select the files you want added to your Repackager project and click
Finish.
5. Save your Repackager project.
Note: Because the Setup Intent Wizard analyzes files in the Repackager project and searches for dependent files, you
must run the Setup Intent Wizard from the same machine where repackaging was performed (with the Repackaging
Wizard). You can then save the Repackager project and transfer it to another machine.

Creating a Setup Capture Report for a Project

You can generate an HTML or text document that summarizes the data that was captured when a setup
was repackaged.
Figure 3-1: Sample Repackager Setup Capture Report
The following information is available to be displayed in this report:

• Captured files
• Captured shortcuts
• Captured .ini file entries
• Captured Registry entries

The report also indicates which of the files, shortcuts, .ini file entries, or Registry entries, if any, have
been marked for exclusion. Those marked for exclusion are not included in the Repackager project.

Task To create a report detailing captured data:
1. From the Project menu, select Create Report. The Create Report dialog box opens.
2. Select whether you want the report to contain All captured data (all of the data collected during
the entire capture), or just the Current view.
3. If you want the report to contain data from the entire capture, specify whether you want to just
display summary information.
4. Specify whether you want to display excluded items in the report.
5. Select the file format for the report. You can generate an HTML report or a Text report.
6. Click Create. A Save As dialog box opens.
7. From the resulting Save As dialog box, browse to the location where you want to save the file, and
provide a name for the report.
8. Click Save. The report is saved to the specified location and automatically opens.
Saving Repackager Projects
Task To save the current Repackager project:
1. Select Save from the File menu.

or
2. Click the Save button ( ) on the toolbar.
Task To save the current Repackager project under a different name:
Select Save As from the File menu.

Scanning InstallShield Professional Setups for Additional Data
Opening InstallShield Editor from Repackager

After building your Repackager project into a Windows Installer package and/or a InstallShield Editor
project, you may want to launch InstallShield Editor for additional modifications.
Task To launch the generated InstallShield Editor project (.ism) in InstallShield Editor:
From the Repackager Project menu, select Edit InstallShield Project. If installed, InstallShield
Editor opens the project file.
Task To launch the generated Windows Installer package (.msi) in InstallShield Editor:
From the Repackager Project menu, select Edit Windows Installer Package. If installed,
InstallShield Editor opens the package in Direct MSI Edit mode.
Scanning InstallShield Professional Setups for

Additional Data
If you are repackaging a legacy installation that was originally created using InstallShield Professional
5.5 and later, you can use the SmartScan Wizard to scan the setup for possible additional files, .ini
files, shortcuts, or registry data (such as for language-specific setups or platform-specific setups).
The SmartScan Wizard is also able to group files, shortcuts and registry entries into features
corresponding to InstallShield Professional components. Any items (files, folders, shortcuts, or registry
entries) that are attached to a component directly or indirectly (through File Groups), are attached to
their corresponding features.
Automatic Launch of the SmartScan Wizard

For your convenience, if a Repackaging project is opened (either by using Open on the File menu or by
using the Repackaging Wizard), and the project meets certain conditions, the SmartScan Wizard is
automatically launched. The SmartScan Wizard is automatically launched:
• if the original setup was an InstallShield Professional 5.5 or later installation, and
• the file has not already been repackaged using the InstallShield Professional Logging Method
(available for InstallShield Editor and DevStudio 9.x InstallScript installations only), and
• the SmartScan Wizard has not already been run on this project

Scanning InstallShield Professional Setups for Additional Data
Task To scan an InstallShield Professional setup:
1. From the Project menu, select SmartScan Wizard. The Welcome Panel appears.
2. Click Next. The Original InstallShield Professional Setup Panel appears.
3. The Specify the path of the original setup executable field will be filled in by default if that
information exists. Browse to the InstallShield Professional setup you want to scan, and specify a
password if required.
4. In the Original target folder field, enter the directory where the product was installed during the
repackaging process. In most cases, this will be a subdirectory of [ProgramFilesFolder],
5. Click Next. The Scanning Panel appears.
6. When scanning is complete, click Next. The Setup Feature Tree Panel appears, listing the
features and components that were configured in the InstallShield Professional project.
7. Select the Add feature tree option if you want to use the feature information defined in the
Professional media.
8. Click Next. The Scanning Media Panel appears, showing the results of Repackager's search for
any extra setup information in the media.
9. Click Finish to apply the results to the project.
• The setup is scanned, and any additional files, shortcuts, .ini files, or registry data is added to
the appropriate view.
• The data captured by the SmartScan Wizard appears in the color designated in the SmartScan
items field on the Colors tab of the Options dialog box.
• If you selected the Add feature tree option, the files, shortcuts and registry entries are
grouped into features corresponding to the InstallShield Professional components.
Note: After you have scanned an InstallShield Professional project and included data from it in your Repackager project,
you can save the project. When you reopen it, this collected data no longer retains the “scanned” color, since it is now part
of the Repackager project.

Creating an InstallShield Editor Template to Use Within Repackager
Creating an InstallShield Editor Template to Use

Within Repackager
One of the main reasons you use Repackager is to significantly reduce the time it takes to package an
application for deployment. You can use the following procedure to speed up the packaging process even
more.
You can create an InstallShield Editor template that you can use within the Repackager interface to save
additional time when customizing a package. By using this template, all future InstallShield .ism project
files generated by Repackager will contain the company-specific default settings that were specified in
the template. Using a template is also beneficial for organizations with multiple packagers, since it helps
enforce consistency by enabling all packagers to make the same standard customizations to packages.
To create an InstallShield Editor template to use within Repackager, perform the following steps.
Task To create a customized InstallShield Editor template:
1. Create a new Basic MSI Project in the InstallShield Editor.

2. On the Installation Designer tab, select the General Information node under Installation
Information, and enter your company-specific information as required.

3. Under Behavior and Logic, select the Property Manager node and add the required properties
like ALLUSERS, ISSCRIPTDRIVEN, etc.
4. You can also optionally set Shallow Folder Structure to Yes under Media-Release view.

5. After making all required changes, save the project as an InstallShield Template (.ist) type.
6. This new template should now be available along with other project types in the InstallShield Editor.

7. From within the Repackager interface, you can start using this customized template by selecting the
Use a customized template option in the Repackaged Output view, and selecting the
InstallShield Editor template that you just created.

Repackager Reference
This section describes each of the dialog boxes and Wizard panels that you might encounter throughout
Repackager. The help topics in the Repackager Reference are the same detailed documentation that is
displayed when you press the F1 key or click the Help button while working in a dialog box.
Reference information is organized as follows:
Table 3-8: Organization of Repackager Reference Section
Section Description
Repackager Interface This section contains reference information pertaining to the Repackager Interface itself. This
includes menus, the toolbar, views, and dialog boxes.
Repackaging Wizard This section provides a panel-by-panel description of the Repackaging Wizard.
SmartScan Wizard This section provides information about the SmartScan Wizard user interface.
Setup Intent Wizard This section provides information about the Setup Intent Wizard user interface.
VMware Repackaging This section provides information about the VMware Repackaging Wizard user interface.
Wizard
Options.ini File The Options.ini file, which contains information used in repackaging, is discussed in this
topic.
Files Associated with This topic describes the various files related to or created by repackaging, including
Repackager Repack.ini.
Troubleshooting This section includes information on troubleshooting a WinINSTALL or SMS conversion, and
how to resolve an “Error Building Table File” error.

Repackager Interface
From the Repackager Interface, you can:
• Open the Repackaging Wizard and repackage legacy setups.
• Open the Exclusions Editor and configure exclusions.
• Convert Novell ZENworks, Microsoft SMS, and WinINSTALL projects into Repackaging projects.
• Create a package exclusion list.
• Build a Repackager project into an InstallShield project and Windows Installer package.
The Interface consists of several menus, a toolbar, the status bar, the output window, the View List, and
several associated views.
• Menus and the toolbar are discussed in the Menus and Toolbar topic.
• Individual views are covered in their respective help topics.
• The status bar, output window, and View List are described in the following table.
Table 3-9: Repackager Interface Elements
Interface Element Description
Status Bar The status bar, which can be toggled from the View menu, displays information when you
hover over buttons in the toolbar.
View List The View List allows you to navigate to different views in the Repackager project. The
corresponding view is displayed when you select an item in the tree. You can also use the
Forward, Back, Navigate Up, and Navigate Down buttons in the View List.
The View List includes the following views:
• Captured Installation View
• Files and Folders View
• Registry Entries View
• Shortcuts View
• INI Files View
• Deleted Files View
• Deleted Registry Entries View
• Repackaged Output View
• Package Information View
• Advanced Settings View
Output Window When you open Repackager 3.x output, Novell ZENworks projects, Microsoft SMS projects,
WinINSTALL projects, or Wise installation projects in the Repackager Interface, conversion
information appears in the Output window. This window can be toggled from the View menu.

Welcome to Repackager Page

When you first launch Repackager, the Welcome to Repackager page opens.
This page gives you a brief overview of Repackager functionality and uses, and gives you links to launch
the Repackaging Wizard, open an existing Repackager project, convert a legacy setup to a Repackager
project, upgrade a legacy InstallShield Repackager file, and open a recently accessed package.
Figure 3-2: Welcome to Repackager Page

Menus and Toolbar

The following table provides a description of each menu command and toolbar button:
Table 3-10: Repackager Menus and Toolbars
Keyboard
Menu Command Toolbar Button Shortcuts Description
File Open Ctrl+O Allows you to open:

• An existing Repackager project (.irp)
• Repackager 3.x output (.inc)
• Novell ZENworks 3.0, 3.1, or 4.0 project
(.axt/.aot)
• Microsoft SMS project (.ipf)
• WinINSTALL converted project (.txt) (6.0, 6.5,
or 7.x)
• Wise Installer project (.wse)
File Save Ctrl+S Saves the current project.
File Save As Saves the current project using the name and
location you specify.
File 1,2,3,4 Allows you to open the four most recently accessed
Repackager projects.
File Exit Exits Repackager.
View Toolbar Toggles display of the toolbar.
View Status Bar Toggles display of the status bar.
View Output Toggles display of the Output window.
View Refresh F5 Refreshes the current view.
Project Edit Windows Once you build the Repackager project into a
Installer Windows Installer package (.msi), opens the
Package package in InstallShield Editor (in Direct MSI Edit
mode).
Project Edit Once you build the Repackager project into an

InstallShield InstallShield project (.ism), opens the InstallShield
Project project in InstallShield.
Project Setup Intent Launches the Setup Intent Wizard.

Wizard
Project SmartScan Launches the SmartScan Wizard, which allows

Wizard you to scan an InstallShield Professional setup for
additional files that may not have been captured
during repackaging because they may be language-
or platform-specific.

Keyboard
Project Create Ctrl+R Allows you to create a report for the project in text
Report or HTML format.
Project Properties Displays properties for the current project, including

exclusion information.
Build Build F7 Builds the Repackager project into an InstallShield

project and a Windows Installer package.
Build Stop Build Ctrl+Break Terminates an in-process build.
Tools Repackaging Launches the Repackaging Wizard.

Wizard
Tools VMware Launches the VMware Repackaging Wizard.

Repackaging
Wizard
Tools Exclusions Launches the Exclusions Editor.

Editor
Tools Options Displays the Options dialog box.
Help Contents Launches the Help Library, displaying the Contents

tab.
Help Index Launches the Help Library, displaying the Index tab.
Help Search Launches the Help Library, displaying the Search

tab.
Help Support Accesses the Macrovision Support Web site.

Central
Help Web Accesses the Community on the Macrovision Web

Community site.
Help ReadMe Displays the AdminStudio ReadMe file.
Help Feedback Accesses the feedback form on the Macrovision

Web site.
Help Macrovision Accesses the Macrovision Web site.

on the Web
Help About Displays the About Repackager dialog box.

Repackager
Up Moves you up one view in the View List.

Keyboard
Down Moves you down one view in the View List.
Back Displays the previously displayed view in the View

List.
Forward Returns you to the view from which you selected the
Back button.
Dialog Boxes
Repackager includes the following dialog boxes to assist you in your project creation:
• Create Report Dialog Box
• Isolation Options Dialog Box
• Options Dialog Box
• Password Required Dialog Box
• Project Properties Dialog Box
• WinINSTALL Conversion Dialog Box
About Repackager Dialog Box

This dialog box available by selecting About Repackager from the Help menu, displays version
information for Repackager.
Figure 3-3: About Repackager Dialog Box

Create Report Dialog Box

The Create Report dialog box, available by selecting Create Report from the Project menu, allows you to
configure a report for the current Repackager project, or a specific subset of captured data.
Figure 3-4: Create Report Dialog Box
This dialog box contains the following options:
Table 3-11: Create Report Dialog Box Options
Option Description
All captured data (files, registry Select to have the report include all captured data.
entries, shortcuts, etc.)
Summary only If you select All captured data, you can select this option to only display
summary information in the report (the number of items captured and the
number of items excluded for files, .ini files, registry data, and shortcuts).
Current view only Select this option to include only the currently selected view in the report.
Indicate excluded items Select to display items that have been marked as excluded in Repackager.
Report File Format Select the file format for Repackager reports: HTML or Text.
Create When you click Create, you are prompted for a name and location for the
outputted report.

Isolation Options Dialog Box

Application isolation reduces versioning conflicts by modifying an application so it always loads the
versions of components—such as DLLs—with which it was originally developed and tested.
On the Isolation Options dialog box, which is opened by selecting Isolation Options from the Tools
menu, you can specify the following Repackager isolation options:
• Assembly Options—Specify the type of assemblies Repackager will create, and the assembly naming
conventions. See Manifest Options Tab
• Digital Signature Options—Configure the certificate information required when using shared
assemblies. See Digital Signature Tab.
Note: The modifications you make on the Isolation Options dialog box will be recorded in the isolationconfig.ini
file, which is stored in the AdminStudio Shared directory.
Manifest Options Tab

The Manifest Options tab allows you to configure several settings associated with manifests.These
settings include
Table 3-12: Isolation Options Dialog Box / Manifest Options Tab
Option Description
Assembly Type This option allows you to select the type of assemblies that Repackager will create and
use:
• Create private side-by-side assemblies in the application folder
• Create shared side-by-side assemblies in the WinSxS folder (Default)
Note: Manifests for shared assemblies must be digitally signed. This can be done in the
Digital Signature Tab.
Note: A 2048-bit key is required to sign a Windows XP assembly/manifest being installed

to the WinSxS folder.
Assembly Naming Specify your company and division information to define the default naming convention
Conventions that Repackager will use when creating assemblies during application isolation
By default, assembly names are specified in the form of:
Company.Division.Assembly
Note: See see About Assemblies and About Manifests for more information.

Table 3-12: Isolation Options Dialog Box / Manifest Options Tab (cont.)
Option Description
Create a new component Select this option if you want to create a new component for each assembly created
for each assembly during isolation. This check box applies to all assemblies created.
Caution: If you are creating assemblies for applications files within multiple components,
this option must be selected for successful application isolation.
If you are planning to deploy this isolated package to operating systems prior to Windows
XP, always check this box.
Digital Signature Tab

On the Digital Signature tab, you can configure the certificate information required when using
shared assemblies.This required digital signature provides an extra layer of protection, allowing you to
obtain information about the company who created a global assembly.
Figure 3-5: Isolation Options Digital Signature Options Tab
Caution: Repackager uses timestamping when signing global assemblies. Consequently, you must have an Internet
connection on the computer when you create a global assembly.

You must configure the following options when signing these assemblies:
Table 3-13: Isolation Options Dialog Box / Digital Signatures Tab
Item Description
Certificate File Click the Browse ( ) button next to the field and navigate to the certificate file you are using to sign
assemblies.
A digital certificate identifies you and/or your company to end users and assures them the data they
are about to receive has not been altered.
Credentials Select this option to use credential files as the code signing technology. If you select this option, you
must supply the name and location of both your software publishing credential files: SPC File and
PVK File.
Note: In order to receive a software publishing credentials and a private key, you must supply a
certification authority, such as such as VeriSign, with specific information about your company and
software.
SPC File Specify the name and location of your software publishing credentials file (.spc).
PVK Specify the name and location of your private key file (.pvk).
Certificate Select this option to use the name of an existing certificate file in the Certificate Store as the code
Name in the signing technology. The Certificate Store is a central repository for certificate files. Using a
Store Certificate Store allows you to reuse the certificate files for different purposes as necessary.
Note: For more information, see About Digital Certificates.

Options Dialog Box

The Options dialog box, available from the Tools menu, presents options on three tabs: Colors, Merge
Modules, and Build Options.
Colors Tab
On the Colors tab, you can configure the color of scanned items and deleted items in Repackager's
exclusion views (Files, .ini Files, Registry Data, and Shortcuts).
Figure 3-6: Colors Tab of the Options Dialog Box
Merge Modules Tab

On the Merge Modules tab, you can specify additional directories containing custom merge modules
to use during repackaging.
Figure 3-7: Merge Modules Tab of the Options Dialog Box

Build Options Tab

On the Build Options tab, you can specify whether or not you want to list ICE validation warnings in
the Repackager output window during the Build process.
Figure 3-8: Build Options Tab of the Options Dialog Box
To display any ICE validation warnings that occur during the Repackager Build process, select the
Display ICE validation warnings option. By default, this option is not selected.
Password Required Dialog Box

The Password Required dialog box is displayed when attempting to run the SmartScan Wizard on an
InstallShield Professional setup which requires a password. Provide the password for the setup and click
OK to proceed.
For InstallShield Professional 6.x and 7.x setups, the SmartScan Wizard can bypass password
protection, and will not prompt you for a password even if one is required to run the installer.
Project Properties Dialog Box

The Project Properties dialog box, accessed by selecting Properties from the Projects menu, contains two
tabs:
Table 3-14: Project Properties Dialog Box Tabs
Tab Description
General Tab Allows you to view properties for the current Repackager project.
Exclusions Tab Use to configure the location of the default exclusion file.

General Tab
The General tab of the Project Properties dialog box displays information about the current Repackager
project (.irp).
Figure 3-9: Project Properties Dialog Box General Tab
The following options are displayed:
Table 3-15: General Tab Options
Option Description
Project Location The full path of the current Repackager project file (.irp).
Project File The name of the current Repackager project file.
Captured Data File The name and location of the captured data file (.inc), which was either created by the
Repackaging Wizard or during conversion of a Novell ZENworks project, Microsoft SMS
project, or WinINSTALL project. The path is relative to the current Repackager project file.
Registry Data File The name and location of the file containing captured registry data. The path is relative to the
current Repackager project file.
Conversion Options The name and location of the Options.ini file, which contains an exhaustive list of all options
File you can use during conversion of the Repackager project to an InstallShield Editor project
and Windows Installer package.
Editor Project File The name and location of the InstallShield Editor project file as set in the Product View (MSI
Package). The path is relative to the current Repackager project file.
Windows Installer The name and location of the Windows Installer package. The path is relative to the current
Package Repackager project file.

Exclusions Tab
The Exclusions tab allows you to select a exclusion file to use as a filter when importing captured data
into a Repackager project.
Figure 3-10: Project Properties Dialog Box Exclusions Tab
Select one of the following options for the configuration file:
Table 3-16: Exclusions Tab Properties
Option Description
Do not use any external Repackager will import all captured data into the Repackager project.
configuration
Use settings from the Repackager will use the settings contained in isRepackager.ini in the AdminStudio
shared location Shared directory (configured during installation). Use this option when you are working
in a team environment where the exclusion list needs to be stored in a centralized
location.
Use settings from Repackager will use the settings contained in the default.ini file in the Repackager
InstallShield defaults folder. These are the InstallShield-recommended exclusions. InstallShield recommends
you do not modify these exclusions so you can return to them if you need to restart
your exclusion list.
Edit Click to open the Exclusions Editor, which you can use to exclude files, registry entries,
.ini files, or shortcuts from the Repackager project. See Configuring Exclusions Using
the Exclusions Editor and Exclusions Editor Interface for more information.
Use settings from a custom Specify or browse to a file created with the Exclusions Editor that you want to use as
file your filter during conversion to a Repackager project. You would create a custom
exclusion file based upon your company's requirements.

Caution: Using the custom settings option, it is possible to use the local settings file (isRepackager.ini) in the
Windows directory. This file is also used for default exclusions for the Repackaging Wizard. By modifying this file, you
introduce the possibility of excluding data at repackaging time in subsequent Repackaging Wizard executions, as opposed
to marking items as excluded in a Repackager project (which does not affect the captured data). For this reason,
InstallShield highly recommends you do not use the isRepackager.ini configuration file in the local Windows folder for your
Repackager exclusions.
WinINSTALL Conversion Dialog Box

When you convert a WinINSTALL project to a Repackager project, this dialog box appears to allow you
to set WinINSTALL-specific variables. These variables are:
Table 3-17: WinINSTALL Variables
Variable Description
@Server The machine name of the server where the WinINSTALL directory is located.
@WinstallDir The location of the directory where the WinINSTALL executables are located.
Views
Repackager includes several views, from which you can examine the captured data that will be used to
create an InstallShield Editor project (.ism) and Windows Installer package (.msi). Depending on the
presence or absence of certain data types, some views may not be displayed. For example, if the setup
does not include any .ini files, the INI Files view will not be displayed in the View List.
The following views are available in Repackager:
• Captured Installation View
• Files and Folders View
• Registry Entries View
• Shortcuts View
• INI Files View
• Deleted Files View
• Deleted Registry Entries View
• Repackaged Output View
• Package Information View
• Advanced Settings View

Note: Information listed in the views (such as files, .ini files, or registry entries) is limited to 267 characters in length.
Anything longer than this limit will be truncated in the view. The full value can be viewed in InstallShield Editor.
Captured Installation View

From the Captured Installation View, you can review summary information about the setup you are
converting into a Windows Installer package.
Figure 3-11: Repackager Captured Installation View
This view lists the operating system (including service pack) where capture was performed, the number
of files captured, the number of .ini file changes made, the number of registry entries captured, and the
number of shortcuts captured. Each subview of this view allows you to view the names and associated
information of each item captured, and selectively exclude (or reinclude) these items from the ultimate
If no entries were captured of a particular type, the corresponding view does not appear in the View List.
For example, if no .ini file changes were captured, the .ini File view is not displayed.
From the Captured Installation view, you can also create a report or scan for setup intent.
Additionally, you must specify the original target folder for the installation. In most cases, this will be a
subdirectory of [ProgramFilesFolder]. Alternatively, you can enter your own target. This value will be set
as the value for INSTALLDIR, and is a mandatory property. Information about the provided install
locations can be found in the System Folder Properties topic of the Windows Installer online help.
You can also perform some tasks from this view—creating a setup capture report, scanning for setup
intent, and scanning InstallShield Professional media (if the original setup was created with
InstallShield Professional) for additional files.

Files and Folders View

From the Files and Folders view, you can examine information about each captured file, selectively
exclude files or directories from the package you are creating, or reinclude files that you previously
excluded.
Figure 3-12: Repackager Files and Folders View
The upper pane displays the number of files captured and how many of these files will be excluded from
the Windows Installer package when built. The lower-left pane provides a tree from which you can see
where files will be installed and the names of the files.
When you select a file from the tree, the lower-right pane displays attributes for that file. These
attributes are:
Table 3-18: File Attributes
Attribute Description
Name The file's name.
Size The file's size in bytes.
Version The file's version.
Short Name The short name for the file (if the file's author defined it).
Language The file's language.

Excluding Files and Subdirectories

To specify which files and subdirectories you want to include in the package, use the Exclude, Exclude
All, Include, and Include All buttons:
• To exclude a captured file from the package, select the file you want to exclude and click Exclude.
• To exclude all captured files and subdirectories within a directory from the package, select the
directory containing the files and subdirectories you want to exclude and click Exclude All.
• To include a captured file in the package that had previously been excluded, select the file you want
to include and click Include.
• To include all captured files and subdirectories within a directory, select the directory containing the
files and subdirectories you want to include and click Include All.
Registry Entries View

From the Registry Entries view, you can examine information about each captured registry entry,
selectively exclude registry values or registry keys from the package you are creating, or reinclude
registry values that you previously excluded.

The upper pane displays the number of registry entries captured and how many of these entries will be
excluded from the Windows Installer package when built. The lower-left pane provides a tree displaying
the registry keys and subkeys captured. When you select a key from the tree, the lower-right pane
displays any registry values for that key. Displayed information includes:
Table 3-19: Registry Attributes
Name The registry value name.
Type The registry value type. This can be either a string value, an expandable string value, a multistring
value, a dword value, or a binary value.
Value The content of the registry value.
Excluding Registry Entries

To specify which registry entries you want to include in the package, use the Exclude, Exclude All,
Include, and Include All buttons:
• To exclude a registry entry from the package, select the registry entry you want to exclude and click
Exclude.
• To exclude all registry entries and subdirectories within a directory from the package, select the
directory containing the registry entries you want to exclude and click Exclude All.
• To include a registry entry in the package that had previously been excluded, select the registry entry
you want to include and click Include.
• To include all registry entries and subdirectories within a directory, select the directory containing
the shortcuts and subdirectories you want to include and click Include All.

Shortcuts View
From the Shortcuts view, you can examine information about each captured shortcut, selectively exclude
shortcuts from the package you are creating, or reinclude shortcuts that you previously excluded.
Figure 3-13: Repackager Shortcuts View
The upper pane displays the number of shortcuts captured and how many of these shortcuts will be
excluded from the Windows Installer package when built. The lower-left pane provides a tree from
which you can see where shortcuts will be installed and the names of the shortcuts. When you select a
shortcut from the tree, the lower-right pane displays attributes for that shortcut. These attributes are:
Table 3-20: Shortcuts View Attributes
Description The name of the shortcut as it appears on the desktop.
Command The fully-qualified path and name of the file to which the shortcut points.
Working Dir The shortcut's working directory, which may need to be specified so required files can load.
This is equivalent of the Start in value found when right-clicking a shortcut from the desktop and
selecting Properties.
Icon File The name of the file containing the shortcut's icon.
Icon Index The index number for the icon in the icon file.

Note: Shortcuts can be excluded from the Windows Installer package you are building on an individual shortcut basis or
by directory.
Excluding Shortcuts
To specify which shortcuts you want to include in the package, use the Exclude, Exclude All, and Include
buttons:
• To exclude a shortcut from the package, select the shortcut you want to exclude and click Exclude.
• To exclude all shortcuts and subdirectories within a directory from the package, select the directory
containing the shortcuts you want to exclude and click Exclude All.
• To include a shortcut in the package that had previously been excluded, select the shortcut you want
INI Files View

From the INI Files view, you can examine information about each captured .ini file, selectively exclude
.ini files or .ini file sections from the package you are creating, or reinclude .ini files or sections that
you previously excluded.
Figure 3-14: Repackager INI Files View
The upper pane displays the number of .ini files captured and how many of these .ini files will be
excluded from the Windows Installer package when built. The lower-left pane provides a tree from
which you can see the full path to captured .ini files and sections contained within the .ini files. When
you select a section from the tree, the lower-right pane displays name/value pairs in that section.

Deleted Files View

From the Deleted Files view, you can examine information about each file deleted during repackaging,
selectively exclude files or directories from the package you are creating, or reinclude previously
excluded files.
The upper pane displays the number of files captured and how many of these files will be excluded from
the Windows Installer package when built. The lower-left pane provides a tree from which you can see
where files will be installed and the names of the files. When you select a file from the tree, the lower-
right pane displays attributes for that file. These attributes are:
Table 3-21: Deleted Files View Attributes
Name The file's name.
Size The file's size in bytes.
Version The file's version.
Short Name The short name for the file (if the file's author defined it).
Language The file's language.
Excluding Files and Subdirectories

To specify which files and subdirectories you want to include in the package, use the Exclude, Exclude
All, Include, and Include All buttons:
• To exclude a captured file from the package, select the file you want to exclude and click Exclude.
• To exclude all captured files and subdirectories within a directory from the package, select the
directory containing the files and subdirectories you want to exclude and click Exclude All.
• To include a captured file in the package that had previously been excluded, select the file you want
• To include all captured files and subdirectories within a directory, select the directory containing the
files and subdirectories you want to include and click Include All.

Deleted Registry Entries View

From the Deleted Registry Entries view, you can examine information deleted from the registry
repackaging, selectively exclude registry keys from the package you are creating, or reinclude previously
excluded data.
The upper pane displays the number of deleted registry entries captured and how many of these entries
will be excluded from the Windows Installer package when built. The lower-left pane provides a tree
displaying the registry keys and subkeys captured. When you select a key from the tree, the lower-right
pane displays any registry values for that key. Displayed information includes:
Table 3-22: Deleted Registry Entries View Attributes
Name The registry value name.
Type The registry value type. This can be either a string value, an expandable string value, a multistring
value, a dword value, or a binary value.
Value The content of the registry value.
Excluding Registry Entries

To specify which registry entries you want to include in the package, use the Exclude, Exclude All,
Include, and Include All buttons:
• To exclude a registry entry from the package, select the registry entry you want to exclude and click
Exclude.
• To exclude all registry entries and subdirectories within a directory from the package, select the
directory containing the registry entries you want to exclude and click Exclude All.
• To include a registry entry in the package that had previously been excluded, select the registry entry
you want to include and click Include.
• To include all registry entries and subdirectories within a directory, select the directory containing
the shortcuts and subdirectories you want to include and click Include All.

Repackaged Output View

From this view, you can configure build options for the project, including whether to build an MSI
package automatically following conversion.
Figure 3-15: Repackager Repackaged Output View
The following properties are available for configuration:
Table 3-23: Repackaged Output View Options
Option Description
Editor project Provide the name and location of the InstallShield project (.ism) file.
Windows Installer package The name and location of the Windows Installer package (.msi). If a Windows Installer
package has not yet been built from this Repackager project, (not built) is listed.
Create a Windows Installer If this option is selected, after creating the InstallShield project file (.ism), a Windows
package after creating Installer (.msi) file will be built based on that project file.
the Editor project

Option Description
Windows Installer Package If you have selected the Create a Windows Installer package after creating the
Options Editor project option, you need to also select one of the following options:
• Create single, compressed .msi file—Select this option if you want to
compress all necessary files inside the .msi package, as opposed to storing them
outside of the .msi database.
• Create single, compressed setup.exe file—Select this option if you want to
compress all files inside a setup.exe file, including the .msi file and all other
necessary files.
• Create .msi file + external compressed .cab file—Select this option if you
want to create an .msi file and want to compress the rest of the necessary files in
an external .cab file.
• Create .msi file + external compressed .cab file + setup.exe—Select this
option if you want to create an .msi file and a setup.exe file, and want to compress
all the rest of the necessary files in an external .cab file.
• Create uncompressed .msi file—Select this option if you want to create an
uncompressed .msi file. All of the rest of the necessary files, in uncompressed
format, would be shipped with the .msi file.
• Create uncompressed .msi file + setup.exe—Select this option if you want to
create an uncompressed .msi file along with a setup.exe file. All of the rest of the
necessary files, in uncompressed format, would be shipped with the .msi and
setup.exe files.
Create an isolated version Select this option to create a second, isolated version of the Windows Installer package
of the Windows Installer when the Windows Installer package is built.
package
Isolation reduces versioning conflicts by modifying an application so it always loads the
versions of components—such as DLLs—with which it was originally developed and
tested.
If this option is selected, an additional Windows Installer package will be created in the
same directory as the .ism file and the other .msi file, with the naming convention of:
For more information on how Repackager isolates applications and the available
isolation options, see Isolating Windows Installer Packages.
Run automated tests Select this option to automatically run PackageExpert tests against the newly built
against the Windows Windows Installer package to determine if it is built according to Windows Installer
Installer package standards, and if it is in compliance with the installation requirements of the Windows
Vista operating system.
All of the tests that are currently selected on the PackageExpert Configuration View
are run, and those selected tests that are automatically resolvable, will be resolved.
Note: For more information on PackageExpert, see Using PackageExpert to Identify

and Resolve Package Errors.

Option Description
Use the default Editor When building an InstallShield Editor project, select this option to use the default
template InstallShield Editor template.
A project template contains all of the default settings and design elements that you want
to use as a starting point when you create an installation project.
Use a customized When building an InstallShield Editor project, select this option to specify a customized
template InstallShield Editor Project Template to use.
For example, if you wanted all of your InstallShield Editor projects to have a special
custom dialog, a set of required redistributables, and a particular SQL script, you could
create a project template that has all of those settings. Then, any time that you wanted
to create a new project, you could base it off of your custom template. This enables you
to avoid re-creating the custom dialog, re-adding the redistributables, and re-adding the
SQL script every time that you create a new InstallShield Editor Project.
Build Click to initiate the build process to build a Windows Installer package.
Repackaged Output Tasks After an InstallShield Editor project and a Windows Installer package has been built, you
can use these links to perform the following tasks:
• Modify the Editor Project—Open this Repackager project’s associated
InstallShield project in InstallShield Editor.
• Modify the Windows Installer package with Editor—Open this Repackager
project’s associated Windows Installer package in InstallShield Editor.
Once you have built the Windows Installer package and/or InstallShield Editor file, you can launch
InstallShield Editor from the Repackaged Output area of the view.

Package Information View

The Package Information view allows you to specify information for the Windows Installer package that
you build from the Repackager project. Much of this information may be prepopulated based on settings
used in the Repackaging Wizard.
Figure 3-16: Repackager Package Information View
You can configure the following options:
Table 3-24: Package Information View Options
Option Description
Company Name The name of the company that developed the product you are repackaging.
Product Name The name of the product you are repackaging.
Version The product's version number.
Product URL The URL for product information. This appears in Add/Remove Programs in the Control
Panel.
Support URL A URL for support information. This also appears in Add/Remove Programs in the Control
Panel, and is often changed during repackaging to provide an internal support URL.

Advanced Settings View

From the Advanced Settings view, you can configure several additional settings that may apply to your
repackaged setup.
Figure 3-17: Repackager Advanced Settings View
Select the appropriate options:
Package Conversion Options

The following package conversion options are available:
Table 3-25: Package Conversion Options
Option Description
Use Editor path variables instead When storing files in the InstallShield Editor project (.ism), the Wizard uses path
of physical source paths variable locations whenever possible.
Display only the Welcome dialog Only the Welcome dialog box is displayed when the Windows Installer package is
box during installation run on a target machine. If this option is unchecked, the default UI sequence is
displayed when the setup is installed.
Replace files with merge modules Following best practice rules, Repackager replaces components with
wherever possible comparable merge modules whenever possible.
Use the language captured by the When selected, the target package's language will be the language detected by
Repackager as the language of Repackager (as displayed in the Captured Installation view).
the setup

Table 3-25: Package Conversion Options (cont.)
Option Description
Include files from Setup Intent Any files identified when running the Setup Intent Wizard will be included in the
scan package (unless you have manually excluded them from the project).
Component Settings Options

The following component settings options are available:
Table 3-26: Component Settings Options
Option Description
Mark components destined for Executable files installed to the system folder (System32Folder) are marked as
the System folder as permanent Permanent files and will not be uninstalled when the package is uninstalled. This
eliminates ICE09 validation errors.
Mark components destined for Executable files installed to the CommonFilesFolder (or a subfolder of
the CommonFiles folder as CommonFilesFolder) are marked as shared files. This ensures that these
shared components can coexist with DLLs installed by previous setups.
Map registry data to the Setting this option reduces the number of ICE33 warnings that can occur during
appropriate COM tables package validation, resulting from data not being mapped to the appropriate MSI
tables.
Map registry data to the If selected, ODBC-related registry data is mapped to ODBC tables instead of the
appropriate ODBC tables Registry table. This data will only function correctly if Windows Installer supports
the ODBC resource being mapped; InstallShield recommends you do not enable
this option if you are unsure whether the ODBC resources are supported
correctly by Windows Installer.
Map NT Service events to the If selected, NT Service–related registry data is mapped to ServiceControl table
ServiceControl table instead of the Registry table.

InstallShield SmartScan Options

The following InstallShield SmartScan options are available:
Table 3-27: InstallShield SmartScan Options
Option Description
Include files from InstallShield Files identified in the Media Scan Wizard will be included in the package (unless
legacy media scan you have manually excluded them from the project).
Exactly match legacy setup’s For SmartScan projects or projects using the Professional Logging Method:
Operating System requirements
• Selected—if this option is selected, component conditions will store
specific operating system information: if the filter was NT4, the condition
will be (VersionNT=4).
• Unselected—If this option is not selected, component conditions will store
a grouping of the operating system: if the filter was NT4, the condition will
be (VersionNT).
• Default—By default, this option is not selected.
Repackaging Wizard
Repackager provides the Repackaging Wizard to convert a legacy setup into a Repackager project. Using
this Wizard, you can select the repackaging method (either Snapshot or Installation Monitoring), specify
the setup(s) you want to repackage, and run the setup(s). When the Repackaging Wizard has finished its
analysis, Repackager automatically creates a Repackager project (.irp) file, which can be modified in
Repackager. You can then convert this file to an InstallShield Editor project (.ism) for further editing, or
convert it directly to a Windows Installer package (.msi).
The Repackaging Wizard includes the following panels:
• Welcome Panel
• Method Selection Panel
• Snapshot Method Panel
• Collect Product Information Panel
• InstallScript MSI Identified Panel
• InstallShield Professional Setup Panel
• Set Target Project Information and Capture Settings Panel
• InstallScript MSI Conversion Output Panel
• Repackaging Panel
• Summary Panel
• Additional Repackaging Wizard Dialog Boxes

Welcome Panel
The Welcome panel appears when you first launch the Repackaging Wizard, providing some
introductory information about the use of the Wizard, including that it is for use with traditional (non-
Windows Installer-based) installations.
Figure 3-18: Repackaging Wizard Welcome Panel
Method Selection Panel

From the Method Selection panel, select the method(s) you want to use for repackaging.
Figure 3-19: Repackaging Wizard Method Selection Panel

The available choices include:
Table 3-28: Method Selection Panel Options
Options Description
Snapshot The Snapshot method involves taking system snapshots before and after an installation,
and then creating the Windows Installer package from the difference between them. Any
configurations you make between snapshots is also included in the generated Windows
Installer package.
Installation Monitoring Installation Monitoring watches all activities generated by an installation, and then
determines the files, .ini files, registry entries and shortcuts that should be included in
the generated Windows Installer package.
Installation Monitoring is significantly faster than the Snapshot repackaging method.
If there are services running on the machine that have nothing to do with the installation
being repackaged, click the Advanced Settings link to open the Excluded Processes
Dialog Box, where you can choose to exclude those processes.
Tip: If you know that the installation that you are capturing is from a self-extracting .exe
file and if you want to use the Installation Monitoring method, you should click
Advanced Settings and add the name of that .exe file to the excluded processes list.
Using the InstallShield Professional Logging Method

The InstallShield Professional Logging Method, which should be used to repackage InstallShield Editor
and DevStudio 9.x InstallScript installations, is not offered as a choice on the Method Selection
Options Panel.
However, if you specify an InstallShield Editor or DevStudio 9.x InstallScript installation on the Collect
Product Information Panel (the next panel in the Repackaging Wizard), Repackager will
automatically detect the InstallScript installation and will display the InstallShield Professional
Setup Panel. On this panel, you can choose to use the InstallShield Professional Logging
Method instead of the Installation Monitoring or Snapshot methods.
It does not matter which option you select on the Method Selection Panel, but if you select the
Snapshot method, you must select Single Step on the Snapshot Method Panel (which appears
next). If you instead select Multiple Steps, Repackager will not recognize the setup as an InstallShield
Editor or DevStudio 9.x InstallScript installation and the InstallShield Professional Setup Panel
will not appear.

System Changes Captured by Repackager

Regardless of the repackaging method used, Repackager captures system changes made to the following:
• Application Paths
• Environment Variables
• Files
• INI Files
• NT Services
• ODBC Data Sources
• ODBC Drivers
• Printer Drivers
• Registry Entries
• Shortcuts
If you are using the InstallShield Professional Logging Method to repackage an InstallShield Editor or
DevStudio 9.x InstallScript installation, the following additional information is also collected:
• Path Variables
• Feature/Component Tree
Snapshot Method Panel

The Snapshot Method Panel, which is only displayed if you use the snapshot technology, allows you to
specify the way in which you perform repackaging.
Figure 3-20: Repackaging Wizard Snapshot Method Panel

On the Snapshot Method Panel, you have the following two options:
Table 3-29: Snapshot Method Panel Options
Option Description
Single Step Repackaging in a single step requires you specify at least one setup program to repackage.
The Repackager first takes an initial system snapshot, then runs the setup program(s) you
specify, and then takes a second snapshot to create the script file that can be converted into a
You also have the option of requiring the Repackager to prompt you before running the setup
program(s), allowing you the opportunity to make changes to your system that you want
included in the final package.
Note: If you are repackaging an InstallShield Editor or DevStudio 9.x InstallScript installation
and want to use the InstallShield Professional Logging Method, select Single Step.
Multiple Steps Repackaging in multiple steps allows you to run the Repackager to obtain an initial system
snapshot, after which the Repackager exits. You can then perform any modifications to the
system, such as changing configurations, running installations, and so forth. After making the
necessary modifications, run the Repackager again to analyze system status changes. The
difference between the second Repackager execution and the first results in the script file that
ultimately can be converted into a Windows Installer package.
The single step method is very straightforward if you are repackaging applications and not performing
many system changes. The multiple step method allows greater flexibility because a setup is not
required. This allows you to capture system configurations within the Repackager output, and ultimately
within a Windows Installer package. For example, you could modify the screen color depth and create an
MSI package for just that configuration.
If Single Step is selected, the Collect Product Information Panel is displayed when you click Next.
If Multiple Steps is selected and you are performing the initial snapshot, the Collect Product Information
panel is displayed, but the Setup Programs area is disabled. If you are performing a system status change
analysis, the Repackaging Panel appears when you click Next.

Collect Product Information Panel

The Collect Product Information panel gathers information necessary for repackaging the
installation(s).
Figure 3-21: Repackaging Wizard Collect Product Information Panel
The information on the Collect Product Information Panel is divided into two sections: Setup
Programs and Product Information.
Setup Programs Area

The Setup Programs area contains information about the setup you are repackaging. Repackager uses
this information to launch the setup correctly following pre-analysis. The information collected
includes:
Table 3-30: Setup Programs Options
Properties Description
Program File The name and location of the setup executable. Click the Browse button to locate this
file. This is a required field.
Command-Line Any command-line arguments to be used when the setup is run.

Argument(s)

Table 3-30: Setup Programs Options (cont.)
Edit Setup List Click to display the Additional Setup Programs dialog box, from which you can enter
additional installations to repackage together with this installation. Additional setups share
the same product name, version number, and company name in the repackaged
installation. However, as you locate each additional setup to repackage, you can specify
command-line parameters pertaining only to that setup. You can also specify the order in
which the installations are run, should it be necessary.
Caution: If you are repackaging an InstallShield Editor or DevStudio 9.x InstallScript

installation and want to use the InstallShield Professional Logging Method, specify only one
Program File. If you specify multiple setup program files, the InstallShield Professional
Setup Panel will not appear, and the Repackaging method that you chose on the Method
Selection Panel will be used instead.
Product Information Area

In the Product Information area, you identify the repackaged installation’s Product Name, Version
Number, and Company Name.
Table 3-31: Product Information Options
Field Description
Product Name Enter the name for final repackaged installation. This could be the name of the original
installation (for example, Tuner), the name of a collective group of products (for example,
InstallShield Applications), or another name of your selection (for example, My Apps). This is a
required field.
Version Number Enter the version of the product.
Company Name Enter the name of the company.
Product Support Information

If you want to associate Web sites with this installation, click the More link in the Product Information
area to open the Additional Product Information dialog box, where you can enter the Product URL and
Support URL for the application you are repackaging.

InstallScript MSI Identified Panel

This panel opens if the Repackaging Wizard identifies an installation as an InstallScript MSI installation
created with InstallShield Editor, InstallShield DevStudio, or InstallShield Developer.
Figure 3-22: Repackaging Wizard InstallScript MSI Identified Panel
InstallScript MSI installations use a Windows Installer database for storage of all file/registry
information, but the actual user interface, and much of the installation logic is driven by the InstallScript
engine via a setup.exe file. This type of installation architecture can cause difficulties during
deployment, such as:
• inability to customize or transform the application
• inability to conflict detect
• inability to suppress the user interface
• difficulty patching or upgrading the application

Also, if an InstallScript MSI installation is repackaged using traditional methods (OS Snapshot or
Installation Monitoring), significant platform-specific or custom installation, maintenance, and
uninstallation logic, and user interface information is lost because those methods only record the
installation activities for the specific platform used during repackaging.
Therefore, it is recommended that you use InstallScript Scan to convert an InstallScript MSI installation
to a Basic MSI package with InstallScript support. InstallScript Scan preserves the original components
and much of the InstallScript installation logic, architecture, and maintainability of the original
installation package.

Select one of the following options:

• Yes—Use InstallScript Scan to automatically extract the MSI package and convert it to Basic MSI,
while preserving the original components and installation logic. This is the default selection.
• No—Repackage the installation using the repackaging method selected on the Method Selection
Panel (Installation Monitoring or Snapshot).
Click Next to proceed.
InstallShield Professional Setup Panel

This panel appears in the Repackaging Wizard if you specified an InstallShield Editor or DevStudio 9.x
InstallScript installation in the Program File field of the Collect Product Information Panel, and if:
• You specified only one program file on the Collect Product Information Panel, and
• You selected the Installation Monitoring method on the Method Selection Panel, or
• You selected the Snapshot method on the Method Selection Panel and then selected Single Step
on the Snapshot Method Panel.
Figure 3-23: Repackaging Wizard InstallShield Professional Setup Panel
If you want to use the InstallShield Professional Logging Method, select the Use InstallShield
Professional Logging instead of repackaging check box.
Using the InstallShield Professional Logging Method, Repackager can read logged output of
InstallShield Editor and DevStudio 9.x InstallScript installations. This method replaces the other
repackaging methods (Installation Monitoring and Snapshot) for InstallShield Editor or DevStudio 9.x
InstallScript installations. By using this method, you will be able to get additional information that
would not be captured by repackaging, including path variables and a feature tree. For more
information, see InstallShield Professional Logging Method.

Set Target Project Information and Capture Settings Panel

The location where you want files created by Repackager stored is defined in the Project path to store
files field on the Set Target Project Information Panel.
Figure 3-24: Repackaging Wizard Set Target Project Information and Capture Settings
It is recommended that this location not be located on your clean machine, but rather on the same
machine as the Repackager executable (most likely on your administrator machine).
You can also review or edit current capture settings by clicking Edit, which displays the Analysis
Options dialog box.
Click Start to begin repackaging and display the Repackaging Panel.

InstallScript MSI Conversion Output Panel

On this panel, specify the location where you want Repackager to store the files it creates during
InstallScript Scan analysis. The converted Windows Installer MSI package will be saved to this location.
Figure 3-25: Repackaging Wizard InstallScript MSI Conversion Output Panel
It is recommended that this location not be located on your clean machine, but rather on the same
machine as the Repackager executable (most likely on your administrator machine).
You can also review or edit current settings by clicking Edit to open the Analysis Options dialog box.
On the Analysis Options dialog box, you can specify capture types for the repackaging session, and,
for snapshot-mode captures, you can restrict directory analysis to specific directories.
Click Start to begin repackaging and display the Repackaging Panel.

Repackaging Panel
The Repackaging panel appears while Repackager analyzes your system.
Figure 3-26: Repackaging Wizard Repackaging Panel 1
Depending on settings configured before starting repackaging, the analysis may stop following the initial
phase, and again after setup has been run.
After the setups have been completed, you are prompted to click the Process button to complete the
repackaging process.
When you click Process, the repackaging is performed and its progress is displayed.

Following repackaging, the Summary Panel is displayed.
Summary Panel
The final panel displayed by Repackager is the Summary panel.
Figure 3-29: Repackaging Wizard Summary Panel
This panel provides confirmation that repackaging was successful, and provides the location of the
source setup program(s), the Windows Installer package, and the InstallShield Editor project.

Additional Repackaging Wizard Dialog Boxes

The following dialog boxes can be accessed from the Repackaging Wizard:
• Additional Setup Programs Dialog Box
• Setup Information Dialog Box
• Excluded Processes Dialog Box
• Analysis Options Dialog Box
Additional Setup Programs Dialog Box

This dialog box, which is accessed by clicking the Edit Setup List button on the Collect Product
Information Panel of the Repackaging Wizard, displays a list of additional setup programs you want
to add to the final Windows Installer package.
Figure 3-30: Repackaging Wizard’s Additional Setup Programs Dialog Box
Essentially, this is a list of the other executables to run, in the order they are to be run, prior to final
analysis. The following buttons are available:
Table 3-32: Additional Setup Programs Dialog Box Buttons
Button Description
New Brings up the Setup Information dialog box to enter information about the setup programs.
Edit Displays the Setup Information dialog box to edit information about the currently selected setup.
Delete Removes the currently selected setup.
Up Moves the selected setup up in the setup programs list.
Down Moves the selected setup up in the setup programs list.

Setup Information Dialog Box

The Setup Information dialog box allows you to enter or edit information pertaining to the installations
you are repackaging.
Figure 3-31: Setup Information Dialog Box
Accessible from the Additional Setup Programs dialog box, you can provide the name and location
of an additional setup program, and any command-line arguments for the setup.
Excluded Processes Dialog Box

During Installation Monitoring, Repackager captures all of the activity of each service or process
running on the machine, and then processes this collected data. However, many services running on a
machine may have nothing to do with the installation being repackaged. Therefore, you may choose to
exclude those processes by adding them to the list on the Excluded Processes dialog box.
Figure 3-32: Repackaging Wizard Excluded Processes Dialog Box
You can open the Excluded Processes dialog box by clicking the Advanced Settings link on the
Repackaging Wizard Method Selection Panel. The Excluded Processes dialog box initially lists a default
set of processes.
• To add a process to this list, click the New ( ) button to add a new blank line to this list, and enter
the name of the process that you want to exclude.
• To delete a process from this list, select the process and click the Delete ( ) button.

Analysis Options Dialog Box

The Analysis Options dialog box, accessible by clicking Edit from the Set Target Project
Information and Capture Settings Panel or the InstallScript MSI Conversion Output Panel,
allows you to specify capture types for the repackaging session.
Figure 3-33: Analysis Options Dialog Box
You can select the following:

• Files
• Deleted files
• .ini files
• .ini files with non-.ini extensions
• Shortcuts
• Registry data

Additionally, for snapshot-mode captures, you can restrict directory analysis to specific directories,
which can significantly improve repackaging performance. Click New to add a directory restriction, edit
to modify an existing restriction, or delete to remove a restriction.
Options set in this dialog box apply to the current and subsequent repackaging sessions.

Repackaging Wizard Command-Line Options

The following command-line options are supported by the Repackaging Wizard:
Table 3-33: Command-Line Options
Option Description
-? Displays a dialog box containing usage information for all options.
-app <setup program list> Allows you to provide a pipe (|) delimited list of setups to run during repackaging.
You can also pass command-line arguments to the setup by separating them from
the setup name with a semicolon:
-app exe1; cmdline1|exe2; cmdline2|...exeN; cmdlineN
-b [<project file path and Specifies the build/release destination folder. If <project file path and name> is not
name>.ism] specified, Repackager uses the folder where the .inc file is stored. The project
name must end in .ism.
-cf <config.ini> This option allows you to select your own configuration template containing
exclusions. A sample of this type of file (named Default.ini) can be found in the
following directory:
AdminStudio Installation Directory\Repackager
This particular file contains the default exclusion information.
-cs <configuration type> This option allows you to select the configuration file type for exclusions. Possible
values are:
• Shared—Use shared settings from those stored in the AdminStudio Shared
directory.
• Custom—Use a custom configuration file (in conjunction with -cf).

Table 3-33: Command-Line Options (cont.)
Option Description
-is Regarding the Repackaging an InstallScript MSI Setup to a Basic MSI Setup
procedure, use this parameter in the command line using the following syntax:
Repack.exe -app "c:\setup.exe" -o C:\apps\output -mm -is
In the above example, the user wants to repackage c:\setup.exe using the
Installation Monitoring repackaging method (as specified by -mm) and InstallScript
conversion (as specified by -is). Repackager would perform the InstallScript
conversion process and produce a Basic MSI package with InstallScript support as
output. Without the -is parameter, Repackager would perform repackaging without
performing InstallScript conversion, and would only create a Repackager .inc file
as the output.
Note: The command line parameter -is will be considered only if the setup to be
repackaged is a InstallScript MSI setup. If user specified any other legacy setup that
is not a InstallScript MSI setup then -is will be ignored.
Note: If user chooses to use the Multiple Step Snapshot repackaging method, then
the -is parameter will be ignored. Even if the setup is an InstallScript MSI setup, -is
will still be ignored when using the Multiple Step Snapshot repackaging method.
-mode <snapshot mode> Repackager supports the following repackaging modes for snapshots:
• single—Single step repackaging that creates an INC file as its output.
• pre—Pre-scanning only scans the local drive for a baseline snapshot of the
system.
• post—Post-scanning only scans the local drive and compares the result with
the pre-scan. The differences are written to the INC file as output.
-mm Instructs Repackager to use installation monitoring as the repackaging technology.
-mp Instructs Repackager to use the InstallShield Professional Logging Method as the
repackaging technology.
-ms Instructs Repackager to use snapshots as the repackaging technology.
-o <.inc path name> Specifies a folder path not including the filename. The file name is derived from the
Product Name unless overridden with the -of switch.
-of <inc file name> Specifies the .inc file name that should be used instead of the product name. Use -o
to specify the path.
-pc <company name> Allows you to set the company name.
-pp <product name> Allows you to set the product name. This will be the same name as the generated
Repackager output file (.inc).
-pv <product version> Allows you to set the product version.

Table 3-33: Command-Line Options (cont.)
Option Description
-sb This option allows you to run Repackager silently, with no user interaction. A
progress dialog box is displayed. If no .ini file is specified using the -i parameter,
Repackager uses Repack.ini as the default input file. If an output folder is not
specified using -o, the default output folder is C:\Packages.
-sn This option allows you to run Repackager silently, with no user interaction and no
progress dialog box. If no .ini file is specified using the -i parameter, Repackager
uses Repack.ini as the default input file. If an output folder is not specified using -
o, the default output folder is C:\Packages.
-version This option displays standard version information for Repackager, including the full
version and copyright information.
Note: In addition to the - sign for command-line arguments, you can also use the / symbol.
Reboot Handling in the Repackaging Wizard

During repackaging, a setup may require a reboot. For example, some operations may require a file
which is in use be replaced, which can only be done after a reboot. Some nuances exist depending on the
repackaging technology you are using (Snapshot or Installation Monitoring). In either case, when the
Repackaging Wizard detects that a reboot is necessary, the Repackaging Wizard saves the appropriate
data and waits until you confirm that you are ready to reboot the machine.
For Snapshot repackaging, the operating system completes the reboot operation. During startup, the
operating system restarts all applications and processes and performs any pending file operations. One
of the applications that restarts is Repackager. Before you continue processing in Repackager, be patient
and ensure all processes and applications have restarted. This may take a minute or two. After the
applications and processes have been launched, you can continue repackaging by clicking Process.
For Installation Monitoring, on reboot the operating system launches the Repackaging Wizard, which in
turn launches applications and processes and waits until these are finished before prompting you to
continue repackaging. However, in some cases the processes or applications launched by the
Repackaging Wizard will launch other applications and processes. As in Snapshot repackaging, it is
generally a good idea to wait a minute or two before clicking Process.
In both circumstances, waiting helps ensure the setup is fully installed and that captured data contains
the necessary information to properly rebuild the setup as an MSI installation.
SmartScan Wizard
The SmartScan Wizard is designed to scan original, InstallShield Professional 5.x and later media for
setup information that may not have been captured during repackaging, such as possible additional files,
.ini files, shortcuts, or registry data (such as for language-specific setups or platform-specific setups).
This primarily involves OS-dependent and language-dependent files that may be included in header
files. Ultimately, this makes the installation more portable.

Tip: Any files found will be displayed in Repackager in a different color (as specified in the Color tab of the Options dialog
box).
The SmartScan Wizard is also able to group files, shortcuts and registry entries into features
corresponding to InstallShield Professional components. Any items (files, folders, shortcuts, or registry
entries) that are attached to a component directly or indirectly (through File Groups), are attached to
their corresponding features.
Automatic Launch of the SmartScan Wizard

For your convenience, if a Repackaging project is opened (either by using Open on the File menu or by
using the Repackaging Wizard), and the project meets certain conditions, the SmartScan Wizard is
automatically launched. The SmartScan Wizard is launched:
• if the original setup was an InstallShield Professional 5.5 or later installation, and
• the file has not already been repackaged using the InstallShield Professional Logging Method
(available for InstallShield Editor and DevStudio 9.x InstallScript installations only), and
SmartScan Wizard Panels

The SmartScan Wizard includes the following panels:
• Welcome to the SmartScan Wizard Panel
• Original InstallShield Professional Setup Panel
• Scanning Panel
• Setup Feature Tree Panel
• Scanning Media Panel

Welcome to the SmartScan Wizard Panel

The first panel in the SmartScan Wizard is the Welcome panel.
Figure 3-34: SmartScan Wizard Welcome Panel
When you click Next, you advance to the Original InstallShield Professional Setup Panel, where
you specify the InstallShield Professional setup you want to scan.
Note: For your convenience, if a Repackaging project is opened (either by using Open on the File menu or by using the
Repackaging Wizard), and the project meets certain conditions, the SmartScan Wizard is automatically launched. The
SmartScan Wizard is launched:
• if the original setup was an InstallShield Professional 5.5 or later installation, AND
• the file has not already been repackaged using the InstallShield Professional Logging Method (available for
InstallShield Editor and DevStudio 9.x InstallScript installations only), AND

Original InstallShield Professional Setup Panel

On this panel, you specify the InstallShield Professional setup executable that you want to scan, and the
original target directory of that executable.
Figure 3-35: SmartScan Wizard Original InstallShield Professional Setup Panel
Enter the following options:
Table 3-34: Original InstallShield Professional Setup Panel Options
Option Description
Specify the path of the original This field is filled in by default if that information exists. Click Browse to specify the
setup executable InstallShield Professional setup executable that you want to scan. If you enter an
invalid path name, the Next button will be disabled.
Specify password if required Specify a password of the path of the original setup executable, if required.
Original target folder By default, this field is populated with information found in the original setup
package. Enter the directory where the product was installed during the
repackaging process. In most cases, this will be a subdirectory of
[ProgramFilesFolder]. Alternatively, you can enter any target where the product was
installed during the repackaging process. For example, if you installed this product
to C:\Program Files\MyCompany\MyProduct Folder, you would enter the following in
this field:
[ProgramFilesFolder]MyCompany\MyProduct
Click Next to proceed to the Scanning Panel, which shows the output and progress of the scan.

Scanning Panel
This panel displays the progress that SmartScan Wizard is making as it scans an InstallShield
Professional setup.
Figure 3-36: SmartScan Wizard Scanning Panel
Setup Feature Tree Panel

The Setup Feature Tree Panel lists the features and components that were configured in the original
InstallShield Professional project. If you want to use this feature and component information, select the
Add feature tree option.
Figure 3-37: SmartScan Setup Feature Tree Panel
Click Next to proceed to the Scanning Media Panel, which first scans the original media, then
displays the results.

Scanning Media Panel

Following the actual scan of the original setup media, the SmartScan Wizard displays a log of files to be
included in the project.
Figure 3-38: SmartScan Wizard Scanning Media Panel
Click Finish to add these to the project. Any default exclusions based on the exclusions file will be
applied.
Setup Intent Wizard

Although an installation may have intended to install certain files, these files sometimes may not be
installed—often because the files already exist on the target machine (either as the same version or a
newer version). These files, although not installed or updated, are needed for the product to execute
properly when the setup is run on a system that does not already have these files.
The Setup Intent Wizard allows you to scan a setup to identify files that may not have been captured
during repackaging—effectively recognizing the installation's intent for these files.
Tip: Any files found will be displayed in Repackager in a different color (as specified in the Color tab of the Options dialog
box).
The Setup Intent Wizard consists of the following panels:

• Welcome Panel
• Scanning Project Panel
• Results Panel

Welcome Panel
The first panel in the Setup Intent Wizard informs you the purpose of the Wizard, and warns you the
source files for your project must be present for successful scanning.
Figure 3-39: Setup Intent Wizard Welcome Panel
Click Next to start the scan and display the Scanning Project Panel.
Scanning Project Panel

The Scanning Project Panel is displayed while scanning is in progress. Each file scanned is listed, and a
progress bar displays the overall scan progress.
When the scan is complete, the Results Panel opens, listing new files that your setup required.

Results Panel
The final panel in the Setup Intent Wizard allows you to view and select new files detected by the
Wizard, but not already included in your Repackaging project.
Figure 3-40: Setup Intent Wizard Results Panel
Select the files you want to include in your project which were not identified during repackaging.
Click Finish to exit the Setup Intent Wizard and return to the Repackaging project (with selected files
automatically added to the project), or click Back to return to the Scanning Project Panel.

VMware Repackaging Wizard

Repackager includes integration with VMware Workstation’s virtual machine technology. This provides
you with the ability to launch a VMware session for repackaging purposes, and run different operating
systems on the same computer. By using VMware, you are able to forego the traditional “ghosting” for
clean images each time a new application is repackaged by simply electing not to save changes to the
VMware session. You can then reload the clean state of the operating system, and proceed to the next
package.
Note: AdminStudio supports VMWare 3.0 and later.
Note: The VMware Repackaging Wizard menu item on the Tools menu is enabled if Repackager finds VMWare 3.0 and
later installed on the workstation, and if a VMware image exists on that machine. If no VMware images are found, the
VMware Repackaging Wizard menu item will be disabled. Repackager reads the information about VMware images from:
<Application Folder>\VMware\Virtual Machines.vmls
Virtual Machines.vmls is a text file that contains information about individual VMWare images and where the
configuration file for each image is located. This file should contain information for at least one VMWare image for the
VMWare Repackaging Wizard menu item to be enabled.
Using the VMware Repackaging Wizard, you select an available VMware operating system, and then
Repackager automatically launches the selected operating system within a VMware session.
The VMWare Repackaging Wizard includes two panels:
• Welcome Panel
• VMware Virtual Machines Panel
Welcome Panel
The first panel displayed in the VMware Repackaging Wizard is the Welcome panel. It explains the
purpose of this Wizard: to display available VMware images on the current workstation, allowing you to
select and launch the one you need.
VMware Virtual Machines Panel

On the VMware Virtual Machines panel, you select a VMware virtual machine available on the current
workstation. Repackager automatically launches the selected virtual machine operating system within a
VMware session so that you can begin repackaging in that environment.
Note: AdminStudio supports VMWare 3.0 and later.
Click Back to return to the Welcome Panel; click Launch to launch the selected VMware image.

Exclusions Editor Interface

The following topics cover each tab, menu, and dialog box in the Exclusions Editor:
• Menus
• Files Tab
• .ini Files Tab
• Registry Tab
• File Exclusion Information Dialog Box
• INI File Exclusion Information Dialog Box
• Choose Registry Key Dialog Box
• Edit Registry Key Dialog Box
• About Exclusions Editor Dialog Box

Menus
Menus are not available when running the Exclusions Editor from within Repackager. They are only
available when you launch the Exclusions Editor by opening the following file:
AdminStudio Installation Directory\Repackager\AnalysisOptions.exe
Note: See Launching Exclusions Editor for more information.
The following table provides a description of each menu command:
Table 3-35: Exclusions Editor Menu Commands
Keyboard
Menu Command Shortcut Description
File New Ctrl+N Creates a new, blank settings file.
File Open | Shared Opens the settings file (isrepackager.ini) from the AdminStudio
Exclusions Shared directory. Open this settings file when working in a team
environment where the exclusion list needs to be stored in a
centralized location.
Open | Custom Allows you to browse to an Exclusions Editor settings file and open it.
Exclusions You would create a custom exclusion file based upon your company's
requirements.
File Save Ctrl+S Saves the current Exclusions Editor settings file.
File Save As Saves the current Exclusions Editor settings file to the name and
location specified.
File Exit Exits the Exclusions Editor.
Help Help Library Displays the online Help Library.
Help About Displays the About Exclusions Editor dialog box.

Exclusions
Editor

Files Tab
File exclusions for Repackager indicate which files are automatically marked as excluded in the
Repackager project. File exclusions in the OS Snapshot Wizard indicate files that will be excluded from
the captured OS snapshot.
Figure 3-41: Exclusions Editor Files Tab
This Files tab contains a list of paths and files currently excluded from the capture process. Specific
files, file extensions, and the entire contents of specified directories can be excluded.
The following three buttons allow you to add, edit, and remove files and directories from the exclusion
list:
Table 3-36: Exclusions Editor / Files Tab Buttons
Button Description
New Displays the File Exclusion Information dialog box from which you can specify additional file
exclusions.
Edit Brings up a dialog box from which you can change settings for the currently selected path in the
exclusion list.
Delete Deletes the currently selected path from the exclusion list.
Note: It is highly recommended that you do not edit the default exclusions for the OS Snapshot Wizard.

.ini Files Tab

.ini file exclusions for Repackager indicate which .ini files and sections are automatically marked as
excluded in the Repackager project. .ini file exclusions in the OS Snapshot Wizard indicate .ini files
and sections that will be excluded from the captured OS snapshot.
Figure 3-42: Exclusions Editor INI Files Tab
The INI Files tab contains a list of the .ini files and sections within .ini files excluded during analysis.
If all sections are excluded, an asterisk (*) is used in the Excluded Sections column.
The following three buttons allow you to add, edit, and remove .ini files from the exclusion list:
Table 3-37: Exclusions Editor / .ini Files Tab Buttons
Button Description
New Displays the INI File Exclusion Information dialog box from which you can specify additional .ini file
exclusions.
Edit Brings up a dialog box from which you can edit currently excluded .ini files.
Delete Deletes the selected .ini file from the exclusion list.

Registry Tab
Registry exclusions for Repackager indicate which registry keys are automatically marked as excluded in
the Repackager project. Registry exclusions in the OS Snapshot Wizard indicate registry keys that will be
excluded from the captured OS snapshot.
The Registry tab contains a listing of keys and values to be excluded during registry analysis. For keys
that have specific values excluded, the value name appears in the Value column. For keys that have all
values excluded, an asterisk (*) represents the entire key in the Value column.
Figure 3-43: Exclusions Editor Registry Tab
There are three buttons available from this dialog box that are used to add, edit, or remove keys from the
exclusion list:
Table 3-38: Exclusions Editor / Registry Tab Buttons
Button Description
New Displays the Choose Registry Key dialog box, from which you can select registry keys and values for
exclusion during analysis.
Edit Brings up a dialog box from which you can modify the selected key's exclusion settings.
Delete Removes the selected key from the exclusion list.

File Exclusion Information Dialog Box

The File Exclusion Information dialog box, which is accessed by clicking New or Edit on the Files Tab,
allows you to specify files to be excluded from analysis by the capture tool.
Figure 3-44: File Exclusion Information Dialog Box
Enter or browse to the path you want to exclude, and provide the file(s) to be excluded. In addition to
specifying individual files, you can also exclude all files with a certain extension by entering an asterisk
(*) plus the extension (for example, *.txt) in the Excluded Files field. You can also exclude all files in a
directory by only entering an asterisk in the Excluded Files field.
Click OK to return to the Files Tab.
INI File Exclusion Information Dialog Box

The INI File Exclusion Information dialog box, which is accessed by clicking New or Edit on the .ini
Files Tab, allows you to specify .ini files to be excluded from analysis by the capture tool.
Figure 3-45: INI File Exclusion Information Dialog Box
Enter or browse to the .ini file you want to exclude, and provide the section(s) to be excluded. Sections
must be enclosed in square brackets ([]), and separated by vertical bars (|) if more than one section in an
.ini file is to be excluded (for example, [Groups],[Settings]). You can also exclude all .ini file sections
by only entering an asterisk in the Excluded Sections field.
Click OK to return to the .ini Files Tab.

Choose Registry Key Dialog Box

The Choose Registry Key dialog box, which is accessed by clicking New on the Registry Tab, provides a
way for you to select registry keys that you want excluded from analysis.
Figure 3-46: Choose Registry Key Dialog Box
Navigate through the tree until you find the key you want to exclude and click OK to return to the
Registry Tab.
By default, all values in that key are excluded. To modify this, select the key from the Registry Tab and
click Edit to display the Edit Registry Key dialog box.
Tip: You can also select a registry hive to exclude. As with individual registry keys, all values (and keys) contained in the
hive are excluded by default.

Edit Registry Key Dialog Box

When you select a registry key on the Registry Tab and click Edit, the Edit Registry Key dialog box
opens.
Figure 3-47: Edit Registry Key Dialog Box
You can modify the Key Name and/or Value Name excluded during analysis.
Click OK to return to the Registry Tab.
About Exclusions Editor Dialog Box

The About Exclusions Editor dialog box displays version and copyright information for the Exclusions
Editor. This may be useful if you need to report a problem encountered when using the Exclusions
Editor.
Figure 3-48: About Exclusions Editor Dialog Box

Options.ini File
The Options.ini file is created by Repackager and is used during the conversion of Repackager output
into an InstallShield Developer project (.ism). It includes basic project settings which are required by
Repackager.
Note: Although many of these settings have a one-to-one correspondence with settings available in the Repackager
interface, some can only be accessed by editing this .ini file directly.
Options.ini File Example

[MMExclusions]
[General]
UseSrcFolder=Y
EnablePathVariables=Y
UseHKCUProxy=N
LimitedUI=Y
SISAuthor=Repackager
OtherFilesNewComponents=N
UseMergeModules=Y
SharedCommonFiles=Y
PermanentSystemFiles=Y
PermanentSystemFilesSubfolders=N
ExtraHKCRPermanent=Y
COMMapping=Y
ServiceControlEvents=N
ALLUSERS=Y
ProjectTemplate=
BuildCompressed=Y
CreateSetupExe=N
MultiUserShortcuts=Y
[IgnoreShortcuts]
TargetExe1=isuninst.exe
TargetExe2=uninst.exe
TargetExe3=setup.exe
TargetExe4=uninst.dll
MMExclusions Section
This section lists the merge module GUIDs that should not be included in your package. This section
only applies if you have selected to replace files with merge modules during conversion.

General Section
Following are descriptions of properties that can be set in the [General] section of the Options.ini file.
Table 3-39: Options.ini File/General Section Properties
AddlMMSearchPath Use to specify additional directories containing custom merge modules to use
during repackaging.
ALLUSERS If this option is set to Y and if the template file (specified using the
ProjectTemplate option) does not contain ALLUSERS in its Property table,
then a property named ALLUSERS with a value of 2 will be added to the
Property table. This will cause silent installs to behave as non-silent installs do
(non-silent installs rely on a custom action to set this property).
This option is set to Y by default.
ARPPublisher This populates the Publisher field in Add/Remove Programs in the Control
Panel.
ARPPublisherURL This populates the Publisher URL field in Add/Remove Programs in the
Control Panel.
ARPSupportURL This populates the Support URL field in Add/Remove Programs in the
Control Panel.
AutoUpgrade Upgrades the InstallShield Editor template project file (if used) if needed.
BuildCompressed This option, set to Y by default, compresses all necessary files inside the MSI
package, as opposed to storing them outside of the MSI database.
BuildFeatures If the SmartScan Wizard is specified to include feature information in this

project, this option will be set to Y.
BuildMSI Specifies whether or not to build the MSI package after building ISM.
BuildProduct Identifies the InstallShield Editor Product configuration to build.
BuildProScannedFiles Files identified in the Media Scan Wizard will be included in the package
(unless you have manually excluded them from the project).
BuildRelease Identifies which InstallShield Editor Release configuration to build.
BuildStaticScannedFiles Any files identified when running the Setup Intent Wizard will be included in the
package (unless you have manually excluded them from the project).

Table 3-39: Options.ini File/General Section Properties (cont.)
COMMapping When this option is set to Y, registry data pertaining to COM information will
be mapped to the appropriate MSI tables whenever possible. This reduces the
number of ICE33 warnings that can occur during package validation.
CreateSetupExe This option, which is set to N by default, allows you to automatically create a
Setup.exe file to begin the installation.
EnablePathVariables Set this option to Y to use path variables. If enabled, the repackaged setup is
significantly more portable between computers (with dependencies to the
system where the setup was repackaged removed).
ExtraHKCRPermanent When this option is set to Y, any changes made to existing registry data
during repackaging which cannot be identified as belonging to a file installed
by the setup are placed in permanent components, which are not removed by
default when the repackaged setup is uninstalled. This prevents inadvertently
removing registry entries required by other applications that were not
originally made by the repackaged setup.
By default, this option is set to Y, and InstallShield strongly recommends
retaining this setting to prevent unexpected results when the package is
uninstalled.
INSTALLDIR This value will be used for INSTALLDIR (the installation directory) and can use
a Windows Installer property such as
[ProgramFilesFolder]\MyProgram
ISProSetup If one of the original setups that was repackaged was created by InstallShield
Professional 5.5 or later, this option will be set to Y.
This option is set to N by default.
LimitedUI Set this option to Y display only the InstallWelcome dialog box when the MSI
package is run.
MultiUserShortcuts When this option is set to Y, non-advertised shortcuts will work for all users on
the target system. This will generate ICE43 warnings when validation is run. If
you know the installation is for a single-user environment, change this option
to N to avoid these warnings.
MMPathVersion When including merge modules, if this option is set to Y, compare path and
version information.
NewInstallDir Value for INSTALLDIR variable.

ODBCMapping If selected, ODBC-related registry data is mapped to ODBC tables instead of

the Registry table. This data will only function correctly if Windows Installer
supports the ODBC resource being mapped; It is recommended that you do
not enable this option if you are unsure whether the ODBC resources are
supported correctly by Windows Installer.
OSGranular For SmartScanned or ProLogged Projects: If this is set to Y, component

conditions will store specific operating system information. For example, if the
filter was NT4, the condition will be (VersionNT=4). If this is set to N,
component conditions will store a grouping of the operating system. For
example, if the filter were NT4, the condition will be (VersionNT).
This is set to N by default.
OtherComponentFileExtensions Specify additional extensions to use when defining components. MSI has rules
governing component creation for file types. For example, PE files must have
separate components. Therefore, certain extensions have been defined (EXE,
DLL, etc.). Additional extensions can be defined in the options.ini file in the
format of:
Type1:Extension1|Type2:Extension2
where Type is one of the following numbers:
0 = other
1 = PE
2 = help
3 = font
4 = INI
This option is set to 1:QTX|1:AX by default.
OtherFilesNewComponents When this option is set to Y, one component will be created for every file in
your setup. Otherwise, new components will only be created for each portable
executable file.
PermanentSystemFiles Set this option to Y to mark portable executable files installed to a system
folder (System32Folder) as Permanent files (will not be uninstalled).
PermanentSystemFilesSubfolders Set this option to Y to mark files installed to a subfolder of a system folder as
Permanent files (will not be uninstalled).
ProductName The name of the product. You must provide a value for this option either in this
file or in Repackager.
ProductVersion The version of the product. You must provide a value for this option either in
this file or in Repackager.
Project Name of InstallShield Editor project file.

ProjectTemplate The name and location of the default InstallShield Editor project template
(.ism) used in the conversion process.
ServiceControlEvents When this option is set to Y, the ServiceControl table will be populated for NT
Services.
SharedCommonFiles Set this option to Y to mark portable executable files installed to the
CommonFilesFolder (or subfolder) as Shared files.
SISAuthor This option populates the Author field of the Summary Information Stream
(accessible from the package's properties).
This option is set to Repackager by default.
SISSubject This option populates the Subject field of the Summary Information Stream
(accessible from the package's properties).
SkipMMIfShortcut Merge Modules that have files pointed to by shortcuts should be skipped even
if they are not in the exclusion list.
SmartScannedOnce Specifies whether or not the SmartScan Wizard was run for this project.
UseAdvertisedShortcuts Create advertised shortcuts where applicable.

UseHKCUProxy Set this option to Y to copy all registry entries in HKEY_CURRENT_USER to

HKEY_USERS\.default.
UseLanguage When selected, the target package's language will be the language detected
by Repackager (as displayed in the Captured Installation view).
UseMergeModules Set this option to Y to replace files with merge modules whenever possible
during conversion. Exceptions are listed under the [MMExclusions] section.
UseSrcFolder Set this option to Y to make the InstallShield Editor project (.ism) folder
default to the Repackager output project (.inc) folder.
IgnoreShortcuts Section
Shortcuts that refer to executables listed in this section will be ignored during conversion.

Files Associated with Repackager

Several files are associated with Repackager. Some are output files, and some contain default
information for Repackager to function. These files are described in the tables below.
Files Used By the Repackaging Wizard

The following files are used by the Repackaging Wizard.
Table 3-40: Files Used by the Repackaging Wizard
File Location Description
Repack.ini Windows This is an input file for the Repackaging Wizard. It

If the file is not found in the Windows contains a list of the exclusions for the files,
directory, then the Repackaging Wizard folders, .ini files and registry entries for the last
extracts a default file from the resource used configuration of Repackager. During the
and stores it in the Windows directory. Snapshot and Install Monitoring modes of
repackaging, the entries in this file are filtered out
from the repackaged output.
See Repack.ini File for more information.
Options.ini Repackager output directory (specified in This is an output file from the Repackaging
the Set Target Project Information and Wizard. It contains configuration information
Capture Settings Panel). about the repackaged setup, including whether to
use path variables, whether to display a limited
The Repackaging Wizard makes a copy
user interface during installation of the
of the default options.ini that is
repackaged setup and whether every file will go
present in the following directory:
into its own component.
AdminStudio Installation
Directory\Repackager
and saves this file in the same location

as the current repackaged output file
(.inc). Additionally, the UseSrcFolder
flag can be used to store the created
InstallShield Editor file in the same
directory as the .inc file.
productname.inc Created in the Repackager output This is an output file from the Repackaging
directory (specified in the Set Target Wizard. It contains the locations of files, .ini
Project Information and Capture Settings files, and shortcuts detected by Repackager as
Panel). having been created, modified, or removed
during repackaging. Also, it contains a link to the
standard.nir and deleted.isr files for
registry information.
updated.isr Created in the Repackager output This is an output file from the Repackaging
directory (specified in the Set Target Wizard when the Install Monitoring method is
Project Information and Capture Settings used. It contains registry additions and
Panel) modifications detected during repackaging using
installation monitoring only.

Table 3-40: Files Used by the Repackaging Wizard (cont.)
deleted.isr Created in the Repackaging output This is an output file from the Repackaging
directory (specified in the Set Target Wizard. It contains registry deletions detected
Project Information and Capture Settings during repackaging using Installation Monitoring
Panel) and Snapshot.
standard.nir Created in the Repackager output This is an output file from the Repackaging
directory (specified in the Set Target Wizard when the Snapshot method is used. It
Project Information and Capture Settings contains registry additions and modifications
Panel). detected during repackaging using the Snapshot
method.
*.spy Created in the following folder: This is an output file from the Repackaging
Wizard when the Install Monitoring method is
WindowsDrive\InstallHook used. It contains API call logs for installation
monitoring.
Default.ini AdminStudio Installation Contains the default configuration for

Directory\Repackager Repackager, including default exclusion
information.
Repack.log WindowsFolder Log file created by the Repackaging Wizard.
Files Used By the Repackager Interface

Table 3-41: Files Used by the Repackager Interface
*.irp Saved in the same location as This is a Repackager project file. It is the main file for
the .inc file. each repackaged or converted setup. It contains
information about the .inc files referred to and also
stores the file, folder, .ini files and registry exclusions
made in the Repackager Interface.
<Exclusion List>.ini varies This is an input file for the conversion of the .inc file to
an MSI package. It contains the list of files, folder, .ini
files and registry entries exclusions. Users can choose
a different exclusion file from the Repackager Interface
and the exclusions will be reflected in the Interface.
Options.ini Saved in the same location as This is an input file for the conversion of the .inc file to
the .inc file. an MSI package. It contains configuration information
about the repackaged setup, including whether to use
path variables, whether to display a limited user
interface during installation of the repackaged setup,
and whether every file will go into its own component.
Additionally, the UseSrcFolder flag can be used to
store the created InstallShield Editor file in the same
directory as the .inc file.

Repack.ini File
The Repack.ini file is the default capture exclusion file for the Repackaging Wizard. It contains
exclusions to be applied during repackaging, and mainly focuses on specific items that should not be
included in applications, such as InstallShield Professional-specific COM settings, OS settings, and
Internet Explorer settings. Any item excluded during capture will not be available for exclusion/
inclusion in the Repackager project file.
The file is located in the Windows folder, and can be edited using the Exclusions Editor, or using a text
editor.
Note: InstallShield strongly recommends you not modify this file, as it increases the likelihood of either inadvertently
omitting necessary pieces of applications you are repackaging, or including registry entries or files that should not be part
of the repackaged application. In the first scenario, you may need to recapture your application; in the second, you may
need to exclude more from the Repackager project.
Instead, capture your application using the default exclusions in the Repackaging Wizard, and then selectively exclude
captured data using the Repackager Interface. This way, if you inadvertently exclude a necessary piece, you need only
reinclude it in Repackager—not recapture the application entirely.
Troubleshooting
Repackager Troubleshooting information is presented in the following topics:
• Troubleshooting Guidelines for WinINSTALL Conversion
• Troubleshooting Guidelines for SMS Conversion
• Resolving an “Error Building Table File” Error
Troubleshooting Guidelines for WinINSTALL Conversion

Use the following troubleshooting guidelines to identify and fix WinINSTALL conversion problems.
• Repackager tool supports 6.0, 6.5, and 7.x project formats only. For all other formats, please use the
WinINSTALL LE tool available as a free download in Windows 2000 to convert to 7.x files.
• Repackager tool cannot convert WinINSTALL .NAI files—It can only convert WinINSTALL projects that
have been converted to text (.txt).
• All files must be available—All the files that were available to the original WinINSTALL installation
project must be available to the converted installation at the exact same locations.
• Not all elements of a WinINSTALL installation are converted—Because WinINSTALL installations are
based on a different technology than Windows Installer, not all elements of a WinINSTALL
installation are converted. Only the installation of files, registry changes, and other system changes
are converted.
• Custom logic is not converted—Custom logic written in WinINSTALL’s custom scripting language is
not converted.

• WinINSTALL environment variable assignments are not converted—To re-add environment variable
assignments in a Windows Installer installation, open the converted project in InstallShield Editor
and use the Environment Variable view.
• WinINSTALL variables are converted to a Windows Installer variable—If the target path of a file contains
a WinINSTALL variable, then the WinINSTALL variable is converted to a Windows Installer
variable.
• Specify @ variables at conversion time—If the source path of a file in WinINSTALL contains either the
@Server or @Wininstall variable, you can specify the values of these two variables at conversion
time in the Repackager.
• The WinINSTALL Preinstall and Postinstall scripts are not converted.
Troubleshooting Guidelines for SMS Conversion

Use the following troubleshooting guidelines to identify and fix SMS conversion problems.
• All files must be available—All the files that were available to the original SMS installation project
must be available to the converted installation at the exact same locations.
• Not all elements of an SMS installation are converted—Because SMS installations are based on a
different technology than Windows Installer, not all elements of a SMS installation are converted.
Only the installation of files, registry changes, .ini Files, ODBC, NT Services, Fonts, Shortcuts,
Variables, and other system changes are converted.
• Custom logic is not converted—Custom logic written in SMS’s custom scripting language is not
converted.
• SMS environment variable assignments are not converted—To re-add environment variable
assignments in a Windows Installer installation, open the converted project in InstallShield Editor
and use the Environment Variable view.

Resolving an “Error Building Table File” Error

When building with Repackager, if you have received the following error message during the build:
ISDEV: fatal error -5023: Error building table File
your first step is to go to the Repackager Interface and check whether the number of files installed by
this setup is greater than 32,767. If it is, this error occurs because Windows Installer supports 32,767
files in the File table but the package being built exceeds this limit. See Authoring a Large Package in
Windows Installer Help for more information.
If you want to fix this error using Repackager, perform the steps listed below.
Task To fix this error using Repackager:
1. Browse to the appropriate directory:
• If you are using the standalone Repackager, browse to the Repackager folder.
• If you are using the Repackager on a machine where AdminStudio is fully installed, browse to
the following directory:
<AdminStudio INSTALLDIR>\Editor\Support\0409
2. Locate the IsMsiPKg.itp and IsMsiPKgLarge.itp files in this directory.

3. Rename IsMsiPKg.itp to IsMsiPKg.itp.bak.
4. Make a copy of IsMsiPKgLarge.itp and rename the copy IsMsiPKg.itp.
5. Perform the conversion and create the MSI.
6. Delete IsMsiPKg.itp.
7. Rename IsMsiPKg.itp.bak back to IsMsiPKg.itp, thereby restoring the original file.
Note: Transforms and patches cannot be created between two packages with different column types.
Note: For more information, see the Authoring a Large Package and File Table topics in the Windows Installer Help.

Index
Symbols About Repackager dialog box 130

Additional Setup Programs dialog box 46, 167
Repackaging Wizard 46, 167
.aot 82
converting to Repackager project 82 AdminStudio
Process Assistant 21
difference from .axt file 82
advanced conversion options 114
.axt 82
converting to Repackager project 82 configuring Repackager 114
Advanced Options view 114
difference from .aot file 82
Advanced Settings view 152
.inc 81, 170, 189, 194
converting to Repackager project 81 ALLUSERS 189
alternate-language repackaging 25
.ipf 81
Analysis Options dialog box 169
converting to Repackager project 81
.irp 40, 194 Repackaging Wizard 169
-app 170
creating 40
application isolation 31, 35
.isl 86
manifests 31
application manifests 31
.ism 107, 170, 189
application object template files 82
building in Repackager 107
.msi 107 assemblies 35
setting naming convention 35
assembly files 29
.spy 194
assembly manifests 31
.txt 85
.wse 85
B
-? 170 -b 170
BuildCompressed 189
A
About Exclusions Editor dialog box 188

Index
C detecting in Repackager 116

directories 98
exclusions 98
Captured Installation view 140
-cf 170 Directories and Files Excluded During Analysis dialog box
186
Choose Registry Key dialog box 187
directories and subdirectories 88
clean machines 24–25
excluding 88
alternate-language repackaging on 25
directory exclusions 98
Repackager 24
Dynamic Dependency Scanner 30
Collect Product Information panel 159
Repackaging Wizard 159
command line 79
running Repackaging Wizard from 79
E
command-line options 170 Edit Registry Key dialog 188
Repackager 170 EnablePathVariables 189
COMMapping 189 engines 19
component settings options 153 including InstallScript engines with installation 19
converting 80–82, 85–86 Excluded Processes dialog box 168
.aot 82 excluding files 88
.axt 82 exclusion list 194
.inc 81 exclusions 87–93, 96–106, 181, 183–185
.ipf 81 all files in a directory 88
.isl 86 all shortcuts in a directory 90
.txt 85 configuring in Repackager 87
.wse 85 directories and subdirectories 88
InstallScript MSI 75 directory 98
InstallShield log files 86 editing existing file 99
legacy setups 80 editing existing INI file 102
Novell ZENworks projects 82 editing existing registry 105
Repackager 3.x output 81 external configuration file in Repackager 91
SMS projects 81 file 96
WinINSTALL projects 85 files 183
Wise Installation projects 85 INI file 100
Create Report dialog box 131 INI file sections 90, 101
CreateSetupExe 189 INI files 89, 184
-cs 170 modifying Repackager external configuration file 92
OS snapshot 93
D OS Snapshot Wizard 93
OS Snapshot Wizard global 93
project 93
data type appearance 26
registry 185
changing Repackager 26
registry data 104
Default.ini 194
registry keys 89
Deleted Files view 146
registry values 89
Deleted Registry Entries view 147
removing existing file 99
Deleted.isr 194
removing existing INI file 103
deleting added setups 47
dependencies 116 removing registry 106
Repackager 93

Index
Repackager file 88 file exclusions 88, 99

Repackager global 93 editing existing 99
repackaging 93 removing existing 99
resetting to default values 181 Repackager 88
shortcuts 90 files
shortcuts from subdirectories 91 excluding 88
specific file extensions 97 exclusion of specific extensions 97
with specific file extensions 97 exclusions 96, 183
Exclusions Editor 93, 96–106, 181–188 Files and Folders view 141
About dialog box 188 Files tab 183
Choose Registry Key dialog box 187 Exclusions Editor 183
Directories and Files Excluded During Analysis dialog
box 186
directory exclusions 98 G
Edit Registry Key dialog box 188
General tab 137
editing existing file exclusions 99
editing existing INI file exclusions 102
editing existing registry exclusions 105
excluding INI file sections 101
H
File Exclusion Information dialog box 186 help
files 96 Help Library conventions 8
Files tab 183 Knowledge Base articles 14
INI File Exlcusion Information dialog 186 Online Communities 14
INI files 100 Support Web site 14
INI Files tab 184 using 8
Keys Excluded During Registry Analysis dialog box
187
menus 182 I
OS Snapshot Wizard exclusions 93
reference 181 INI File Exclusion Information dialog 186
INI file exclusions 102–103
registry data 104
editing existing 102
Registry tab 185
removing existing 103
removing existing file exclusions 99
removing existing INI file exclusions 103 INI file sections 90, 101
excluding 90, 101
removing registry exclusions 106
INI files 89, 100, 184
Repackager exclusions 93
exclusions 89, 100, 184
resetting exclusions to default values 181
INI Files tab 184
specific file extensions 97
Exclusions Editor 184
Exclusions tab 138
INI Files view 145
external configuration file 91–92
install monitoring 37–38
modifying Repackager 92
installation monitoring 37–38
specifying in Repackager 91
excluding processes from 168
ExtraHKCRPermanent 189
-installdir 170
installing
F Novell ZENworks Desktop Management Agent 82
InstallScript Engines 19
File Exclusion Information dialog 186 InstallScript MSI 75

Index
converting 161 contacting 15

converting to Basic MSI with InstallScript support 75 products 12
converting to Repackager project 75 Professional Services 13
InstallScript MSI Conversion Output Panel 164 Support Web site 14
Repackaging Wizard 164 Technical Support 14
InstallScript MSI Identified Panel 161 Training 13
Repackaging Wizard 161 manifest files 29
InstallScript Scan 19, 75 manifests 31
InstallShield Editor 119 application 31
Dynamic Dependency Scanner 30 assembly 31
editing generated Repackager projects 119 menus 128, 182
InstallShield Editor project 107 Exclusions Editor 182
building in Repackager 107 Repackager 128
InstallShield log files 86 Method Selection Panel
converting to Repackager project 86 advanced settings 168
InstallShield Professional 162, 175 Method Selection panel 155
SmartScan Wizard 176 Repackaging Wizard 155
InstallShield Professional Setup Panel 162 -mm 170
Repackaging Wizard 162 -mode 170
InstallShield Professional setups 119 -mp 170
scanning in Repackager 119 -ms 170
InstallShield SmartScan options 154 MSI packages
-is 170 building in Repackager 107
isolated components 29 MultiUserShortcuts 189
isolation 29
Isolation Options dialog box 132
ISRepackager.ini 194, 196 N
ISRIsolation 33
nested .msi custom action 86
Novell ZENworks Desktop Management Agent
K installing 82
Novell ZENworks projects 82
Keys Excluded During Registry Analysis dialog 187 .aot and .axt files 82
Knowledge Base articles application object template files 82
help 14 converting to Repackager project 82
L O
legacy setups 19, 41, 80 -o 170
converting 80 -of 170
repackaging 19, 41 Online Communities
LimitedUI 189 help 14
Options dialog 135
Options.ini file 189, 194
M options.ini file
OtherComponentFileExtensions 189
Macrovision 11
support for user-defined extensions 189
Consulting Services 13

Index
Original InstallShield Professional Setup Panel 175 registry keys 89

Repackaging Wizard 175 excluding 89
OS requirements 152 Registry tab 185
option to match legacy system's OS requirements for Exclusions Editor 185
SmartScan 152 registry values 89
OS snapshot 93 excluding 89
exclusions 93 remote repackaging 77
OS Snapshot Wizard 93 Repack.log 194
exclusions 93 Repackaged Output view 107, 148, 151
OtherComponentFileExtensions 189 building InstallShield Editor projects 107
OtherFilesNewComponents 189 building MSI packages 107
Repackager 19, 24–26, 40, 77–78, 80–82, 85–93,
114–119, 127–128, 130–131, 135–136, 139–
P 142, 144–148, 151–152, 170, 172, 177, 180, 189,
196–198
package conversion options 152
About Repackager dialog 130
PackageExpert
additional setup programs 46
automatically running PackageExpert tests during
Advanced Settings view 152
Repackager build process 112, 149
automatically running PackageExpert tests upon build
Password Required dialog 136
112, 149
-pc 170
building InstallShield Editor projects 107
PermanentSystemFiles 189
building MSI packages 107
PermanentSystemFilesSubfolders 189
Captured Installation view 140
-pp 170
changing data type appearance 26
Process Assistant 21
clean systems 24
Professional Services
command-line options 170
Macrovision 13
component settings options 153
project path 48, 58, 66, 74
configuring advanced conversion options 114
specifying in Repackaging Wizard 48, 58, 66, 74
configuring exclusions 87
Project Properties dialog box 136–138
conversion problems 196–197
Exclusions tab 138
converting .axt 82
General tab 137
converting .inc 81
ProjectTemplate 189
converting .ipf 81
properties 115
converting .isl 86
viewing Repackager project 115
converting .txt 85
-pv 170
converting .wse 85
converting InstallShield log files 86
R converting legacy setups 80
converting Novell ZENworks projects 82
reboot handling 172 converting Repackager 3.x output 81
registry 104, 106, 185 converting SMS projects 81
exclusions 104, 185 converting WinINSTALL projects 85
removing exclusions 106 converting Wise Installation projects 85
Registry Entries view 142 Create Report dialog box 131
registry exclusions 104–106 creating projects 40
editing existing 105 creating reports 117
removing global 106 Deleted Files view 146

Index
Deleted Registry Entries view 147 SmartScan Wizard 172, 176

detecting dependencies 116 SMS conversion problems 197
dialog boxes 130 specifying external configuration file 91
editing generated projects in InstallShield Editor 119 support of user-defined extensions in options.ini 189
Error Building Table File error 198 toolbar 128
excluding all files in a directory 88 troubleshooting 196–198
excluding all shortcuts in a directory 90 viewing properties 115
excluding directories and subdirectories 88 views 139
excluding files 88 VMware Repackaging Wizard 180
excluding INI file sections 90 WinINSTALL Conversion dialog box 139
excluding INI files 89 WinINSTALL conversion problems 196
excluding registry keys 89 Repackager 3.x output 81
excluding registry values 89 converting to Repackager project 81
excluding shortcuts 90 Repackager error building table file 198
excluding shortcuts from subdirectories 91 Repackager projects 40, 118
exclusion list 194 creating 40
exclusions 93 saving 118
file exclusions 88 Repackager Start page 127
Files and Folders view 141 repackaging 19, 25, 41, 77–78, 93
files associated with 194 alternate-language 25
INI Files view 145 an installation from a self-extracting .exe 44
InstallShield SmartScan options 154 excluding processes from 168
ISDEV fatal error -5023 198 exclusions 93
Isolation Options dialog box 132 legacy setups 19, 41
launching 25 remote 77
menus 128 remotely on Windows NT4 78
modifying external configuration file 92 repackaging methods 37–38
Options dialog box 135 selecting 52
Options.ini file 189 Repackaging Wizard 77–79, 154–155, 157, 159, 161,
OtherComponentFileExtensions 189 163–169, 172
package conversion options 152 additional panels 167
Package Information view 151 additional setup programs 46
Password Required dialog box 136 Additional Setup Programs dialog box 167
Project Properties dialog box 136 Analysis Options dialog box 169
Registry Entries view 142 Collect Product Information panel 159
remote repackaging on Windows NT4 78 deleting added setups 47
Repackaged Output view 148 Excluded Processes dialog box 168
repackaging legacy setups 41 InstallScript MSI Conversion Output Panel 164
running automated tests against the .msi package at InstallScript MSI Identified Panel 161
build 112, 149 InstallShield Professional Setup Panel 162
running the Repackaging Wizard remotely 77 Method Selection panel 155
saving projects 118 Original InstallShield Professional Setup Panel 175
scanning InstallShield Professional setups 119 reboot handling 172
setting digital signature options 132 Repackaging panel 165
setting manifest options 132 running from command line 79
Setup Intent Wizard 177 running remotely 77
Shortcuts view 144 running remotely on Windows NT4 78

Index
Set Target Project Information and Capture Settings Repackager 176

panel 163 Scanning Media panel 177
Setup Information dialog box 168 Welcome panel 174
Snapshot Method panel 157 SMS conversion problems 197
specifying project path 48, 58, 66, 74 Repackager 197
Summary panel 166 SMS project 81
using 42 converting to Repackager project 81
Welcome panel 155 -sn 170
reports 117 snapshot 37–38
creating in Repackager 117 Snapshot Method panel 157
Results panel 179 Repackaging Wizard 157
Setup Intent Wizard 179 Standard.nir 194
Summary panel 166
S
-sb 170
Scanning Media panel 177
T
SmartScan Wizard 177 Technical Support
Scanning project panel 178 Macrovision 14
Setup Intent Wizard 178 toolbar 128
ServiceControlEvents 189 Repackager 128
Set Target Project Information and Capture Settings panel training
163 Macrovision 13
Setup Information dialog box 168
Repackaging Wizard 168 U
Setup Intent Wizard 116, 177–179
Updated.isr 194
Results panel 179
UseHKCUProxy 189
Scanning project panel 178
UseMergeModules 189
Welcome panel 178
UseSrcFolder 189
setup programs
adding additional in Repackaging Wizard 46
setups 19
deleting added in Repackaging Wizard 47
V
repackaging legacy 19, 41 version 170
SharedCommonFiles 189 VMware 180
shortcuts 90–91 VMware Repackaging Wizard 180
excluding 90 VMware Virtual Machines panel 180
excluding all in a directory 90 Welcome panel 180
excluding from subdirectories 91 VMware Virtual Machines panel 180
Shortcuts view 144 VMware Repackaging Wizard 180
SISAuthor=InstallShield Repackager 189
SmartScan Wizard 119, 172, 174, 177
automatic launch 172 W
conditions for automatic launch 172
Welcome panel 155, 174, 178, 180
launching automatically 172
option to match legacy system's OS requirements 152

Index
Setup Intent Wizard 178 Wise Installation project 85

SmartScan Wizard 174 converting to Repackager project 85
VMware Repackaging Wizard 180
Welcome to InstallShield Repackager 127
Windows Installer package Z
ZENworks Desktop Management Agent
WinINSTALL Conversion dialog box 139
installing 82
WinINSTALL conversion problems 196
ZENworks projects
WinInstall conversion problems
.aot and .axt files 82
Repackager 196
application object template files 82
WinINSTALL project 85
converting using Repackager 82

Re Packager User Guide

Uploaded by

Copyright:

Available Formats

Re Packager User Guide

Uploaded by

Document Information

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Re Packager User Guide

Uploaded by

Copyright:

Available Formats

Repackager

Restricted Rights Legend

1 Repackager 8.0 User Guide . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7

3 Repackaging Legacy Installations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19

Repackager 8.0 User Guide RPK-0800-UG00 3

Setting Isolation Options. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33

4 RPK-0800-UG00 Repackager 8.0 User Guide

Repackager 8.0 User Guide RPK-0800-UG00 5

SmartScan Wizard . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 172

6 RPK-0800-UG00 Repackager 8.0 User Guide

Table 1-1: Repackager Help Library

Repackaging Methods Describes the methods of repackaging that Repackager supports.

Repackager 8.0 User Guide RPK-0800-UG00 7

Table 1-1: Repackager Help Library (cont.)

Repackager Reference Describes Repackager wizards, views, and dialog boxes.

Repackager Help Library

Web-Based Online Help

Reader Alert Conventions

Table 1-2: Reader Alert Conventions

Image Alert Name Description

8 RPK-0800-UG00 Repackager 8.0 User Guide

Table 1-2: Reader Alert Conventions (cont.)

Image Alert Name Description

Security Security alerts identify security issues.

Procedure The Procedure graphic indicates that procedural instructions follow.

External Web Site Graphic

For more information, see Microsoft MSDN Library .

Table 1-3: Style Conventions

Style Example Description

Variables fileName Variables appear in italics.

Code #define HWND_BROADCAST 0xffff Code snippets appear in a monospace

User Inputted Type $D(install). Text that is to be entered as a literal value is

Repackager 8.0 User Guide RPK-0800-UG00 9

Table 1-3: Style Conventions (cont.)

Style Example Description

10 RPK-0800-UG00 Repackager 8.0 User Guide

Repackager 8.0 User Guide RPK-0800-UG00 11

Table 2-1: Macrovision Software Value Management Solutions

Industries & Activities FLEXnet Software Value Management Solutions

Software Vendors: • InstallShield and InstallAnywhere—Tools for authoring installations and

• Prepare & Deploy Software

Try a Macrovision Solution Today!

12 RPK-0800-UG00 Repackager 8.0 User Guide

Macrovision Professional Services

Expert Training Services

• Every class features hands-on training for solving real-world issues.

Product Support Services

Expert Consulting Services

• Achieve professional results without tying up your company’s internal resources.

Repackager 8.0 User Guide RPK-0800-UG00 13

Additional Contact Information

Table 2-2: Additional Contact Information for Macrovision Professional Services

Location Telephone Number

The Americas, Australia, New Zealand (847) 466-6000

Europe, Middle East, Africa (44) (117) 903 0650

Asia-Pacific (81) (3) 5774 6253

Technical Support Resources

• Submit Repackager feedback.

• Perform Repackager registration.

• Obtain object libraries and sample projects.