FSlogix

Traditional Profile management

when user1 will login to VM user profile will store on the network share as files and folders.
Every time user add or read data it increase IO operations

FSlogix Solution


First time when user login to vm1 vhd will be created on network share

next time user login to different vm such as vm2 then vhd from network share will be mounted to vm2 itself

whenever user logout vhd will be detached and released to the storage

when vhd attach to vm2, vm2 will think it has locally attach disk

question

Even though vhd is stored on network share in remote location then how it is reducing latency and IOps

Answer

During mounting 50 iops will be required

once vhd attached it will be local to VM

Entire VHD will be presented to VM, any subsequent read/write will not travel to remote location

Fslogix containers

Fslogix has two types of containers:

Profile container (Documents/Desktop)
Office 365 container 

All cached data related to Microsoft products (Teams/Sharepoint/outlook/onedrive)



In some environment both profile and office container data is present in same folder under user profile folder.

Other environment profile data and office data present in separate folders.

How to configure FSlogix

To configure we need to have storage/share

  • On prem
  • Azure Premium File
  • Azure Netapp

Azure premium file provide minimum 100gb storage and Microsoft will encrypt customer data using platform managed key

Azure netapp file option provide minimum 4TB

Some customers such as banking donot want to trust Microsoft encryption, customer can use their own key called customer managed key to encrypt their data.

Note:

Whatever storage option you choose make sure VM and storage are in same region to avoid latency.

Storage Account

Storage account in Azure is a container to store all the data.

Storage container option:

Azure premium File
Azure netapp file

Create storage account

Location is very important storage account should be same where VM is located.

Important: We need to join storage account to Active Directory Domain Controller.

Why?

Users using AD credentials they have to authenticate to storage account to get their files and folders.