Virtualisr is a tool used for App-V 4.6, App-V 5 and App-V 5.1 automated sequencing/virtualisation. It can convert scripted installs (VBS, BAT, CMD) to App-V, convert MSI to App-V and convert executables/legacy installers to App-V. It can rapidly accelerate application migrations and save your company hundreds of man-hours and thousands of pounds. Other virtualisation technologies can be supported upon request.
PLEASE NOTE: There seems to be a bug with the New-AppvSequencerPackage cmdlet in the Windows ADK version of the sequencer. PSR mode may not work with this version.
PLEASE ALSO NOTE: I generally only use Virtualisr when I have a batch of pre-configured (or default) apps that I need to quickly convert, or if I’m performing a migration for a client. In reality this is probably every few months since most of the time I will package ad-hoc requests. During this period Oracle tend to update VirtualBox and as part of these updates they usually alter the command line syntax! This may stop Virtualisr from functioning correctly. If this is the case please contact me and I will attempt to resolve any issues as soon as possible.
- FREE! (for a limited period – licenses will be provided in batches of 10). License key must be obtained from us first. Contact us here
- App-V 4.6, App-V 5 and App-V 5.1 Automated Sequencing/Virtualisation
- Sequence on your own custom virtual machines
- Keep your installation files local and secure
- Utilise industry leading Oracle virtualisation software
- Bulk import multiple applications to convert, and perform batch conversion whilst you make a brew!
- Perform batch automated* conversions of .EXE (legacy installers), .MSI, .VBS, .BAT and .CMD to App-V 4.6 and App-V 5 formats
- Supply command-line arguments for your installation target
- Apply one or many transforms (MSTs) to MSI installations
- Manually specify package names (auto-generated from imported MSI/MST name as default)
- Perform MNT/VFS installations (App-V 4.6)
- Manually specify PVAD, or automatically set PVAD to actual installation directory (App-V 5/MSI only)
- Specify App-V templates, Full Load, Mount Drives etc
- Record Problem Step Recorder screenshots to use as part of your discovery inventory
- Output conversions to a logical folder structure
- Compatible with Oracle VirtualBox and VMWare Workstation** virtual machines
- License not used for failed conversions***
- Unlimited remote support
* scripted installations can only be automatically converted if the scripts themselves are automated with no human interaction required.
** VMWare Virtual Machine needs to be hosted inside Oracle VirtualBox
*** sufficient error handling required in scripts
Missing any functionality? Contact us here to request it.
There are products such as Autonoware ConversionBox and Flexera AdminStudio Virtualization Pack which already provide automated App-V virtualisation and do a decent job of it. However these are costly (certainly when we’re talking about multiple application portfolios containing several hundred applications), cumbersome installations with often complex licensing agreements. Virtualisr is a lightweight (under 500kb) executable used alongside Oracle VirtualBox and is completely free.
- 6GB Memory (minimum)
- 2.5 GHz dual-core Intel or AMD processor
- Powershell 2
- Microsoft .Net 3.5
- Oracle VirtualBox (https://www.virtualbox.org/wiki/Downloads)
The Virtualisr executable does not install anything. The program is run directly. It works by launching virtual machines that are hosted in Oracle VirtualBox (since VirtualBox is free). You can also mount your VMWare virtual machines in VirtualBox in order to use Virtualisr.
Step 1 – Install Oracle VirtualBox
You can download it from this location: https://www.virtualbox.org/wiki/Downloads
Step 2 – Create your Sequencing Virtual Machine base image
NOTE: If you already have VMWare virtual machines set up you can use these by importing them into Oracle VirtualBox (Just select ‘Use an existing virtual hard drive file’ and then specify the VMDK/VDI when asked to configure the hard drive). If you already have VirtualBox virtual machines configured you can use those too. In both cases, just ensure you have the latest Guest Additions (see below) and you can then ignore this step and step 3.
Get hold of an ISO of the Windows operating system that you want to sequence applications on. Open Oracle VirtualBox. Create a new Virtual Machine, specifying memory amount and hard disk configurations. Be wary that there are some large applications out there. I’ve created mine as the default 25GB.
Once you’ve created it, start the VM and point to your Windows ISO when it prompts to select a start-up disk. Follow the usual instructions to install your copy of Windows. Ensure that you give the admin account a password and don’t just leave it blank.
Once this is complete and you’re logged in to the operating system, install the latest Guest Additions (I installed 4.3.12 at the time of writing this). You can obtain it from this location:
VirtualBox Guest Additions (choose version and downoad the .iso, for example VBoxGuestAdditions_4.3.8.iso)
and instructions are here:
Reboot your VM. Configure the base image as required (service packs, windows updates etc). Once done, disable Windows Updates, stop the Windows Defender and Windows Search services. Disable Action Center messages. And disable User Account Control.
Create a snapshot. I called mine ‘base’
Step 3 – Create your App-V 4.6 and App-V 5.0 snapshots
With our base snapshot running, install the App-V 4.6 sequencer with all the relevant service pack and hotfixes. Once done, create a snapshot called ‘App-V 4.6 <Service Pack/Hotfix etc>’. For example, mine is called ‘App-V 4.6 SP3’.
Now revert back to the base snapshot. Install the App-V 5 sequencer, again with any service packs and hotfixes. You may also need to install the relevant prerequisites for the App-V 5 Sequencer. Once done create another snapshot. I called mine ‘App-V 5.0 SP2 HF5’.
You should now be ready to sequence! It’s pretty self explanatory (i think!), but just in case it’s not, here are a few instructions:
How it Works:
Before you start, create a folder and dump all of your installation source in there. I created a folder on the root of C: called ‘ToConvert’. I also organised each application into their own folder for clarity.
Step 1 – Launch Virtualisr.exe
Step 2 – Import Packages to Virtualise
Specify your license key. You can check how many licenses you have available by clicking ‘Get Status’.
Click ‘Import Source Files’ and point to your source dump location. In my case, as mentioned above, my source dump is C:\ToConvert. Click Ok and all of the .MSI, .MST, .CMD, .BAT and .VBS files will populate in the DataGrid. You can filter which file type you want to view. From the screenshot above, you can see there are 11 columns. They should all be self explanatory but you can hover over the header for more information.
- Dark grey denotes a disabled cell
- Select zero to many transforms. If you need them to apply in a specific order I suggest you name them alphabetically (or prefix with a number) to order them as they will install in the order shown in the GUI
- The Package Name column is editable. By default it will give this the name of the MSI/First MST/Script provided as install source.
- The PVAD columns are also editable
- The MNT checkbox will (in the case of and MSI) attempt to install the MSI to the PVAD location. Otherwise it will perform a VFS installation.
- The O/R (Override) checkbox will attempt to get the INSTALLDIR of an MSI and set the App-V 5 PVAD to this location
- Select the ‘AV4.6’ or ‘AV5’ check box to convert the installer to the relevant format
- Configure Feature Block 1 with FullLoad
- Specify the Virtual Machine to use, and select the appropriate snapshots for sequencing App-V 4.6 and App-V 5 packages. You must also specify the login credentials for the admin user.
Step 3 – Click Virtualise!
Two folders will be created in your source dump folder called ‘Virtualisr-AV5’ and ‘Virtualisr-AV46’. Your packages will be output to these locations, and named according to the package name you specified in the DataGrid.
A log file will also be created in the source dump folder called virtualisr.log. This is appended to each time you run Virtualisr, and is opened at the end of each session. It should contain installer exit codes (in case the installer fails), sequencer exit codes (in case the sequencer fails) and VBoxManage.exe exit codes (in case the VirtualBox element fails).
A HTML report will be generated called Virtualisr_Report.html. This will contain information from the sequencing session such as success rate, time elapsed, configurations, and package success etc. Remember that ‘green’ means it has been successfully virtualised, but this does not imply that it will work in the App-V technology. You will need to use a compatibility toolset to find this out before passing the application through Virtualisr.
Under the hood:
When the conversion process starts, a shared folder is created on the guest virtual machine and is mapped to the source dump folder on the host (in our example this is C:\ToConvert). This is the only location on the host that the VirtualBox session has access to. Hence any installation source, App-V templates, log files, reports and App-V output is located here. See the screenshot below for an example of the files required for input, and the files which are output:
I’m aware that once you kick off the conversion process that the GUI becomes unresponsive. However the status in the bottom left will update, the log file will update and also the datagrid cells will be highlighted red (failure)/green (success) after each application has been processed.
Multi-threading in Powershell is not trivial, and one day I may look into using the Start-Job cmdlet and timers, as referenced to here: http://www.sapien.com/blog/2012/05/16/powershell-studio-creating-responsive-forms/. But until that day, click ‘Virtualise’ and go and make yourself a brew (or a few brews, depending upon how many apps you choose to virtualise).