Windows Remote Desktop Services issue - different AD domain and DNS domain/zone causing problems....

yccdadmins used Ask the Experts™
Hello all,

Here is my scenario.

- I have set up Windows RDS on a 2012 server.  Also set up WebApp and published an application.
- Server is part of an Active Directory domain called
- Server is part of a DNS zone

At this point - remote desktop works but I am unable to connect to the published application.

- When I set up RDS services, I did everything using - which is the FQDN of the server as presented to the world.
- Tested RD and it worked fine.  Tested opening the published application via HTTPS and an error came up stating "unable to find".  This is because the server is known in DNS as

In the DNS section of the network configuration for the NIC on this system I set "DNS suffix for this connection" to but that had no effect.

An quick and easy solution would be to get with the separate organization that runs and have them create a cname pointing to but I would much rather find a way to change everything in RDS Service to see the system as

Anyone else had this issue or something similar?

Watch Question

Do more with

Expert Office
EXPERT OFFICE® is a registered trademark of EXPERTS EXCHANGE®
Distinguished Expert 2018
Your RDS farm deployment name should match to one present in certificate (which should be connection broker internal IP)
Note that all client connections (web access also) are 1st hits to RD connection broker and then RD connection broker handles redirection to appropriate RD Session host

Run below PowerShell command on RD Connection broker
Set-RDSessionCollectionConfiguration –CollectionName QuickSessionCollection -CustomRdpProperty “use redirection server name:i:1 `n alternate full”
Make sure would resolve to connection broker server IP address from internal network (the same name should present in certificate as subject name / SAN entry and used while you configured SSO in RDS manager)
You might need to create dns zone and record in internal DNS

Other alternative is to change RDS deployment name to match FQDN mentioned in certificate (FQDN should resolve to internal IP of connection broker server) via below script

Go through below article:

Do more with

Expert Office
Submit tech questions to Ask the Experts™ at any time to receive solutions, advice, and new ideas from leading industry professionals.

Start 7-Day Free Trial