Installing an existing GoDaddy SSL on another SBS box....
- From: "Lanwench [MVP - Exchange]" <lanwench@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx>
- Date: Wed, 14 May 2008 17:44:40 -0400
This is probably a dumb question; I'm pretty much an IIS moron. But I've got
a functional GoDaddy SSL cert installed and working on my own SBS box...and
I'm now moving that server to new hardware (well, technically, I'm
rebuilding it in a virtual server). It's a pretty vanilla install so far.
When I first ran the CEICW I just entered a bogus / placeholder self-signed
SSL cert - I now want to replace it with my real one so it's ready to go
when I do my cutover.
I installed the intermediate certificate properly, and then re-ran the CEICW
to install the main cert, thinking that would simply work, silly me! I got
an error that there was no pending request for the default website (there
wasn't, of course) so I prepared one. I did this by following the "official
SBS Blog" instructions, which are what I'd followed to order the cert in the
first place - I created a new website using the appropriate host.domain.com
name & got the certreq.txt generated.
The CEICW still wouldn't let me install the existing CRT file - same error.
I then tried removing the existing request from host.domain.com and running
the same request on the *default* website. Same error; no dice.
Abandoning the CEICW, I ran through the SBS blog instructions again &
recreated host.domain.com and prepared a new request. Then tried to go
through & assign the .crt file. That yielded "The pending request for this
response file was not found. This request my be canceled. You cannot install
selected response certificate using this Wizard"
I tried copying the certreq.txt from my existing server to the new one to
see if that made any difference - no dice.
When I've gotten third party certs before I've always created the
certreq.txt file on the server & run through it with the SSL cert provider
at ordering time - it's always worked fine that way. However, I've never
done anything like this after I've already *got* a valid certificate and
want to install it on a new box.
Q1: Do I have to go back to GoDaddy to get a new one issued for download,
just as though I'd never done this before?
Q2: Will that do anything bad to my existing, working SSL cert on the
as-of-yet production server?
I haven't run into this at a client site yet, but I'm sure it can and will
happen, and I'd like to know what the proper procedures are so I don't show
them what an IIS moron I am. Help!
.
- Follow-Ups:
- Prev by Date: Re: Exchange maintenance after loading/deleting messages.
- Next by Date: Re: NTBackup Problem
- Previous by thread: svchost 100% CPU is back!
- Next by thread: Re: Installing an existing GoDaddy SSL on another SBS box....
- Index(es):
Relevant Pages
|
Loading
