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

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?

Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

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:

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Windows Server 2012

From novice to tech pro — start learning today.