Hi All,
I have been asked to build a terminal server so that members of my team (who mostly use Macs) may be able to get a virtual desktop to run windows based applications and gain access to restricted services. I have been doing quite a bit of reading and I would
like some expert opinions to make sure I've done things right before going forward this project.
All servers will be running virtually on ESXi 5.1 and the OS is Server 2008 R2.
Requirements:
- Ability to deliver desktops to users
- Ability to deliver applications to users via RemoteApp
- Ability to extend this design to incorporate a Session Host server farm (2-3 servers) in the future for business critical ERP applications.
- NICE TO HAVE: RD Web Access for application/desktop enumeration.
- NICE TO HAVE: Ability to add an RD Gateway at a later date
Design:
Client ----> RD Connection Broker ---> RD Session Host Host/RemoteApp/RDWeb ----> Licensing Server
Pretty simple eh? Basically, I'd like to have all clients connecting to an RD Connection Broker installed on it's own server. From here, that server will request licenses from the Licensing Server, also installed on it's own server. From there, requests can
be handed off to the Session Host server for virtual desktops/applications.
I would also like to have clients to be able to use RDWeb to enumerate resources but can't really afford to spend money on another server that will just host this (like it is in the Microsoft Architecture poster: Remote Desktop Services Component Architecture Poster) so I was thinking of installing it on the Session Host server. This this acceptable? Or does it really need to sit on it's own server.
As mentioned there will also be a need to installed 2-3 more Session Host servers (in a farm) that will host our Navision ERP system and deliver it to clients via RemoteApp. With this solution, I believe I will be able to leverage the existing Licensing/Connection Broker servers before finally sending the requests off to the Session Host servers. Can someone please confirm my reasoning is solid here?
Lastly, there is not yet a need to deliver desktops/applications through the Internet, but that may be required at a later date. Is it trivial to simply install the RD Gateway (or install it on the Connection Broker) and have everything work as it was before without major configuration changes or breaking anything?
I hope I have made sense. Please do not hesitate to ask questions if I have not covered everything.
Cheers!