The Awingu 5.2.4 maintenance release is now available!

FSLogix is now included in your RDS license, and that is great for your users

Back in November 2018, Microsoft announced acquiring FSLogix. The acquisition should be seen within the context of the WVD launch, and as a continuous effort to improve the adoption of Office 365.

What issue does FSLogix solve? They write the following: “FSLogix is a next-generation application provisioning platform that reduces the amount of hardware, time, and labor required to support virtual desktops. We provide solutions for enterprises to easily and cost-effectively execute their strategic IT vision of the enterprise-class virtual workspace.”

In a 2017 webcast, they highlight FSLogix as being a leading provider in 4 domains:

      1. Office 365 containers
      2. Profile containers
      3. JAVA conflict management
      4. Application masking

In this article, we will give a high-level overview of user profile management techniques & solutions, and, we’ll zoom into FSLogix as a solution for Office 365 containers and Profile containers. We’ll also look into deploying FSLogix as part of an Awingu deployment.

User Profile Management: the basics

Microsoft writes: “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:

      1. An upgrade of the operating system
      2. A replacement of an existing Virtual Machine (VM)
      3. A user being part of a pooled (non-persistent) RDSH or VDI environment

Microsoft products operate with several technologies for remote user profiles, including these technologies:

      • Roaming user profiles (RUP)
      • User profile disks (UPD)
      • Enterprise state roaming (ESR)

UPD and RUP are the most widely used technologies for user profiles in Remote Desktop Session Host (RDSH) and Virtual Hard Disk (VHD) environments. […] Existing and legacy Microsoft solutions for user profiles came with various challenges. No previous solution handled all the user profile needs that come with an RDSH or VDI environment. For example, UPD cannot handle large OST files and RUP does not persist in modern settings.”

What is FSLogix?

Where classic solutions such as RUP & UDP run short, FSLogix steps in. It is designed to roam profiles in remote computing environments. “FSLogix 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.”*

For example: Without the use of tools such as FSLogix – it takes ages before your Outlook application is loaded. Technically, the moment when you want to start the application, your back-end system needs to upload and install your Offline OST file, profile, etc, and that tends to be a lot of data. FSLogix solves this, making this process much faster. This vastly improves customer experience and creates a gain in productivity.

Based on our analysis, we have composed a very simple pros and cons analysis for the adoption of FSLogix – basically, it only has pros.


  • Faster login and application load times
  • Easily added to existing environments
  • Office 365 data stored in VHD so no more need to fetch all data online which can take a long time
  • User profile always available when starting a session
  • User profile can be stored on a separate disk to reduce data on servers


  • Log out takes additional time when RW VHD is being merged
  • Changes made in profile (like saving a file in documents) on a session where only the READ disk is attached are lost
  • Multiple identical office 365 containers to make it work with outlook cached mode, where if one of these containers is not used for some time it needs to sync a lot of data again

Microsoft describes the benefits of FSLogix through these key drivers:

FSLogix is now part of your RDS license

And now the good news: Since March 2019 FSLogix is available for anyone with an RDS CAL or SAL at no extra cost.

This tweet from Microsoft RDS group manager Scott Manchester sums it up:

“Who will be entitled to #FSLogix?  Anyone with an RDS-CAL, RDS-SAL, VDA, or WVD entitlement. Use the full suite for on-prem or in the cloud. #WVD”

Basically, if you own or subscribe to anything on the following list, you’ll also be entitled to FSLogix:

      • Microsoft 365 E3/E5
      • Microsoft 365 A3/A5/Student Use Benefits
      • Microsoft 365 F1
      • 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) (SA not required)
      • Remote Desktop Services (RDS) Subscriber Access License (SAL)

For businesses that operate Office 365 or desktops in a server-based computing environment, this will translate to a significant improvement in User Experience, with opening times for Outlook reduced from minutes to seconds.

Given that this is still fairly new, admins need to request access to the FSLogix license specifically. Go to these pages (1 & 2) for the download information.

on July 1st 2019, Microsoft officially releases FSLogix as a Microsoft Product. Find out more about it here!


Leverage all FSLogix benefits within Awingu

FSLogix plays out completely in the back-end system. Meaning Awingu customers also enjoy the benefits. So if you are hosting Office 365 on non-persistent VDI’s or use RemoteApp, we recommend looking into adding the Microsoft FSLogix component as it can significantly improve the end-user experience.

Awingu 4.2 also supports RDP session merging

In version 4.2, Awingu introduces RDP session merging, meaning the ability to merge application session in the same RDP stream. This will work independently of using UPD or RUP as a profile management solution.

There won’t be any impact on the first application session open time. But as of the 2nd application, the Awingu platform will try to open this from within the same RDP stream. As a result, the user profile data does not need to be loaded as it’s already open from the first application. It will also result in lower CPU and memory usage.

In the back-end, this approach requires running multiple application in the same VM (otherwise, Awingu will not be able to merge the apps in the same RDP session). RDP session merge can be activated per application by the company admin (it is disabled by default). When activated, it also means that Awingu-based features such as ‘session sharing’, ‘session recording’ and ‘open in new tab’ will impact all applications running a session (and not just the one visible to the end-user).

The following picture gives a high-level view of the flows:

Want to find out more and see Awingu in action? Reach out to us!

Table of contents
Want to learn more about Awingu?
This website uses cookies. Read our transparent cookie policy!