Fslogix: is a type of user profile solution which enhance and enables a consistent experience for windows user profiles in virtual desktop computing environment. Fslogix is not limited to virtual desktop environments and could be used on physical desktop where a more portable user experience is desired.

Fslogix Function:

1. Roam user data.

2. Minimize sign in times for virtual desktop environments.

3. Optimize file I/O (input/Output)

4. Provide a local profile experience.

5. Simplify the managements of applications and Gold images.

Why we use Fslogix.

1. Filter driver masks the folder where the VHD is mounted.

2. Behaves as if its locally-mounted, avoiding the problems introduced by using junction points.

3. Enables use of Teams and OneDrive.

4. Fslogix containers supports concurrent sessions.

5. RDS Client access license (CALs)

6. RDS subscriber Access License (SAL)

7. Azure virtual desktop per-user license.

FSLOGIX Supported OS: Supports all MS supported a partially system

1. Windows 11 single or multi session.

1. Windows server license (2016,2019,2022,2025)

Types of containers: Fslogix has two primary containers:

1. Profile container: A profile container is all the data related to a user's profile which is directly stored in the VHD(X).
   i) It’s a full remote profile solution for non-persistent environment.
   ii) Redirects the entire user profile to the remote location.
   iii) Its configuration defines how and where the profile is re-directed.
   iv) The entire profile except redirection.XML is included in the profile container.
   v) Profile container includes all the benefits of the Office container.
   vi) Profile container VHD will contain the entire windows profile for the user except for:
       a) The temp folder location.
       b) The IE Crash folder location.
   
   Note: Exclusions are done with a "redirection.xml" file.

2. ODFC Container: An ODFC container type which is focused on storing profile content that is unique to Microsoft Office applications:
   
   i) It redirects only area of the profile that are specific to Microsoft Office.
   ii) A default ODFC container includes:
   Office activation, outlook, outlook personalization, SharePoint, OneDrive, Skype for Business (legacy support)

• ODFC containers are an optional configuration.

• ODFC container is not backed up or replicated to alternate location since the data is recoverable from the source.

Agent components of FSLOGIX:

1. FRX.exe - it is the command line utility. Installed to C>program files>Fslogix>apps
   
     

Services:

1. FRXSVC.exe: Service that communicates with the command line tool, the drivers and monitor the rule folder for changes.

2. FXRCCDS.exe: Service responsible for handling cloud cache operations.

Drivers:

1. FRXDRV.sys: this driver is responsible for handling file system and registry request to make hiding and redirection work.

2. FRXDRVVT.sys: This driver provides the advanced redirection capabilities for profile on ODFC containers.

3. FRXCCD.sys: responsible for handling cloud cache.
     

Prerequisites for FSLOGIX:

1. Supported OS (Windows 11, WS 2016, 2019, 2022, 2025)

2. Eligible licenses (E3/E5, A3/A5, F1)

