The U.S. Energy Policy Act of 2005 has extended Daylight Saving Time by approximately four weeks. Starting with the second Sunday in March 2007, Daylight Saving Time will begin three weeks earlier and end one week later than previously observed.
Updating the time zone definitions using the Automatic Update patch provided by Microsoft® (which comes standard on Windows Vista) will overwrite the singular time rule used in North American Time Zones. As a result, all software that directly or indirectly uses the Operating System to translate time will retroactively and incorrectly believe that Daylight Saving Time also began on the second Sunday in March in previous years.
The changes to North American Daylight Saving Time and their implementation in Windows can affect software in subtle ways. At ipMonitor, we've given this issue much thought and thorough testing.
With the release of the latest build of the software, we have updated our existing internal database of Daylight Saving Time rules. Customers running up to date versions of ipMonitor (version 8.06, Build 1130 as of February 8, 2007), do not need to concern themselves with whether Microsoft's update will negatively impact their network monitoring system.
ipMonitor 8.06, Build 1130 (and up) will correctly adhere to the new Daylight Saving Time rules on all of the following Operating Systems:
To assist you with determing whether your system is ready to properly handle the changes to Daylight Saving Time, we've queried your Operating System's Time Zone settings. The results displayed below the table explain the way your Operating System will handle Daylight Saving Time from 2004 to 2009.
For additional information regarding the new Daylight Saving Time rules and their impact, refer to the following Microsoft articles:
For information on other features and concepts related to those discussed in this article, refer to the following ipMonitor resources:
Last Updated: February 13, 2007 | What did you think of this topic?