Forum Discussion

Steve_Downs's avatar
Steve_Downs
Icon for Microsoft rankMicrosoft
Mar 29, 2022

Announcing General Availability of FSLogix 2201 (2.9.8111.53415)

Today we are announcing the General Availability of FSLogix 2201. Updates include improvements to login and logoff times, cloud cache performance improvements, and 30+ accessibility updates. Downl...
Ryand32's avatar
Ryand32
Copper Contributor
Apr 08, 2022

kesslerseb I've asked Microsoft for a response on this a few months back and never received a response if this has been removed, the thing is this a requirement for alot of VDI deployments with Cloud Cache so until this is available in the admx template of the new version, I will stick with the older version. https://docs.microsoft.com/en-us/fslogix/whats-new#fslogix-apps-release-2004-29734930108

Steve_Downs's avatar
Steve_Downs
Icon for Microsoft rankMicrosoft
Apr 08, 2022
Ryand32 can you clarify why you need concurrent connections with Cloud Cache? The two things are not related and you're actually missing out on significant improvements to Cloud Cache by not upgrading - and exposing yourself to a security vulnerability that we patched in cloud cache.

Concurrent connections only apply to a niche scenario where a single user must be able to have multiple WINDOWS sessions simultaneously on the same session host. Most customers do not need or want the same customer to have multiple Windows sessions on the same VM. They might allow multiple Citrix or VMware sessions - but all those sessions, by default, share a single Windows session.

That said, we only removed the concurrent setting from FSLogix because the setting is already available as an RDS policy. If you wish to allow users to launch multiple sessions then you'll find the setting in "Computer Configuration > Administrative Templates > Windows Components > Remote Desktop Services > Remote Desktop Session Host > Connections". From there, set "Restrict Remote Desktop Services user to a single Remote Desktop Services session" to "Disabled".
  • mirtelo's avatar
    mirtelo
    Brass Contributor
    Apr 26, 2022
    Hi Steve, but there is a Problem in the new Release wich results in a BlackScreen at Login. I will try to explain it: We have a User, SoftwareAdmin. This User is Member of LocalAdmin Group and Member of FSLogix Profile Exclude List Group. This User generates a Sheduled Task at the System, this Task starts a Process at Systemstart in the Context of the User SoftwareAdmin. With the new Version in Place it is no longer possilbe to Logon with the User SoftwareAdmin.
    • Jason_Parker's avatar
      Jason_Parker
      Icon for Microsoft rankMicrosoft
      Apr 28, 2022
      mirtelo I am not sure I follow this sequence of events.
    • EvaSchwarz's avatar
      EvaSchwarz
      Copper Contributor
      Apr 27, 2022

      mirtelo kesslerseb
      That sounds to me like a topic that goes in the direction of "https://www.mycugc.org/blogs/mike-streetz/2022/03/23/fslogix-concurrentusersessions-controversy".

      • steveturnbull1975's avatar
        steveturnbull1975
        Brass Contributor
        Apr 27, 2022

        Steve_Downs The issue with leaving the local_username even exists with a basic avd image in azure with fslogix installed as we had the same issue today. Surely this issue needs to be fixed? The fslogix cache folder also leaves behind empty user profile folders most of the time at logoff. Do we have any eta on when these logoff issues will be resolved?

  • Ryand32's avatar
    Ryand32
    Copper Contributor
    Apr 08, 2022
    This should clear up this setting for all.
    https://www.mycugc.org/blogs/mike-streetz/2022/03/23/fslogix-concurrentusersessions-controversy