0% found this document useful (0 votes)
22 views6 pages

Azure+Virtual+Desktop+User+Data+Storage

Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
0% found this document useful (0 votes)
22 views6 pages

Azure+Virtual+Desktop+User+Data+Storage

Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
You are on page 1/ 6

Azure Virtual Desktop User Data Storage

examlabpractice.com
FSLogix for User Data Storage
• The Azure Virtual Desktop service recommends FSLogix profile containers as a user
profile solution.
• FSLogix is designed to roam profiles in remote computing environments, such as Azure
Virtual Desktop.
• 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.
• This article describes how FSLogix profile containers used with Azure Files function in
Azure Virtual Desktop.
User Profiles
A user profile contains data elements about an individual, including
configuration information like desktop settings, persistent network
connections, and application settings. By default, Windows creates a
local user profile that is tightly integrated with the operating system.

A remote user profile provides a partition between user data and the
operating system. It allows the operating system to be replaced or
changed without affecting the user data. In Remote Desktop Session
Host (RDSH) and Virtual Desktop Infrastructures (VDI), the operating
system may be replaced for the following reasons:

• An upgrade of the operating system


• A replacement of an existing Virtual Machine (VM)
• A user being part of a pooled (non-persistent) RDSH or VDI
environment
FSLogix profile containers
On November 19, 2018, Microsoft acquired FSLogix. FSLogix addresses many profile container
challenges. Key among them are:

• Performance: The FSLogix profile containers are high performance and resolve performance
issues that have historically blocked cached exchange mode.
• OneDrive: Without FSLogix profile containers, OneDrive for Business is not supported in non-
persistent RDSH or VDI environments. The OneDrive VDI support page will tell you how they
interact. For more information, see Use the sync client on virtual desktops.
• Additional folders: FSLogix provides the ability to extend user profiles to include additional
folders.
Azure Files integration with Azure Active
Directory Domain Service
• FSLogix profile containers' performance and features take
advantage of the cloud.
• Microsoft Azure Files now supports authentication with Azure
Active Directory Domain Service (Azure AD DS).
• By addressing both cost and administrative overhead, Azure Files
with Azure AD DS Authentication is a premium solution for user
profiles in the Azure Virtual Desktop service.
Best practices for Azure Virtual Desktop
Azure Virtual Desktop offers full control over size, type, and count of VMs that are
being used by customers.

To ensure your Azure Virtual Desktop environment follows best practices:

• Azure Files storage account must be in the same region as the session host VMs.
• Azure Files permissions should match permissions described in Requirements -
Profile Containers.
• Each host pool VM must be built of the same type and size VM based on the
same master image.
• Each host pool VM must be in the same resource group to aid management,
scaling and updating.
• For optimal performance, the storage solution and the FSLogix profile container
should be in the same data center location.
• The storage account containing the master image must be in the same region
and subscription where the VMs are being provisioned.

You might also like