Depending upon your network connectivity, you should configure Repackager on a clean machine in one of the
following ways:
Table 7-5 • Methods to Configure Repackager
Repackager Configuration
Launching Repackager
Remotely
Installing Repackager on a
Clean Machine
Note •
You cannot repackage remotely from a Windows NT4 system because a file required during repackaging on
that operating system,
system, install Standalone Repackager on that machine, as described in
Launching Repackager Remotely
Because you want to avoid installing applications on the clean machine, you should launch Repackager remotely
from the clean machine.
To launch Repackager remotely, perform the following tasks:
•
Sharing Directories on a Machine with an Installation of AdminStudio
•
Creating a Shortcut to Repackager on the Clean Machine
•
Launching Remote Repackager on the Clean Machine
Sharing Directories on a Machine with an Installation of AdminStudio
To share directories on a machine where AdminStudio is installed, perform the following steps:
Task:
To share the Repackager and AdminStudio Shared folders:
1.
Locate a production machine with network access that has AdminStudio installed on it.
Tip •
Check to make sure that this installation of AdminStudio has already been activated before proceeding.
2.
Open Windows Explorer and locate the following directory:
C:\Program Files\AdminStudio\9.5\Repackager
AdminStudio 9.5 User Guide
Chapter 7: Repackaging Legacy Installations Using the Repackaging Wizard
Description
If you have connectivity from a clean machine to a computer or network
location that contains an installation of Repackager, you should launch
Repackager remotely.
If you do not have any network connectivity on the clean machine, you
should install Repackager on the clean machine.
, must be installed locally. Therefore, when repackaging on a Windows NT4
MSCVRT.dll
ADS-0950-UG00
Configuring Repackager to Ensure Optimal Installation Capture
Installing Repackager on a Clean
Machine.
451