Forum Discussion

ryanquiggin's avatar
ryanquiggin
Copper Contributor
Oct 09, 2019
Solved

User's logged off when they disconnect their session

Our enviroment consists of the following;

 

2 x WVD Session hosts (Windows 10)

Profiles stored on a file server in Azure and accessed from the session hosts via FXlogix

 

User's report that when they dissconnect from their session they would normally expect to be reconnected to the same session with all of their work / apps still open. This is not so much an issue for users in the office, but more for remote workers with unreliable internet connections, as when they are dissconnected even for a short period, they will be logged off their session and put onto a new one. We have not have this issue in the past with Citrix or RDS.

 

Does anyone have any ideas?

  • David Brophy's avatar
    David Brophy
    Brass Contributor
    Oct 30, 2019

    ryanquiggin I'm actually having the exact same issue in testing. Did you ever get it fixed?

    What's happening for me is that if a user disconnects their session stays logged in in a disconnected state as you can see in task manager. But when they log back in you can see in the fslogix operational log that fslogix unloads the profile and then loads it again.

    • ryanquiggin's avatar
      ryanquiggin
      Copper Contributor
      Oct 30, 2019

      David Brophy In the end, I created a new VM image from scratch using the Windows 10 Multisession +Office 365 apps built into the WVD deployment template. This resolved the issue. I think previously I used the Windows 10 Multisession image without the 365 apps and thats what gave me issues.

      • David Brophy's avatar
        David Brophy
        Brass Contributor
        Oct 30, 2019

        ryanquiggin I figured it out. I was following the article described at https://docs.microsoft.com/en-us/azure/virtual-desktop/set-up-customize-master-image#software-preparation-and-installation which references the below registry entries. I deleted them from my VM and all good now. I'd imagine it was the RemoteAppLogoffTimeLimit set to 0.

         

        reg add "HKLM\SOFTWARE\Policies\Microsoft\Windows NT\Terminal Services" /v RemoteAppLogoffTimeLimit /t REG_DWORD /d 0 /f
        reg add "HKLM\SOFTWARE\Policies\Microsoft\Windows NT\Terminal Services" /v fResetBroken /t REG_DWORD /d 1 /f
        reg add "HKLM\SOFTWARE\Policies\Microsoft\Windows NT\Terminal Services" /v MaxConnectionTime /t REG_DWORD /d 10800000 /f
        reg add "HKLM\SOFTWARE\Policies\Microsoft\Windows NT\Terminal Services" /v RemoteAppLogoffTimeLimit /t REG_DWORD /d 0 /f
        reg add "HKLM\SOFTWARE\Policies\Microsoft\Windows NT\Terminal Services" /v MaxDisconnectionTime /t REG_DWORD /d 5000 /f
        reg add "HKLM\SOFTWARE\Policies\Microsoft\Windows NT\Terminal Services" /v MaxIdleTime /t REG_DWORD /d 10800000 /f

Resources