You can define a relationship between two different App Volumes applications. This capability determines the order of attachments at end user login or computer startup when delivering these applications to an entity. As a result, you have more control in application management.
To ensure applications are delivered in a specific order, use the application relationship capability. Without this capability, the virtualization order of the applications cannot be determined. As a result, the same set of applications assigned to multiple users can get delivered in a different order for each user.
To determine order of precedence between multiple packages of a single App Volumes application, see Order of Precedence for Assigning App Volumes Applications.
You can define three types of application relationships: Dependency, Application Conflict, and Install Order (Precedence). For more information about the types of application relationships, see Understand Types of App Volumes Application Relationships.
Considerations when using Application Relationships
-
Ensure that all Windows endpoints are installed with App Volumes agent 2603 and later. If the installed version is earlier than 2603 and App Volumes Manager is installed with version 2603, then the application relationship capability cannot be used.
-
Any relationship defined or changed in App Volumes Manager between two applications which are already delivered to the entity is ignored until the subsequent computer startup or user login.
When the App Volumes agent is installed on the Windows endpoint in a local copy mode, these changes take effect when the next synchronization occurs between App Volumes Manager and the Windows endpoint. -
If an application already delivered to a Windows endpoint in local copy mode later enters or comes out of a relationship with another application, an in-place application swap occurs at the endpoint.
This in-place swap happens when the endpoint device synchronizes with App Volumes Manager in the next sync interval. The latest changes in entitlements are retrieved from App Volumes Manager. As a result, the existing application gets uninstalled or reinstalled after meeting the relationship criteria depending on the relationship type.
Add an Application Relationship
To define a relationship between two different applications, use the ADD RELATIONSHIPS button. An application relationship determines the order of attachment at end user login or computer startup when delivering the applications to an entity.
Prerequisites
Ensure that you are aware of each application relationship type, behavior, use cases, and limitations.
For more information, see Understanding Types of App Volumes Application Relationships.
Procedure
-
In App Volumes Manager admin UI, navigate to INVENTORY > Applications.
-
Click the required application and open the application details page.
-
Click ADD RELATIONSHIPS.
-
In the Add Relationship page, from the Select an Option drop-down, select the following:
-
Relationship
-
Related application
A relationship is defined between the source (current) application and the related application.
-
-
Click Add.
After a relationship is successfully added, in the Application details page, a Relationships table is displayed. This table lists the Relationship Type, Relationship, and Related Application Name.
What To Do Next
Continue with the rest of the application and package workflow and deliver the applications to the entity. When the applications get delivered to the entity, you can validate in the Windows endpoint whether the defined relationship for the delivered applications is successful. For more information about how to validate, see Validate An App Volumes Application Relationship in the Windows Endpoint.
¿Le resultó útil esta página?