Wise Package Studio Reference
217
Capturing Applications
In the Professional Edition, you can use Virtual Capture to simulate a clean machine.
Before using Virtual Capture, read the guidelines in
Using SetupCapture With Virtual
Capture
on page 237.
z
You can capture an installation in a virtual software layer and then delete or
deactivate the layer and restore the computer to its original state.
See
Capturing an Installation in a Virtual Software Layer
on page 219.
z
During a capture, SetupCapture tries to convert computer- and user-specific data in
the registry to generic data that will work on any computer. It does this by
searching for standard paths (example: C:\Winnt) and replacing them with Windows
Installer properties (example: [WindowsFolder]).
Part of this process includes searching for the computer name and currently logged-
on user name. To make the search for computer and user names as accurate as
possible, make sure the computer name and user name on the capture computer
are set to unique names four or more characters in length. Avoid having the user
name or computer name set to any common file or folder names. An example of a
unique user name is: repackage-1-user.
z
Before you run SetupCapture, exit all other applications, including background
services or applications. (Example: Norton AntiVirus.)
z
If you capture to a WiseScript package, be aware that for display purposes, the
registry entries are split into multiple Edit Registry actions. (Not available in
Standard Edition.)
z
During SetupCapture, changes to an .INI file are recorded as changes to an .INI file
only if the .INI file follows standard .INI file format. Otherwise, the changes are
recorded as a file change.
z
Do not capture an .MSI-based installation. Instead, open the .MSI directly in
Windows Installer Editor. To customize it for specific workgroups, create a
transform.
See Creating a Transform Based on an Existing .MSI in the Windows Installer Editor
Help.
z
You must be able to run the original installation to repackage it with SetupCapture.
Example: If the installation requires a serial number, you must have the serial
number.
z
SetupCapture does not monitor any internal logic within the installation and it does
not replicate the user interface of the original installation.
z
SetupCapture creates a separate feature for each .EXE that’s installed that has a
shortcut. Isolating .EXE components into features results in more efficient repairs,
because if there is a problem with a component, only the problem component and
the .EXE are reinstalled instead of the entire feature containing the problem
component.
(Windows Installer packages only.)
z
To capture an uninstall, you must mark Include files deleted during capture and
Include registry keys deleted during capture in SetupCapture Configuration
General Settings. In Windows Installer Editor, deleted items are located in the
RemoveFile and RemoveRegistry tables in Setup Editor > Tables tab.
In WiseScript Package Editor, deleted items are located in Delete File(s) or Edit
Registry statements in the script.
z
Registry keys that define an environment variable are converted to an environment
variable in the repackaged installation.
