Microsoft DST information site

[Smilin]

This should be a first stop for information relating to Daylight Savings changes for MS customers.

http://support.microsoft.com/gp/dst_hottopics

Included in the above site is a link to http://blogs.technet.com/dst2007/ which covers many of the topics I have seen posted today.

Update:
Several potential causes for zone change failures have been identified and are being investigated. Thusfar using the script as a workaround is 100% successful in resolving this. See blog.

**You can probably unsticky this now. Show's over, move along **

 

[bendixG15]

Another molehill made into a mountain by MS.

Just go into the BIOS and change the damm time..easier than reading that BS from MS

 

[ITJunkie]

Originally posted by: bendixG15
Another molehill made into a mountain by MS.

Just go into the BIOS and change the damm time..easier than reading that BS from MS

Fine if you have only one system. Not so great when you're dealing with 150+ Win2k Servers.

Thanks for the link(s) Smilin!

I would only add this Link to the Intelliadmin patch too...which worked very well for me.

 

[stash]

Why the hell would you go into the BIOS to make a DST change??

If you did that, your time would be off by an hour, which would cause much havok wit Kerberos if you are on a domain.

I'm curious why you think it's BS...the four hour hold times last week to talk about DST issues with PSS would seem to indicate otherwise.

 

[Takeoff250]

quote:

--------------------------------------------------------------------------------
Originally posted by: bendixG15
Another molehill made into a mountain by MS.

Just go into the BIOS and change the damm time..easier than reading that BS from MS
--------------------------------------------------------------------------------

Stop eating mushrooms.. Do you know at least what he's talking about?

oh and don't forget to change you're bios time in 3 weeks again....

 

[loup garou]

Originally posted by: bendixG15
Another molehill made into a mountain by MS.

Just go into the BIOS and change the damm time..easier than reading that BS from MS

Talk about boneheaded comment of the week.

 

[IEC]

Originally posted by: bendixG15
Another molehill made into a mountain by MS.

Just go into the BIOS and change the damm time..easier than reading that BS from MS

Alternatively, simply turn off DST altogether and manually adjust the clock. For home users that's fine, for anyone else that's just asking for trouble...

 

[RebateMonger]

<=== so happy right now that he lives in Arizona, which avoids all the DST nonsense.

And, bendixG15, the DST change is MUCH more complex than you might think. Yeah, it's not a big deal in a home. But create a Domain, and communications between computers stops when the time synchronization ends.

 

[Genx87]

It is terrible MS didnt make a patch available to Win2K customers. WinXP and Win2003 were not an issue to deal with as you had a patch you could deploy.

For my lone Win2K box which happens to be our PDC, I had to use a tool to edit the timezones. A simple fix but not something I'd want to do on 150 machines.

 

[Smilin]

Originally posted by: loup garou

Originally posted by: bendixG15
Another molehill made into a mountain by MS.

Just go into the BIOS and change the damm time..easier than reading that BS from MS

Talk about boneheaded comment of the week.

Yeah, that was a pretty bad one.


Bendix, your bios time has nothing to do with timezones. If you do it this way it will just make sure your time is correct in the next zone over. The numbers appearing on your clock in the corner of your screen will appear correact but they will not be. You will be unable to do time sensitive tasks like obtain credentials from a kerberos server. You may also notice things like your emails going out to people with the wrong time. Also, this information is really for enterprise administrators who have to do this on potentially tens of thousands of computers.

For your single machine:
1. Make sure all critical updates have been applied from Windows Update.
2. If your time does not appear correct simply set to a different time zone, hit apply, then set to the correct timezone then hit apply.

 

[Smilin]

Originally posted by: RebateMonger
<=== so happy right now that he lives in Arizona, which avoids all the DST nonsense.

And, bendixG15, the DST change is MUCH more complex than you might think. Yeah, it's not a big deal in a home. But create a Domain, and communications between computers stops when the time synchronization ends.

Yeah, I used to be in Indianapolis back before they observed DST. It's definately the way to go. Too bad they caved in

Even though your state doesn't observe DST be sure your machines are getting the patch ok. If you hit anything cross-state from your network you'll want this working right.

 

[stash]

