Windows 2000 and XP

As you are all aware, the DST2007 change took place yesterday.

With XP workstations, there was a patch that was applied.

With windows 2000, you had to modify the registry. I modified the windows registry on the 2k workstations as recoomended by microsoft with a start up script via active directory.
http://support.microsoft.com/kb/914387/en-us

I went around and did "spot checks" usint "tzedit.exe" to verify that the workstation had the correct timezone information.

Exchange 2000 was a whole other story but that seems to be fine via workaround.

Today, users are calling saying that their time didn't change. I look at the workstation and the time zone is set correctly (GMT -5 Eastern Time US and Canada) and there is a check in Automatically adjust clock for daylight saving changes. However, the clock is off by one hour. This is happening on BOTH 2K AND XP workstations...

via command prompt, issue a net time and get this:

Quote:

---

Microsoft Windows XP [Version 5.1.2600]
(C) Copyright 1985-2001 Microsoft Corp.

C:\Documents and Settings\teller02>net time
Current time at \\timesvr is 3/12/2007 8:45 AM

Local time (GMT-04:00) at \\timesvr is 3/12/2007 9:45 AM

The command completed successfully.

---

Where the hell is it getting the GMT -4?
The timesvr machine has the correct time and timezone...

If I change the time zone from GMT -5 Easter Time to GMT -5 Indiana Time and then back again... the time is correctly updated! I don't get it.

DST is technically GMT -4 (for EST timezones) :)

http://wwp.greenwichmeantime.com/time-zone/usa/

Ok, but Windows still calls it GMT -5. The workstations are off by one hour when reading GMT -4. As soon as you change the time zone and put it back, it's fixed.

Note: On the time clock, it does say easter daylight time when the automatically adjust is checked off...

And the checkbox for "Automatically adjust for DST" is checked?

I used the DST download from this site on all my 2000 workstations...

http://www.intelliadmin.com/Daylight...tSavingFix.exe

Have had no issues with time change....although I did not apply to any servers...they are all 2003

MLF

Mittens is correct you are GMT -4 for a few days :p

This sounds like a minor oversight in the work around........... as soon as you change the time and then reset it you are OK? I bet that would be the same as if you started (and therefore ran the script) then rebooted?

A lot of things need bump starting........... with MS it is usually a warm reboot, other stuff like FireFox just need you to close and reopen the application?

Actually, changing the time zone does not fix it.

I have to uncheck the option to adjust the time zone. Press apply. THen check it off again and press apply. Then it is fixed.

Freaking weird.

Phish,
Microsoft uses Pacific Time in the example below, but apparently they wanted users to change the time zone twice to make the fix work. I found this info somewhere in the middle of that MS article you linked.

Quote:

---

h. Click Start, point to Settings, point to Control Panel, and then double-click Date/Time.
i. Click the Time Zone tab.
j. Select a different time zone than the (GMT-08:00) Pacific Time (US & Canada); Tijuana time zone, and then click Apply.
k. Click (GMT-08:00) Pacific Time (US & Canada); Tijuana, and then click OK.

Note Steps j and k are required for the new changes to take effect.

---

I was actually having the same problem with my 2000 clients until I changed the time zone like MS says. BTW, I like that time zone tool - not that it will come in very handy anytime soon :eek:

ShagDevil: Thanks, somehow I overlooked that. It's weird though, this only happened on some of the workstations. It sucks that you have to manually do this. What about users who don't have the permission to change their date/time info? I have to walk around to all workstations and do this. Sucks!

Actaully, that should have been done automagically with the script they provide. That should have run without problem as I put it in a group policy and set it as a startup script (not logon script.)

Some of them worked... some of them didn't. I enabled that script over 2 weeks ago... so you would that it would have worked. Figures...

What I had to do here to "fix" this on Windows 2000 systems that are never turned off was open the clock from the system tray. Click on "time zone". Click on OK. Then I had to do it again. When I clicked OK on the second attempt the time changed to the correct time. For Windows 2000 systems that were turned on this morning I only had to do it once. All of the XP machines handled it just fine.

Interesting to say the least.

Stuart

You know what's interesting about all this: the recent DST change was done so the US gov't could save about 4% off their electrical bill. And yet I wonder how much more was spent adjusting for the time change and for workers to adjust their internal biological clocks to the change?

I wondering the same thing Ms M

When I got up this morning...it was dark...I had to switch on the lights.

Last week it was light at the same time..

and yes it was hard...first to force myself to bed lastnight...and then to drag my butt out of bed this morning.

Its gonna be a looooooooonnnnnnnng day :(

MLF

Quote:

---

Some of them worked... some of them didn't

---

Phish, you must have possessed computers -

Quote:

---

SAVANNAH, Ga.-- Your computer may be possessed by a demon, a leading minister warns. "While the Computer Age has ushered in many advances, it has also opened yet another door through which Lucifer and his minions can enter and corrupt men's souls," said the Reverend Jim Peasboro, author of an upcoming book, The Devil in the Machine.

---

Quote:

---

"Any PC built after 1985 has the storage capacity to house an evil spirit," the minister confirmed. The Savannah clergyman says he became aware of the problem from counseling churchgoers.

---

Here's the fix -

Quote:

---

The minister estimates that one in 10 computers in America now houses some type of evil spirit. Rev. Peasboro advises that if you suspect your computer is possessed, you consult a clergyman or, if the computer is still under warranty, take it in for servicing. He says, "Technicians can replace the hard drive and reinstall the software, getting rid of the wicked spirit permanently."

---

:rofl:


yeah...like my boss is gonna buy that....
Good one

MLF

EDIT> I am hoping I can charge more for exorcising evil spirits from harddrives...thats gotta pay more ;) LOL

Ok, I've determined that all of the workstations had the new registry info. Just not all of them executed the script to refresh the tzinfo.

Oh well, at least I'm not scratching my head anymore.

The PC's could certainly be posessed... There are a couple of people here who beleive that this building is haunted. I've seen some stuff late at night when I'm the only one here working overtime... One incident spooked me so much I get the F out of here and didn't complete my tasks.

Did you see this...
http://isc.sans.org/index.html?on=diary


may explain the ...um...demons

MLF

While you all are experiencing the pain of this update, the Dept. of Energy is tasked with measuring if there is a significant savings by making this change. If they determine there isn't, guess what? You got it. The time change is supposed to go back to the way it was.

So much for progress.

--TH13

PS
I had none of these issues when deploying the DST patch to Win2000 and XP hosts.

I found out that several of our workstations were updated, but they were updating from a time server that didn't refresh the tzinfo. Those were the XP workstations that I was talking about. This affected a couple of my remote/branch offices... but it didn't matter either way. Overall, it wasn't too bad. I was just confused as to why they wern't correct because the tzedit tool claimed they were. The darn refresh... :(

Quote:

---

PS
I had none of these issues when deploying the DST patch to Win2000 and XP hosts.

---

So, what do you want? :D