For ISVs
White Papers
Video Garden

Deploy Virtual Applications To Image

In this step, we will deploy the full list of virtual applications to our Golden Image. This will alter the image in the following ways:

  • The package contents will be 100% streamed into the cache.
  • The package application OSDs and ICOs will be cached.
  • The packages and applications will be registered in the App-V registry.
  • The application shortcuts and file type associations will be published only to the administrator user account that performs this action. (This allows testing, if desired. All package shortcuts are added, without respect to the Applications OU).

Later on, we will extract the sftfs cache file that contains 100% of the streamed package contents, however it is important that the second and third items be part of the golden image. Shortcuts and file type associations for VDI users will be layered on when the user logs into their VDI session, based upon membership in the Applications OU groups.

We deploy the packages using the AppV_DeployContent tool. This tool allows you to select a folder. The tool will walk the folder structure and identify packages (using the _manifest.xml file) and import them into the App-V client. It will also stream 100% of the package content into the local cache.

Here is an image of the tool when it is first launched. The tool remembers the default folder input during the install, in our case, the ContentLinks share that contains links to 14 packages.

Clicking the Add/Load Packages button starts the process. Immediately, the center section of the dialog displays the detected packages, and begins processing them. The bottom of the screen indicates what package the tool is currently working on and an overall status.

I have intentially included several packages that will fail, in order to demonstrate certain types of failures. You can see that the second and third packages failed to be added. In one case, the package was sequenced and marked to only work on Windows XP. In the other, the package was sequenced and marked to only work on 32-bit operating systems (this was an x64 OS). In both cases, checking the App-V client log would identify the specific issue.

Here you can see the error for one of the packages in the App-V log file. Error 44-00001007 is welll known as an incorrect OS Version tag issue inside the OSD.

I also included another type of problem package - one which you hopefully will never see (except in my "App-V Masters Level Training Class")! The issue with this package is that it has a duplicate package GUID. This only happens in App-V if you don't follow the best practices we teach you in the class. Note that the popup error dialog could have been avoided by checking the "Prevent App-V Error GUIs" checkbox.

These package failures do not harm our image, the packages are properly excluded from the Golden Image. In the screen shot below, you can see the final results, with 11 of the 14 packages sucessfully deployed.

Starting with version 1.7, a log file is automatically generated with the results from each package. This file is written to the install folder of the program. The log may be disabled by launching AppV_DeployContent with a /NOLOG parameter.

As I indicated, shortcut publishing occurred to the admin that ran the tool. So, if desired, the admin may immediately test the applications prior to finalizing the Golden Image. Because of the virtualization, nothing the admin does will affect application useage by other users that use VDI sessions from this Golden Image.

Not shown in the AppV_DeployApp tool. We do not need this tool as we can deploy all of the applications to create the Golden Image by pointing to a share folder with links to everything we want to deploy. AppV_DeployApp might be used if we later want to open up the Golden Image to add a few additional packages. That tool works like AppV_DeployContent, except that you speicify an individual _manifest.xml file rather than a folder.

Return to Preparation of Golden Image