|
Be aware: This chapter describes how to use RayPack on virtual machines to provide a clean repackaging without requiring a separate license for the packaging machine. In most cases, it is better to use PackBot to automate this task, but users may use the following instructions to revert to a fallback in case PackBot is unavailable or the repackaging must be done on a remote machine or on a machine virtualized by anything other than VMWorkstation, ESX, or Hyper-V. |
Using RayPack requires a product activation. Whilst the implemented web-based activation procedure works fine for permanent packaging machines, it is not the handiest possible solution for the maintenance of several clean machines for repackaging. Usually, these are various sets of virtual machines which are reset for every new repackaging process. Installing the full RayPack framework on every clean machine would also lead to a high number of required licenses. This is not the intended licensing model Raynet has in mind for RayPack.
The solution to this issue is a special mode in which RayPack provides the basic functionality without checking for a full product license. This means that the product configured in the standalone mode can be used on as many machines as required. The standalone mode does not require an internet connection or access to the activation server. It is fully portable and requires no installation (although it is possible to install the product in the standalone mode).
Limitations of the Standalone Mode
There are several limitations of the functionality. Basically, using a standalone installation allows to perform the whole repackaging process and to create RCP projects.
Some selected features that are not present in the standalone mode are:
•Editing and creating MSI / RPP projects (PackDesigner).
•Creating response transforms (PackTailor).
•Building to deployable formats (MSI, MST, MSP, App-V, ThinApp, SWV, MSIX, VHD, LAYPKG).
In order to create a deployable package (MSI, MSIX, virtual packages, etc.) or use features that are not otherwise present in standalone mode, a full valid RayPack license is required. In a typical scenario, the standalone mode can be used to perform the repackaging on a clean virtual machine, capture changes, and produce the .rcp project. Then, the source files have to be copied to a physical machine where the full RayPack is installed in order to customize the package and convert it to required format.
Installing PackRecorder in Standalone Mode
During the installation it is possible to select the Standalone installation mode. Such an instance can be used on any machine.
Starting RayPack from Network Shares / Flash Drives
When RayPack is started from a network share, a mapped network drive, or a flash stick and no other license is present on the machine, then the product will automatically start in the Standalone mode.
The Standalone mode can also be forced by using the -Remote command line switch.
Using Portable Repackager
The Portable Repackager is a command-line based tool which can create snapshots and produce RCP files on any machine without RayPack license. You can find out more about its usage and syntax in the chapter Portable Repackager.