Guest

Cisco Unified MeetingPlace

Field Notice: FN - 62665 - US Daylight Savings Time Policy Change Effective March 2007 - for MeetingPlace (MP) Products


Revised November 5, 2007

January 31, 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.


Revision History

Revision

Date

Comment

1.7

05-NOV-2007

Updated the list of full MSC OS versions in section 1a of the FAQ.

1.6

18-OCT-2007

Added DDTS ID CSCsh20360. Added **UPDATED list of fixed MCS OS versions due to CSCsh20360 on October 18, 2007** to question 1a of FAQ section.

1.5

17-OCT-2007

Updated the list of versions that contain the fix for the MCS OS in FAQ 1(a) section.

1.4

15-MAR-2007

Added note to FAQ #3 regarding MP Web. Corrected command regarding tzupdatertool (step 6) - removed "-" from tzudater.jar.

1.3

09-MAR-2007

Added "Apply an MCS OS update, which only contains the fix for the new DST policy. The MCS OS update can be found in the above URL listed with the file name of "win-OS-Upgrade-K9.2007-DST-Update.1-0-1.exe". This update is applicable for MCS OS versions 2000.2.7, 2000.4.2, 2000.4.3, 2000.4.3a, 2000.4.4, and 2000.4.4a." to FAQ #1

1.2

23-FEB-2007

Added several items to FAQ section, made changes throughout relating to MeetingPlace for Outlook plug-in

1.1

09-FEB-2007

Modified the FAQ section.

1.0

31-JAN-2007

Initial Public Release

Products Affected

Products Affected

Comments

MP GWSIM - 5.2.0.x

MeetingPlace GWSIM versions 5.2.0.44 and earlier are affected

MP Outlook GW - 5.3

MeetingPlace for Outlook versions 5.3.0.132 and earlier are affected.

MP Server - 5.3

MeetingPlace Audio Server versions 5.3.0.31 and earlier are affected. This includes PCI servers running versions 4.x.

MP Web - 5.3

MeetingPlace Web versions 5.3.235 and earlier are affected.

Problem Description

New U.S. Daylight Savings Time rules go into effect in March 2007. Consequently, MeetingPlace meetings may occur and appear one hour off of their intended scheduled time. Timestamps for MP system logs may also be off by an hour.

Background

On August 8, 2005, the Energy Policy Act of 2005 (H.R.6.ENR) was signed into law. Section 110 of this Act modified the time change dates for Daylight Saving Time (DST) in the US.

Beginning in March of 2007 and beyond, DST will begin on the second Sunday of March at 2:00 AM and end the first Sunday of November at 2:00 AM.

For more information on the Energy Policy Act of 2005 (Section 110), see H.R. 6.

The old DST policy dictated the start of DST was the first Sunday of April and ended on the last Sunday of October.

Problem Symptoms

MeetingPlace meetings may appear one hour off than their original time on Meetingplace Audio Server and MeetingPlace for Outlook between the old DST dates and new DST dates in 2007:

-March 11 to April 1 in 2007

-October 28 to November 4 in 2007

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

To identify which meetings are potentially one hour off, see the FAQ section below.

Workaround/Solution

There is no automatic script/tool from Cisco which can update the meetings that are one hour off.

To prevent the possibility of future meetings from being scheduled one hour off between the old DST dates and the new DST dates, the affected MeetingPlace software must be updated. To find out which software versions of the new DST policy implementation, see the FAQ section below.

Meetings that were scheduled prior to the software upgrade will need to be manually re-scheduled. To find out how to correct affected meetings, see the FAQ section below.

MeetingTime provides an option to get Raw Detail reports. Use this option to obtain the MtgIds of all the meetings during the transition period from old DST dates to the new DST dates. End users will need to manually re-schedule these meetings using the MtgIds obtained from the Raw Detail report. In the case of meetings scheduled using MeetingPlace for Outlook Plug-in, there is an option for the scheduler to reschedule the meetings to the correct time and all the participants will receive update notifications with the correct time.

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

