Doug Poulin
asked on
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?
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?
ASKER
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.
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.
Brill you got it sorted
ASKER
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?
Into your COMPUTER/PERSONAL STORE on the server + import the intermediary cert as well
plus follow that
http://community.spiceworks.com/how_to/show/15809-dealing-to-the-annoying-certificate-errors-and-multiple-credential-requests-in-remote-desktop-services-2008-r2
plus follow that
http://community.spiceworks.com/how_to/show/15809-dealing-to-the-annoying-certificate-errors-and-multiple-credential-requests-in-remote-desktop-services-2008-r2
ASKER
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.
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.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
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
Yup i know Microsoft shot itself in the leg doing that :)
this certificate to work properly would have to be a SAN cert
does it have Subject Alternative Name (SAN) control?
http://www.digicert.com/subject-alternative-name.htm
how to request san cert on windows
http://technet.microsoft.com/en-us/library/ff625722(WS.10).aspx
is the problematic clients with cert errors windows 2003 servers?
if so read that
http://support.microsoft.com/kb/931351
2003 doesn't support san out of the box