We recently upgraded our server to Win 2003 - from nt4.

We created a SSL Certificate backup key according to this instructions:
HOW TO: Import and Export an IIS 4.0 Certificate by Using Key Manager
http://support.microsoft.com/defaul...;en-us;324904#2

My question is: can I import this nt4 backup key file - and thus the certifi
cate
- into the Windows 2003 box?

So far, i am getting an incorrect password or your certificate has expired
error message.

Francisco,
http://franjalova.monoforge.com/

[ Post a follow-up to this message ]

I would notify your CA.  I don't think you can since the 4.0 key and
subsequent backup/export was based on an original 4.0 key request by IIS 4.0
.
I don't think 6.0 on your new box will appreciate what you're trying to do
and it sounds like this is the problem you're having.

See if your CA will reissue the certificate from a 6.0 request at little or
no charge.

"Francisco Lopez" wrote:

> We recently upgraded our server to Win 2003 - from nt4.
>
> We created a SSL Certificate backup key according to this instructions:
> HOW TO: Import and Export an IIS 4.0 Certificate by Using Key Manager
> http://support.microsoft.com/defaul...;en-us;324904#2
>
> My question is: can I import this nt4 backup key file - and thus the certi
ficate
> - into the Windows 2003 box?
>
> So far, i am getting an incorrect password or your certificate has expired
> error message.
>
> Francisco,
> http://franjalova.monoforge.com/
>
>
>

[ Post a follow-up to this message ]

Hello Tim,
Thanks, will do. It is almost time to renew anyhow.

Francisco,
http://franjalova.monoforge.com/
[vbcol=seagreen]
> I would notify your CA.  I don't think you can since the 4.0 key and
> subsequent backup/export was based on an original 4.0 key request by
> IIS 4.0.
> I don't think 6.0 on your new box will appreciate what you're trying
> to do
> and it sounds like this is the problem you're having.
> See if your CA will reissue the certificate from a 6.0 request at
> little or no charge.
>
> "Francisco Lopez" wrote:
> 

[ Post a follow-up to this message ]