I figure most of the people who need this warning aren't the kind of people who will get hammered by multiple thousands of client machines.
But yeah. If you have a domain with win2K clients or servers, get 'em *all* updated or either all the 2K or all the XP machiens will break come Monday morning.
Thanks for posting this. The machine that runs my apparatus is Win2K and I had no idea that it would not be automatically updated. (And we are too small to have a dedicated on-site IT person so it's every person for her or himself.)
AZ doesn't use DST. Which means I need to check my computer and any others I use to make sure they've been set with Mountain Standard (AZ) as their time zone. And not just plain MST...
(no subject)
Date: 2007-03-05 06:40 pm (UTC)(no subject)
Date: 2007-03-05 07:04 pm (UTC)But yeah. If you have a domain with win2K clients or servers, get 'em *all* updated or either all the 2K or all the XP machiens will break come Monday morning.
(no subject)
Date: 2007-03-05 07:05 pm (UTC)(no subject)
Date: 2007-03-05 07:27 pm (UTC)(no subject)
Date: 2007-03-05 07:48 pm (UTC)(no subject)
Date: 2007-03-06 12:38 am (UTC)(no subject)
Date: 2007-03-06 01:34 am (UTC)