Enabling and Licensing RDS
- Once installed, open the Remote Desktop Licensing Manager
- In this application, you will need to activate your server and install the RDS Licensing.
Note: The Leostream HTML5 Viewer counts as a single device under Device CAL. The HTML5 Viewer can support ~75 concurrent HTML5 sessions
Now that you have a licensed RDS server, it's time to integrate it with Leostream.
- The first step is to install the Leostream Agent (https://license.leostream.com/download.html) on the RDS server. For instructions on Leostream Agent installation, please see our Installation Guide
- In the Connection Broker, you should be able to find the imported RDS Server in Resources > Desktops. If you are having trouble, please use the System > Log to see if you can find a recent "Imported" message
- Next, navigate to Setup > Centers and add a new "Remote Desktop Services/Multi-User" center. In this form, you can name the Center, select the RDS server, and specify how many concurrent sessions that server can support
Note: There is no inherit limit for the amount of concurrent sessions allowed, but this should be based on the server hardware capacity. In addition, if you're using the HTML5 viewer, please consider the ~75 concurrent user limit
After the Center is created, you'll notice that the original RDS server desktop record is marked "Unavailable" and new desktops are created to match the number of sessions you've defined:
These can be treated like any other desktop object, and you can hard-assign or pool-assign these machines based on your preferred method.
The last part of the configuration, aside from the policy + pool assignments, is to define the protocol plan that will allow for RemoteApp streaming. In this example, I will use "Paint" as the remote application.
HTML5 RDP with RemoteApp:When defining the RemoteApp, it's crucial to prefix the alias on the RemoteApp with "||"
Native RDP with RemoteApp:When defining the RemoteApp, it's crucial to prefix the alias on the RemoteApp with "||". The two highlighted parameters are the only required ones to stream the RemoteApp.
Once you have your sessions and an appropriate protocol plan, you can now setup your policy and pool assignments to stream applications to your end users: