Hi everyone,
There seems to be a blizzard of questions and misunderstandings about certificates for Svr 2012 TS.
Here is another one. I've just set up a TS system and its working using its self signed certificates. There are three servers; 2 are session hosts and everything else is on the 3rd. All three are domain member servers and there is a domain CA.
I've search and googled this issue and read many of the articles on the subject. Maybe I'm just not getting some of the finer points of detail.
For example this post looks promising
https://technet.microsoft.com/en-us/library/cc732329?f=255&MSPPError=-214721739
as it has the statement
"You can generate and submit a certificate request to obtain a certificate from a stand-alone or an enterprise certification authority (CA)."
Great we are making progress here, but wait, it then keeps the answer a secret. :-(
Is there a way to get a Certificate Signing Request out of a TS system and install a signed certificate? I read one article that described getting a CSR from IIS on the RDGW server, which I did and I then got a signed certificate from the domain CA and tried to install it on the RDGW server. The certificate from the Domain CA is in .cer and .p7b format. But the "Configure the Deployment" wizard wants the certificate to be in .pfx format. That, I believe, includes the private key. Why would I want to replace the private key?
I've probably missing something obvious here, or missing the point completely, as this process appears at best obfuscated and at worst is downright user aggressive!
I've been generating CSR's and installing signed certificates on MS and Open Source web and e-mail systems for years. I have a fair idea what I'm doing - I'm not a guru but not daft either. But there must be a subtlety I'm missing on this one.
So can this be done? I'm beginning to doubt it. I looked for how-to's on some well known public CA's Knowledge Bases. They don't seem to know either.
If there is a in depth "how to" that describes this in excruciating detail, I'd really like to read it.
Thanks for reading so far
Pointers and wisdom most welcome.
:-)
Ken