Signed into law in August 2005, the federal Energy Policy Act of 2005 moved the start of DST from the the first Sunday in April to the second Sunday in March and delayed the return of standard time in the autumn by a week, to the first Sunday in November. The idea: Shifting the time change by a few weeks can save on energy use.
For IT, that means every software and hardware system relying on time stamps should now be checked, evaluated and tested — and, if need be, patched with software updates or modified to work properly. But with a wide range of security issues, compliance requirements, spam-fighting efforts and other concerns already on their to-do lists, many IT administrators are only now evaluating what the DST change will mean and how they need to respond.
Read this article from ComputerWorld with commentary from ZDNet
