We have several different Remote Desktop (aka: Terminal Service) deployments that users access via RD Gateway Server (2012 R2) setups. Some deployments have a separate connection broker server and others have the connection broker service collapsed onto the RD Gateway Server. Connections are established to the Gateway Server via a public IP on TCP:443 or UDP:3391 depending on the connection transport method being used. The user is ultimately routed through an authentication/load balancing process which connects them to one of the Remote Desktop servers allowing for secured connections without deploying site-to-site VPNs.
In the past several months, we have had occasions where the Gateway Server stops processing inbound connections requests which stops any new sessions from being created. Existing sessions typically continue to operate. The users do receive a generic RD Gateway error stating that the remote computer they are trying to reach is unavailable. When this happens, we sometimes have to restart the Gateway Svcs or often times it takes a reboot of the Gateway server.
I would really like to monitor this process better, so we would be able to respond quicker to the incident prior to having a user alert us of the issue. Ideally, I would like to be able to setup monitors that would login as a test user via the RD Gateway system and record average login times and then trigger an alert if it were to be unsuccessful. If not the ideal method, then any other suggestions on how to monitor would be greatly appreciated.
Is there anyway of doing this with PRTG? We have a few thousand sensors deployed and being able to do this would really help remove a thorn from our side while we continue to investigate the root cause of the underlying issue.