Using the Add Application workflow in the Horizon Universal Console, you can add an application to your organization's inventory. You can either add a package immediately when creating an application or you can use the Add Package workflow and add a package to the existing application at a later point in time.

Note: If you want to add a package to an existing application, it is not necessary to create the application again.
  • After using the Add Application workflow for the first time, the same user must not attempt to use that option a second time for the same image until they have completed the steps to capture an application package in the capture desktop VM. If they try to use the option again for the same image before finishing the steps to capture an application package, a message displays stating that a request to create a package is already initiated. A different user in the same tenant, however, can initiate creating a package for that image whether or not the first user has finished.
    Note: When selecting different images, either on the same Horizon Edge or another Horizon Edge, the same user can run multiple captures simultaneously. They cannot run multiple captures simultaneously for the same image.
  • The first time you click the Add Application option to initiate the capture process, the system can take up to 10 minutes before the capture desktop VM is ready and the status changes to Desktop ready for application capture. For this first time, this 20-minutes time is because the system is creating a desktop assignment and two desktop VMs to support the capturing process. After you have completed capturing your first application package, and then want to initiate a new capturing process, the time between when you click the Add Application option and the status changes to Desktop ready for application capture is shorter, around 10 minutes. The times after the first time are shorter because the system does not have to create the capture desktop assignment like it did for the first time. For the second time, the system deletes the previously used capture desktop VM and uses a new one.

Each package has a delivery option. Using this option, you can configure the package delivery mode as Classic or On-demand. With classic delivery, any assigned application is delivered to an end user immediately at computer startup or user login. With on-demand delivery, a shortcut appears, but the application is not delivered until the user opens the shortcut. For more information, see VMware Horizon® Cloud Service™ - next-gen - Understanding Package Delivery Modes of an App Volumes Application Package.


Confirm that your environment meets all the prerequisites listed in App Volumes Applications for VMware Horizon® Cloud Service™ - next-gen - Overview and Prerequisites.

The Add workflow is only available for images with single-user, client, or VDI types of Microsoft Windows operating systems, and not for multi-session types of operating systems. Before you perform the steps in the task that follows, you must have an available image with the App Volumes agent installed. When adding an image from the Microsoft Azure Marketplace and publishing the image, ensure that you have turned on the App Volumes toggle button. By default, this toggle is turned off. This toggle button is listed in the Agent section when publishing an image.

App Volumes toggle is present in the Agent window in the Publish Image page. To ensure that the App Volumes agent is installed on the image, toggle must be enabled.

To add an image and publish an image, see the Managing Horizon Images from the Cloud.


  1. In the Horizon Universal Console, navigate to Desktop and App Catalog > App Volumes.
  2. Click Add > Application.
  3. On the Add Application page, add Application Name and Description.
  4. Add the Owner Details by selecting the owner from the available domains from the Active Directory
  5. Select the toggle to Add Package.
    Note that you can either add the package right away or later. To add the package later, you can use the Add Package workflow.
  6. Add Package Name and Description.
  7. Select the Horizon Edge where the application will be packaged.
  8. Select the Provider in which the packaging VM is created to capture the package.
  9. Select the Machine Identity.

    You can choose either the Azure Active Directory or a configured Active Directory domain registered with your environment. If you choose the configured Active Directory domain, ensure that the domain is reachable from the selected Horizon Edge.

    Note: For Azure Active Directory, all Windows 11 and Windows 10 devices are supported, except Home editions Windows Server 2019 and newer Virtual Machines running in Azure (Server core isn't supported).
  10. Select the Packager or the user that is allocated the VM for capturing the application.
    The domain of the user must be same as the selected Active Directory domain.
  11. Select between Classic and On-demand delivery.

    By default, the package delivery is Classic. If you configure the package as On-demand, package attachment occurs only when the end user launches the application.

    Note: For packages created using versions of Horizon Agent Installer and earlier which do not have on-demand support, an administrator can still change from On-demand to Classic and Classic to On-demand. However, App Volumes agent cannot virtualize the existing package as per the on-demand behavior.
  12. Select the Image used by the VM to capture the package.
    Ensure that the image has the App Volumes agent installed.
  13. Select the Image version used by the VM to capture the package.
  14. Select the Desktop Model used to create the VM for packaging.
  15. Click Save.


  • As soon as the package is added, status of the package is Desktop provisioning is in progress.
  • After desktop provisioning is done and the packager is assigned a VM, status of the package is Ready for capture.

What to do next

After creating an application, you can perform any of the following tasks: