Certificate for Remote Desktop using a Comodo Multi-domain certificate

I have UC certificate from Comodo which allows us to have certificates for a number of servers and domains included in one file.

This works well on our Apache web server (Linux server).  I want to use the same certificate in Remote desktop under windows 2012.  I've exported it as a .pfx file and told remote desktop to use this certificate.

openssl pkcs12 -export -out server.pfx -inkey server.key -in server.crt

 The problem I have as that when people connect they get a certificate error message that says the server name in the certificate is wrong.  It picks the first server name in the certificate and display that name.  It doesn't appear to understand that it's elsewhere in the certificate.

Not sure how to fix this.  Is there a way to create the pfx file with just the hostname that I need?  Would it work if I used the certificate and not a pfx file?
Who is Participating?
JAN PAKULAConnect With a Mentor ICT Infranstructure ManagerCommented:
JAN PAKULAICT Infranstructure ManagerCommented:
if its not a wildcard cert like *.domainname.com

this certificate to work properly would have to be a SAN cert

does it have  Subject Alternative Name (SAN) control?


how to request san cert on windows


is the problematic clients with cert errors windows 2003 servers?

if so read that


2003 doesn't support san out of the box
geekdad1Author Commented:
Turns out I needed to use a slightly different openssl command to generate the pfx file.

openssl pkcs12 -export -out server.pfx -inkey server.key -in server.crt -certfile server.ca-bundle

I didn't originally get the bundle file, I had to request it.  Once I got it, then the procedure worked perfectly.
Making Bulk Changes to Active Directory

Watch this video to see how easy it is to make mass changes to Active Directory from an external text file without using complicated scripts.

JAN PAKULAICT Infranstructure ManagerCommented:
Brill you got it sorted
geekdad1Author Commented:
New question on same issue, if that's allowed.  I have another server 2012 server, that is our active directory server and we (admins) use remote desktop to get onto it.  So it's not part of the remote desktop server farm.  However I need to know where to install the certificate on it.  What I did in the past was use the certificate snapin, and import it into the personal/certificates section.  That doesn't seem to be correct.  Where do I install a certificate manually in this instance?
JAN PAKULAICT Infranstructure ManagerCommented:
Into your COMPUTER/PERSONAL STORE on the server +  import the intermediary cert as well  

plus follow that

geekdad1Author Commented:
I'm using the .pfx file that I setup for the other server (see above)
I have a bundle file that presumably helps with this problem and I used it when creating the .pfx file

I deployed the certificate on the actual remote desktop server and it works fine.  I just need to know how to deploy it manually for this server.

I read the link above, but alas it only applies to server 2008.  In 2012 they've removed the remote desktop host configuration utility.
geekdad1Author Commented:
Yes, it is part of the domain.  But this server will not be part of the RDS server pool.  I just need to get to it remotely using terminal services.  The fact that I get a certificate error is annoying but not critical to the operation, since only the admins will have access to this machine.  My preference is to keep it separated from the pool that the general public will use, so the above solution doesn't work in my case
JAN PAKULAICT Infranstructure ManagerCommented:
Yup i know Microsoft shot itself in the leg doing that :)
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.