Prevent Login With Failure and Citrix Published App not working

Alessandro Albertazzi 11 Reputation points
2021-02-19T13:21:53.55+00:00

When i try to open a published app with citrix virtual apps 1912 LTSR (based on OS Server 2019) if the profile container is inaccessibile the session is opened even if the preventloginwithfailure is activated.
If i try to open a desktop session instead of a published app on the same enviroment the preventlogin block the session correctly.

It's seems a different behavior between desktop session and published app session: any ideas?

FSLogix versione 2.9.7654

Windows for business | Windows Client for IT Pros | User experience | FSLogix
0 comments No comments
{count} votes

7 answers

Sort by: Most helpful
  1. Paul McGregor 0 Reputation points
    2023-05-26T01:14:13.54+00:00

    Any update anyone? I'm experiencing the same issue for Published apps in an RDS environment running FSLogix v2.9.8440.42104. This is leading to some major profile issues.

    0 comments No comments

  2. Jason Lucas 0 Reputation points
    2024-12-03T22:13:56.3266667+00:00

    I can confirm that this issue persists with FSLogix and RemoteApp for Azure Virtual Desktop. I am currently using FSLogix 2210 Hotfix 4 (version 2.9.8884.27471) on Windows 11 Enterprise multi-session. After contacting Microsoft, they acknowledged that they are aware of this issue. Below is the response I received from Microsoft.

    "If using Remote Apps with a FSLogix Profile in one Host Pool and then attempting to connect to another Host Pool with the same FSLogix Profile, that profile will not load and will result in a Temp Profile. In Azure Virtual Desktop, it is possible for a user to be assigned to multiple Host Pools with different Remote Apps. If the machines in both of those Host Pools are configured to the same profile file share in FSLogix, they will be using the same profile on both sessions. This is why the PreventLoginWithFailure and PreventLoginWithTempProfile registry settings will not work correctly: FSLogix uses frxshell.exe to replace the standard Windows shell.exe when configured to prevent a user's sign-in when their profile fails to attach or a temporary Windows profile. Users who use a remote application versus a full desktop experience won't be blocked from signing in. Remote applications don't call the standard Windows shell.exe and FSLogix is unable to hook to the direct application during sign-in.

    As for plans to address this issue, there hasn't been a specific announcement from Microsoft regarding a fix for FSLogix profile locking in RemoteApps. However, the FSLogix team is aware of various user concerns and continues to update the software. It's advisable to keep an eye on the official FSLogix documentation and community forums for any updates or workarounds that may emerge. I take this as feedback to discuss in the internal FSLogix triage meeting with the concerned team.

    https://techcommunity.microsoft.com/category/windows/blog/fslogix-blog"

    0 comments No comments

Your answer

Answers can be marked as Accepted Answers by the question author, which helps users to know the answer solved the author's problem.