CSCsh20360 (registered customers only)

Looping in System Date & Time due to Daylight saving correction

Frequently Asked Questions

What must be done to update the MeetingPlace software and related software?

  1. Update any MeetingPlace gateway's Microsoft OS with a patch for the new DST policy. The fix for the new DST policy can be achieved in one of two ways:

    1. **UPDATED list of fixed MCS OS versions due to CSCsh20360 on October 18, 2007**Apply a full MCS OS upgrade, which contains fixes for both the new DST policy and for other defects. The full MCS OS upgrades are 2000.4.5b(sr3), 2000.4.4a(sr4), OS 2000.4.3aSR9, or OS 2000.4.2sr16 (or higher OS release) and can be downloaded from the CallManager & Voice Apps Crypto SoftwareDownload page.

    2. **Added March 6, 2007** : Apply an MCS OS update, which only contains the fix for the new DST policy. The MCS OS update can be found in the above URL listed with the file name of "win-OS-Upgrade-K9.2007-DST-Update.1-0-1.exe". This update is applicable for MCS OS versions 2000.2.7, 2000.4.2, 2000.4.3, 2000.4.3a, 2000.4.4, and 2000.4.4a.

    To find out which MCS OS version is in use, please do the following on the MCS server: Start Menu --> Cisco OS Version

  2. Make sure all the Meetingplace components are at the latest software release. MeetingPlace 5.4 has all the DST changes for 2007 incorporated, so upgrading to Meetingplace 5.4 is recommended. Upgrading to 5.4 will not fix problematic meetings that were previously scheduled before the upgrade.

    Cisco Unified MeetingPlace 5.4 Software (registered customers only)

  3. If upgrading to MeetingPlace 5.4 is not an option, then the following 5.3 versions of MeetingPlace components have the DST changes. Upgrading to the latest 5.3 versions will not fix problematic meetings that were scheduled prior to the upgrade.

    -MP Audio Version 5.3.0.32 or above - Cisco MeetingPlace Server Software (registered customers only)

    -GWSIM version should be 5.2.0.46 or above - Cisco MeetingPlace GWSIM Software (registered customers only)

    -MP Outlook version 5.3.0.138 or above - Cisco MeetingPlace for Outlook Software (registered customers only)

    -MP Web Version 5.3.0.333** or above - Cisco MeetingPlace Web Conferencing Software (registered customers only)

    **Note: If the previous version of MP Web that does not support the new DST policy was installed after the time zone fix was made available, then the fix will not be applied when the system is upgraded with the MP Web version that does support the new DST policy because the timestamp on the existing time zone file will be later than that of the new time zone file being applied. This issue is addressed in CSCsi12901 (registered customers only) . Please contact Cisco TAC for a solution to this issue.

    For example, MP Web 5.3.235 does not support the new DST policy. MP Web 5.3.447 supports the new DST policy. If MP Web 5.3.235 is installed after the release date of 5.3.447 (5/9/2006) and an upgrade to 5.3.447 is performed later on to obtain the new DST policy support, then the 5.3.235 time zone file will not be replaced by the 5.3.447 time zone file because the 5.3.235 time zone file will have a later "last modified" time stamp than the 5.3.447 time zone file. Therefore, the time zone file installed with MP Web 5.3.447 will not have the new DST policy support.

  4. For customers who are on MeetingPlace 4.3 PCI servers, contact Cisco TAC to obtain the hotfix for DST 2007. Upgrading to the latest 4.3 version will not fix problematic meetings that were previously scheduled before the upgrade.

  5. Microsoft has released an update for Windows XP that corrects Windows timezone definitions to reflect DST the changes. For more information about updating Windows, see Windows preparations for daylight saving time changes in 2007.

    Every MeetingPlace end user must install the appropriate Windows patch on their desktops. Windows 2000 version of this patch is available for Microsoft premium support users only.

  6. Microsoft has released an update for Exchange 2003. Customers who use MeetingPlace Outlook with Exchange 2003 must apply this patch: Update for daylight saving time changes in 2007 for Exchange 2003

    Steps to install this package on MeetingPlace:

    1. Install this package on your exchange server and extract the CDO.dll from it. This CDO.dll contains the DST fixes.

    2. Stop MeetingPlace services on your MeetingPlace Outlook gateway server.

    3. Copy the CDO.dll from this patch onto the Meetingplace Outlook gateway server.

    4. Reboot the Meetingplace Outlook gateway server.

  7. Microsoft has incorporated a new feature into Microsoft Office Outlook 2007 to help adjust calendar items affected by time zone changes. Currently, MeetingPlace for Outlook does not support Outlook 2007. The MeetingPlace for Outlook Plug-in does not install on Outlook 2007. For other releases of Outlook, Microsoft has released an Outlook Data Update tool:

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

    This tool updates the problematic meetings to the correct time in the user's Outlook calendar, but does not update the meeting time on the MeetingPlace Server. So meetings in the Outlook calendar will display at the correct time in regards to the new DST policy, but the meetings on the MeetingPlace Server will still show one hour off. In order to fix the MeetingPlace Server meetings, please see #2 or #3 in the FAQ section.

