Networks

Ask something
Discussion Locked

Dealing with 2007 DST

0 helpful
4 replies

by tech06

Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.

I was wondering how do other IT admin handle this upcoming DST change. We already have 70 client computers on Win98/2000/XP that sync the clock to the domain server through a logon script and the server has been patched with the DST update. Is it still required to install TZEDIT.exe (or KB928388 for XP sp2) on each client computer?

Thanks for all input.

4 replies

by drastikdmedia

We are trying how to go about this issue also for our POS division. We service over 100 locations and need a way to push out a script to all the servers and terminals. Unfortunately we do not have a scripter.

by jasonsantiago1

Try using Sysinternals psexec tools they can allow you to remotely deliver the script to your systems.

Jsantiago

by davidlsharpe

Thanks for pointing this out. IT professionals worldwide need to be cognizant of the DST2007 problem, especially if your organization, your organizations customers, or your partners have a physical or electronic presence in the United States or Canada. There is a small but growing body of information available online to help address the DST2007 problem. For example, there is a tool available at sharpebusinesssolutions.com/dst2007.htm to help with one of the toughest parts of the problem - unsupported versions of Microsoft Windows.

by techbro

I was a late adopter of the value and power of Group Policies (GP), but is was a HUGE help in dealing with the DST fixes.

One of my clients has a network with both WinXP and Win2K clients. The XP clients were easy, I just made a script that forced all XP clients to run Microsoft's TZmove application.

For the Win2K folks, I had to really get the GP religion and do this the Microsoft Way. If you follow the links on the Microsoft site, and respond as an IT professionsl, you will eventually end up at a very detailed, step-by-step method on creating a regisitry patch and pusing it through GP. It took me about 90 minutes in all (read the directions a couple of times so you'll have an idea of what awaits). I thne force rebooted all of my Win2K machines, and pow!, the fix was applied. I was on pins and needles the whole time, but it worked and saved me a ton of time.

The link to Microsoft's DST page is:
http://support.microsoft.com/gp/cp_dst

This discussion is closed to new replies.