Best Practices for FSLogix profile in multi OS environment

Hi Martin,

For FSLogix Profile Container:

• ProfileType = 0 (default): used for normal single-session scenarios.
• ProfileType = 3: required for concurrent or multiple connections.

When ProfileType = 3 is used, FSLogix enables concurrent access using VHD(x) differencing disks. One session has read-write access to the base VHD, while additional sessions attach in read-only mode using differencing disks.

Multiple connections (same user on different machines) are only supported with this differencing disk model. No other configuration is supported. You can read this information in this link: https://learn.microsoft.com/en-us/fslogix/reference-configuration-settings?tabs=profiles

For concurrent sessions on the same host (RDS), the following settings are also required:

• fDenyTSConnections = 0
• fSingleSessionPerUser = 0

ODFC containers use VHDAccessMode instead of ProfileType.

Reference for ProfileType setting:

https://learn.microsoft.com/en-us/fslogix/concepts-multi-concurrent-connections

One more important Microsoft note is OneDrive does not support multiple simultaneous connections using the same profile under any circumstance.

Hi Martin,

Yes, you can use the same FSLogix profile container path for Windows Server 2019 and Windows Server 2022, because FSLogix supports both OS versions and profile containers are designed to roam the user profile across devices/ sessions. Microsoft also notes that a profile container already includes the Microsoft 365 app data, so you do not need a separate ODFC container if the profile container is your main profile solution.

For simultaneous logon: by default, no - FSLogix keeps an exclusive lock on the container, so the same user cannot normally use the same profile at the same time on two different servers.

This typically does not cause profile corruption, but rather logon failures or container attach issues when the profile is already in use.

Concurrent usage is only supported if you explicitly configure FSLogix for multiple connections using VHDX differencing disks and the required settings. Otherwise, it is not supported. Also, OneDrive does not support multiple simultaneous connections to the same profile under any circumstances.

So the official recommendation is: using the same container across 2019/ 2022 is supported, but you should avoid simultaneous logons unless you have a properly configured multiple-connections design.

If this helps resolve your issue, feel free to mark the answer so others can benefit as well.

TV

FSLogix supports both Windows Server 2019 and Windows Server 2022, and profiles can roam between supported Windows versions. However, the context provided does not contain an explicit Microsoft statement that a single FSLogix profile container is supported and recommended for concurrent use across different OS versions and different Microsoft 365 app versions.

From the available information, only the following can be stated:

• FSLogix is supported on Windows Server 2019 and Windows Server 2022 and is designed to roam user data between remote computing session hosts and provide a consistent profile experience in virtual desktop environments.
• FSLogix profile containers are, by default, configured for single connections to a profile (ProfileType default is single connection). This reduces complexity and increases performance and is the recommended setting.
• When a profile is in use on another computer, FSLogix by default allows only one session to attach to that profile container. If a second session attempts to use the same profile, the user may receive a temporary profile unless configuration is changed (for example, enabling multiple or concurrent connections). This behavior is independent of OS version and is about concurrent access to the same profile.
• Microsoft documents that single connections reduce complexity and increase performance, and that multiple or concurrent connections are an optional configuration that organizations must evaluate based on their needs.

Based on this context:

1. Using the same profile path/container across different session hosts (for example, Server 2019 and Server 2022) is within the general FSLogix design of roaming profiles between hosts, but there is no explicit official recommendation in the provided material specifically addressing mixed-OS and mixed-Office-version sharing of a single profile.
2. Concurrent logons using the same FSLogix profile (same container) from two different hosts (regardless of OS version) are, by default, not allowed with a single-connection profile. Attempting this will typically result in a temporary profile or blocked sign-in, depending on configuration (for example, PreventLoginWithTempProfile and ProfileType).
3. The documentation emphasizes that single connections are recommended to reduce complexity and potential issues. It does not provide detailed guidance on the risk of profile corruption when sharing one profile across different OS and Office versions.
4. Official support boundaries require that issues be reproducible from a clean installation and that FSLogix is kept on the latest version. Complex configurations (such as multi-OS, multi-version Office, concurrent connections) fall into scenarios where Microsoft may recommend consulting Microsoft Consulting Services or partners.

Therefore, from the provided context only:

• It is supported to use FSLogix with both Windows Server 2019 and 2022, and to roam profiles between remote session hosts.
• Default and recommended configuration is a single connection per profile container (ProfileType default), which effectively prevents simultaneous use of the same profile from two different machines.
• Multiple or concurrent connections are possible but are an advanced configuration that each organization must evaluate; no explicit best-practice statement is given here for mixed OS and Office versions.

For an environment where users might connect to both Windows Server 2019 and 2022, and where different Microsoft 365 app versions are installed, the safest interpretation from this context is to:

• Keep ProfileType at its default single-connection setting to avoid concurrent access to the same profile.
• Avoid relying on simultaneous logon to both OS versions with the same FSLogix profile container.
• Ensure FSLogix is updated to the latest version and that the environment is designed and tested carefully if considering multi-OS or concurrent-connection scenarios.

References:

• What is FSLogix?
• Prerequisites
• Configure profile containers using FSLogix
• Configuration examples
• Troubleshooting issues with old, temporary, or local profiles
• FSLogix product support