FSLogix Profile's disconnect during clustered file server failover

AGarA 21 Reputation points
2021-05-28T18:41:35.84+00:00

We are currently using FSLogix as a user profile solution. We save our profile disks to a DFS path (\ADdomain.com\FSlogixProfiles). That DFS path points to a Microsoft Continuously Available File Server running Server 2012r2.

If we migrate the file server role from one host to another - Our VDI desktops all crash and the profile becomes disconnected. Then the users cannot get back in because the systems are all locked.

All of our other applications handle a failover without an issue. Windows 10 & SMB3 allows this failover to be transparent to the users and has never caused any issues with other applications accessing shares on this cluster.

So why is FSLogix not able to?

We have the re-attach settings as follows:
* Re-AttachIntervalSeconds = 5
* ReAttachRetryCount = 30

Anyone else see this behavior? Or have any suggestions to keep this from happening?

FSLogix
FSLogix
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.
475 questions
0 comments
Accepted answer
  1. Andy YOU 3,071 Reputation points
    2021-05-31T14:24:46.373+00:00

    HI AGarA-2861,

    1.Do you use Multiple SMB Locations with Multiple VHD Paths in your current envrionment?
    Multiple SMB Locations with Multiple VHD Paths
    https://jkindon.com/2019/08/26/architecting-for-fslogix-containers-high-availability/

    2.When the disconnect issue happen, we can try to capture the fslogix log of user's fail logon

    On the problematical rdsh, download the support tool from
    https://aka.ms/fslogix_support_tool
    1).Run the FSLogix Support Tool.
    2).Fill in the company name (we use this to separate the information from others).
    3).click "enable logging" and Select "Gather Rule files", and "Gather Dump Files".
    4).Click "Gather FSLogix Content" ( Please note: this will take several minutes)
    5).Once complete, please locate the resulting zip file from C:\ProgramData\FSLogix\Support and attach it to your support ticket.

    95869-16.png

    ============================================
    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.

1 additional answer

Sort by: Most helpful
Most helpful Newest Oldest
  1. François Rabinowicz 1 Reputation point
    2021-05-31T20:03:53.56+00:00

    Hi,

    We were with Microsoft Scale Out Files servers and Cloud Cache on 3 locations for more than a year and had some many issues that FSLogix couldn't fix.
    We recently learn from FSlogix support that they have an issue with Cluster and to use direct server name instead. It was not possible as disk could change inside the cluster anytime that we reboot a node.

    We have move away from Clustering and are using dedicated servers with Cloud Cache on 3 locations and almost all our issues are now gone.

    I would recommend to stop using Cluster.