About Repackaging On Clean Systems - Novell ADMINSTUDIO 9.5 User Manual

Chapter 7: Repackaging Legacy Installations Using the Repackaging Wizard
About Repackaging
Note • Since Windows Installer does not support packaging device drivers, you would need to create Custom
Actions to install device drivers. See
information.
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.
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 (
•
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.
Also, Repackager is not intended for repackaging operating system installations or service packs, or deeply
integrated operating system components such as Internet Explorer. Moreover, components such as MDAC or
DCOM should be included in the clean image, or installed by a setup using the vendor's redistributable.

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 • For more information on setting up a clean system to repackage on, see
Optimal Installation
446
Using Custom Actions
Capture.
in the Windows Installer help section for more
) packages for the following reasons:
.msi
ADS-0950-UG00
Configuring Repackager to Ensure
AdminStudio 9.5 User Guide