Hi there. AT was never part of the collection in the first place. It was found to be part of its own RD Quick Deployment. I tried a fair few things since posting this and ultimately decided to remove and re-add Gateway and WebAccess features as I believe that was where the problem was. It did solve it.
RDWeb and RemoteApp not going to session host
I've built a standard RDS farm. I have the following servers.
RDCB my connection broker and licence server
RDGW my gateway and web access
RDSH is my session host.
I'm really not sure how but when I connect to my collection via RDWeb or RemoteApp, the connection that is made is going to a completely different server. For the purposes of this post, the new server is called AT.
I'm really struggling how this could be happening. The only things I have found is that AT did have a standalone RDS deployment which has since been removed. Equally I can't find anything in DNS.
Any ideas where to look?
1 additional answer
Sort by: Most helpful
-
Eleven Yu (Shanghai Wicresoft Co,.Ltd.) 10,756 Reputation points Microsoft Vendor
2021-01-11T06:45:47.18+00:00 Hi,
- Do you have only one collection?
- Have you confirmed only the server RDSH was added to below Host Server list? And AT has been removed from the list?
- Since the RDS deployment has been removed from AT, you should not be able to remote connect to the server. Are you sure the remote desktop session host role has been removed from it? If so, could you please share a screenshot to show your issue that connectind to AT cia RemoteApp?
Thanks,
Eleven----------
If the Answer is helpful, please click "Accept Answer" and upvote it. Thanks.