For my lone Win2K box which happens to be our PDC, I had to use a tool to edit the timezones. A simple fix but not something I'd want to do on 150 machines.

The tool wasn't required, it was just one way of doing it for 2000 machines. You could also run a reg file and a VB script both of which were in a KB article

 

[Genx87]

Originally posted by: stash

For my lone Win2K box which happens to be our PDC, I had to use a tool to edit the timezones. A simple fix but not something I'd want to do on 150 machines.

The tool wasn't required, it was just one way of doing it for 2000 machines. You could also run a reg file and a VB script both of which were in a KB article

I know, but for me the tool was easy to use on a single machine.

 

[kt]

Originally posted by: Genx87
It is terrible MS didnt make a patch available to Win2K customers. WinXP and Win2003 were not an issue to deal with as you had a patch you could deploy.

For my lone Win2K box which happens to be our PDC, I had to use a tool to edit the timezones. A simple fix but not something I'd want to do on 150 machines.

MS did provide a fix for Win2k boxes. Although you do have to do some reading to get the patch working. We used what MS provided to patch all our Win2k boxes via GPO without any problems.

 

[owensdj]

Microsoft messed up big time with the Win2K DST fix. They put a fix on the Windows Update page but it doesn't actually fix anything. You have to manually edit your time zone's DST start and end dates using a utility called TZEdit. I guess now that they're not making money from Win2K anymore they just don't care.

 

[Smilin]

Originally posted by: owensdj
Microsoft messed up big time with the Win2K DST fix. They put a fix on the Windows Update page but it doesn't actually fix anything. You have to manually edit your time zone's DST start and end dates using a utility called TZEdit. I guess now that they're not making money from Win2K anymore they just don't care.

They whipped up a "Y2K" fix in record time. Based on the guys bored half-asleep in the "DST war-room" I would assume the rollout was a phenomenal success.

For Windows 2000 it's just a reghack. Do it by hand if you want

But you're right. Windows 2000 is now SEVEN years old. They are making the fix that is available as a way to help customers, not generate profit. Go compare with say, SUN who isn't providing any fix at all for older Java versions.

Yeah, I'm a fanboy but you're just a thread-crapper so there.

 

[owensdj]

Smilin, I don't think I'm thread crapping. My post was on topic and has important info about the DST fix. My point was if Microsoft didn't want to fix Win2K because it's too old they shouldn't have released a broken fix at all. At least then users would have known they needed to do something on their own to fix the DST change.

 

[Smilin]

Originally posted by: owensdj
Smilin, I don't think I'm thread crapping. My post was on topic and has important info about the DST fix. My point was if Microsoft didn't want to fix Win2K because it's too old they shouldn't have released a broken fix at all. At least then users would have known they needed to do something on their own to fix the DST change.

Is the fix broken? What issues are you having with it?

 

[owensdj]

Smilin, like I said in my first post, the fix for Win2K machines doesn't allow the OS to change the time correctly. The user has to run TZEdit to change the DST Start and End days. This is a problem for users because they're going to think their machine is patched for the new DST, but it isn't.

 

[Smilin]

Originally posted by: owensdj
Smilin, like I said in my first post, the fix for Win2K machines doesn't allow the OS to change the time correctly. The user has to run TZEdit to change the DST Start and End days. This is a problem for users because they're going to think their machine is patched for the new DST, but it isn't.

I understand that. But please understand that Windows 2000 only has one set of settings per time zone. When this came along there was no easy way to fix this. If congress does something nutty at this point the extra settings in 2003 will already be exhausted and you'll see the same sort of problem on it.

You're asking MS to magically go back to 1999 and predict an issue that occurs 8 years in the future. If congress goes and splits the US into 12 time zones you think Windows 2000 is going to be the very first thing MS fixes? At least there is a fix available. Use it or don't. It's the best you're going to get when a miniature y2k gets thrown on everyone with little notice.

Also, instead of bitching about how awful MS has handled this you could be thanking them for handling it at all.

Per Apple:
If you're still using Mac OS X 10.2.8 or earlier, you can adjust your clock manually using Date & Time preferences. Deselect the option to set date and time automatically, then set the time for your local time zone as needed.

...and don't forget to repeat twice a year forever.