Repackaging in Virtual Machines

The Repackager can be configured to capture an installation running on your local machine, where Advanced Installer is installed, or in a virtual machine, where nothing else is installed, thus a much cleaner system which can yield much more accurate results.

Repackaging in Virtual Machines

Besides getting very accurate results, VM repackaging provides another important advantage, i.e. it dramatically reduces the time it takes to repackage and test an application. This is done by the use of snapshopts from the VM, our repackager can use existent snapshots or create new ones on the fly, so for you it will be like running directly in the host OS but without having to cleanup the application that got installed during the repackaging operation. This is done automatically by the repackager, as part of its VM snapshots management system.

Supported Virtual Machines

Currently the Repackager supports integration with VMware and Hyper-V virtual machines. Check your existent virtual machines against the minimum requirements listed below, to see if you can use them for repackaging your applications.

Repackaging in VMware virtual machines

  • The minimum required versions are VMware Workstation 10 and VMware Player 6.
  • Make sure you have the latest VMware tools version installed.
  • Virtual machines created with an older version of VMware Workstation should make sure they have VMCI driver enabled. This is enabled by default in VMs created with the latest editions.
  • If the state of the VM is powered off, you should power it on and login with the specified username and password before continuing. The repackager wizard will power the VM for you but you will have to login manually.
  • During repackaging, the repackager tool will require elevation so be sure to check the VM for any prompts.

ImportantIf you have only VMware Player, i.e. no VMware Workstation, installed on your machine it is mandatory to install VIX SDK from VMware. If VIX SDK is not installed the repackager will not be able to connect with the VM player.

The tutorial for repackaging in VMware VMs shows you step by step how you can capture, edit and build your legacy installations into standard MSI packages.

Repackaging in Hyper-V machines

  • The Repackager supports the following Hyper-V virtualization platforms (64-bit):
    • Windows 8 Pro/Ent
    • Windows 8.1 Pro/Ent
    • Windows Server 2012
    • Windows Server 2012 R2
    • Windows 10 Pro/Ent
  • The supported VM guest OS is Windows XP SP3 (or newer), both 32-bit and 64-bit versions.
  • Make sure the latest version of Hyper-V Integration Services is installed.
  • If the state of the VM is powered off, you should power it on and login with the specified username and password before continuing. The repackager wizard will power the VM for you but you will have to login manually.
  • During repackaging, the repackager tool will require elevation so be sure to check the VM for any prompts.

The tutorial for repackaging in Hyper-V VMs is another example of how you can convert legacy installations into standard MSI packages.

NoteRepackaging in virtual machines requires administrative credentials.

Advanced Installer tools

For a better repackaging experience on both VMware and Hyper-V virtualization providers Advanced Installer will require installing Advanced Installer tools.

To avoid having to install the tools everytime, simply copy and install osprovision.exe from the following location, then save the snapshot:

C:\Program Files (x86)\Caphyon\Advanced Installer 13.0\bin