Okay some more information for you. Interesting how this coule be a one off as “Congress retains the right to resume the 2005 Daylight Saving Time schedule once the Department of Energy study is complete”
UPDATE #1: Just found this too. it would seem that TWO calendar update tool are going to be avaialble. It looks like the Outlook Tool will run against a user, so I suspect the Exchange Tool will just do a batch conversion for ALL the users on a server. One for users and one for administrators to run. To modify a users mailbox, the Exchange Tool is going to need “god” access to all the mailboxes, so you will need an account setup with the right permissions. What will be interesting is how the tool works? Will it just update the meeting request or will it update and then send out a change to all the attendees? If it does the later and you batch the messages on the server, make sure you have enough log disk space and you do it out of hours. We will have to wait and see what the tool does. Check out: http://support.microsoft.com/kb/931667. Right down the bottom. Q: How does the Exchange tool compare to the Time Zone Data Update Tool?
A: The Exchange tool will allow you to apply the time zone update in ‘silent mode’ to a set of chosen mailboxes on the Exchange server. This will mean the user will not have a chance to uncheck appointments that do not need updating.
The Exchange tool only works on server-side calendars. This means that any local Calendars that a user might have, such as in PST stores, can only be updated by the client-side Time Zone Data Update Tool.
and in http://office.microsoft.com/en-us/outlook/HA102086071033.aspx under “Steps you need to take” #4 Run the Time Zone Data Update Tool to update Outlook calendars that are saved on servers running Exchange and on individual computers. End users use the Time Zone Data Update Tool. IT administrators use the Exchange version of the update tool.
Source: http://en.wikipedia.org/wiki/Dst
Rationales for DST: One of the major reasons given for observing DST is energy conservation. Theoretically, the amount of residential electricity needed in evening hours is dependent both on when the sun sets and when people go to bed. Because people tend to observe the same bedtime year-round, by artificially moving sunset one hour later, the amount of energy used is theoretically reduced. A 1975 United States Department of Transportation study showed that DST would theoretically reduce the country’s electricity usage by 1% from March to April, if implemented during these months. These numbers have been supported in Mexico, which began implementing daylight saving time in 1996. Evaluations show national savings of 0.7% of national electric consumption (1.3 billion kWh (TWh)) and reduction of peak load by 500 MW.
Part of the reason that it is normally observed only in the early spring, summer, and early autumn instead of the winter months is that the amount of energy saved by experiencing sunset one hour later would be negated by the increased need for artificial morning lighting due to a later sunrise. During the summer most people would wake up after the sun rises, regardless of whether daylight saving time is in effect or not, so there is no increased need for morning lighting to offset the afternoon drop in energy usage. Another reason for not observing daylight saving time in the winter is concern about children walking to school in the dark.
Another argued benefit of DST is increased opportunities for outdoor activities. Most people plan outdoor activities during sunlight hours. Other benefits cited include prevention of traffic injuries (by allowing more people to return home from work or school in daylight), and crime reduction (by reducing people’s risk of being targets of crimes that are more common in dark areas).
When the U.S. went on extended DST in 1974 and 1975 in response to the 1973 energy crisis, Department of Transportation studies found that observing DST in March and April saved 10,000 barrels of oil a day, and prevented about 2,000 traffic injuries and 50 fatalities saving about U.S. $28 million in traffic costs.
Source: http://www.worldtimezone.com/daylight.html
| Date |
Country changing DST time |
Description |
| Mar 2007 |
USA |
All States except:
i) Hawaii
ii) Arizona (the Navajo Indian Reservation in Arizona observes DST).
iii) American Samoa, Guam, Arizona, Puerto Rico, the U.S. Virgin Islands
Dates: 11-Mar 2007 to 04-Nov 2007 |
| Mar 2007 |
Canada |
All States except Saskatchewan and parts of Quebec, B.C., and Ontario
Dates: 11-Mar 2007 to 04-Nov 2007 |
| Mar 2007 |
Bermuda |
All of Bermuda
Dates: 11-Mar 2007 to 04-Nov 2007 |
DST 2007 changes for US, Canada and Bermuda
This information applies to users in the areas of the United States and Canada that observe daylight saving time.
For the latest information on DST 2007 check out: http://www.microsoft.com/windows/timezone/dst2007.mspx
On August 8, 2005, President George W. Bush signed the Energy Policy Act of 2005. This Act changed the time change dates for Daylight Saving Time in the U.S. Beginning in 2007, DST will begin on the second Sunday in March and end the first Sunday in November. The Secretary of Energy will report the impact of this change to Congress.
Congress retains the right to resume the 2005 Daylight Saving Time schedule once the Department of Energy study is complete.
Canada and Bermuda made similar changes to their DST rules to be consistent with the U.S. time changes.
The 2007 daylight saving time implementation is as follows:
Clocks change at 02:00 A.M. local time.
On March 11, 2007, clocks will move forward one hour from 01:59 A.M. to 03:00 A.M. On November 4, 2007, clocks will move back one hour from 01:59 A.M. to 01:00 A.M.
This change affects the following time zones:
GMT-3:30 Newfoundland
GMT-4 Atlantic
GMT-5 Eastern US
GMT-6 Central US
GMT-7 Mountain US
GMT-8 Pacific US
GMT-9 Alaska
How do DST changes affect I
T systems worldwide?
Source: http://www.ibm.com/support/alerts/daylightsavingstimealert.html
Date and time processing functions in systems and applications in countries implementing the new DST rules (U.S., Canada, Bermuda) are affected. Systems and applications in countries not implementing the DST changes could be affected if they support users, transactions, or applications involving countries that are implementing the new DST rules. For example, scheduling or synchronizing problems may arise where systems make or check date or time stamps relating to transactions in other countries, or there may be difficulty in applications that perform scheduling calculations. Any time-sensitive functions could be impacted by this change.
DST rules affect date and time processing functions in computers and applications. If not set properly, depending upon how uniformly updates are applied, the time could be incorrect by one hour for four weeks each year.
Areas Impacted by this change in daylight saving time:
Preparing for daylight saving time changes in 2007 (http://www.microsoft.com/windows/timezone/dst2007.mspx)
| Windows Vista |
No update needed |
| Windows XP (SP2), Windows Server 2003, Windows Server SP1 |
Update available
2007 time zone update for Microsoft Windows operating systems (http://support.microsoft.com/kb/928388)
|
| Windows 2000 |
Update available – (under Extended Hotfix Support) |
| Windows XP SP1 |
Not Supported |
| Windows NT 4 |
Not Supported |
| Outlook |
Outlook 2007: No update needed.
Outlook 2003, XP and 2000: An Outlook Data Update Tool will be available in January from the Download Center.
Addressing daylight saving time using the Outlook Time Zone Data Update Tool (http://support.microsoft.com/default.aspx/kb/931667)
Prepare Outlook calendar items for daylight saving time changes in 2007 (http://office.microsoft.com/en-us/outlook/HA102086071033.aspx)
|
| Exchange Server |
Exchange Server 2007: No update needed.
Exchange Server 2003 Service Pack 2: Exchange update (addressing changes in the United States and Canada, excluding Newfoundland) is available through CSS, Microsoft Update (currently as an optional update), and the Microsoft Download Center. For more information, refer to KB article 926666.
Exchange Server 2003 Service Pack 1: SP Service Support will be retired January 9, 2007 so Exchange 2003 SP1 is not eligible to receive this update.
Exchange Server 2000/Exchange Conferencing Server 2000: Updates are available now. Exchange 2000 is under Extended Support. Customers with Extended Hotfix Support Agreements (EHSAs) can request hotfix through their Technical Account Managers.
Exchange Server 5.5: The update is available now. Exchange 5.5 is under Custom Support phase until January 2008. Customers with Customer Support Agreements (CSAs) can request a hotfix through their Technical Account Managers.
Exchange Server 2003 Lotus Notes Connector: Download available at Microsoft Download Center (search for “Exchange Server 2003 Connector for Lotus Notes”).
Exchange versions out of mainstream support without EHSA or CSA: No workaround or update available. |
| Windows SharePoint Services |
Windows SharePoint Services 3.0: No update needed.
Windows SharePoint Services 2.0: A single global time zone update including changes for the United States and Canada DST change will be made available on January 9 via Microsoft Download Center and on January 29 through Microsoft Update as a critical update. (http://support.microsoft.com/kb/924881) |
| Microsoft Dynamics CRM |
Microsoft CRM 3.0: Update delivered via Hotfix available in March 2007. See KB article 925874. |
| Windows Mobile |
Windows Mobile: See KB article 923953. |
| Windows CE based devices |
Windows CE: See KB article 923027. |
| RIM Blackberry |
Impact of North American Daylight Saving Time changes in 2007 on BlackBerry device users. |
Technorati tags:
flaphead,
dst 2007
flaphead.com 