Detecting when a RDS Session Host does not reconnect to the broker
Hello all,
We have recently migrated to Azure and have found that powering off one of our two session hosts during off-peak hours has significantly reduced our costs. The process is automated and works well. All servers in the RDS farm are Server 2012 R2.
The issue is that every few weeks or so, the host that was powered off will boot up and come back online at its specified time, however, it for some reason will not accept new connections. We then very quickly max out the capacity of the first host and new connections to the RDS farm are dropped.
When this happens, the broker shows that the server is connected and does not seem to report any issues. That being said, the broker shows the server is connected even after it has been powered off for ~8 hours so we can't really rely on that. Using Get-RDSSessionHost to try and detect when the server is having issues is of no help as it always shows connected.
The solution is to reboot the host and on the next reboot it starts accepting connections and the issue is resolved. The problem is that we need a way to detect this issue before it gets to the point where users are not able to connect. So we are looking for a way to monitor this and alert when users are not able to connect to the second host. Hoping someone here has some ideas on how to go about this.
Thanks!
We have recently migrated to Azure and have found that powering off one of our two session hosts during off-peak hours has significantly reduced our costs. The process is automated and works well. All servers in the RDS farm are Server 2012 R2.
The issue is that every few weeks or so, the host that was powered off will boot up and come back online at its specified time, however, it for some reason will not accept new connections. We then very quickly max out the capacity of the first host and new connections to the RDS farm are dropped.
When this happens, the broker shows that the server is connected and does not seem to report any issues. That being said, the broker shows the server is connected even after it has been powered off for ~8 hours so we can't really rely on that. Using Get-RDSSessionHost to try and detect when the server is having issues is of no help as it always shows connected.
The solution is to reboot the host and on the next reboot it starts accepting connections and the issue is resolved. The problem is that we need a way to detect this issue before it gets to the point where users are not able to connect. So we are looking for a way to monitor this and alert when users are not able to connect to the second host. Hoping someone here has some ideas on how to go about this.
Thanks!
Philip Elder
Are you able to script a direct log on and log off of the session host that is shut down (thinking off the top).
This question needs an answer!
Become an EE member today
7 DAY FREE TRIALMembers can start a 7-Day Free trial then enjoy unlimited access to the platform.
View membership options
or
Learn why we charge membership fees
We get it - no one likes a content blocker. Take one extra minute and find out why we block content.