I have a GroupPolicy set up to sync all machines on my network to the time on a domain controller, which is server2003 and which had the right time automatically.
But I still had to use this fix on all my server2000 machines.
But I still had to use this fix on all my server2000 machines.
That's because the vast majority of networked computers don't actually use local time for synchronization. They use UTC (Universal Time Coordinated), which is Greenwich Mean Time, without DST. The local time that they display is an offset of UTC, based on the time zone and DST settings.
MS included the DST fix last year as part of the Windows Updates for XP and Windows Server 2003, but not for Windows 2000. Instead, in order to change the start and end dates for those systems, just download TZEDIT from Microsoft. It's easy to use and completly self explanatory. If the computer system isn't updated with the date for the earlier change over for DST, the local time change won't be seen until the old, later DST start/end date rolls around.
If this seems like a pain in the butt, it's really not, once you get used to it, plus it's extremely important for keeping servers and databases synchronized across multiple time zones.
Mark
Add the .exe or a .bat for the .reg to the Default Domain Controller GPO Startup/Script. That way you can set the dates months out and forget it.