Using Terminal Server Proxy webapps with Round Robin DNS

Using Terminal Server Proxy webapps with Round Robin DNS

My Terminal Server Proxy webapp does not always connect to my backend server, when using the Round Robin DNS name. If we go directly to one of the relays, we can connect 100% of the time.



Assign individual DNS names to your relay IP addresses. 
relay1.example-cloud.com 
relay2.example-cloud.com 
etc... 

Add those DNS names to the Virtual Hosts section of the respective relay objects. 

Create your Terminal Server Proxy webapp and get it working. 
When editing the webapp object, make a note of the webapp DN. 
This is listed at the top of the properties page when editing the webapp object. 
It looks something like : cn=mywebapp,ou=WebApps,ou=webNetwork,o=stoneware 

Assign the link to your test account. Test the link and make sure it works properly. 

Assign this "rights" link to all users who will eventually have access to this webapp. 

Remove the visible option for the "rights" link so it does not show up on the users' menu. 

This link will act as a way to give users rights to the back end web server. 

Next, make a standard link. We are going to set the url to launch the application from a specific relay. 
This is done by using the webapplication's DN that you made a note of earlier. 
Set the URL for the standard link to https://relay1.example-cloud.com/StartWebApplication/cn=mywebapp,ou=WebApps,ou=webNetwork,o=stoneware. 

Set a restriction on the link to only be visible on that specific relay. 
Now assign this link to the appropriate users. 

Login to that relay and test, this should work just like the original "rights" link that you originally created. 

Now make as many separate links like the above, changing the relay DNS and restriction as needed. 

Common quesions 
1) What is the "rights" link for ? 

Answer :
All access to webapplications is granted to users via link objects.  If users do not have access to a link that is a webapplication type link then they will not have access to the back end server. 

2) Why does the "rights" link not need to be visible? 
Answer : Because it is just granting the user rights, all of the launching of the webapp is done with the standard links. 

We are investigating methods of automating this process in our code, so that this method isn't necessary.