Server Application Virtualization with the VMM 2012 App-V Server
In this article I will discuss the creation of virtualized application packages. This feature is essential to automate the creation of services as discussed in the previous article available at
Understanding Virtualized Applications
The application virtualization feature is nothing more than a process where is captured any activity during the installation of a software registry keys, files, settings, and shortcuts.
The diagram below gives an overview of how the process works, and I will address each part of the package creation in this article.
Installing the Server Application Virtualization Sequencer
The Server App-V is part of the VMM 2012 and can be found on the installation media in the D:\SAV\amd64 directory with the name of SeqSetup.exe:
After running the installer shall produce a shortcut on the start menu to call the Server Application Virtulization Sequencer, which we call Server App-V or just SAV, and to run it will have access to their main functions consist in creating or editing packages:
Virtualizing an Application
When choosing the option to create a new package will be driven by a very simple wizard, but that requires some care.
The first step is to choose the executable that will be used to install the application:
Following enter the name that will be given to the package and the directory where it will be generated:
The wizard will run the installer indicated, with a very important warning: the directory set to the application have to be the same created in the previous step to disk q:
Important: If you choose a directory that is different from what is listed in the first step (creating the package) files of the application are not in the package, compromising the performance.
When you finish the application installation it is important that you do not run until you finish the wizard, clicking Finished:
At this point the FVO will look for changes in files and record the application has performed, and can be a quick process (2 minutes) or slow (up to 1:0) depending on what will be collected and the size of the disk:
Now is the time to run the application and make customizations, once the FVO has carried out an inventory of changes made by the installer:
In my example, I set the theme of the application and the closed. The wizard has detected the closing of the application and indicates that were captured the information:
So, the package is created and the wizard displays the success message:
By clicking Close will automatically open the package editor, that can also be run in the home menu of SAV, for you to validate what will be installed. In this step it is important to look carefully what was collected to avoid conflicts between different versions of operating systems or other applications.
When done editing, save the package. In this case it is not only created the package but also the HVO’s project files in the directory shown below:
The Edition is held at the end of a sequence or by the initial menu of the VAS that is in the previous topic and is to open the SPRJ file created.
As mentioned above, it is important to remember to check in detail the package and avoid that cause problems when installed on a server, since the Edit allows you to change, delete and add new items:
Creating an application profile
To apply a Service package in a VM or Template Template we can create a profile including one or more applications. To profile applications use the menu corresponds in the VMM Library
What operating systems are supported by the application and include the package created within Applications:
Important: for the application appear in the list above, the directory created by the sequencer must be copied in the VMM Library: 2012
Including a Virtualized Application in a Template
As I reviewed the application can be included in a Service Template as well as commented in the article on service models.
To do this click the Add Application area of the template and select the profile or even the application directly:
Ready!!!! The application is linked to the VM that is instantiated by the Service Template: