Exchange 2000 and Daylight Savings Time change for US scheduled for March 2007
I am trying to find out exactly what has to be done for those of us still running exchange 2000. We will be upgrading in a few months, but not before the Daylight Savings Time change.
I have been researching this on line and get conflicting information. Some say if you don't have extended life support you are SOL. Some articles have said the clients can be updated, but exchange does not have to be. Some say you can't update the client until the exchange servers are updated. Some say update the OS the exchange Server is running on, but exchange itself does not have to be updated, however OWA will still be affected. One person said the client pc's, the exchange server OS, AND the Exchange Server 2000 ALL need to be updated and will have to be "maintained" on an on-going basis, but gave no details as to what she meant by "maintained on an on-going basis".
Does anyone have a definitive answer as to what exactly MUST be updated? Will updating the OS on the exchange servers be enough? If not, without extended support, how will the exchange itself be updated? Anyone??????? Microsoft does not have a comprehensive detailed explanation on this regarding exchange 2000 that I can find anywhere.
Software/Hardware used:
Software/Hardware used:
ASKED:
January 17, 2007 3:53 PM
UPDATED:
January 24, 2007 9:26 AM
Answer Wiki:
In a nutshell you are SOL without extended support.
Microsoft calendar software such as Outlook depends on the operating system time zone information to display time information. However, Collaboration Data Objects (CDO)-based programs such as Outlook Web Access depend on separate internal time zone tables. This update modifies these internal time zone tables to match the changes in time zone settings.
Without this update, calendar items in CDO-based programs will operate as if standard time is in effect during the extra weeks of daylight saving time. For example, without this update CDO-based programs will operate in standard time during the following periods in 2007:
? March 11, 2007 through April 1, 2007
? October 28, 2007 through November 4, 2007
See http://www.microsoft.com/windows/timezone/dst2007.mspx for more info.
To see all answers submitted to the Answer Wiki: View Answer History.
What is the fuss about? I am sure that microsoft will update the system and Windows Time Server synch will be according to the Time zone set by the atomic Clock
The fuss is because apparently Exchange does not just take it’s time from the system clock, and Exchange 2000 is in extended life support, which means if you did not purchase extended life support, then you are not eligible to get the hotfix that will change DST and when you open OWA your apointments will all be off by an hour for 3 weeks between March 11th and April 1st.
Read the Microsoft Exchange Team blog here to see why this is a problem.
http://msexchangeteam.com/archive/2006/11/13/431471.aspx
For our corporation we decided we will be forced to do an in place upgrade on 2 mail servers to exchange 2003 to resolve the DST issues. We are ordering new hardware to do a complete install of server 2003 and Exchange 2003, but it won’t be in time to meet the new DST change. So in the mean-time we are upgrading our existing mail servers because we have over 300 executives and VIP’s who can not afford to have their appointment times wrong for 3 weeks.
Dumb question, but is this likely to affect any non-international users, e.g. we are based in the UK, use Exchange 2000 and should theoretically not be affected by the US’s DST change.
Many thannks,
John
JohnTWT,
This change will only have an affect on Exchange servers that are in one of the North American time zones.
U.S.A. (except Hawaii, Arizona)
Canada (except Saskatchewan)
Saint Pierre and Miquelon (Fr.)
Bahamas
Bermuda