I have a 2012 R2 RemoteApp environment with the following servers:
Server1 - Session host, internal web gateway, connection broker (HA configured)
Server2 - Session host, internal web gateway, connection broker (HA configured)
Server3 - Session host
Server4 - External web gateway (published to web on port 443)
Server5 - External web gateway (one should always have redundancy right?)
Servers 1,2,3 are all in a single RDSH collection, lets call it RemoteApps. All apps work properly from the inside and outside through all connection methods from desktop RDC clients to web interface to iOS and Android devices. (this still seems like magic
to me)
Now let me introduce our new friend Server6. Server6 is just session host. It has been added to a new collection, lets call it AdminDesktop. Server6 has exactly the same programs installed as Servers 1,2,3 but is in a new collection so I can access the full
desktop remotely from my tablet when I travel. It is also there so I can isolate it and any work done on it will not effect the production sessions on Servers 1,2,3.
Server6 rarely gets attention. Most of my connections to the published AdminDesktop service are instead directed to one of the application session servers (1,2,3). Since they are all identical I have to check every time I connect to make sure I'm not on
a production server before I begin working.
The reverse situation never happens. If I launch an individual application I am always 100% of the time directed to one of the proper RemoteApps collection servers (1,2,3).
I have verified all servers are in the proper AD RDS groups, and my gateway policy has been setup (for testing purposes) to allow me to access any domain computer through the gateway.
How can I configure this so the AdminDesktop sessions will always go to Server6 in the AdminDesktop collection?