Setting up a Microsoft Windows 10 or 11 Enterprise Multi-Session Image with App Volumes Applications in Horizon Cloud Pods in Microsoft Azure

If you choose to use a Microsoft Windows 10 or 11 Enterprise multi-session image with App Volumes in Horizon Cloud in Microsoft Azure, you must take specific actions during the process, which begins with creating the underlying Microsoft Windows Enterprise multi-session operating system and ends with providing applications to users by creating an App Volumes assignment, as illustrated by the following high-level sequence.

For background information on the procedures that follow, see App Volumes Applications for Horizon Cloud on Microsoft Azure - Overview and Prerequisites.

To use the App Volumes features with Microsoft Windows 10 or 11 Enterprise multi-session operating system, the pod must be of manifest 2747.x or later.

When you perform the procedures linked to in the following list, observe any instructions specific to configuring a Microsoft Windows 10 or 11 Enterprise multi-session image for use with App Volumes features in Horizon Cloud pods in Microsoft Azure.

Important:

• On a multi-session machine, application package detachment happens after the last user assigned that package logs off. Shutdown of the corresponding VM is not required to detach volumes.
• The system's in-cloud capturing workflow is not available for multi-session or RDS types of operating systems. This in-cloud capturing workflow is performed using the console to select App Volumes > Create.

  Therefore, to add App Volumes applications into your tenant inventory using the in-cloud capturing workflow, you must use an image based on the client type of Microsoft Windows 10 or 11 Enterprise multi-session operating system, sometimes referred to as the VDI type of the operating system, and use that for the in-cloud capturing workflow. Then, when those applications are in the inventory, they can be used with session-based desktops provisioned by the farms using Microsoft Windows 10 or 11 Enterprise multi-session images. You assign the session-based desktop to an end user for the underlying desktop and then also assign those captured App Volumes applications to that same end user for their use within that session-based desktop.

1. Add App Volumes Applications to the Horizon Cloud Inventory

Before you can assign an App Volumes application to end users whom you entitled session-based desktops, your tenant's inventory must contain that App Volumes application. You can use the console's Create workflow or Import workflow to add App Volumes applications to your tenant's inventory.

However, the Create workflow is not available for a multi-session type of operating system. If you want to use the Create workflow to add an application to the inventory, you must have a client-type, VDI-type of Microsoft Windows 10 or 11 operating system to use with that workflow and capture the applications from that VDI-type of operating system.

• Use the console's Create workflow to add the applications from a VDI-type of Microsoft Windows 10 or 11 operating system into the inventory. For the steps, see Add an App Volumes Application to Your Horizon Cloud Tenant's Inventory Using the Create Workflow.
• Use the console's Import workflow to add App Volumes applications to your inventory that you manually captured outside of your Horizon Cloud tenant and manually uploaded into your pod's staging fileshare using the Microsoft Azure portal. The main use of this workflow is for when you already have App Volumes packages from some on-premises App Volumes installation and you want to reuse those packages in your Horizon Cloud inventory. See Horizon Cloud - Add an App Volumes Application by Importing an Existing App Package

2. Entitle the App Volumes Applications to the New Users

Create an App Volumes assignment for the new users that includes one or more of the App Volumes applications you just created. See Horizon Cloud - Create an App Volumes Assignment.

Important: If a service requiring administrative privileges is captured in a Microsoft Windows 10 or 11 Enterprise multi-session app package, any user being assigned that app package must also have administrative privileges.

3. Create the Underlying Desktop for the Microsoft Windows 10 or 11 Enterprise Multi-Session Operating System and Entitle to Users

This first part of the process includes the procedures that follow.

1. Create a desktop image of the Microsoft Windows 10 or 11 Enterprise multi-session operating system. See Creating Desktop Images and Your Horizon Cloud Pods in Microsoft Azure.
   Note: When you create the base VM for the image, install the App Volumes Agent.
2. Create a farm using the new Microsoft Windows 10 or 11 Enterprise multi-session operating system desktop image. See Horizon Cloud Pods - Create a Farm.
3. Entitle the new Microsoft Windows 10 or 11 Enterprise multi-session session desktop to end users based on the new farm. See Horizon Cloud Pods - Provide Desktop Sessions from RDS Hosts for Your End Users by Creating an RDS-Based Session Desktop Assignment.