RDWeb Administrator Guide
RDWeb Administrator Guide
A Comprehensive Guide for Resolving Issues with RDweb Applications
Introduction
Welcome to RDWeb Administrator’s guide. This guide is designed to assist technical support in identifying and resolving various issues that may arise with the RDWeb applications.
Contents
Introduction ........................................................................................................................... 1
RDWeb Servers ...................................................................................................................... 1
Setting a user up with access to RD Web Applications ............................................................. 2
Helping a user whose apps won’t load .................................................................................... 3
RDWeb Servers
There are many RDWeb servers, but for the sake of support we are only interested in the RDWeb Broker and RDS Host servers.
The servers are allocated as such:
•
Brokers
o
“GB-P-RDCB01”, “GB-P-RDCB02”
▪
These servers are the target of RD shortcuts and depending on requested application, act as load balancers and routers.
•
RDS Host servers
o
“GB-P-RDSH01, 2 3 4 5 6”
▪
The host servers have the applications installed and so it is worth noting that not all hosts have the same applications.
▪
The reason we have say Sentinel on hosts 1 and 2 but not the rest as that hosts 1 and 2 live in Birmingham right next to the databases.
▪
The same is true for the rest hosting Dymension and Protean up in Bradford to be near those databases.
Setting a user up with access to RD Web Applications
Until Intune can automatically connect someone to work resources, when they log into a laptop for the first time, their profile will not be connected to the RDWeb system and so the applications will not be available to them.
To get them connected, follow these steps:
1.
Search Windows for “Remote Apps”
a.
2.
If when you come to this window, it shows they have an active connection, this is good, you can use the “View Resources” button to be taken to the resources shortcuts and put some on their desktop for them, they are good to go really:
a.
b.
3.
If however, you see no connections, click “Access RemoteApp and desktops” on the left hand side:
a.
4.
You will be greeted by this window, type in https://rdweb.kingsltd.co.uk and hit next:
a.
5.
It will prompt for credentials, you need the current end user to enter their AD credentials, do not use any one elses as the resource list is determined by security access etc.
6.
You will now have access to the resource shortcuts like in point 2A
7.
Move yourself a relevant shortcut to their desktop for them and have they open the shortcut and log in with their AD credentials.
Helping a user whose apps won’t load
If a user is set up for RDWeb work resources and has their shortcuts, they click them and enter their credentials but no application ever seems to load, this can be fixed by cancelling/terminating their open sessions in the RDS environment using one of the RDSH servers.
1.
Remotely access a RDSH server, any should do.
2.
Log in as your admin user, i.e Tpadmin
3.
Once connected and logged in, go to Server Manager
a.
4.
If you have never connected to Server Manager on this particular RDSH Server (skip to step 5 if this is not your first time), you will need to add the RDS servers to your Server Manager, follow these sub steps to do so:
a.
Click “Manage”, then “Add Servers”:
i.
b.
In the Name (CN) search box, type “GB-P-RD” as all servers we want begin that way, highlight all of them and click the right arrow:
i.
c.
If your permission levels are correct, the resources and roles of these servers are now manageable for you via this server manager window, and “Remote Desktop Services” should now be a choice on the dashboard:
i.
ii.
NOTE: If this does not work, you will need to have your permissions increased, please escalate internally to have your permissions amended.
5.
We are now in a position to control Remote Desktop Services, click into Remote Desktop Services, then click on the location of the affected user, note that your user may be Node 4 or Bradford if they are North based staff.
6.
Find the user who is having issues, right click on their name on the right hand side under “connections” and click “Disconnect”:
a.
7.
Give it a few seconds, and then have the affected user retry their shortcut and they will now be successfully logged into the application.