Good Morning Guys -
After setting up a 2012 R2 server for RemoteApp a few weeks ago, we are now adding 2-4 additional ones. The only thing we use RemoteApp for is publishing individual applications - not desktops - which users are accessing via the web interface or by adding the URL to Windows 7 as a RemoteApp URL connection. The goal of these multiple servers is not only to act as a fail over, but for load balancing, too. The published apps will only be accessible on the LAN - not over the internet.
When researching the best way to configure this, I've found a few contradicting methods. Also, most seem to be for setting the broker up for virtual desktops and not just published apps. Below is how I currently have things configured after trying a few things. Many of the posts I've also seen involve the Gateway Manager, but don't know why I need to use it if sessions wil only be used locally.
Current Configuration
Server01
- Server configured for RemoteApp weeks ago which has ~15 published apps in single collection
- Created a "Server Group" in Dashboard which includes 01 and 02 server
- Holds RD Session Host Role
- Holds Web Access Role and can browse and use it, but isn't listed under "Deployment Servers"
- Certificate added which is signed from our domain's CA
Server02
- Newly built RemoteApp Server which currently only has default "Quick Start" published collection
- Created a "Server Group" in Dashboard which includes 01 and 02 server
- Holds RD Connection Broker, Session Host, and Web Access Roles
- Certificate added which is signed from our domain's CA
If you could advise on what steps I need to take to get this going and/or point me in the right direction, I'd appreciate it very much! I'll be happy to submit any additional information if needed.
Thanks!
Ben K.