Forum Discussion

Pylsa's avatar
Pylsa
Copper Contributor
Jun 25, 2020
Solved

WVD broker doesn't route to disconnected/existing session

We have a farm set up with about 13 WVD session hosts based on Windows 10 2004 Multi-session. We use FSLogix on Azure File Shares to store user profiles.   Whenever a user wants to reconnect to his...
  • Pylsa's avatar
    Pylsa
    Sep 08, 2021

    Chris1989 tapandewanjee19 Daniel Cairns 

     

    Apologies everyone, I have not been actively monitoring this question! My bad!

    In the end, we ended up creating a ticket with Microsoft and then escalating it further and further with our own (deep-dive) technical findings. We ended up being connected to the actual dev team for AVD (then WVD) and they found the error for us.

     

    Spoiler
    Surprise: It was in the AVD back end.

    What ended up being the case was that we had previously synchronised on-prem users to AAD and used AVD with those users. We then deleted everything from AAD to start afresh with the Azure/O365 side of things as there was a lot of polution. We then synchronised the on-prem users back to AAD which created new user objects for all of them with the same UPN as before but with a new SID on AAD.

     

    Because the SID changed for these users. the Microsoft-managed broker service thought these users were actually different users from the one we had created initially and then made two "slots" available for these users in the brokering service.

     

    However, FSLogix (and lots of other services) use the UPN for reference so everything windows-based in our AVD environment went wrong when two users with the same UPN were logged on.

     

    The product team manually removed the duplicate entries for us in the back end and that resolved all of our issues. We have now successfully rolled out and are successfully using and managing AVD for multiple (large) clients and we have been ever since this issue.

     

    Again, apologies for the late solution but I hope this helps someone else!

Chris1989's avatar
Chris1989
Copper Contributor
Aug 18, 2020
Spoiler
Same Problem

Helo,

 

same Probleme here since 2019. Never find a solution!!
I opened a ticket last year and Microsoft did some changes into my Azure Agent Token.

Our 8 vm's weren't shown via system management powerShell as online. Just one of them appearing randomly. But they all must be shown as in the picture:

Get-RdsSessionHost -Tenant "name" -Hostpool "pool" | ft SessionHostName, AssignedUser, HostPoolName, AllowNewSession, Sessions, LastHeartbeat, AgentVersion, Status, UpdateState, LastUpdateTime, UpdateErrorMessage

This Problem has been fixed. Since this we are sometimes! able to reconnect existing session.

I think we are able to reconnect a closed session when the MS WVD Client APP is closed via "X".
But most users aren't able to reconnect after a user's client device dies, goes to sleep, or loses connection otherwise and the user the tries to reconnect.

 
 

We are using FSLogix with an SMB share on a classic Windows File Server. Multi Session is denied. We wan't the users to get his same session always.


Any update on this ?

Regards


Resources