How do I identify meetings that are potentially one hour off?

**Note: The problem will only occur for meetings that were scheduled by users in the US and for meetings that have invitees in the US. The problem is not limited to the specific timezones used in the examples below. MeetingPlace for Outlook is used in the both of the examples below as it is a widely utilized implementation. Hoewever, it is important to note that regardless of which notification gateway is used, meetings may occur and appear one hour off if they are scheduled prior to DST patched software releases being applied and occur during the transition period.

For MP Web/MeetingTime scheduled meetings using Outlook to send meeting notifications:

Scheduler and Invitees are in PST:

-Single meetings occurring before March 11th are not affected.

-Single meetings occurring between March 11th and April 2nd are off by one hour.

-Single meetings occurring after April 2nd are not affected.

-Recurring meetings starting before March 11th and going forward are off by one hour in the weeks between March 11th and April 2nd. The remainder of the instances are OK.

-Recurring meetings starting on March 11th and going forward are off by one hour in the weeks between March 11th and April 2nd. The remainder of the instances are OK.

-Recurring meetings starting after April 2nd are not affected.

-Single meetings occurring from October 28th to November 4th are off by one hour.

-Single meetings occurring after November 4th are not affected.

-Recurring meetings starting before October 28th and going forward are off by one hour in the week between October 28th and November 4th. The remainder of the instances before October 28th and after November 4th are OK.

-Recurring meetings starting on October 28th and going forward are off by one hour in the week between October 28th and November 4th. The remainder of the instances after November 4th are OK.

-Recurring meetings occurring after November 4th are not affected.

Scheduler in PST & Invitees in Asia/Hong Kong:

-Single meetings occurring before March 11th are not affected.

-Single meetings occurring between March 11th and April 2nd are off by one hour.

-Single meetings occurring after April 2nd are not affected.

-Recurring meetings starting before March 11th and going forward are off by one hour in the following weeks starting from March 11th. Previous instances are OK.

-Recurring meetings starting on March 11th and going forward are off by one hour for all instances.

-Recurring meetings starting after April 2nd are not affected.

Scheduler in PST & Invitees in Europe/Paris:

-Single meetings occurring before March 11th are not affected.

-Single meetings occurring from March 11th to April 2nd are off by one hour.

-Single meetings occurring after April 2nd are not affected.

-Recurring meetings starting before March 11th and going forward are off by one hour in the following weeks starting from March 11th to April 2nd. The remainder of the instances are OK.

-Recurring meetings starting from March 11th and going forward are off by one hour for all instances.

-Recurring meetings starting after April 2nd are not affected.

