Chapter 12: Implementing and Managing FSLogix

In this chapter, we take more of an in-depth look at FSLogix and the benefits associated with it. First, in Chapter 5, Implementing and Managing Storage for Azure Virtual Desktop, we covered some of the planning requirements for FSLogix and storage, and now we move on to the implementation and management of FSLogix.

FSLogix profile containers enable you to roam user data between computing session hosts. This allows you to remove the user's dependency on a specific device. The benefits of this include the fact that the user's sign-in times are minimized as they don't have to create a new profile with each logo, along with providing the flexibility of connecting to different business desktops/remote apps with the same user profile experience.

To summarize how FSLogix works, it uses both a filesystem driver and a registry filter driver, which handles any filesystem or registry requests that allow the user profiles to...

Installing and configuring FSLogix

The following conceptional architecture diagram shows how FSLogix works within the Windows operating system:

Figure 12.1 – Architecture diagram of FSLogix

The preceding architecture diagram shows how the FSLogix filter driver sits within an operating system and some of the services it redirects. The diagram depicts the redirection of user data using filter drivers to a remote storage solution.

Now, let's take a brief look at the license requirements for FSLogix profile containers.

License requirements for FSLogix profile containers

To use FSLogix profile containers, you must have one of the following licenses:

• Microsoft 365 E3/E5
• Microsoft 365 A3/A5/Student Use Benefits
• Microsoft 365 F1/F3
• Microsoft 365 Business
• Windows 10 Enterprise E3/E5
• Windows 10 Education A3/A5
• Windows 10 VDA per user
• Remote Desktop Services (RDS) Client Access License (CAL)
• RDS Subscriber Access...

Configuring antivirus exclusions

This section looks at the required antivirus file and process exclusions as are necessary for FSLogix. Even if you are using Microsoft Defender Antivirus, it is recommended that you configure the recommended exclusions.

The following table shows the files, processes, and Cloud Cache file exclusions you should configure in your Azure Virtual Desktop environment:

Configuring exclusions using PowerShell

The following script can be used to configure your template image with the required exclusions for FSLogix profile containers. You will note that this particular script is for Microsoft Defender. The script essentially adds exclusions for the profile container virtual disks, both VHD and VHDX:

# A140 FSLOGIX AV Exc 
#Defender Exclusions for FSLogix
  $Cloudcache = $false             # Ensure you Set for true if using cloud cache
  ...

Configuring Cloud Cache

Cloud Cache is a technology (a part of FSLogix) that enables you to use multiple remote locations continually updated during the user session. One of the use cases for Cloud Cache is disaster recovery and business continuity as it provides real-time, active-active redundancy for a profile container.

If the main or a storage provider becomes unavailable, Cloud Cache will continue to function/operate with the other storage providers. If an unavailable storage provider becomes available within the user session, it will be updated with the local cache. If the provider does not become available until after the user has signed out of their session, then the storage provider will be updated during the next session.

Important Note

When using Cloud Cache, all profile data writes go through the local cache first, and then the remote storage locations.

It is important to note that configuring Cloud Cache differs from configuring the typical FSLogix profile...

Microsoft Teams exclusions

Microsoft Teams has a caching folder that can cause bloat on your user profile disk. The following details show how you can set an exclusion using an XML file to prevent both the media stack folder and meeting-addin\Cache from being stored in the profile container.

You first need to create an XML file with the required exclusions; you can do this using notepad.exe or another text editing tool. You then enter the required exclusions:

• media-stack folder
• meeting-addin\Cache (%appdata%\Microsoft\Teams\meeting-addin\Cache)

The XML file should look something like the following example:

?xml version="1.0" encoding="UTF-8"?>
<FrxProfileFolderRedirection ExcludeCommonFolders="0">
<Excludes>
<Exclude Copy="0">AppData\Roaming\Microsoft\Teams\media-stack</Exclude>
<Exclude Copy="0">AppData\Roaming\Microsoft\Teams\meeting-addin\Cache</Exclude>
</Excludes...

FSLogix profile container best practices

This short section details the best practices for enterprises. There are a few settings you can apply to your FSLogix deployment to improve management and the cleanup of profiles.

The following table shows some of the best practice settings when configuring FSLogix profile containers within an enterprise:

In this section, we briefly took a look at some of the best practices/recommended configurations you should apply when configuring FSLogix profile containers.

Summary

In this chapter, we ran through the implementation of FSLogix profile containers and Cloud Cache. First, we started with the basics of installing the software on a session host and the configuration of antivirus exclusions, and then we moved on to what is required to set up profile containers. We then discussed the need to remove the profile containers' VHDLocation path when configuring Cloud Cache and some of your other options. We then took a look at creating profile exclusions for Microsoft Teams and finished off the chapter by looking at a few enterprise best practices you can configure for FSLogix.

In the next chapter, we will take a look at configuring user experience settings. We will talk about Universal Print, group policy configurations, and troubleshooting both user profile issues and Azure Virtual Desktop clients.

Questions

1. What are the maximum concurrent handles you can have in Azure Files?
2. When configuring the storage path for FSLogix Cloud Cache, what is the correct value for the storage location?
3. What is the reason for configuring Microsoft Teams exclusions for FSLogix profile containers?
4. What do you need to do before you can start configuring and using FSLogix profile containers?

Answers

1. 2,000 handles.
2. CCDLocations.
3. Microsoft Teams has a caching folder that can cause bloat on your user profile disk.
4. Ensure that you download and install FSLogix Apps. Remember that if you are using a Microsoft gallery image, this is usually installed as part of the image. Always check beforehand.