Well... the funny thing is that our Mirosoft TAM (Technical Account Mgr) even confided that MS can't fix it all. If you're on XPSP2, you're safe. If you're using Outlook for mail, make sure you do an Office Update to patch Outlook. Other than that, we were pretty much told "Good Luck!"
Our environment has MANY 2000 workstations and almost 150 Win2000 Servers. We had to pay for an extra patch for those machines. Our NT4 servers (as few as they may be) are up the creek without a paddle. We migrated them to VMs.
If you're a home user, I'd suggest patching current with whatever OS you're using and see what happens. If your time doesn't tick over, manually set it and Google for a fix.
Here are patches for 98 and up:
http://www.intelliadmin.com/Daylight%20Saving%20Fix%20Download.asp
I tried it on mine (and I'm typing from it now). No problems.
Thanks, I appreciate the explanation.
We have SP2 so I guess we will be fine. I will make sure it changes, but we should be fine. ;)
I know how you feel! We've got 120 Windows 2000 Terminal Services servers, plus another 20 or so Win2k servers, and 25 Windows 2003 servers. We've been busy! We use some ADP/Oracle software for time cards, and that update on just 2 Win 2003 servers took more than 6 hours!
And we've got about 2400 Windows 2000 workstations, remote, and NOT on our domain, so we couldn't push out the registry fix using a GPO! The help desk had to run the registry fix on every one of those computes!
Oh, and 1 Novell server!
Mark
How come you could not use TZedit on your NT4, and 2000 systems?