Server Fault is a question and answer site for system and network administrators. Join them; it only takes a minute:

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

The company I work for still uses Windows 2000 Server for most, if not all of its infrastructure. I recently joined my Vista laptop to the domain and noticed the system clock jumped ahead by an hour. I know the cause of this is because the time is synchronized with the domain server (which has dst turned off, because no one could get the patch working correctly after the law change a few years ago). I turned dst off on my laptop so the time would be correct. The problem I'm having is that every few minutes I see the clock jump ahead again, only to jump back a few seconds later. This is causing problems with a few programs I have that use the system time to determine if files need to be updated.

Any ideas on how to fix this problem? If I haven't given enough information to troubleshoot with let me know and I try to fill in the missing details.


As I mentioned above I don't have access to the PDC or any of the other servers (nor do I want to be held responsible for the results if something gets messed up). For the time being I'm going to turn dst on my laptop back on and change my clock setting to a different timezone and see how that works.

share|improve this question
There are no "PDC" computers in Active Directory. All domain controllers host equal copies of the Active Directory database. There is a "role" held by a single domain controller, "PDC Emulator", but that role only slightly changes the behavior of Active Directory. It's not like NT 4.0 where there is only a single writeable copy of the database. – Evan Anderson Jul 2 '10 at 13:53

Update the Windows 2000 Server machine to the current Daylight Saving Time rules and you'll be fine.

You can use one of the older unofficial patches (which aren't really "patching" files-- they're just updating the registry). If you're in the US and using an English language version of Windows 2000 then you'll be fine (until the next update to DST in the US).

The official Microsoft WayTM appears to include an automated fix tool that may take care of your needs (I haven't tried it). Otherwise, you're stuck making registry modifications by hand.

We made some registry merges to take care of the few W2K Server machines we still had hanging around, but I don't have them handy to give to you.


The only "fix" that won't involve computers being set to the wrong time zone is to update the Windows 2000 Server computer's time zone information. Anything else isn't really a "fix" and will leave you with a mixture of machines set to different time zones even though they're physically in the same time zone.

share|improve this answer
I used TZedit (the Official MS way) on several older machines (Win2000, and Win98) when the law changed several years ago, and had no issues. – BillN Jun 30 '10 at 22:48

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.