Skip Links

Network World

  • Social Web 
  • Email 
  • Close

Daylight-saving time issue reappears on IT radar

Applications, servers, desktops added after March 11 need check before Nov. 4 to ensure they have daylight-saving time patches
By John Fontana , Network World , 09/17/2007
  • Share/Email
  • Comment
  • Print

The daylight-saving time scramble of last spring may be in need of a cleanup this fall for companies that spent the summer rolling out new servers, desktops and time-sensitive applications.

On Nov. 4, clocks will “fall back” to standard time, but companies with systems that are not patched will fall back a week early throwing off calendars, transaction systems and anything that relies on clock time for accuracy and execution.
daylight-saving time (DST) comes to a close one week later this year – Nov. 4 instead of Oct. 28 – as part of the Energy Policy Act of 2005.

DST began three weeks earlier this year, kicking off March 11. That milestone had corporate users scrambling to patch systems so they would not suffer time-related hiccups in their operating systems, applications and other infrastructure.
Early this year, most major IT vendors, including Cisco, IBM, Microsoft, Novell, Red Hat and Sun rolled out DST fixes for their products.

Daylight-saving time checklist
"Fall back" has another meaning this year as corporations return to the daylight-saving issues they corrected in the spring and recheck systems rolled out since then to assure they are patched.

Take inventory of servers, desktops and applications that were rolled out after March 11, the day daylight-saving time kicked in this year.
Focus particularly on Window PCs, Java programs, calendaring, billing and other time-related applications.
Check with vendor Web sites to confirm what patches are needed and validate those patches are installed.
Verify that Windows desktop and servers using automatic updates via Windows Server Update Services have downloaded and installed patches.
Check other copies of Windows-based systems, especially those that are not automatically updated.
Complete testing by Oct. 28. That is the day unpatched systems will revert to standard time, which is one week before the new date Nov. 4.
Be aware that network time servers will not solve the problem.
Click to see: Daylight-saving time check list

Now the “fall back” side of the DST issue could be a problem for those who rolled out new computers or applications after March 11. If those systems have not been updated with the correct DST patches they will revert to standard time a week early.

“That will make you an hour late to all your meetings,” says Eric Schultze, chief security architect for patch vendor Shavlik Technologies. “Companies without patch management processes that scrambled in March are going to scramble again.”
Schultze says machines that were patched last spring are set. “It is the computers you just bought last month that might not  have the patches on them or the systems you have rebuilt that need the patch reapplied,” he says.

  • Share/Email
  • Comment
  • Print
Partner Content

SMART Steps Toward Consolidated Workload Automation

Consolidating job scheduling into a single, comprehensive workload automation solution is a critical first step to effective workload automation (WLA).

White paper on WLA here


A Comprehensive Approach to Practicing ITIL Change Management

Read a compelling whitepaper by EMA, Inc. to learn best practices for integrating workload automation.

Whitepaper here

2 Minutes to IT workload automation

BMC CONTROL-M can put money back into your IT budget and strip the complexity and risk from workload automation.

View video here

Gain a faster, cheaper way to manage workload

BMC CONTROL-M can help you migrate to a workload automation solution to meet your organization’s goals.

Listen here for more info

Comments (5)
Login
Forgot your account info?

Maybe you should look around you...By Anonymous on September 24, 2007, 6:45 pmThe US is not the only country changing its time. New Zealand is moving its change to Daylight Saving to September 30th which is 1 week earlier than typical.

Reply | Read entire comment

A very US centric articleBy Doug Blake on September 21, 2007, 7:54 amYou call yourself Network World and then distribute articles like this that make out the only place in the world is the US. Its only you guys decided to change your...

Reply | Read entire comment

FixedBy Adam Gaffin on September 20, 2007, 10:31 amWe'll just have to make like that mattress company with the 800 number and leave off the last 'S' for saving.

Reply | Read entire comment

Article doesn't mention somethingBy westside guy on September 20, 2007, 1:48 amOkay, this past Spring we - like many businesses - had significant issues with Outlook calendars on fully patched Windows XP SP2 boxes connected to a fully patched...

Reply | Read entire comment

RE: Daylight Savings Time issue reappears on IT radarBy Brian Purcell on September 18, 2007, 8:54 amActually, it's "Daylight Saving Time" (no "s" on "Saving").

Reply | Read entire comment

View all comments

Add comment
Anonymous comments subject to approval. Register here for member benefits.
Have a NetworkWorld account? Log in here. Register now for a free account.

Videos

rssRss Feed