Unofficial Windows 2000 Daylight Saving Time Fix

This year (2007), we’re going to be going into a new Daylight Saving Time. Crazy isn’t it. But the change was proposed two years ago. Unfortunately, Microsoft will NOT be providing patches for Windows versions 2000 and previous. There is a workaround, but it’s not easy. So the guys at IntelliAdmin decided to whip up a patcher for those of us that actually have machines running 2k and before.
And they even provide their source code in case you figure they might be up to no good (the boys at IntelliAdmin know what they’re doing). So off with you, and go patch your 2k. Because we know you still have one of those machines around. Who doesn’t?
Slashdot < IntelliAdmin

  • David Sharpe

    Although I totally understand and appreciate why IntelliAdmin took a stab at a free DST2007 tool, it really should either be fully updated or pulled down entirely. I am afraid that IntelliAdmin is exposing themselves to unnecessary liability risk by having some serious defects (missing required functionality) in the provided code. The code does hit the right registry entries for the US and Canada, but doesn’t alert Windows itself to the change. Many of those that have used this tool might be disappointed when they find out that the servers and clients that don’t get rebooted might still have incorrect notions of the local time at the DST2007 cutover point. Also, as the author correctly points out, you MUST wait for the Outlook and Exchange tools to materialize from Microsoft prior to rolling out any OS DST2007 fix (if you use either Outlook on Exchange in your shop). To the authors of the tool I can only point out that “No good deed goes unpunished”. To everyone else, the authors were just trying to help and provide something FOR FREE, so please don’t judge them too harshly. The instructions that Microsoft offers now DO WORK. For the truly lazy, there is a tool available at http://www.sharpebusinesssolutions.com/dst2007.htm that covers NT4, Windows 2000 Pro and Server, Windows XP, Windows Server 2003, and Vista (yes it needs edits for Newfoundland and Western Australia).

  • David Sharpe

    Although I totally understand and appreciate why IntelliAdmin took a stab at a free DST2007 tool, it really should either be fully updated or pulled down entirely. I am afraid that IntelliAdmin is exposing themselves to unnecessary liability risk by having some serious defects (missing required functionality) in the provided code. The code does hit the right registry entries for the US and Canada, but doesn’t alert Windows itself to the change. Many of those that have used this tool might be disappointed when they find out that the servers and clients that don’t get rebooted might still have incorrect notions of the local time at the DST2007 cutover point. Also, as the author correctly points out, you MUST wait for the Outlook and Exchange tools to materialize from Microsoft prior to rolling out any OS DST2007 fix (if you use either Outlook on Exchange in your shop). To the authors of the tool I can only point out that “No good deed goes unpunished”. To everyone else, the authors were just trying to help and provide something FOR FREE, so please don’t judge them too harshly. The instructions that Microsoft offers now DO WORK. For the truly lazy, there is a tool available at http://www.sharpebusinesssolutions.com/dst2007.htm that covers NT4, Windows 2000 Pro and Server, Windows XP, Windows Server 2003, and Vista (yes it needs edits for Newfoundland and Western Australia).