Using the Horizon Universal Console, you can create an app package and add it to an existing App Volumes application.


  1. In the console, select Inventory > Applications.
    The App Volumes tab of the Applications page displays.
  2. Click New > Create.
  3. Under Definition in the New Application Package window, enter the values shown below.
    Option Description
    Application Select the Existing radio button and select the application from the drop-down menu.
    Description This is not editable when Existing is selected above.
    Package Enter a unique name for the package.
    Description (Optional) Enter a description for the package.
  4. Below the list of applications, select whether the applications are delivered on-demand or at the next login or startup.
    • On demand - Select this option to deliver the package only after the user clicks the package shortcut.

    • At login - Select this option to deliver the package on login or startup. This is the default.

  5. Under Desktop for Application Package in the New Application Package window, enter the values shown below.
    Option Description
    Location Select a location to filter the set of pods displayed in the Pods drop-down menu.
    Pod Select a pod to filter the set of pods displayed in the Image drop-down menu. The Pod drop-down menu displays only pods that have App Volumes enabled, have at least one image with the App Volumes Agent installed, and have Unified Access Gateway enabled.
    Image Select an image. The Image drop-down menu displays only images with the App Volumes Agent installed.
  6. Click Save.
    The first time you initiate the capture process, the system takes up to 20 minutes before the capture desktop VM is ready to use for capturing an application. During these 20 minutes, the system is creating a capture-process VDI desktop assignment and two desktop VMs to be used for the capture desktop VMs. It can take the system up to 20 minutes to create that underlying assignment and VMs.
    • The system creates one assignment per user per image per pod. For this reason, it might create one assignment or multiple assignments.
    • There are two desktops in each assignment so that you can start a second capture quickly after the first has finished.
    • These assignments are named according to the pattern appcaptureXXX, where XXX is a randomly generated number.
    • Depending on your tenant's configuration on the console's Broker page and due to the dynamic nature of the console reflecting that configuration, the console's left-hand navigation for assignments will have some combination of the labels Desktops and Apps, such as Assignments > VDI Desktops & Apps or Assignments > RDSH Desktops & Apps or some combinations along those lines. For whichever type of path in the console that has the Apps label, these assignments are listed there.
    • If you want to update the image that is used for the packaging process, you must delete these assignments before doing so.
    • If you are not planning to perform additional capture in the near future, you can delete these assignments so they are not in your environment for no reason. If you delete them, however, the next time you perform a capture the system will take up to 20 minutes to create new ones.
    Note: If a capture fails, you can look under Monitor > Notifications to see any errors that have been reported.
    There is now an entry for the application package in the list on the Applications page. If you point to Status for this list entry, it indicates the status of the capture VM. When the status is Desktop ready for application capture, you can proceed with the steps to log into the capture desktop VM and start installing an application for your app package.
    Note: You must begin the steps below within 6 hours of the capture VM being ready for application capture, or the capture VM will no longer be usable for application capture. You must also finish the steps below within 6 hours of performing the first step. If you do not, the system gives a warning and then 30 minutes later cancels the capture process and shuts down the capture VM, changing the app package status to Error. You can retry by removing the app package that is in Error state and clicking New > Create again on the Applications page.
  7. On the Application page, click the name of the application.
    The application detail page for the application displays.
  8. Select the new application package and then click Start Capture.
    The Horizon HTML Access (Blast) login form opens in a new browser tab.
  9. Log in using the same credentials that you used to log in to the console at this procedure's starting point.
  10. In the Horizon HTML Access client, launch the capture desktop VM.
    Note: The user name used to log in to the capture VM must have local administrator privileges to avoid the User Access Control (UAC) prompt.
    A VMware App Volumes - Packaging in progress dialog box with the message Packaging... is displayed on the Windows desktop.
    Important: Do not close this dialog box. If necessary, move it out of the way until you are finished installing the application you want in the application package.
  11. Install an application that you want to package in the application package.
    Note: It is a best practice to capture only one application per capture session. Install one application and then finish the capture process. When the application package for that application is visible on the console’s Applications page, then you can capture another application in a new package. See Horizon Cloud - Add a New App Package to an Existing App Volumes Application.
  12. Click OK in the VMware App Volumes - Packaging in progress dialog box. After you are finished installing the application, in the App Volumes – Packaging in progress window click OK. The next App Volumes – Packaging in progress window appears.
    A VMware App Volumes - Packaging in progress dialog box with the message Installation complete? is displayed.
  13. Click Yes.
    A VMware App Volumes - Finalize Package dialog box displays.
  14. Make any desired changes to the name and version, and optionally add a description.
  15. Click Finalize.
    A message displays prompting you to reboot the VM.
  16. Click OK and let the VM reboot.
    As the capture desktop VM is rebooting, your HTML Access client session displays a message that you have been disconnected.
  17. After the capture desktop VM is back online, log in again to see the Packaging successful! message.
  18. Log out of the capture desktop VM.


On the application detail page, the new app package appears with status of Application capture in progress. The status changes to Success when the app package import is complete.