Check DC time

We have a domain with around 120 DCs across various parts of the world,
and it appears there is at least on rogue DC with incorrect time
settings. Is there any tool available to check the time on all the DCs
and report back any anomalies?

"EMB" <> wrote in message
news:hm5f7q$ac1$...

> and it appears there is at least on rogue DC with incorrect time

How does "it appear"? If you know it is happening then why don't you know
what DC it is? By the same token, if you don't know what DC it is, then how
to you know it is even happening?

--
Phillip Windell

The views expressed, are my own and not those of my employer, or Microsoft,
or anyone else associated with me, including my cats.
-----------------------------------------------------

On 26/02/2010 4:28 a.m., Phillip Windell wrote:
> "EMB"<> wrote in message
> news:hm5f7q$ac1$...
>
>> and it appears there is at least on rogue DC with incorrect time
>
> How does "it appear"? If you know it is happening then why don't you know
> what DC it is? By the same token, if you don't know what DC it is, then how
> to you know it is even happening?

A client computer set to the correct time on a subnet not defined in
sites and services (ie it will randomly select a DC for authentication)
will refuse to log on due to a time difference with the DC.

Manually checking every DC is not a realistic option.

"EMB" <> wrote in message
news:hm9eei$f31$...
> On 26/02/2010 4:28 a.m., Phillip Windell wrote:
>> "EMB"<> wrote in message
>> news:hm5f7q$ac1$...
>>
>>> and it appears there is at least on rogue DC with incorrect time
>>
>> How does "it appear"? If you know it is happening then why don't you
>> know
>> what DC it is? By the same token, if you don't know what DC it is, then
>> how
>> to you know it is even happening?
>
> A client computer set to the correct time on a subnet not defined in sites
> and services (ie it will randomly select a DC for authentication) will
> refuse to log on due to a time difference with the DC.
>
> Manually checking every DC is not a realistic option.

There should not be any subnets "not defined" in Sites & Services.

Assign all the "unassigned" Subnets to a correct Site.

Wait to see what machine has problems after that,...the DC in the same site
will be the one with the time problem. If there is more than one DC in the
Site,...and one has a PDC role,...then that is the DC. If there are
multiple DCs in the Site, and none have the PDC role,...then at least you
narrowed it down to the smaller number of DCs in the one Site.

--
Phillip Windell

The views expressed, are my own and not those of my employer, or Microsoft,
or anyone else associated with me, including my cats.
-----------------------------------------------------

In message <hm9eei$f31$> EMB <> was
claimed to have wrote:

>Manually checking every DC is not a realistic option.

It occurs to me that this shouldn't be substantially difficult to script
since the time is remotely queryable.