How to run Setupcapture without a clean machine?

Article:HOWTO9274  |  Created: 2008-07-23  |  Updated: 2008-07-23  |  Article URL
Article Type
How To

How to run Setupcapture without a clean machine?


Running SetupCapture Without a Clean Machine


Capturing vendor software packages has typically been a lengthy process. The majority of time for any repackaging project is spent re-imaging the machine. In the past, this was necessary because running a package on a clean machine with SetupCapture was the only way to guarantee no extraneous resources were included during the capture. It also guaranteed no resources were omitted from the package because they pre-existed on the machine. With the introduction of Virtual Capture in Wise Package Studio 4.0, this time-consuming process is eliminated.


Virtual Capture, the newest capture tool in Wise Package Studio 4.0, joins ApplicationWatch and SetupCapture as capture programs. Not only does Virtual Capture run very quickly, it is the only capture method that can use a non-clean machine.


Initial Configuration of Virtual Capture

Before using Virtual Capture, you must complete some preliminary steps. First, capture the resources of a clean machine into a Virtual OS file. To generate the file, run the VirtualOS.exe located in the Workbench directory under the Wise Package Studio directory. To capture the resources of a clean machine, run VirtualOS.exe on a machine that contains only the operating system and a service pack. This machine should also have the same version of system components as the base build for your environment. These system components include Internet Explorer, Windows Media Player, MDAC, and other components that integrate with the Windows operating system. Other components safe to include are low-level utilities universal throughout your environment that are part of the base build.


The VirtualOS.exe tool copies the Virtual OS (.WOS) file to the Wise Share Point directory in the Virtual OS subfolder. After the copy is complete, run SetupCapture and select the Virtual Capture option to install the Virtual OS onto the computer. Virtual OS does not need to be installed on a clean machine and can be your primary workstation. However, this machine must have the same operating system, service pack, and same versions of MDAC and Internet Explorer as the Virtual OS file you install.


The Virtual OS file is placed at the root of your system drive in a folder named WiseImg. The WiseImg folder replicates the resources of the clean machine, including the entire file system and complete registry, stored as a .REG file.


How Virtual Capture Works

After the initial Virtual Capture configuration, captures run very rapidly. Aside from installing the Virtual OS file, the capture process is nearly identically to a standard SetupCapture. You select a configuration file, set SetupCapture options, and determine file and registry exclusions. Then in the Execute dialog, execute the application installation you wish to capture.


During installation, Virtual Capture intercepts and redirects API calls the installation makes. Files and shortcuts are placed in the replicated file structure of the clean machine, and registry keys are written to the replicated registry in the .REG file under the WiseImg directory. Virtual Capture leaves your primary machine unaffected by the capture process.


To make modifications or test application features, launch the installed application in the Execute dialog. Browse to the application’s .EXE file under the WiseImg folder because there will be no shortcuts to the application on your primary machine. The application runs using the files from the Virtual OS and accesses the registry of this replicated clean machine. In addition, Virtual Capture is still intercepting and redirecting system calls.


After making changes to your installation, finish the capture to generate the package. Then, if not done during the capture, move the package’s source files to the Wise Share Point or other network repository. Once you initiate another Virtual Capture, the Virtual OS stored on the primary machine is automatically cleaned, and all resources from the previous Virtual Capture are deleted.


Once you configure Virtual Capture, the tool captures applications rapidly and requires only seconds to prepare for subsequent captures. Because Virtual Capture gives you the ability to capture on a non-clean machine, all packaging can take place on your primary workstation. You no longer need to wait through another slow re-imaging process.


Legacy ID


Article URL

Terms of use for this information are found in Legal Notices