Win2K3 TS Certificate newbie questions

Win2k3 TS, clients RDC RDP WinXP.

Looking at TLS 1.0 for server authentication

1a.  Will ALL RDC clients have to obtain and use the certificate, or just those that choose to?  Is there a cost for them?
1b.  Will ALL RDC clients have to use RDC RDP 5.2 from the Win2k3, I think most XP PCs use 5.1?

Certifcate?:  On the TS Box I found the MMC Certificate screens.
2a.  I see a lot of cerificates already there (out of the box Win2k3), will any of these do TLS?
2b.  Do I have to buy something?  How?  Where?  $?
2c.  I tried the Certificate Request Wizard via the MMC and get a red X dialog "There are no trusted CAs available".  What does that mean I have to do?
2d.  I'm gathering that there are more than one certificate to choose from.  I'd lean toward easy and cheap.  Does MS supply/sell certificates themselves?
2e.  Is SSL in this picture?
2f.  Does any of this add any significient resource drain on the server?

I've read the MS article "How to configure a Windows Server 2003 terminal server to use TLS for server authentication" ( , but I still confused about the basics of certificates.    The MS link to "Microsoft Cryptographic Service Providers" ( just left me more cunfused.

If I get further into this, and decide I gotta back out, can I undo everything?

Be gentle.  Newbie with a lot of questions.  500 Points.

Who is Participating?
Rich RumbleConnect With a Mentor Security SamuraiCommented:
You don't buy a CA unless your Verisign:
You still need to have your own installed CA server, you can buy a signed certificate from Thwate, Verisign, Go-Daddy etc... or you can create and sign your own certs. I've not setup TS to use certs myself, but from what I've read, once you have the Cert and it's present on the CA server, all you  should have to do is follow the instructions in your first link:
Don't tkae this very literally... "Obtain a certificate from a third-party certification authority, and then manually install the certificate." you can install your own.
You can create your own certs with native windows tools and or use OpenSSL to do so

Rich RumbleSecurity SamuraiCommented:
A local CA server (certificate authority) is much like that you see on the web, when you access a HttpS site for the first time you might be prompted to view this site's SSL certificate, and accept. It's the same thing, you can self sign and create your own certs, or purchase one from those such as Verisign or Thwate
M$ OS's come with a variety of root certificates and the domain your in likely has some self-generated ones as well as your PC for things like EFS.
TLS is simply SSL's replacement:
RDP is fairly secure, and stepping the bit's up from 56 to 128 is typically a good move, the overhead is the same really. term-your-looking-for
I'll look for the answers to some of the other q's...
JReamAuthor Commented:

Rich -

My objective remains: Getting a Certificate on Terminal Server via the Certificate Request Wizard.

Status:  Frustrated.  Hours/days burning by.

Here's the documented process:
If you plan to obtain a certificate by using the Certificate Web pages or Certificate Request Wizard, a public key infrastructure (PKI) must be configured correctly to issue SSL-compatible X.509 certificates to the terminal server. Each certificate must be configured as follows:
•The certificate is a computer certificate.
•The intended purpose of the certificate is server authentication.
•The certificate has a corresponding private key.
•The certificate is stored in the terminal server’s personal store. You can view this store by using the Certificates snap-in.
•The certificate has a cryptographic service provider (CSP) that can be used for the SSL (TLS) protocol (for example Microsoft RSA SChannel Cryptographic Provider).

Here's where I'm at.
 - We set up an Ent CA on one of our Domain member Win2k3 Servers.  OK so far I think.   (Our DC and servers are Win2k3 Std, not EE.)
 - I see all the Certs under Certificate Templates, such as "Computer" + "Server Authentication".  This one seems to be the one I want, I think.. :(.
 - I CAN"T seen to ISSUE this one.  It does not appear on the "New Certificite to Issue" list of choices.  I'm not even sure

I'm dying out here.

JReamAuthor Commented:

How about this Idea for me next:

1.  Forget the idea of setting up our own CA.  I'll uninstall the Ent CA we set up today.

2.  Buy one.  Where?
2a.  I need simple SSL for TS.
2b.  Would prefer low hassle on CLient side.  If I'm reading thing right, most CA vendors are already 'trusted' by most WinXP PCs.  

Where should I go?  Is this a better plan?  

JReamAuthor Commented:

SOLUTION for: How to Install Win2K3 Terminal Server SSL Certificate

Short Answer to reply/close to various posts I made:

- Do not Install Windows Server 2003 Certificate Services.
- Produce a CSR (Certificate Signing Request) on any available IIS6 box, any website. Yes CSP, select MS RSA
-    In CSR be sure to specify your FQDN intented for use by remote RDC Users, same as RDC “Server” text box.
-    My FQDN is a Registered Whois Domain with resolves to IP like any other Domain.
- Buy a SSL Certificate from any CA.  Apply your CSR at CA.  Get CRT files, two in my case, Web Cert & Intermediate Certificate.
- Apply CRTs to IIS6 Box, ICert to MMC and WCert to IIS6.
- Export Certificate from IIS6 Website as .PFX file, remove CRTs from IIS6 Box.
- Apply both CRTs to TS Box via MMC.
- TS Configuration will should now properly see your SSL Certificate.
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.