Forum Discussion
Session count discrepancy
Hi,
We have a host pool with two sessions hosts. They are set to a maximum limit of 4 sessions each and depth-first.
A user with the same UPN and session number shows up twice in the session list. Azure was counting this as two separate sessions. Since there were two other users on, this added up to 4 sessions and new connections went over to the other host.
Looking at the Session Hosts view shows this machine has 3 active sessions rather than 4 so it does seem to know that one is duplicated.
Would anyone know what would cause the same user to show up as two different sessions? Thanks.
10 Replies
- There is a Group policy to limit users to single session. If you don’t set what can happen when there window closes and they reconnect it connects as a separate second session.
- Thanks Steven. A few months ago I asked about that specific GPO when we were first setting up the host pools with a Azure consulting firm (a leading Azure services firm) and they said it was not needed in WVD because the load balancer will tie session state into an individual pool allocation. I tested this with logging into a VM via rdweb, closing out the browser, verifying that I show up as disconnected in Azure, starting up the browser and logging into rdweb and the VM again. It connected me back to my previous session. In the list of users, it showed this one user as having the same session number (although listed twice) so I am wondering if this is an issue with Azure reporting it incorrectly or if there really was something up with the user being connected to a different session.
- Hi, I find found in my testing stage that without it it was a bit of a lottery as to how it responded and the gpo just makes it work as you want so for how difficult it is to enable I don’t see why you just would t do it rather leave it to chance. Like wise temp profiles are a lottery and they give you an option to not login with a temp which makes more sense from a service side to stop as when a user logs on with a temp it causes more damage long term than if they never get on.
