Forum Discussion
WVD broker doesn't route to disconnected/existing session
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.
SpoilerSurprise: 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 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.
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!
- Thank you
This thread should be a bible for Microsoft, just going through the same with MS support now.
Issue occurred when the Azure AD accounts were deleted and re-synced. Now we get duplicate sessions. Hopefully an automated solution can be developed. - Thank's for that information.
I opened a ticket and they resolved the issue. Even if the support case said that they haven't found anything the problem is gone => there was a problem on the session broker side 100% sure..
Regards
Christoph - Thank you. It's possible that we are issuing the same problem during the switch from Azure AD sync from an old server to a new one.
I'll open a ticket wihtin Microsoft to get resolved this finally.
Thank you
