As the title indicates...I'm curious about the capabilities of RDG. Here is my hypothetical situation:
Let's say I have an existing 2012 R2 RDS deployment (including Gateway) that is functioning as MS intends. Certificates are all in place, etc. etc. etc. Clients have no problem accessing RDSH sessions, RemoteApps, etc. The setup is essentially totally "vanilla". Life is good.
Now...I have a new system to put in place which relies on the RDS stack. The new system requires that a plugin be installed in Connection Broker which modifies default load balancing behavior. I would prefer to not install this into my current RDS stack that's working so beautifully. But I'd also rather not have to deploy a second RD Gateway, etc.
So, is there a *supported* way to utilize my existing RD Gateway to route incoming client sessions to both the existing RDS setup and a "new" RDS setup (presumably consisting only of RDSH servers, a connection broker and RD Web)? FWIW I have looked for docs from MS that speak to this but can't find any.