Guest

Cisco Unified MeetingPlace Express

Field Notice: FN - 62872 - New Zealand Daylight Saving Time Policy Change Effective September 2007 - for Cisco MeetingPlace Express (MPE)


September 7, 2007

NOTICE:

THIS FIELD NOTICE IS PROVIDED ON AN "AS IS" BASIS AND DOES NOT IMPLY ANY KIND OF GUARANTEE OR WARRANTY, INCLUDING THE WARRANTY OF MERCHANTABILITY. YOUR USE OF THE INFORMATION ON THE FIELD NOTICE OR MATERIALS LINKED FROM THE FIELD NOTICE IS AT YOUR OWN RISK. CISCO RESERVES THE RIGHT TO CHANGE OR UPDATE THIS FIELD NOTICE AT ANY TIME.


Products Affected

Products Affected

Comments

MPE - 2.0

MeetingPlace Express versions 2.0 and earlier are affected.

  

Problem Description

New New Zealand Daylight Saving Time rules go into effect in September 2007. Consequently, certain instances of recurring meetings on MeetingPlace Express may occur and appear one hour off than their intended scheduled time. Timestamps for MPE system logs will also be off by an hour.

Background

On April 30, 2007, the Minister of Internal Affairs issued a statement regarding a change in Daylight Saving Time policy for New Zealand. The change in policy has modified the start and end dates for Daylight Saving Time (DST). Beginning in 2007 and beyond, Daylight Saving Time in New Zealand will start on the last Sunday of September at 2:00 A.M. local time and end on the first Sunday of April at 3:00 A.M. local time.

Specifically for 2007-2008, Daylight Saving Time will begin at 2:00 A.M. local time on September 30, 2007, and end at 3:00 A.M. local time on April 6, 2008.

For more information, see the statement issued by the Minister of Internal Affairs: Daylight saving to be extended.

The old Daylight Saving Time policy dictated that DST started on the first Sunday in October and ended on the third Sunday in March.

Problem Symptoms

Recurring meetings with some, but not all, instances occurring during the below time frames may have start times that are off by one hour from the original, intended start time:

-September 30, 2007, to October 6, 2007

-March 15, 2008, to April 6, 2008

System logs may also show up as one-hour off during the above time frames.

Workaround/Solution

There are two possible solutions for fixing this problem on the MeetingPlace Express server:

  1. Wait for and upgrade to the next software release, which is 2.0.2. Problematic meetings scheduled prior to the upgrade will still need to be manually re-scheduled. Until the next software version is released, meeting owners will need to manually fix the problem by re-scheduling the meeting instances which are scheduled to occur during the transition time period noted in the Problem Symptom section above. You can find detailed instructions on how to do this in the NZ_Daylight_Saving_Time_Fix.zip file in the Software Download page for MeetingPlace Express (registered customers only) .

  2. Run the script fix_timezone_data.sh contained within NZ_Daylight_Saving_Time_Fix.zip. All meetings scheduled after running the script will have the correct start time. The script will also provide a list of meetings which have to be manually rescheduled. You will still have to manually reschedule all meetings that were scheduled for the problematic time periods before the script was applied. The provided list may contain duplicate incidents without specifying the date of occurrence, this is expected behavior. You can find detailed instructions on how to manually reschedule meetings and how to use the fix_timezone_data.sh script in the NZ_Daylight_Saving_Time_Fix.zip file in the Software Download page for MeetingPlace Express (registered customers only) .

*Important Note: The instructions provided in the NZ_Daylight_Saving_Time_Fix.zip file are supported only for MeetingPlace Express versions 1.1.4, 1.2.1 and 2.0.1. MeetingPlace Express servers running earlier versions than 1.1.4, 1.2.1 or 2.0.1 will need to be upgraded before the instructions in NZ_Daylight_Saving_Time_Fix.zip can be applied.

DDTS

To follow the bug ID link below and see detailed bug information, you must be a registered user and you must be logged in.

DDTS

Description

CSCsj64732 (registered customers only)

MPE does not adjust properly to New Zealand DST in Sept 2007

  

Frequently Asked Questions (FAQs)

If I use Microsoft Exchange with MeetingPlace Express, what updates need to be applied?

For customers using MeetingPlace Express with Microsoft Exchange, the following Microsoft updates will need to be applied:

1) Microsoft Update for all Windows machines (Exchange server and end user PCs)

2) Update required for Exchange 2003 only

How do I use the fix_timezone_data.sh and list_meetings.sh scripts contained within NZ_Daylight_Saving_Time_Fix.zip?

* fix_timezone_data.sh - Updates the time zone data, which fixes the problem for any newly scheduled meetings after the time zone data is updated. Also, this script displays a list of meetings which need to be manually rescheduled.

Script: fix_timezone_data.sh

Usage: ./fix_timezone_data.sh

Permission: The script should be run as root. su to root. Download the entire package with both scripts, tzdata.rpm and tzupdater-1_2_1-2007f.zip in the NZ_Daylight_Saving_Time_Fix.zip file to a folder on the MeetingPlace Express system. Then make every file in the extracted folder executable with the command - chmod +x -R DSTfix. Position yourself in that folder - cd DSTfix. And finally run the script - ./fix_timezone_data.sh.

The script updates the time zone and local time data which fixes the problem for any newly scheduled meetings after the time zone data is updated. It will also display a list of meetings which still need to be manually rescheduled.

Note: This script can be safely run any number of times whether it is needed or not.

* list_meetings.sh - Displays a list of meetings which need to be manually rescheduled. The provided list may contain duplicate incidents without specifying the date of occurrence, this is expected behavior. Make sure to run fix_timezone_data.sh prior to manually re-scheduling problematic meetings, this will insure meetings are scheduled for their proper start time.

Script: list_meetings.sh

Usage: ./list_meetings.sh

Permission: The script should be run as root. su to root and copy the script to a folder and then make it executable - chmod +x list_meetings.sh.

The script displays a list of meetings which may need to be manually rescheduled.

Revision History

Revision

Date

Comment

1.0

07-SEP-2007

Initial Public Release

  

For More Information

If you require further assistance, or if you have any further questions regarding this field notice, please contact the Cisco Systems Technical Assistance Center (TAC) by one of the following methods:

Receive Email Notification For New Field Notices

Product Alert Tool - Set up a profile to receive email updates about reliability, safety, network security, and end-of-sale issues for the Cisco products you specify.