How To Setup RD Web Access In Windows 2008 R2

RD Web Access allows you to publish applications through a web interface. To setup RD Web Access in Windows 2008 R2, you need to decide how many server you want to use for load balancing and if you are appending the RD Web Access servers to an existing Remote Desktop Services environment.

This tutorial guides you through the setup of RD Web Access in Windows 2008 R2, assuming that you require two load balanced RD Web Access servers, with an RD Connection Broker (load balancer). To setup RD Web Access in this configuration, you will require 3 Windows Server 2008 R2 servers.

Step By Step – How To Setup RD Web Access

To setup RD Web Access in Windows 2008 R2:

  1. Name, activate, allocate an IP address to and join each 2008 R2 Server to the domain
  2. Run Windows Update and reboot afterwards
  3. On the two RD Web Access Servers, install the Remote Desktop Services role, selecting the Remote Desktop Web Access and RD Session Host role services. You can also install Remote Desktop Session Host if you want users to be able to launch remote desktop connections through the RD Web Access interface instead of just published applications. You can also install the Remote Desktop Gateway if you want users to be able to access terminal services over the internet. This article will only be covering the publishing of remote desktop applications. Memory tells me that you also need the Web Server (IIS) role for RD Web Access, though I can’t be sure because my RD Web Access server already has the role installed
  4. You’ll need to setup the options for the RD Session Host role. I elected not to Require Network Level Authentication because some of the computers in my organisation are running older, non-Windows RDP clients. My licensing is Per User, but this will depend on the licenses that you bought. Next you will have to select which users can connect to the server via RDP. Best practice is to great an AD group for users with remote access, but I will simply be adding the Domain Users group so that all users on the domain have access. Next, select the tick boxes for the user experience. Ticking more boxes increases the traffic sent over the network, but can be overridden locally on the client.
  5. On the third server, install the Remote Desktop Services role with the RD Licensing (If you don’t have an RD Licensing Server – Not covered in this article) and RD Connection Broker role services. Again, I think the Web Server (IIS) role may be required
  6. Reboot the servers
  7. Login as an Administrator.
  8. Reboot the servers
  9. Next install the programs that you would like to publish
  10. Reboot if necessary
  11. On the RD Web Access servers, go to Start -> Administrative Tools -> Remote Desktop Services -> RemoteApp Manager
  12. In the RemoteApp Manager, you will see an overview of the RDS environment. If there are any red crosses or yellow triangles with exclamation marks in them, then these highlight issues with RDS that need to be addressed
  13. At the bottom of the RemoteApp Manager, right click the table of RemoteApp Programs, and click Add RemoteApp Programs
  14. Follow through the wizard to add a Remote App. Once you’ve done this, the program will be published. There are additional configuration options available, such as changing the name of the published application or restricting it to specific users or groups, which can be done by right clicking the application and going to the properties, but these are not covered in this article
  15. Next secure RD Web Access with an SSL certificate
  16. Start the Server Manager on each RD Web Access server (Or manage them all from one central Server Manager!)
  17. Click configuration -> Local Users and Groups -> Groups
  18. Add the group of computers that you wish to allow to run RemoteApps from to the TS Web Access Computersgroup. To allow all, add the Domain Computers group
  19. Add the Domain Administrators group to the TS Web Access Administrators group
  20. Under the Overview,
  21. Next we need to configure an RD Licensing Server to point to. To do this, go to Start -> Administrative Tools -> Remote Desktop Services -> Remote Desktop Session Host Configuration and click on RD Session Host Configuration: ServerName
  22. Under Licensing, right click Remote Desktop license servers and click Properties
  23. Click Add… to add an RD Licensing Server and add your RD Licensing Server…
  24. On the RD Web Access servers, go to Start -> Administrative Tools -> Remote Desktop Services -> Remote Desktop Web Access Configuration
  25. Log on using an administrative account
  26. Under Configuration, select One or more RemoteApp sources with the Source name set to localhost, click OK

Sorry, this article is incomplete. I don’t have time to write the rest of the guide, but hope that you find my article useful up to here.

If someone else wants to finish the guide in the comments section, I (and other readers) would be very grateful!

VN:F [1.9.22_1171]
Rating: 10.0/10 (1 vote cast)
How To Setup RD Web Access In Windows 2008 R2, 10.0 out of 10 based on 1 rating

2 thoughts on “How To Setup RD Web Access In Windows 2008 R2

  1. Am using RDWEB ACCESS. I had a doubt. Is RD web access need license? Please clarify..

    VA:F [1.9.22_1171]
    Rating: 0 (from 0 votes)
    • Yes, I believe that you need CAL licenses to access applications and desktops published in RD Web Access. Best thing to do is consult a Microsoft Licensing specialist, such as Insight.

      VN:F [1.9.22_1171]
      Rating: +1 (from 1 vote)

Leave a comment

Your email address will not be published. Required fields are marked *