Windows Server 2012 - TSE - RemoteApp (on multiple servers through the broker)

Page 1 / 4
  • Published on : 03 September 2014 at 13:59 UTC
  • By Lionel Eppe

In an old tutorial, we have explained how to publish "RemoteApps" on Windows Server 2012 In summary, this technology allows you to run applications on a server and use them through a remote connection (RDP). This technology allows you to save money in your business because you will only need to purchase a high-performance server and guests can use computers with lower performance.
For more informations about this technology, please refer to the previous tutorial named "Windows Server 2012 - TSE - RemoteApp (on one server)".

In this tutorial, we will explain :

  • how to deploy this solution across multiple servers
  • how to distribute the load across multiple servers (through the broker)
  • use the user profile disks to allow users to access their documents through any "Remote Desktop Session Host" server.
  • add a "Remote Desktop Session Host" server when you need an additional server (to maintain acceptable performances)

For the rest of the configuration, you will be redirected to the end of the previous tutorial named "Windows Server 2012 - TSE - RemoteApp (on one server)".

Before you begin, here is the configuration we will use :

  • an Active Directory server. IP : 192.168.1.10
  • a broker server where we will install also the web access. The broker service can't be installed on a server where an Active Directory is installed. IP : 192.168.1.11
  • 2 TSE servers (Session Host Remote Desktop). You can use as many servers "Session Host Remote Desktop" as you want (if you buy the number of Windows Server licenses required). IP : 192.168.1.12 and 192.168.1.13
  1. Binding the server to Active Directory
  2. Install web access and service broker
  3. Install a "Remote Desktop Session Host" server (with at least one license manager)
  4. Deployment of the "Terminal Server" solution (RemoteApp)
  5. Adding a license server to the deployment
  6. Add a "Remote Desktop Session Host" Server to this "Terminal Server" solution
  7. Creating a shared folder for the configuration of the user profile disks
  8. Creating a collection and selecting "Remote Desktop Session Host" servers to use
  9. Publishing RemoteApp programs
  10. Testing and functioning of the user profile disks
  11. Activation of the license servers
  12. Securing servers with valid certificates
  13. Configuring Remote Connections of Windows (Work Resources)
  14. Previews of the final functioning

1. Binding the server to Active Directory

To deploy the Terminal Server solution, you must login with a user account of the domain.
To do this, you must link your server to your Active Directory server.

Notes :
- To install an Active Directory server, follow the tutorial "Windows Server 2012 - Creating an Active Directory".
- To link your server to your Active Directory, refer to point 3 of this same tutorial.

2. Install web access and service broker

To begin, we will install the "Access Remote Desktop Web" and "Service Broker for Remote Desktop connections" roles services.

To do this in the Server Manager, click "Add roles and features" and select "Application based on a role or a feature".

Select the broker server.

Select "Remote Desktop Services".

No special features.

Select "Access Remote Desktop Web" and "Service Broker for Remote Desktop connections" role services.

The broker service will distribute users on different servers "Session Host Remote Desktop."
Web access will allow users to choose the desired program.

Because we install the Web access, the server will install the IIS web server (if not already installed).

Leave these options to default.

Check the "Automatically restart ..." box and click "Install".

The broker service is installed.

3. Install a "Remote Desktop Session Host" server (with at least one license manager)

A "Remote Desktop Session Host" server is a server that will be used to run the "RemoteApp" applications used by clients.
It's on this or these servers that will have to install programs to publish.
Warning : If you are updating a published program on a server, you must also perform this update on other servers concerned by this "RemoteApp". Otherwise, it may cause problems someday.

In this tutorial, we will install a single "Remote Desktop Session Host" server and then we will install a second server after the deploy. So you know how to add a "Remote Desktop Session Host" server in the future.
To do this, select "Installation based on a role or a feature".

Note : Link your server to the Active Directory before installing roles on this server.

Select the concerned server. In our case, the tse01 server.

Select again : "Remote Desktop Services".

No special features.

Select "Remote Desktop Session Host ".
In a "Terminal Server" (or RemoteApp) deployment, you must have at least one license server. It's recommended to install two servers by distributing the licenses on these 2 servers to avoid blocking all users during a failure of the concerned server. To install the license server on this server, also select "Remote Desktop Licensing Manager".

Check the "Automatically restart ..." box and click "Install".

Services "Remote Desktop Session Host" and "Remote Desktop Licensing Manager" (if applicable) are installed.