Computer Performance, Windows 2003 Vista Best Practice

Daylight Saving Time (DST) - Starts Sunday March 11th

Daylight Saving Time (DST 2007)

March 11th is 'D' day.  Beware, next Sunday is the start of the new American Daylight Saving Time (DST 2007).  To recap on the problem, in previous years, Microsoft operating systems had the built-in ability to adjust their clocks for the one hour spring forward (and the one hour fall back each autumn).  However, XP and Windows Server 2003 don't understand that the America government has brought in a new decree for energy saving; as a result, DST 2007 has been brought forward three weeks, and will start on March 11th.

Problems Caused By DST

A key problem is domain authentication, Domain Controllers only allow a 5 minute time discrepancy for authentication.  On March 12th users may not be able to logon to their domain because they are 1hr out of synch with their servers.

Other more general consequences of DST include:

  • Exchange and Outlook email problems
  • Tariff billing applications - Peak rate phone calculations incorrect
  • Transaction logging errors (UTC vs. Local Time)
  • Niche industries such as stock traders and online-auction bidding
  • Calendar programs (Would it matter if people missed meetings!)
  • Backup / Restore problems, due to incorrect dates in the journals, restore is impossible

Who will be affected by the DST problem?

Directly affected: USA, Canada and Bermuda
Indirectly: Anyone who has business links to computers in America.

Neither Paul, nor I, is a professor of DST, therefore I suggest you double check your local situation, try 'Googling': DST YourCountry.  As an example, I cannot fully understand the situation of DST in Mexico.

As an aside, I wonder how countries, which have always had non-standard rules for summer time, managed in previous years.  Perhaps research may predict what, if anything, will happen in the USA on March 11th.  Australia maybe the place to start such summer time investigations.

What to do if you are in one of the affected areas?

Paul DeBrino has kindly researched these articles for Exchange, Outlook and XP.  Their content is comprehensive, but it does require careful sifting so that you apply the correct to fix for your particular combination of Microsoft products.  Perhaps the best advice is what ever you decide to do, do it to ALL your machines.

http://support.microsoft.com/gp/dst_topissues

http://support.microsoft.com/?kbid=930879 (Look for PDF files rather than .xps)

http://office.microsoft.com/en-us/outlook/HA102086071033.aspx

If you are looking for good network and server utilities, then check out Tools4Ever

Positive Spin-offs from DST

The DST threat is a classic opportunity for medium sized companies to ask for an extra budget to create a test network.  For smaller companies, or meaner financial directors, at least ask for money to buy VMware, so that you can perform experiments on DST.  Now I know it's easy for me to say, 'ask for more IT budget', but I truly believe that you are always allowed to ask nicely for more resources.  Often it's only the steady drip of such well timed requests that eventually breaches the financial director's defences.

On a lighter note I will tell you what my friend 'Barking' Eddie is doing about DST.  One fact you should know about Eddie is that he is a doom and gloom merchant.  Another fact is Eddie's favourite saying is, 'Where there is muck there's brass'.  It's no surprise then, that Eddie is looking for a chance to make money out of misfortune.  He lectured me on how the stock market will crash as a result of DST, also something about a Triple Witching hour, and how he is betting that on March 12 the DOW index would open-up, down; it sounded gibberish to me.  Nevertheless, I took his point that where there is a problem, there is an opportunity.

Will and Guy's Humour

In times of adversity you have to laugh; I wonder how these funny political systems would react to DST?

 

 *


Google

Web  This website

Review of Orion NPMGuy Recommends: Orion's NPM - Network Performance Monitor

Orion's performance monitor is designed for detecting network outages. A network-centric view make it easy to see what's working, and what needs your attention.

This utility guides you through troubleshooting by indicating whether the root cause is faulty equipment or resource overload.

Download a free trial of the Network Performance Monitor

 

Home Copyright © 1999-2009 Computer Performance LTD All rights reserved

Please report a broken link, or an error.