Convert Enterprise Root CA to Standalone CA and moving to Multiple Subordinate CA structure



Hi, my existing setup is/was simple. Had a single site active
directory for 30 users and an exchange server.

All computer workstation identification certs were pushed out via
autoenrollment and as such they trust the root CA which was the one to
issue the certificates.

As i will now have a number of sites i think it would be prudent to
have subordinate CAs at each remote location to issue certificates
there.

My question is, how would this affect the current computers having the
existing CA where it is directly issued from the enterprise root,
compared to other computers who were issued via the subordinate CA
when i get them running? Im guessing not much, since all computers
will trust the root anyway through thet certificate tree? Only down
side is if the root got comprimised in this scenario since they would
still trust it.

To aid my understanding, do enterprise root CA issue certificates to
workstations by default? Im guessing not, since i had to create a
workstation identification template.

How could i ensure in future that the root CA only issues certificates
for other subordinate CA's and NOT workstations? Would this be through
the certificate management mmc console? Is this controlled by active
directory GPO or some other setting?

Finally, given the site links are expanding, Is it possible to move my
existing enterprise root CA to a standalone root CA, and then create
multiple subordinate CAs to issue certs on the clients behalf? This
would be the ideal setup as a managed upgrading process.

Many thanks in advance,

Chris
.



Relevant Pages

  • Convert Enterprise Root CA to Standalone Root CA and create new Subordinate CAs
    ... All computer workstation identification certs were pushed out via ... autoenrollment and as such they trust the root CA which was the one to ... how would this affect the current computers having the ... do enterprise root CA issue certificates to ...
    (microsoft.public.security)
  • Re: Using Certificates with IPSEC
    ... > What is the process of trusting other computers for IPSEC using Certificates? ... >> same root CA, or to CAs that are trusted by the opposite endpoint. ...
    (microsoft.public.win2000.security)
  • Re: Alerting - Malicious software removal tool
    ... >needed to install an application that she could not install from ... >"Administrator" account. ... You failed to analyze the root cause and correct it ... use their computers to have fun. ...
    (microsoft.public.security.virus)
  • Re: Enterprise root CA not re-trusted after manually deleted
    ... published) autoenrollment queries AD for CA certs and installs them. ... CA certs in AD). ... deleted root certs can automatically return or need a manual repair. ... If root CA certificates are distributed using autonenrollment (meaning ...
    (microsoft.public.windows.server.security)
  • Re: Certificate issue on Exchange ActiveSync setup (WM6) - UPDATE
    ... In the Certificates snap-in box it is very important you choose "Computer ... Finish out of the standalone boxes and view the Console Root window. ... should now see a Console Root folder, with a Certificates folder under it, ...
    (microsoft.public.pocketpc.activesync)