You can create an application package and add this package to an existing App Volumes application.
Note: If you want to add a package to an existing application, it is not necessary to create the application again. Instead, select the existing application from the list of applications displayed in the App Volumes tab and continue creating a package as per the steps mentioned in this task.
After using the Add Package 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: Administrators can run multiple captures simultaneously on the same image or on different images. The image can either be on the same or on another Horizon Edge.
The first time you click the App Package 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 start a new capturing process, the time between when you click the Add Package 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 user login. With On-demand delivery, a shortcut appears, but the application is not delivered until the user opens the shortcut.
Procedure
-
In the Horizon Universal Console, navigate to App Volumes > Packages.
-
Click Add.
-
Select an existing application to which this package must be added.
-
Enter the Package name and Description.
-
Select the Horizon Edge where the application will be packaged.
If the Horizon Edge deployed is for a vSphere provider type, two image sources are supported: Source vCenter and Source Image Catalog.
-
Select the Provider in which the packaging VM is created to capture the package.
-
If the Horizon Edge deployed is for a vSphere provider type, perform the following steps based on the image source:
Image source Action vCenter 1. Select the Golden image in vCenter.
2. Select the Snapshot.Image Catalog Similar to the other deployments such as Microsoft Azure and Amazon Workspaces Core, select the image and image version as described in the next steps.
-
-
Select the Image used by the VM to capture the package.
Ensure that the image has the App Volumes agent installed.
-
Select the Image version used by the VM to capture the package.
-
If you want to route outbound requests to the Internet through a proxy server, activate the Use outbound proxy toggle and provide the values for Proxy host and Proxy port.
-
Optional: If you have already configured outbound proxy settings (proxy host and proxy port) for the Horizon Edge selected in this workflow, then turn on the Copy Horizon Edge proxy toggle to use the same configuration here. As a result, Horizon Edge proxy settings are automatically carried over to these fields: Proxy host and Proxy port.
-
Select the Desktop Model used to create the VM for packaging.
-
Select the Machine Identity.
You can choose either the use 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).
-
If you have selected an Amazon Workspaces Core provider type in one of the previous steps, select a Directory ID for this package from the drop-down box.
The Directory ID indicates a directory created in the Amazon Web Services (AWS) console. For more information about the directory created in AWS, see Create a Pool.
-
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.
-
Select between Classic and On-demand delivery.
By default, the package delivery mode is On-demand. In this mode, package attachment occurs only when the end user launches the application.
Note:
-
For packages created using versions of Horizon Agent Installer 23.1.0.21387799 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.
-
If you want to deliver a package in real time rather than at user login, you can use the command-line delivery option. To use this option, at the time of creating an entitlement, you must enable the Do not deliver at login setting. When command-line delivery is used, the application is not available at login regardless of the package delivery mode (
Classic,On-demand) selected.In on-demand package delivery mode, application shortcuts are delivered at login but the applications are delivered only when the shortcut is launched. Whereas in command-line delivery, the application shortcuts are also not delivered at login.
For more information about the command-line delivery option, see Use Command-line to Deliver App Volumes Applications.
-
-
In the Networks section, depending on whether the Horizon Edge selected in an earlier step is Microsoft Azure or Amazon Workspaces Core, do the following:
Options Procedure Microsoft Azure To select the virtual network and tenant subnet for this package, click the drop-down boxes for Virtual Network and VM Subnet respectively and choose the desired values.
When a system pool is created during application capture, the selected tenant subnet is considered instead of all the subnets associated with the provider which was selected earlier in this procedure.Amazon Workspaces Core For the specified Virtual Private Cloud ID (VPC), select Availability Zone 1 and Availability Zone 2 and the respective Subnet from each of these Availability Zones.
Note: If the Directory ID selected in an earlier step is registered, then changing the Availability Zones and Subnets is prevented. The values for these fields are automatically added. This behavior is the same as when creating a pool. See Create a Pool. -
If the Horizon Edge deployed is for a vSphere provider type, then configure the vCenter Settings.
vCenter settings are required to create the capture desktop VM.
-
Select the Datacenter.
-
Select the vSphere cluster, where the VDI desktops get deployed to, and click Save.
-
Select the Resource Pool .
-
Select the VM folder where the VM is stored.
-
Select a datastore for the pool.
-
Select the same network as the image or choose from the list of available options.
-
Enter the number of CPUs.
-
Enter the amount of memory in GB.
-
-
Click Save.
Results
-
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
To capture the application package, follow the steps in Capture an App Volumes Application Package Using Horizon Cloud.
Was this page helpful?