DST Update for Windows 2000 computers connected to 2003 domain

[chuck2002]

Microsoft isn't providing a DST time patch for Windows 2000. They provide an executable to use to change the time on each computer.
I have a Server 2003 domain and the computers get time from the domain controllers at login, so I am wondering if this will take care of the time change for me on the sprinkle of old windows 2000 computers I have.
If not, what are you all doing to update the Windows 2000 computers without having to visit each one?

 

[stash]

so I am wondering if this will take care of the time change for me on the sprinkle of old windows 2000 computers I have.

No.

The time service in Windows (w32tm) uses UTC time always. The timezone is applied afterwards, by each computer locally.

In AD, it is critical that you do not adjust the time manually. For instance, say you apply the patch to a 2003 DC and it is currently 12pm EST. For w32tm and Kerberos, the time is 1700. When your 2000 machine syncs with the DC, it will sync to 1700. But if you don't patch the machine, the clock on the system will read 11am (because DST will start earlier this year). If you were to manually bump up the clock on the 2000 machine by an hour, you would break Kerberos authentication between the 2000 server and any other machines. This is because the 2000 machine would now think it is 1800 UTC, even though the clock would read 12pm EST.

 

[nweaver]

so...you can't fix it, and MS is not fixing it for us?

OP, the only other option I can think of is a GPO to change timezones?

 

[tyanni]

http://support.microsoft.com/kb/914387

 

[stash]

Originally posted by: nweaver
so...you can't fix it, and MS is not fixing it for us?

OP, the only other option I can think of is a GPO to change timezones?

We are fixing it, as the article below shows. The TZEdit manual fix can be scripted and put into a GPO pretty easily. You can also purchase a patch for 2000 for $4000 if you have a Premier contract (or you can convert existing hours from your contract).

The patch was originally being offered for $40,000 as part of an extended support contract, but you can now get it for the 4k price, and you do not need to get an extended support contract.

OP, the only other option I can think of is a GPO to change timezones

Which is essentially what the TZEdit fix in the article does. If you script it and put it in a GPO, you're done.

 

[RebateMonger]

Speaking of the DST boondoggle:

Pretty much all my clients are in Arizona, which does NOT practice Daylight Savings Time. We use the special "Arizona" time zone in Windows, which is GMT -7 and NEVER changes. If I didn't want to, I could leave all my Servers unpatched for the DST changes and it would have NO effect on my Servers, right?

The reason I'm curious is that I have an ex-client that has a Windows Server 2000 as their sole Domain Controller. I doubt that anybody is managing their Servers anymore, so I'm wondering if I should expect a phone call from them on March 11 when their XP clients stop talking to their Server? But, I think not....or am I missing something?