- This topic has 22 replies, 4 voices, and was last updated 4 years, 1 month ago by
.
-
Posts
-
We have bought a wildcard certificate I can use, as far as I know.
Just assumed I could test things out seeing the RDP desktop and so on before building the “big setup”.
I will check the guide (I have a lot of tabs open anyway about this) 😀
It seems some things has changed since 2012R2, but I’m not sure.
The “Be aware that you will probably not be able to order a Publicly signed certificate with .local domain names as SAN DNS entries, so Internal clients will need to be able to resolve the Public DNS name and get the Internal IP (Split DNS).” part I’ll have to read a bit about.
This process: https://msfreaks.wordpress.com/2018/10/06/step-by-step-windows-2019-remote-desktop-services-using-the-gui/ looks almost the same as for 2012R2.
It also covers the Split DNS issue and Redundant Brokers, in case you need that./Frank
I’ve already have this open.
When it mentioned SQL I didn’t follow the whole guide to the dot.
I guess I must look through that guide more thoroughly 🙂
Just noticed that the SQL installation for Redundant Brokers is not itself redundant, so you are just moving single-point-of-failure to the SQL instance.
And it is a Lab guide – You should not install SQL Server on a DC in real life.
Also be careful when setting up Split DNS, you are changing the way Internal clients resolve your Public domain name hosts, so it can cause a lot of issues of you don’t do it correctly and cover all public hostnames.
/Frank
The SQL on DC is mentioned 🙂
The Split DNS sounds fun….. 🙂
Regarding the Redundant Brokers with SQL sounds like I don’t need it then (?)
To me, Redundant Brokers only makes sense if you also have Redundant SQL Servers.
Yes, the need for Split DNS is an unfortunate side-effect of the way the Certificates are used for validating the hostnames. I don’t know of any way around that when you are running the RDS Infrastructure in-house.
Some Routers/Firewalls support “Hairpinning”, where Internal clients can use the External IP for Internal resources, but I would not rely on that.
/Frank
I am getting a certificate common name error as well. The broker server is actually cloud based web client. Is this possible?
Certificate common name is bad. I have added the cert as required from Microsoft but the error persists.
- You must be logged in to reply to this topic.