3. User should have access to the storage provider
   \\{server-name}contoso.com\{share-name}
   \\{RDCB.contoso.com\fileshare. Or
   \\{storage-account-name}.File.core.windows.net\{sharename}

4. Configure anti-virus exclusion (av=anti-virus)

Note: Anti-virus products are known to conflict with Fslogix containers and requires that specific files and folders are excluded from any type of scanning.

• The VHD(X) can be located on the local drive or on a network drive.

FSLOGIX installation path:

C > Program files > Fslogix > apps

Cloud cache:

1. Used for high availability environment.

2. Location: registry/policy: CCDlocation

Path: HKLM > SOFTWARE >FSLOGIX > Profile (For Profile)

HKLM > SOFTWARE > Policies > FSLOGIX > ODFC  (for ODFC )

CCDLocation and VHD location must not be present at the same time.

• Cloud cache: is a feature that works with profile and ODFC containers to provide resiliency and high availability.

FSLOGIX logs

C > Program data > Fslogix > logs

Common log files in Fslogix:

By default logging is enabled for all log files.

Logging configuration (how many days to keep the logs etc)

HKLM > SOFTWARE > Fslogix > logging

Profile Container related logs:

Directory: %programdata%\fslogix\logs\profile

For ODFC container:

Path: %Programdata%\Fslogix\logs\ODFC

Rule Compilation

%Program%\fslogix\logs\rulecompilation

Fslogix Service logs:

%programdata%\fslogix\logs\service

How to install and configure Fslogix:

• Download the latest version

• Extract the files

• Move the .admx file to C > Windows > Policydefinitions

• Move the .adml file to C > Windows > policydefinition > En-US

# We move both these files so that Fslogix can appear in Gpedit.msc  (both these files are template)

Note: After FSLogix is installed 4 user groups are created:

1. Fslogix ODFC exclude list

2. Fslogix include list

3. Fslogix Profile Exclude list (add domain administrator using lusrmgr.msc)

4. Fslogix Profile Include list

Profile Type:

Type= Dword

Default value = 0

1. 0 : Normal profile behavior

2. 1: Machine should only be the RW profile instance

3. 2: Machine should only be the RO profile instance

4. 3: Machine should try to take the RW role and if it can't, it should fall back to a RO role.

VHDX Disk Compaction: VHD disk compaction is a process that runs every time a user signs out. The compaction process is designed to automatically decrease the amount of storage a user's container, depending on a predefined threshold. VHD disk compaction is enabled by default.

Disk compaction dependency:

VHD  disk compaction process depends on the optimize drivers service ( Defragsvc)

Requirement for Disk compaction:

1. Drivers should be dynamically expandable (VHDX)

2. Disk compaction should be enabled (it is enabled by default)

3. Disk defragment should not be disabled.

4. Size of the container must be greater than 1gb for disk compaction to run.

A-B=c

If C >= (A x 0.2), compaction runs

If C < (A x 0.2 ), compaction doesn't run

FSLOGIX Workflow/Connection flow.

1. User logs in to the Windows Machine with Fslogix installed and configured.

2. Fslogix agents reads through the Fslogix configuration and checks VHD location.

3. If the user has correct permission (read/write), the VHD(X) is dynamically attached/mounted to the machine.

4. The user profile is immediately available and appears in the system and behaves like a local profile.

5. After user logs off, the VHD is detached/unmounted gracefully and ready to be attached the next time user logs in.

On-Premise:

1. On supported windows machine install Fslogix apps.

2. Fslogix,m it can be configured in two ways:
   i) GPO
   ii) Registry

3. If using GPO to configure Fslogix, we need to add the Fslogix.admx and Fslogix.adml files to %sysvol%\policydefinition and %sysvol%\policydefinition\en-us respectively
   This will add the policy template to the local group policy.

4. Create a file share and share with the users (allow read\write)

5. Configure below GPOs: Enabled: set to enabled and select Enabled.
   * VHD Location: Set to Enabled and specify the path of the file share (eg: \\fileserver.domain.com\fileshare)

6. Set optional GPO such as:
   i) Delete local profile when VHD should apply
   ii) Volume type
   iii) Prevent login with temp profile
   iv) Prevent login with failure
   v) Size in MB

7. Ensure that the user is member of the "FSLOGIX profile include group" in the local user groups (by default everyone is added)
   i) It is recommended to add the administrators to the "FSLOGIX profile Exclude group" for troubleshooting purpose.

8. Login to the configured windows machine using the account added to the FSLOGIX include group.

9. User should have Fslogix profile created and loaded.

FSLOGIX Deployment (AVD Entra- joined)

1. On the session host, install the Fslogix app using Fslogix app setup.

2. Fslogix can be configured in two ways, GPO and registry.

3. If using GPO to configure Fslogix, we need to add the Fslogix.admx and Fslogix.adml files to %sysvol%\policydefinition and %sysvol%\policydefinition\en-us respectively.

4. Create a storage account and a file share within the storage account
   - Using access control fomr the file share assign below Rbac role to the user:
   -Role: SME share contributor

5. Configure below GPO (required):
   - Enabled: set to Enabled and select Enabled.
   -VHD location: et to enabled and specify the path of the file share (eg: \\stroage account name.file.core.windows.net\fileshare

6. -Set option GPO such as:
   - Delete local profile when VHD should apply
   -Volume type
   - Prevent login with temp profile
   - Prevent login with failure
   - Size in MB

7. Ensure that the user is a member of the "FSLOGIX profile include group" In the local user group (by default everyone is added)"
   - It is recommended to add the administrator to the "FSLOGIX profile exclude group" for troubleshooting purpose.

8. Login to the AVD using the Windows app.

9. Users should have FSLOGIX profile created and loaded.

Cleanup Invalid Sessions

 HKLM > SOFTWARE > FSLOGIX > APPS

Dword > cleanupInvalidSessions

Enabled value=1

Disabled value= 0 (default)

When cleanup invalid session is configured FSLOGIX attempts to clean up the invalid session (The VHD(X) mounted for the user profile isn't properly detached) and allow a successful sign-in when the user sign-in next time.