Lumenix
asked on
RDS Farm across two subnets
To put it simply I am curious if there are limitations with having RD Session hosts in the same collection across two subnets. I have added one to an existing farm but it throws an error and no remote users get directed to it.
Here is what we have going on. We have two datacenters, our HQ which is VLAN 800 (10.200.x.x) and our remote failover site on VLAN 806 (10.206.x.x). We have an RDS Collection that our remote users connect to, there are two blades in HQ and we are planning for two blades at the remote site for failover/load balancing. The problem is that when I add the RDS host server from the remote site to our RDS Collection in HQ I get an error (which I can ignore and it get added to the collection anyway) and no users are routed to that host.
Here is what we have going on. We have two datacenters, our HQ which is VLAN 800 (10.200.x.x) and our remote failover site on VLAN 806 (10.206.x.x). We have an RDS Collection that our remote users connect to, there are two blades in HQ and we are planning for two blades at the remote site for failover/load balancing. The problem is that when I add the RDS host server from the remote site to our RDS Collection in HQ I get an error (which I can ignore and it get added to the collection anyway) and no users are routed to that host.
David Johnson, CD
What you need to do is set up a proper fail over and be able to test it This entails having 2 of everything that is essential. With RDS cal's this will double your cost. As you will need 2 license servers and 2 rd-hosts.
ASKER
That's kind of what I figured. So having a live environment across two subnets isnt going to be possible then?
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
I see, so if I was going to setup HA over two subnets across a WAN link I will need to use two brokers, license servers etc? There doesn't seem to be alot of documentation on this particular setup for Server 2012 RDS
the pricey point is the item that detects if the local network is down and routes it to the offsite network.. or simply use your domain settings from the domain registrar to point to your network and then all you have to do is change the A record to point to the offsite network. (keep your ttl small like 1 hour) Personally I use cloudflare since domain registrars are usually terrible when it comes to domain management.
ASKER
Thanks, Ill obviously need to give this some more thought of course but thank you for your suggestions.