2007 Daylight Saving Time Changes
Transition for NotifyLink Users

With the passage of the Energy Policy Act of 2005, starting in March 2007, daylight time in the United States will begin on the second Sunday in March and end on the first Sunday in November.  (In 2007, daylight time begins on March 11 and ends on November 4.)

Who is Affected   Users in the United States, Canada, and Mexico are directly affected and should install all required updates prior to March 11, 2007.  Users in other countries should install updates if they travel in the U.S., Canada, or Mexico or make calendar appointments that include attendees based in the U.S., Canada, or Mexico. 

What is Affected: Consequences of Failure to Upgrade   Failure to upgrade in ALL environments will result in clients experiencing clocks, appointments, and reminders that appear 1 hour off during one of the following windows of time in any year:

            Between the second Sunday in March and the first Sunday in April

                        (In 2007: March 11 to April 1)

            Between the last Sunday in October and the first Sunday in November

                        (In 2007: October 28 to November 4)

The Patches: Coordinating a Thorough Update   For the new Daylight Saving Time (DST) definitions to be effective, DST patches must be applied to ALL of the following environments:

In the following sections of this document you will find suggestions on where to find Resources for each of these updates and a Checklist for making sure all bases are covered.

Installation Tips  

• The best strategy for applying updates is to perform the steps all at once and as soon as possible prior to March 11, 2007.  Until ALL fixes are applied, it is possible for data with inaccurate times to be generated.
• Patches will correct the source of appointment generation, but may not correct data created prior to the application of the updates.  End users may still have to manually correct appointments and reminders occurring between March 11 - April 1 and October 28 - November 4, 2007.

Easing the Transition

With so many variables out of the end user's control, it is probable that they will experience erroneous appointment data in the affected time periods.  Here are some suggestions you might give to make their transition easier.

• Give extra attention to meetings, appointments and reminders scheduled between March 11 and April 1, 2007 and between October 28 and November 4, 2007.
• Including the time of a meeting in the email request or appointment subject will provide a means of double-checking times for events in the affected time period.
• Suggest that end users print out their weekly calendars for the affected time periods so they can keep track of appointments before and after the patches are applied.

The Patches:  Resources for Implementation

Vendor links to 2007 DST fixes should be researched thoroughly as information may have been added or changed since this document was released.

Operating System of the Server on which the Collaboration Suite Runs

The operating system of the server running the mail/PIM server software may need updated with a patch to handle the new DST definitions.  Check product websites to determine if this is necessary for the collaboration suite you use.  Operating systems involved may include:

• Windows - http://support.microsoft.com/kb/928388
• Unix
• Mac                 
• Linux
• Solaris
• Netware

 Operating System on which NotifyLink Enterprise Server (NLES) Runs

The operating system of the server(s) running NLES components will need updated with a patch to handle the new DST definitions.

Apply patches provided by Microsoft for Windows 2000 / Windows 2003.

Collaboration Suite Patches

Apply patches provided by mail/PIM server software provider. 

See Appendix A.

NotifyLink Enterprise Server Software Hotfix versions 4.0, 4.1, 4.3 

Hotfix will post week of February 26, 2007 or sooner.  You'll find the hotfix at http://notifylink.notify.net/ .  Navigate to the page for the collaboration suite you use and click on Software Updates and Hotfixes.  Look at the hotfix ReadMe.txt file for additional information.

To apply the change, perform the following steps on the server running the NotifyLink Enterprise Server (NLES) Messaging component:

1. Stop all NLES services and the Web server including IIS Admin Service if using IIS.

2.       Backup existing files.  In the NotifyLink Enterprise Server directory (default location C:\Program Files\NotifyLink Enterprise Server), backup the existing ntc_core.dll and nlpim.exe by renaming the files or copying to a different folder.

1. Save the hotfix files to the directories. 

1. Save the ntc_core.dll and nlpim.exe hotfix files to the NotifyLink Enterprise Server directory
2. Save the ntc_core.dll hotfix file to the WINNT\system32 directory

1. Start the Web server and all NLES services.

Workstation Operating System & Workstation Collaboration Suite Software

The trick here is to get everyone "on the same page" - quickly.  If some users have not updated their workstation's operating system or mail/PIM software it will affect other users.  (Ex:  If a meeting organizer's workstation is not updated, those invited to the meeting will experience erroneous meeting times even if their own workstation and device are updated.)

Windows Overview:  http://support.microsoft.com/gp/cp_dst

Microsoft Windows XP & 2003:  http://support.microsoft.com/kb/928388/en-us

Apple OSX: http://docs.info.apple.com/article.html?artnum=303411

            See Appendix A for information on collaboration suite software.

Device Operating Systems

Again, the goal should be to get everyone updated quickly.  If some users have not updated their device it will affect other users.   Meetings generated from an un-updated device will appear incorrect to attendees receiving the invitation on an updated device or computer.

BlackBerry

http://www.blackberry.com/select/dst2007/index.shtml

http://www.blackberry.com/select/dst2007/planned_resolutions/device_impact.shtml

Palm

Check the Palm website, http://www.palm.com/ for more information.

Windows Mobile

http://support.microsoft.com/kb/923953

MS posted this for WM devices recently -- it has a link to download a utility that will update time zone definitions on the device:

http://www.microsoft.com/windowsmobile/daylightsaving/default.mspx

Checklist for Troubleshooting the Cause of Erroneous Data

If users are still experiencing incorrect data in the date ranges between March 11 and April 1 and between October 28 and November 4 check the following:

Appendix A:  Collaboration Suite Resources

Vendor links to 2007 DST fixes should be researched thoroughly as information may have been added or changed since this document was released.

* Both CommuniGate Pro and Zimbra have chosen to accommodate the new DST definitions through the release of their latest software versions:  CommuniGate Pro v5.1.5 and Zimbra v4.5.1 

Though no official ETA has been established, Notify Technology Corporation is in the process of verifying the new versions against the NotifyLink Enterprise Server software.

NotifyLink Enterprise Server currently operates with:

CommuniGate Pro - versions 4.2.9 through 5.0.8

Zimbra - versions 3.1.0 through 4.0.0