Assign an App Volumes Application to an Entity

To deliver an Omnissa App Volumes application package to an end user, you must assign an application to an entity that belongs to the registered domain.

If this application is in a synchronization relationship with an application on a source instance and the assignment synchronization setting is activated on the source, you cannot perform the assign operation from this instance. The assign operation is deactivated on this instance (target) and can be performed only from the source instance by using the Manage Source button.

For more information about the manage source feature, see Manage a Synchronized App Volumes Application at the Source. For information about the assignment synchronization criteria, see Criteria for Application Synchronization.

Some of the considerations to be noted while assigning an application to an entity are as follows:

• An application can be assigned to a single entity or multiple entities.

• If you select the assignment type as Marker and the application package is not yet marked CURRENT, the application is assigned to the entity and the assignment is deactivated until a package is marked CURRENT.
  For information about assignment types, see Understanding Assignment Types.

• The assignment type Multiple is used to represent multiple package assignments for on-demand delivery.
  For information about this functionality, see Understanding Multiple Assignments.

• In an application, a package set with the CURRENT marker can be assigned to multiple entities.

• By using the option of limiting delivery of assignments to specific computers, entities can have different application assignments on different computers.
  For more information about this option, see Application Assignment to Specific Computers.

• To deliver applications real time, App Volumes provides command-line delivery options. To use the command-line options, when assigning an application package to an entity, you must select the Do not deliver for these assignments at startup or login option to not deliver the package at user login or computer startup.
  For more information about the command-line delivery behavior, see Command-line Delivery of Applications in App Volumes.

  Note: This assignment option when selected overrides configured package delivery mode. For more information about package delivery modes, see Understanding Package Delivery Modes in App Volumes.

• App Volumes supports package capture and delivery across different operating systems within the same Windows operating system architecture.

  For example: If the package is captured in a virtual machine running a 64-bit operating system architecture, then the package can be delivered to a machine running a 64-bit operating system architecture only. The package cannot be delivered to a machine running a 32-bit operating system architecture due to architecture mismatch.

Prerequisites

• Ensure that the status of the entity, to which the application must be assigned, is Available.
• For the Package assignment type, an application must have at least one package.
• If you are assigning an MSIX app attach format to an entity, ensure that the certificate which was used while packaging the MSIX is installed on the machine where App Volumes agent is installed.
• When using the Multiple assignment type, ensure that you already have a package set with the CURRENT marker and are aware of the rest of the considerations for using this assignment type.
  For information about the considerations, see Understanding Multiple Assignments.

Procedure

1. From App Volumes Manager, go to INVENTORY > Applications.

2. Select the application to which an entity must be assigned.

3. Click Assign.

4. Search for an entity.

   With Entra ID, you can assign applications to Users, Groups, and Computers.

5. Select the entity.

   The Status of the entity must be Available.

6. Select Assignment Type.

   Option	Action
   Marker	If the application has no package or if the package is not yet set with CURRENT marker, application is assigned to the entity and the assignment type is deactivated until a package is marked CURRENT. If the package has the CURRENT marker, entity receives the CURRENT package version. Select Marker.
   Package	Select the package that must be assigned to the entity.
   Multiple	Select the packages that must be assigned to the entity. Package set with the CURRENT marker is selected by default. You can set another package with the CURRENT marker even after assignment creation.

   

   Note: If the selected package is configured for an On-demand delivery mode, the package attachment occurs only after the end user launches the shortcut of the application. This action changes the attachment and attachment count. For more information about this behavior, see the characteristics section in Understanding Package Delivery Modes in App Volumes.

7. (Optional) To only allow attachment of packages to a specific set of computers based on the name of the computer, select Limit delivery for these assignments.

   This option is available only for non-computer entities (Users, Groups, and OUs).

   1. Enter the prefix of the computer name.

      Packages are only attached to computers whose names start with the prefix specified in the text box.

      

8. (Optional) To not deliver the package at user login or computer startup, select Do not deliver for these assignments at startup or login.

   On all the Assignments listing pages, such an assignment is marked with a special icon which indicates that package must not be delivered either at user login or at computer startup.

9. Click Assign.

10. On the Confirm Assign window, click Assign.

Results

On the Applications page, assignment details are updated.

What to do next

End users can use an App Link URI to launch an App Volumes application. For more information about App Links, see Launch an App Volumes Application with an App Link.