Hi Everyone,

I don't know if I'm being dumb but I'm looking for a fail over solution for Remote Desktop services. I'm using Windows Server 2012 R2. I am aware of the Remote Desktop Connection Broker that gives you best of both world for load balancing and fail over to an extent and would love to use it but my problem is that we are using HP Thin Client which is very dumb and can't use WebApp. Now to use the RDCB in HA you will need to publish your collection as a WebApp.

DNS Round Robin doesn't do the trick as it takes to long to realize the server is down or unavailable and Network Load Balancing is very limited to load balancing and might over load a server. I have looked into Failover cluster but my knowledge is very limited with it and it doesn't seems to support the RDS roles for fail over.

How can I go about making my RDS servers highly available without using WebApps?

Thanks for the help in advance!

Hi Everyone,

I don't know if I'm being dumb but I'm looking for a fail over solution for Remote Desktop services. I'm using Windows Server 2012 R2. I am aware of the Remote Desktop Connection Broker that gives you best of both world for load balancing and fail over to an extent and would love to use it but my problem is that we are using HP Thin Client which is very dumb and can't use WebApp. Now to use the RDCB in HA you will need to publish your collection as a WebApp.

DNS Round Robin doesn't do the trick as it takes to long to realize the server is down or unavailable and Network Load Balancing is very limited to load balancing and might over load a server. I have looked into Failover cluster but my knowledge is very limited with it and it doesn't seems to support the RDS roles for fail over.

How can I go about making my RDS servers highly available without using WebApps?

Thanks for the help in advance!

• Merged by Amy Wang_Microsoft contingent staff, Moderator Monday, August 03, 2015 6:06 AM Duplicate

Hi,

I am aware of the Remote Desktop Connection Broker that gives you best of both world for load balancing and fail over to an extent and would love to use it but my problem is that we are using HP Thin Client which is very dumb and can't use WebApp Now to use the RDCB in HA you will need to publish your collection as a WebApp.

As far as I know, we dont have to deploy RD Web Access to be able to take advantages of RD Connection Broker, and we dont need to publish collection as RemoteApp.

Regarding fail over:

The Microsoft VDI solution supports highly available Hyper-V virtual machines. Setting up a failover cluster environment with multiple Hyper-V hosts will ensure that in the event of a hardware failure on a Hyper-V host, the virtual machines will fail over to another Hyper-V host and automatically start.

Quoted from this article below:

Microsoft VDI High Availability Deployment Options

http://blogs.msdn.com/b/rds/archive/2010/03/01/microsoft-vdi-high-availability-deployment-options.aspx

By the way, an active-active RD Connection Broker installation is supported now.

RD Connection Broker High Availability in Windows Server 2012

http://blogs.msdn.com/b/rds/archive/2012/06/27/rd-connection-broker-high-availability-in-windows-server-2012.aspx

Best Regards,

Amy

Thank you Amy, I will look in to the Connection broker without WebApp. Will mark this forum once I tested the solution.

Regards