Root certificate authority no longer added to client machines

Root certificate authority no longer added to client machines

Secure Home | Search | About
 Microsoft Applications 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 add this group's latest topics to your Google content
Subject Author Date
Root certificate authority no longer added to client machines Stuart Hudman 12-15-2006
Posted by Stuart Hudman on December 15, 2006, 8:15 am
If you were  Registered and logged in, you could reply and use other advanced thread options
I have read as many articles/KB that I can and would like some clarification
if anyone can,
PLEASE!!.

We have a standalone RootCA, with Enterprise issuing CAs. We have ran
DSpublish for the RootCA into the AD, but clients do not get entries added
to
their trusted store. From what I understand, and read many times, is things
like: "When you install an enterprise root CA or a stand-alone root CA, the
certificate of the CA is added automatically to the Trusted Root
Certification Authorities Group Policy for the domain.". Well, if this is a
standalone Root, how the heck does it put it into a GPO ? Another article
states, that if the client is a domain member, then they will automatically
receive the CAs in the trusted store....but negates to say how.

So...in a complete Microsoft world (RootCA, SubEntCAs and clients)...how
does the trusted store get populated on a client ? Do you need a GPO or not
? Is it a sub-process of auto-enrollment ?

Thanks

Stuart



Posted by Paul Adare on December 15, 2006, 8:54 am
If you were  Registered and logged in, you could reply and use other advanced thread options
says...

> I have read as many articles/KB that I can and would like some clarification
> if anyone can,
> PLEASE!!.
>
> We have a standalone RootCA, with Enterprise issuing CAs. We have ran
> DSpublish for the RootCA into the AD, but clients do not get entries added
> to
> their trusted store.

What OS is running on your domain controllers? If you're running
Windows Server 2003 then you should be publishing the root
certificate with certutil and not dspublish.


> From what I understand, and read many times, is things
> like: "When you install an enterprise root CA or a stand-alone root CA, the
> certificate of the CA is added automatically to the Trusted Root
> Certification Authorities Group Policy for the domain.". Well, if this is a
> standalone Root, how the heck does it put it into a GPO ? Another article
> states, that if the client is a domain member, then they will automatically
> receive the CAs in the trusted store....but negates to say how.
>
> So...in a complete Microsoft world (RootCA, SubEntCAs and clients)...how
> does the trusted store get populated on a client ? Do you need a GPO or not
> ? Is it a sub-process of auto-enrollment ?

If the standalone certificate is _properly_ published to the the
directory then Group Policy will ensure that is installed on all
Windows clients in the forest. Note that Group Policy is the
publishing mechanism, there's no need to create a specific GPO
to do this.


--
Paul Adare - MVP Virtual Machines
Waiting for a bus is about as thrilling as fishing,
with the similar tantalisation that something,
sometime, somehow, will turn up. George Courtauld


Posted by shudman on December 15, 2006, 5:02 pm
If you were  Registered and logged in, you could reply and use other advanced thread options
Thanks for the reply.
All servers and DCs are Windows 2003 SP1.
The commands I am running are :

certutil -dspublish -f c:\rootca.crt RootCA
certutil -dspublish -f c:\rootca.crl

These are obviously done from a Ent Subordinate CA, which has connectivity
to the AD. Re-running these, actually states that is it is already
published (only cuz I tried again!).

Stuart


> says...
>
>> I have read as many articles/KB that I can and would like some
>> clarification
>> if anyone can,
>> PLEASE!!.
>>
>> We have a standalone RootCA, with Enterprise issuing CAs. We have ran
>> DSpublish for the RootCA into the AD, but clients do not get entries
>> added
>> to
>> their trusted store.
>
> What OS is running on your domain controllers? If you're running
> Windows Server 2003 then you should be publishing the root
> certificate with certutil and not dspublish.
>
>
>> From what I understand, and read many times, is things
>> like: "When you install an enterprise root CA or a stand-alone root CA,
>> the
>> certificate of the CA is added automatically to the Trusted Root
>> Certification Authorities Group Policy for the domain.". Well, if this is
>> a
>> standalone Root, how the heck does it put it into a GPO ? Another
>> article
>> states, that if the client is a domain member, then they will
>> automatically
>> receive the CAs in the trusted store....but negates to say how.
>>
>> So...in a complete Microsoft world (RootCA, SubEntCAs and clients)...how
>> does the trusted store get populated on a client ? Do you need a GPO or
>> not
>> ? Is it a sub-process of auto-enrollment ?
>
> If the standalone certificate is _properly_ published to the the
> directory then Group Policy will ensure that is installed on all
> Windows clients in the forest. Note that Group Policy is the
> publishing mechanism, there's no need to create a specific GPO
> to do this.
>
>
> --
> Paul Adare - MVP Virtual Machines
> Waiting for a bus is about as thrilling as fishing,
> with the similar tantalisation that something,
> sometime, somehow, will turn up. George Courtauld
>



Similar ThreadsPosted
Clients no longer pick up the Root CA as a trusted root authority June 6, 2006, 6:59 pm
Renaming a Certificate Root authority June 28, 2006, 5:16 pm
what type of certificate authority? June 16, 2005, 4:08 pm
Certificate Authority type June 16, 2005, 6:01 pm
Problem with certificate authority January 27, 2006, 9:03 am
Certificate Authority (CA) - Failover Possible? February 24, 2006, 8:20 pm
Microsoft Certificate Authority June 14, 2006, 8:25 am
Problem in Certificate Authority February 23, 2007, 4:09 am
Certificate Authority Settings May 22, 2007, 3:46 pm
Certificate Authority Configuration February 25, 2008, 11:47 pm

The site map in XML format XML site map

Contact Us | Privacy Policy