Meetings scheduled using MeetingPlace for Outlook Plug-in:

-Single meetings occurring before March 11th are not affected.

-Single meetings starting from March 11th to April 2nd are off by one hour.

-Single meetings occurring after April 2nd are not affected.

-Recurring meetings starting before March 11th and that have instances that occur between March 11th and April 2nd are OK.

-Recurring meetings starting from March 11th and going forward are off by one hour for all instances.

-Recurring meetings starting after April 2nd are not affected.

How do I correct affected meetings?

For MP Web/MeetingTime scheduled meetings using Outlook to send meeting notifications:

Meetings which have been scheduled before applying the above updates and are one hour off must be manually moved to the correct timings by the scheduler and invitees. All new meetings scheduled after the above updates are installed will be scheduled appropriately.

Some exceptions are listed below:

-For Asia/Hong Kong timezone recurring meetings which begin before March 11th and have instances from March 11th and onwards will be off by one hour even after applying the CDO patch. These problematic meetings need to moved manually by the scheduler and invitees.

-For Europe/Paris timezone recurring meetings which begin before March 11th and have instances from March 11th to April 2nd will be off by one hour even after applying the CDO patch. These problematic meetings need to moved manually by the scheduler and invitees.

-For Europe/Paris timezone recurring meetings which begin on March 12th and have instances from April 2nd will be off by one hour even after applying the CDO patch.

Meetings scheduled using MeetingPlace for Outlook Plug-in:

-Single meetings scheduled to occur between March 11th and April 2nd from unpatched desktops will be off by one hour on the MeetingPlace Audio Server. After the patch is applied, the meeting scheduler will need to move the meeting to its correct time.

-For recurring meetings that begin before March 11th and have instances that occur between March 11th and April 2nd:

After the patch is applied, the meeting instances between March 11th and April 2nd will be off in the calendar by one hour and the meeting scheduler will have to move these instances to the correct time.

-For recurring meetings that begin in the time frame March 11th to April 2nd:

All instances of the series must be adjusted by the scheduler.

What corrective action should be taken for MeetingPlace SMTP gateway?

Follow steps #1 - #4 in the section of "What must be done to update the MeetingPlace software and related software?" Any meetings that were scheduled prior to the software upgrade will need to be manually re-scheduled.

What corrective action should be taken for MeetingPlace for Notes gateway and Lotus Notes/Domino?

Follow steps #1 - #4 in the section of "What must be done to update the MeetingPlace software and related software?" Any meetings that were scheduled prior to the software upgrade will need to be manually re-scheduled. Follow the instructions provided by IBM for Lotus Notes/Domino:

Daylight Saving Time (DST) 2007 information for Lotus Notes and Domino

What corrective action should be taken for Cisco Unified Video Administration?

If the Cisco Unified Video Administration "All Meetings" interface is used, then the 'tzupdatertool' from Sun should be installed to display the correct start times. If the 'tzupdatertool' is not installed, then the meetings will display incorrect start times, but will occur at the correct time. The tzupdatertool should be installed on the machine that has Cisco Unified Video Administration installed.

Please follow the steps below to install the tzupdatertool:

  1. Download the tzupdater tool from the Sun Java site: Sun Java SE JDK tzupdater Tool

  2. Extract the downloaded zip file.

  3. Copy the tzupdater.jar file to C:\Program Files\Cisco\Video Admin\VA\jre1.5.0\bin or to the respective path where Video Administration is installed.

  4. Open a commmand prompt and change to the C:\Program Files\Cisco\Video Admin\VA\jre1.5.0\bin directory or to the respective path where Video Administration is installed.

  5. Stop the Cisco Video Administration service from the Windows Services control panel.

  6. Run the command as per the instructions on the Java site: java -jar tzupdater.jar -u

  7. Restart the Video Administration service.

The meetings in Cisco Unified Video Administration will display the correct time after the patch is applied.

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.