None of this makes any sense.

I run an enterprise with 2003 servers and XPSP2 workstations. I'll
use mine as an example. Yesterday, my time was an hour off.
Understandable. So I downloaded the patch for DST. Like magic, the
time reads correct. Sometime during the day, it went ahead an hour.
(???) All our servers, including DHCP are patched and showing the
right time so why is the time advancing itself again? I've got an
office full of machines that say either 3pm, 4pm or 5pm. Is this the
new hell for the next 3 weeks?

Thanks!

Tom wilson wrote:
> None of this makes any sense.
>
> I run an enterprise with 2003 servers and XPSP2 workstations. I'll
> use mine as an example. Yesterday, my time was an hour off.
> Understandable. So I downloaded the patch for DST. Like magic, the
> time reads correct. Sometime during the day, it went ahead an hour.
> (???) All our servers, including DHCP are patched and showing the
> right time so why is the time advancing itself again? I've got an
> office full of machines that say either 3pm, 4pm or 5pm. Is this the
> new hell for the next 3 weeks?
>
> Thanks!
>
If you manually adjust the time you should be fine until
1. the first Sunday in April?
2. the last Sunday in October?
3. the first Sunday in November?

The ultimate suggestion is to move to Arizona or Hawaii. <g>

Bill

The workstations are probably syncing to an unpatched server.

John

Tom wilson wrote:

> I tried manual, the time just goes back. Many of our drive shares and
> our terminal services are returning the error "There is a time
> mismatch between the client and the server" so I manually set the
> workstation to the server and I get the same error.
>
> It would be nice if Microsoft gave 2 craps but instead I'm once again,
> spending days and days on newsgroups and message boards, ripping my
> hair out as the office loses it finding nothing but "I have the same
> problem". I hate this garbage.
>
> Thanks for the reply.
>
>
> On Mon, 12 Mar 2007 15:47:12 -0700, Bill Sharpe
> <(E-Mail Removed)> wrote:
>
>
>>Tom wilson wrote:
>>
>>>None of this makes any sense.
>>>
>>>I run an enterprise with 2003 servers and XPSP2 workstations. I'll
>>>use mine as an example. Yesterday, my time was an hour off.
>>>Understandable. So I downloaded the patch for DST. Like magic, the
>>>time reads correct. Sometime during the day, it went ahead an hour.
>>>(???) All our servers, including DHCP are patched and showing the
>>>right time so why is the time advancing itself again? I've got an
>>>office full of machines that say either 3pm, 4pm or 5pm. Is this the
>>>new hell for the next 3 weeks?
>>>
>>>Thanks!
>>>
>>
>>If you manually adjust the time you should be fine until
>>1. the first Sunday in April?
>>2. the last Sunday in October?
>>3. the first Sunday in November?
>>
>>The ultimate suggestion is to move to Arizona or Hawaii. <g>
>>
>>Bill
>
>

I tried manual, the time just goes back. Many of our drive shares and
our terminal services are returning the error "There is a time
mismatch between the client and the server" so I manually set the
workstation to the server and I get the same error.

It would be nice if Microsoft gave 2 craps but instead I'm once again,
spending days and days on newsgroups and message boards, ripping my
hair out as the office loses it finding nothing but "I have the same
problem". I hate this garbage.

Thanks for the reply.


On Mon, 12 Mar 2007 15:47:12 -0700, Bill Sharpe
<(E-Mail Removed)> wrote:

>Tom wilson wrote:
>> None of this makes any sense.
>>
>> I run an enterprise with 2003 servers and XPSP2 workstations. I'll
>> use mine as an example. Yesterday, my time was an hour off.
>> Understandable. So I downloaded the patch for DST. Like magic, the
>> time reads correct. Sometime during the day, it went ahead an hour.
>> (???) All our servers, including DHCP are patched and showing the
>> right time so why is the time advancing itself again? I've got an
>> office full of machines that say either 3pm, 4pm or 5pm. Is this the
>> new hell for the next 3 weeks?
>>
>> Thanks!
>>
>If you manually adjust the time you should be fine until
>1. the first Sunday in April?
>2. the last Sunday in October?
>3. the first Sunday in November?
>
>The ultimate suggestion is to move to Arizona or Hawaii. <g>
>
>Bill

Tom wilson wrote:
> I tried manual, the time just goes back. Many of our drive shares and
> our terminal services are returning the error "There is a time
> mismatch between the client and the server" so I manually set the
> workstation to the server and I get the same error.
>
> It would be nice if Microsoft gave 2 craps but instead I'm once again,
> spending days and days on newsgroups and message boards, ripping my
> hair out as the office loses it finding nothing but "I have the same
> problem". I hate this garbage.
>
> Thanks for the reply.

Forget the time. Set the DATE ahead one month.