need a new SSL cert on production web

I have a web server running IIS 5.0. It hosts our company's website with the
head as www.mycompany.com. VeriSign cert issued to www.mycompany.com is
applied at this level. Two virtual dirctories under this website is
configured to require SSL. Now, we need to change the website to another
head as www.yourcompany.com. So, we need a new cert. (right?) But here is
my problem.

1. with IIS 5 since it already got a cert at the website (for
www.mycompany.com) the only options I got under Directory Security, Server
Certificate is to 1. renew current certificate 2. remove current certificate
3. replace current certificate. with option 1 it wil be based on existing
cert which is for www.mycompany.com so I can't do that. with option 2 my
production website won't have cert till I got a new one. Nee to avoid that
if possible. with option 3 I can't see current (unexpired) certificate. I
only can see one expired cert.

So how can I get a new cert under new header? The header can be added under
Website, Advanced for port 80. BTW. Do I need to restart WWW svc after
adding the new header?

2. another alternative to avoid impact on production website is to create a
new website for www.yourcompany.com. Then generate a new CSR, then apply the
new cert once received. It's easy and safe. But how can I copy or duplicate
everything (virtual directories and folders) under www.mycompany.com to the
new website www.yourcompany.com?

Also, usually how long does it take to get a new cert from verisign?

thanks in advnace.

Re: need a new SSL cert on production web

You need a new cert, another virutal web to install it on, and another IP to
run that on... which in turn needs the DNS entry for "yourcompany.com".

In other words, just repeat what you did for the first site.

Or, just use the original cert on those folders.

You don't need to restart IIS after adding a header. (That's irrelevant to
your problem though, as that's not where the cert goes.)

New certs take 1 to 7 days, depending on how hard it is for them to verify
the organization is legit. (Hint: remind your client they must answer the
phone or call Verisign back.)

The amount of effort required to copy a site with all it's settings is much
greater than it is to spend a few minutes to re-configure by going through
each tab. So just duplicate it by hand.

"Chris" wrote in message
news:6A56C03E-DFEB-4698-9FBE-0748572247CF@microsoft.com...
>I have a web server running IIS 5.0. It hosts our company's website with
>the
> head as www.mycompany.com. VeriSign cert issued to www.mycompany.com is
> applied at this level. Two virtual dirctories under this website is
> configured to require SSL. Now, we need to change the website to another
> head as www.yourcompany.com. So, we need a new cert. (right?) But here
> is
> my problem.
>
> 1. with IIS 5 since it already got a cert at the website (for
> www.mycompany.com) the only options I got under Directory Security, Server
> Certificate is to 1. renew current certificate 2. remove current
> certificate
> 3. replace current certificate. with option 1 it wil be based on existing
> cert which is for www.mycompany.com so I can't do that. with option 2 my
> production website won't have cert till I got a new one. Nee to avoid
> that
> if possible. with option 3 I can't see current (unexpired) certificate. I
> only can see one expired cert.
>
> So how can I get a new cert under new header? The header can be added
> under
> Website, Advanced for port 80. BTW. Do I need to restart WWW svc after
> adding the new header?
>
> 2. another alternative to avoid impact on production website is to create
> a
> new website for www.yourcompany.com. Then generate a new CSR, then apply
> the
> new cert once received. It's easy and safe. But how can I copy or
> duplicate
> everything (virtual directories and folders) under www.mycompany.com to
> the
> new website www.yourcompany.com?
>
> Also, usually how long does it take to get a new cert from verisign?
>
> thanks in advnace.