Forum Discussion
Solved
Unable to start more than 1 session per session host during normal business hours
We have a bit of a strange and frustrating issue going on. I am hoping someone else may have had this issue before. We have an open support ticket, but so far microsoft support has no solution for u...
- Hi, Really sounds like you need to open a ticket with Microsoft as from what you have described it all sounds like your set up correctly. Sorry I couldn't be anymore use, however id be interested to know what the fix ends up being.
The hostpool and all resources are in the the east region. I have no doubt a scaling script would work but it kind of defeats the purpose of having a pooled hostpool if I have have to add a new host for each user. The key here is outside of the hours from 8:00 AM to 5:00 pm WVD works as expected allowing many sessions per session host. It seems to me that some thing about the activity on our on prem network is causing some sort of authentication error or permissions error to happen. I have been unable to see any log errors or performance issues that would back up my theory or shed any light on the actual cause of the issue.
the reason I ask is because it almost sounds like a time zone issue if it allows multiples out of hours but not in hours. The scaling script i use to to say when in office hours keep X amount of seats available and then turns on and off resources to keep availability as close to X as possible, then out of hours X is a much lower figure to only have a small number of resource availble. Obviously power on connect is currently in preview and will help resolve that. Is your hostpool set to Pooled?
- the host pool is set to pooled. The logs / messages provided by wvd seem to indicate users start having some sort of authentication issue once there is one user per session host when we have most of our users connected to our network and working. I have seen multiple users create sessions on day's when we had a significant portion of our work force off during normal business ours due to an internal event. I believe the issue is some how related to the level of activity on our network.
- Hi, Really sounds like you need to open a ticket with Microsoft as from what you have described it all sounds like your set up correctly. Sorry I couldn't be anymore use, however id be interested to know what the fix ends up being.
- Thanks for your time and suggestions. I have had a ticket open with microsoft for a little over a week. I opened this conversation because so far they have not been able to help. Figured asking the community could not hurt. I have been able to get the ticket escalated, so hopefully we will have a resolution soon.