Presentation on theme: "Daylight Savings Time Phillip Morgan, COT CTC Meeting February 2007."— Presentation transcript:
Daylight Savings Time Phillip Morgan, COT CTC Meeting February 2007
Daylight Savings Time Definition and Objective Operating Systems Applications Questions
On August 8 th 2005, the Energy Policy Act of 2005 was signed. Section 110, amends the Uniform Time Act of 1966 to change the beginning and ending of daylight-saving time (DST). Effective 1 March 2007, DST begins almost one month earlier on the second Sunday of March (March 11 th instead of the first Sunday in April) and ends on the first Sunday in November (November 4 th instead of the last Sunday of October). Definition
Identification of Risk Items to look for during a risk assessment Internal clocks / calendar with time zone and DST tables Local time vs. Coordinated Universal Time (UTC) May or may not be synchronized with a time service via NTP (Network Time Protocol) Calendar / scheduling applications Transaction logging (UTC vs. Local Time) Calendaring with time zone and DST tables. (Outlook and Exchange) Systems for logging of transactions (Universal Time)
If you employ the use of external service providers, check with them to see whether they are taking appropriate steps to mitigate risk. Plan on having time-critical jobs scheduled so that they are guaranteed to finish before the time transition (or delayed until after it). Begin now to schedule operations and other support staff to be available during the changeover. Outputs of Risk Assessment
Mainstream Support –Windows Server 2003, Windows XP SP2, Exchange 2003, Exchange 2007 Premier customers receive remediation assistance at no charge from February 1 to March 1, 2007 Extended Support –Windows 2000, Exchange 2000, Outlook 2000 Extended Support for all is $4,000 Custom Support –Windows NT4, Exchange 5.5, Windows XP SP1 Custom Support Agreement Premier Customer Support Fee in Arrears Hotfix fee
Patch Deployment GPO’s for distribution Windows Update Distribution Tool Desktops and Laptops will need attention Home Computers
UNIX COT has patched supported servers at Cold Harbor or has scheduled installation times. Patches are available from vendors for supported versions.
z/OS Patches have been applied. Applications that use WebSphere 5 may have issues.
Users should be made aware of the calendar issues resulting from Daylight Saving Time changes. Only the users will know if their appointments are correct. Appointments scheduled during the delta period (March 11 th – April 1 st ) need to be reviewed and considered suspect. Users need to know that they will have to verify the meeting times themselves and with any other attendees. Using informal methods such as documenting the meeting time in the subject or body of the meeting request may be beneficial. Outlook
User Participation Consider including Start Time in Subject Run DST Tool after patches are applied Run DST Tool on Public Folder Calendars Stay aware of calendar appointments May see a large number of “Updates” Manual corrections should be a last resort Assemble help desk scripts
Conclusion Assess any potential ramifications for Cabinet-Agency technologies and applications. Construct a project management team now as a central clearinghouse for all DST remediation and research efforts. Develop hotline where questions can be fielded from potentially affected individuals and organizations. Review your technology inventory and ascertain which products are supported. Check with vendors regarding the relevant patching programs. Follow formal change & release management procedures, If you employ the use of external service providers, check with them to see whether they are taking appropriate steps to mitigate risk. Plan on having time-critical jobs scheduled so that they are guaranteed to finish before the time transition (or delayed until after it). Begin now to schedule operations and other support staff to be available during the changeover.