[ShiftAltNumlock]

I have Windows 2000 server with BES 4.1 installed on it. It is a domain controller. I have my Exchange 2003 server running on Windows 2003 server. Is this going to be a problem with the DST 2007 issue? MS does not appear to be making a patch for 2000.
don't I have to patch the machine with BES on it also?

[Zro]

This could very well cause issues. You may see that calendar appointments between March 11th and April 1 show up on the handheld 1 hour late.

I'd say find some way to upgrade Windows or force MS to give you a patch

Zro

[Ekrimmer]

Microsoft doesn't have an actual patch for Windows 2000 but they have made available tzedit - a tool that lets you modify the existing DST rules.

How to configure daylight saving time for the United States in 2007

[edonin]

I wound up using their sample registry and vbs file templates found on the same "How to configure daylight saving time for the United States in 2007" web page, deploying it as group policy.

The registry/vbs file combo has been working fine and was a whole lot less labor intensive than using the TZEdit tool. (I had to use that sucker for our legacy worldwide NT boxes and that killed half a morning going through each time zone manually). Beat a sharp stick in the eye though.

[ShiftAltNumlock]

Ekrimmer and edonin, I very much thank you for point me in the right directions. I will check these strategies and deploy 1 or both, which ever works best for my situation. Again, thank you! I have been dealing with the AdminSD holder issue and finnaly got that resolved, and then this thing came up. I thought I was going to have to install 2003 on my BES just so I could get the DST update. I will let you know when I have completed to work.

Update: Thanks guys, I have updated my BES + 10 other Windows 2000 servers. It worked like a charm.

BTW: I choose to use the VBS script + regedit. It took longer to read about and put the files together than it di to apply the fix to all servers. Much better idea than upgrading to Win2003.