My current RDS Collection deployment has the following deployment servers and their respective roles:
SERVER01 - RD Connection RD Broker, RD Session Host, RD Gateway, RD Web Access
RDSSQL01 - Connection Broker SQL
SERVER02 - RD Connection RD Broker, RD Session Host, RD Gateway, RD Web Access
RDSSQL02 - Connection Broker SQL
SERVER03 - RD Session Host
DC01 - Licensing
___________________________________________________________________________________
For third party application performance reasons, we have implemented quarterly reboots of the RDS Environment.
However, as the Gateway role is on the same server as the Session Hosts, (and there is no efficient way of draining a Gateway like you can the Session Hosts), we have to remove it from DNS and wait for the remote client DNS servers to update before we can reboot the server without impacting the customer.
This means our quarterly reboots can take days to complete (our product is 24/7 in production)
My question comes in the "information gathering" stage of the solution. I'm just trying to get thoughts on what more experienced RDS Admins think about moving the RD Gateway Role to the RDSSQL01 and RDSSQL02 servers, thus officially making them deployment servers which do not necessarily need to be rebooted.
The total solution is accommodates less than 100 remote clients, and the entire RDS Collection consists of Virtual Machines in Hyper-V.
Any and all thoughts are welcomed and greatly appreciated.
Thanks in advance.
Best Regards
-sMh-