Skip to content

Latest commit

 

History

History
51 lines (34 loc) · 3.26 KB

03-AVD-FSLogix.md

File metadata and controls

51 lines (34 loc) · 3.26 KB

Challenge 3: Enable FSLogix Profile Container

Previous Challenge - Home - Next Challenge

Introduction

The Azure Virtual Desktop service recommends FSLogix profile containers as a user profile solution. FSLogix is designed to roam profiles in Azure Virtual Desktop, mostly needed for multi-session with floating user scenarios.

It stores a complete user profile in a single container. At sign in, this container is dynamically attached to the computing environment using natively supported Virtual Hard Disk (VHD) and Hyper-V Virtual Hard disk (VHDX). The user profile is immediately available and appears in the system exactly like a native user profile.

In this challenge, you'll learn how to:

  • Setup and configure an Azure storage account for authentication using Microsoft Entra Kerberos
  • Assign access permissions to an identity
  • Create a profile container with FSLogix for your session hosts in your multi-session Hostpool

Note: Hybrid identities are needed for this challenge. The users and groups must come from a traditional Active Directory domain.

Task 1: Set up an Azure Storage account

  • Setup an Azure Storage account and a File Share
  • Enable Microsoft Entra Kerberos for Azure files

Task 2: Assign access permissions to an identity

  • AVD users will need access permissions to access the file share. You need to assign each user a role with the appropriate user access permissions

Task 3: Create a profile container with FSLogix

In order to use profile containers, you'll need to configure FSLogix on your session host VMs.

Note: If you're using a custom image that doesn't have the FSLogix Agent already installed, follow the instructions in Download and install FSLogix.

Note: The FSLogix agent is already installed on the Windows 10 or 11 Enterprise Multisession Gallery images provided by Microsoft.

  • Enable FSLogix profile settings via a custom script extension or via Intune.

Pro Tipp: 💡 To setup FSLogix on the session Hosts with a custom script extension, you can to upload the setupFSLogix.ps1 into a Container in your Storage Account. As an argument: provide the UNC Path of your fileshare, e. g. \uniquesamicroh.file.core.windows.net\fslogixfs without brakets.

  • Delete local profiles when a VHD profile is applied
  • Create a profile container with FSLogix during user login

Success Criteria

  • Storage Account and File share is setup correctly
  • Microsoft Entra Kerberos is enabled on the File share
  • Appropriate user access permissions are configured on the file share
  • A profile container with FSLogix is successfully created
  • Check that your profiles are working as expected

Learning Resources