Prevent Login With Failure and Citrix Published App not working

Alessandro Albertazzi 6 Reputation points

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

A set of solutions that enhance, enable, and simplify non-persistent Windows computing environments and may also be used to create more portable computing sessions when using physical devices.
406 questions
0 comments No comments
{count} vote

6 answers

Sort by: Most helpful
  1. Karlie Weng 8,736 Reputation points Microsoft Vendor

    Hello @ AlessandroAlbertazzi-0809

    What if you configure the following registry settings at the same time?


    Best Regards


    If the Answer is helpful, please click "Accept Answer" and upvote it.
    Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.

  2. Alessandro Albertazzi 6 Reputation points

    Same behavior with PreventLoginWithTempProfile activated. In fact, when a published application session is launched and the container is not available, a new local profile is created, not a temp profile (so the settings above is inapplicable) . When try to start a desktop session, the PreventLoginWithFailure work correctly.

    0 comments No comments

  3. Gisle 21 Reputation points

    I am also experiencing the same thing. Didnt understand why these settings didnt apply, but yes, its because they dont work with remote app session, only desktop sessions.
    If you are using fslogix with azure virtual desktop, you need to be cautious with deploying remote app shortcuts from different host pools, as the user would end up with a local profile if connecting to both at the same time.
    The same goes for the setting DeleteLocalProfileWhenVHDShouldApply, it didnt delete the local profile from a remote app connection, only from a desktop connection.

    0 comments No comments

  4. NBL 61 Reputation points

    anyone any update...?

    Seeing the same issue in Azure Virtual Desktop Environment

    0 comments No comments

  5. Garry Down 1 Reputation point

    Any update to this seeing the exact same issue

    0 comments No comments