Forum Discussion
Fslogix (2.9.8308.44092)
Scherubini Problem is known officialy now:
https://learn.microsoft.com/en-us/fslogix/troubleshooting-known-issues#azure-ad-authentication-for-applications
Users may be required to authenticate to their applications (for example, Microsoft 365 apps, Teams (work or school), OneDrive, etc.) at every sign-in. The repeated authentication prompts are due to the virtual machines Azure AD device state. We recommend virtual machines are Azure AD Joined (AADJ) or Hybrid Azure AD Joined (HAADJ) for the best user experience.
Virtual machines, which are AADJ or HAADJ create the user's primary refresh token (PRT) at sign-in. Primary refresh token(s) created at sign-in will be used to authenticate to Azure AD based applications. Standard Domain Joined (DJ) virtual machines don't create a PRT at sign-in, instead rely on the Microsoft Azure AD broker plugin.
Azure AD broker directories and apps
Starting in FSLogix 2210 (2.9.8361.52326) and later versions, all content stored in following locations is no longer roamed as part of the user profile.
%USERPROFILE%\AppData\Local\Packages\Microsoft.AAD.BrokerPlugin_cw5n1h2txyewy
%USERPROFILE%\AppData\Local\Packages\Microsoft.Windows.CloudExperienceHost_cw5n1h2txyewy
%USERPROFILE%\AppData\Local\Microsoft\TokenBroker
- We have the same issue. RDS 2019 and FSLogix 2210 (2.9.8361.52326).
We are using the registry key mentioned in the article. Since we do not want multiple devices in Azure AD. Regkey below
"HKLM\SOFTWARE\Policies\Microsoft\Windows\WorkplaceJoin: "BlockAADWorkplaceJoin"=dword:00000001"
The way I see it is two options.
1. Keep this version and wait for a new version release that fixes the issue.
2. Roll back to a version below 2210 (2.9.8361.52326)- hello do you know if fslogix solved the problem?
- There is a 2210 hotfix 1 out on private preview. However if you want to address this problem I would recommend you to install version (2.9.8228.50276) for the time being
