Click here to get back home

Moving Enterprise Root CA

 HomeNewsGroups | Search | About
 microsoft.public.windows.server.security    Post an article   get this group's latest topics as an RSS feed add this group's latest topics to your My MSN content add this group's latest topics to your My Yahoo content
Subject Author Date
Moving Enterprise Root CA Richard Gadsden 03-22-2007
Posted by Richard Gadsden on March 22, 2007, 11:05 am
Please log in for more thread options
I have an enterprise root CA on a Windows Server 2003 Standard Edition
server.

I have (finally) got the budget to put Windows Server 2003 Enterprise
Edition in, but it will have to be on another server - and the previous
server cannot be taken out of service or renamed.

I'm trying to think through my options to migrate it. What seems to
make sense to me is:

1. Export the Root CA certificate

2. Set up a Stand-Alone Root CA using the exported certificate - on a
server that can then be taken offline (probably a virtual one, unless
someone has a good reason that a root CA can't be on a virtual server).

3. Create a new Subordinate Enterprise CA on the new Enterprise Edition
server, subordinated from the new Root CA

4. Take the new Root CA off-line

5. Remove the old Enterprise Root CA and tell the domain to use the new
Subordinate Enterprise CA

Does that make sense, and are there any tricks I'm missing?

--
Richard Gadsden richard.gadsden@cobbetts.co.uk
Nothing in this message is, or should be taken to be, representative
of the views of Cobbetts LLP

Posted by Ray on March 22, 2007, 3:49 pm
Please log in for more thread options
Everything should be OK if you keep the name of new server same as that of
old server

--
Ray

MCSE+Internet, MCDBA, MCP

>I have an enterprise root CA on a Windows Server 2003 Standard Edition
>server.
>
> I have (finally) got the budget to put Windows Server 2003 Enterprise
> Edition in, but it will have to be on another server - and the previous
> server cannot be taken out of service or renamed.
>
> I'm trying to think through my options to migrate it. What seems to make
> sense to me is:
>
> 1. Export the Root CA certificate
>
> 2. Set up a Stand-Alone Root CA using the exported certificate - on a
> server that can then be taken offline (probably a virtual one, unless
> someone has a good reason that a root CA can't be on a virtual server).
>
> 3. Create a new Subordinate Enterprise CA on the new Enterprise Edition
> server, subordinated from the new Root CA
>
> 4. Take the new Root CA off-line
>
> 5. Remove the old Enterprise Root CA and tell the domain to use the new
> Subordinate Enterprise CA
>
> Does that make sense, and are there any tricks I'm missing?
>
> --
> Richard Gadsden richard.gadsden@cobbetts.co.uk
> Nothing in this message is, or should be taken to be, representative
> of the views of Cobbetts LLP


Posted by Richard Gadsden on March 27, 2007, 8:10 am
Please log in for more thread options
Ray wrote:
>> I have an enterprise root CA on a Windows Server 2003 Standard Edition server.
>>
>> I have (finally) got the budget to put Windows Server 2003 Enterprise Edition
in, but it will have to be on another server - and the previous server cannot be
taken out of service or renamed.

>>
>> I'm trying to think through my options to migrate it. What seems to make
sense to me is:
>>
>> 1. Export the Root CA certificate
>>
>> 2. Set up a Stand-Alone Root CA using the exported certificate - on a server
that can then be taken offline (probably a virtual one, unless someone has a
good reason that a root CA can't be on a virtual server).

>>
>> 3. Create a new Subordinate Enterprise CA on the new Enterprise Edition
server, subordinated from the new Root CA
>>
>> 4. Take the new Root CA off-line
>>
>> 5. Remove the old Enterprise Root CA and tell the domain to use the new
Subordinate Enterprise CA
>>
>> Does that make sense, and are there any tricks I'm missing?
>
> Everything should be OK if you keep the name of new server same as that
> of old server

I can't rename the old server, so the new server will have to have a
different name.

--
Richard Gadsden richard.gadsden@cobbetts.co.uk
Nothing in this message is, or should be taken to be, representative
of the views of Cobbetts LLP

Posted by Ray on March 27, 2007, 10:14 am
Please log in for more thread options
Then you will have trouble to move CA.

--
Ray

MCSE+Internet, MCDBA, MCP

> Ray wrote:
>>> I have an enterprise root CA on a Windows Server 2003 Standard Edition
>>> server.
>>>
>>> I have (finally) got the budget to put Windows Server 2003 Enterprise
>>> Edition in, but it will have to be on another server - and the previous
>>> server cannot be taken out of service or renamed.
>>>
>>> I'm trying to think through my options to migrate it. What seems to
>>> make sense to me is:
>>>
>>> 1. Export the Root CA certificate
>>>
>>> 2. Set up a Stand-Alone Root CA using the exported certificate - on a
>>> server that can then be taken offline (probably a virtual one, unless
>>> someone has a good reason that a root CA can't be on a virtual server).
>>>
>>> 3. Create a new Subordinate Enterprise CA on the new Enterprise Edition
>>> server, subordinated from the new Root CA
>>>
>>> 4. Take the new Root CA off-line
>>>
>>> 5. Remove the old Enterprise Root CA and tell the domain to use the new
>>> Subordinate Enterprise CA
>>>
>>> Does that make sense, and are there any tricks I'm missing?
> >
>> Everything should be OK if you keep the name of new server same as that
>> of old server
>
> I can't rename the old server, so the new server will have to have a
> different name.
>
> --
> Richard Gadsden richard.gadsden@cobbetts.co.uk
> Nothing in this message is, or should be taken to be, representative
> of the views of Cobbetts LLP


Posted by Brian Komar [MVP] on March 27, 2007, 3:24 pm
Please log in for more thread options
richard.gadsden@cobbetts.co.uk says...
> Ray wrote:
> >> I have an enterprise root CA on a Windows Server 2003 Standard Edition
server.
> >>
> >> I have (finally) got the budget to put Windows Server 2003 Enterprise
Edition in, but it will have to be on another server - and the previous server
cannot be taken out of service or renamed.

> >>
> >> I'm trying to think through my options to migrate it. What seems to make
sense to me is:
> >>
> >> 1. Export the Root CA certificate
> >>
> >> 2. Set up a Stand-Alone Root CA using the exported certificate - on a
server that can then be taken offline (probably a virtual one, unless someone
has a good reason that a root CA can't be on a virtual server).

> >>
> >> 3. Create a new Subordinate Enterprise CA on the new Enterprise Edition
server, subordinated from the new Root CA
> >>
> >> 4. Take the new Root CA off-line
> >>
> >> 5. Remove the old Enterprise Root CA and tell the domain to use the new
Subordinate Enterprise CA
> >>
> >> Does that make sense, and are there any tricks I'm missing?
> >
> > Everything should be OK if you keep the name of new server same as that
> > of old server
>
> I can't rename the old server, so the new server will have to have a
> different name.
>
>
You must decommission the old server, build the new
server using the new name, recover the CA, and then
redeploy the old server using the name that you want.

Brian

Similar ThreadsPosted
Migrate Enterprise root authority CA to stand-alone root CA December 13, 2005, 7:57 am
Stans-alone root CA or Enterprise root CA August 31, 2006, 6:32 pm
More than one enterprise root CA in a forest? January 18, 2006, 4:13 am
move enterprise root ca September 13, 2006, 8:09 am
Installing Enterprise Root CA March 3, 2007, 10:00 am
Re-Configuring LDAP CDP on Enterprise Root CA February 17, 2007, 1:31 am
EFS concerns before removing enterprise root CA March 23, 2007, 8:59 am
0x424 (WIN32: 1060) in Enterprise Root CA June 6, 2005, 9:03 am
Enterprise Root Certification Authority not trusted February 16, 2006, 2:07 pm
Prevent Folder moving July 11, 2005, 9:17 am

Our other projects:

Art Dolls, Fairies and Mermaids - Sunnyfaces.net

Roy's Linux, Programming and Search Engines messages

1-Script XML SitemapXML Sitemap