Go Premium for a chance to win a PS4. Enter to Win

x
?
Solved

Remote Desktop Services Certificate Mismatch

Posted on 2015-01-05
9
Medium Priority
?
478 Views
Last Modified: 2015-01-11
I am setting up a remote desktop services farm, and I'm getting a certificate mismatch when connecting to the session host. The notification says that the requested computer has a local domain, but the certificate on the remote computer is a .com domain. Does anyone know what I'm missing to make this work? It would seem that I have to change the FQDN of each TS to remote.company.com, but I don't know how to do that. Any help is greatly appreciated.
0
Comment
Question by:Brad212
  • 6
  • 3
9 Comments
 

Author Comment

by:Brad212
ID: 40531888
Screenshot of the certificate mismatch notification
0
 

Author Comment

by:Brad212
ID: 40531890
These are the details of my deployment: My farm has 4 servers all running Windows Server 2012 R2. One server, let's call it TS-Services, holds 3 roles - RD Web Access, RD Gateway, and RD Connection Broker. The other 3 servers are session hosts. Let's call them TS1, TS2, and TS3. All 4 servers use the same wildcard certificate - *.company.com, and my RD Gateway external FQDN is set to remote.company.com. I believe I had to change the published RDS name of the Connection Broker (TS-Services) from the local FQDN to remote.company.com. However, I can't seem do that on the TSs because they are not connection brokers. My clients are connecting from Windows 7 PCs.
0
 

Author Comment

by:Brad212
ID: 40531931
This is the notification that appears when trying to connect externally over the internet.
0
Get your Conversational Ransomware Defense e‑book

This e-book gives you an insight into the ransomware threat and reviews the fundamentals of top-notch ransomware preparedness and recovery. To help you protect yourself and your organization. The initial infection may be inevitable, so the best protection is to be fully prepared.

 
LVL 12

Assisted Solution

by:David Paris Vicente
David Paris Vicente earned 400 total points
ID: 40531941
Hi,

You can find here in EE an answer to a similar problem.

If you continue to struggle with the problem let us know.


Hope it helps.

D.
0
 

Author Comment

by:Brad212
ID: 40532399
Update: My second screenshot is unrelated. I had neglected to setup a computer group in Remote Desktop Gateway Manager. Once that was I done, I was able to connect to the session hosts.
0
 
LVL 12

Expert Comment

by:David Paris Vicente
ID: 40533034
Ok.

But the certification problem persists?
Did you check the EE link?
0
 

Accepted Solution

by:
Brad212 earned 0 total points
ID: 40533817
Thanks for you comment. While the post you referenced is similar, I found a different solution. The other post recommends a SAN certificate, but because I had already purchased a wildcard cert - as most of the documentation I found online suggested, I was reluctant to change the cert. After some digging I found that RDP 8.0 (included with Windows 8) somehow works around the problem and doesn't present the certificate mismatch notification. My solution will be to update my Windows 7 clients to RDP 8.1 which is the latest version. Hopefully this will help someone else save some time and effort.
0
 
LVL 12

Expert Comment

by:David Paris Vicente
ID: 40533900
Great, keep the good work.

Regards
0
 

Author Closing Comment

by:Brad212
ID: 40542922
I believe that using RDP 8.0 in conjunction with a Windows Server 2012 R2 RDS farm configured with 3rd party and self-signed certificates is the more modern approach than using SAN certificates. Some SSL cert providers have discontinued SAN certs.
0

Featured Post

Creating Active Directory Users from a Text File

If your organization has a need to mass-create AD user accounts, watch this video to see how its done without the need for scripting or other unnecessary complexities.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

The recent Microsoft changes on update philosophy for Windows pre-10 and their impact on existing WSUS implementations.
How to deal with a specific error when using the Enable-RemoteMailbox cmdlet to create a mailbox in the cloud-based service, for an existing user in an on-premises Active Directory.
In this Micro Tutorial viewers will learn how they can get their files copied out from their unbootable system without need to use recovery services. As an example non-bootable Windows 2012R2 installation is used which has boot problems.
In this Micro Tutorial viewers will learn how to restore their server from Bare Metal Backup image created with Windows Server Backup feature. As an example Windows 2012R2 is used.

926 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question