Re: SSL - TS Configuration will not show installed certificates

I can't tell you exactly what is going wrong with your setup, but I can tell you how I have got it to work every time:

1. Request, obtain, & install cert from CA using the IIS Web Server Certificate Wizard (in my case it has always been a purchased cert marked for Server Authentication)

2. Select the above Certificate in the RDP-Tcp Properties

On my servers, the certificate does NOT show up in the Personal section of IE. I think this makes sense, because this should be the personal ceritificates for my user account. It does show up in the Personal list through the Certificates snap-in computer account.

Thanks.

-TP

Christopher Smith wrote: 
I am trying to setup a Terminal Server to use SSL, as described in
this KB article:

http://support.microsoft.com/?kbid=895433

We are using our own in-house CA to create an sign Certificates. It
is a Linux machine, using OpenSSL. We have already used it to
successfully setup SSL for our Exchange OWA users, along with
numerous internal SSL-protected websites (albeit running on
Apache/Linux).

The problem I am having is that when I open up the Properties of the
RDP-TCp connection in Terminal Services Configuration, then hit the
Edit button (as directed in the KB article), there are no
certificates listed to choose from. 

The process I used for "importing" the computer certificate was (I
also did the same to import our CA's cert):

1.  Open up MMC and add the "Certificates" snap-in, selecting
"Computer Account" when prompted.
2.  Right click "Personal" -> All Tasks -> Import
3.  Choose the x509 cert generated on, and signed by, the CA.
4.  Direct it to place the cert in the "Personal" store.

After that, the cert is shown in the Personal - Certificates store. It shows up in IE under Tools -> Options -> Content -> Certificates
-> Personal. It has <all> under its "Intended Purposes".

But it won't show up in the RDP connection properties, so I can't
select it to use with Terminal Services.

I assume there's something "special" that needs to be done either when
importing or creating the cert, does anyone know what that is ?  Has
anyone successfully used OpenSSL to create and sign certificates for
use with a Terminal Server ?

Cheers,
CS

.