I have a single user (known to us at least) who is using Outlook 2003 with the 7.0.1 connector. The issue also occurs with the Outlook connector 6.0.10.
Essentially when we setup a meeting in Outlook at 8am for Bob and send it to a ZWC user John who sees 7am instead in the wording. The strange part is that the meeting will show 8pm in the calendar preview pane and then create the meeting for 8pm as well on John's calendar.
I attached a screenshot for easier reference.
Everything seems OK between ZWC users, is the Outlook connector not aware of Daylight Saving Time or have incorrect time zones? We're in Alaska (-9 gmt, DST used) if it makes a difference.
UPDATE: Edited the title
calendar.jpg
Outlook 2003 meetings display 1 hour early, schedule correctly
Outlook 2003 meetings display 1 hour early, schedule correctly
Could be a bug with a MAPI property, I suppose. Does it only happen with users in GMT -9?
Outlook 2003 meetings display 1 hour early, schedule correctly
I'm not sure really, I only have users in Alaska. My loaner laptop was out most of last week so I wasn't able to replicate the issue on another system yet. I'll see if I can duplicate the error on WinXP and Office 2003 this week, plus my own Win7 with Office 2010.
Outlook 2003 meetings display 1 hour early, schedule correctly
Hhhm, this seems to still be an issue in 7.1 with the newer as well as older ZCO software. Any ideas?
Outlook 2003 meetings display 1 hour early, schedule correctly
I've narrowed this down to our users with Outlook 2003 and ZCO. This bug was around with ZCS 6, 7.0, and now 7.1.
Below I pasted the original info for two meetings. One made in Outlook 2003, the other in 2010. I think it might make a difference, but 2003 does not include the TZ lines for Time Zone information. The 2010 meetings work and display correctly, while the 2003 schedule correctly but will not display in the message body correctly.
Meeting created in Outlook 2003
BEGIN:VCALENDAR
PRODID:Zimbra-Calendar-Provider
VERSION:2.0
METHOD:PUBLISH
BEGIN:VEVENT
UID:040000008200E00074C5B7101A82E00800000000406D85F9CC29CC010000000000000000100000005FA7F29E92A7714F90F0215095C871E2
SUMMARY:Test meeting
DESCRIPTION:
LOCATION:Here
ATTENDEE;CN=cu;ROLE=REQ-PARTICIPANT;PARTSTAT=ACCEPTED;RSVP=TRUE:mailto:user2@domain.com
PRIORITY:5
ORGANIZER:mailto:user1@domain.com
DTSTART:20110613T230000Z
DTEND:20110613T233000Z
STATUS:CONFIRMED
CLASS:PUBLIC
X-MICROSOFT-CDO-INTENDEDSTATUS:BUSY
TRANSP:OPAQUE
LAST-MODIFIED:20110613T212242Z
DTSTAMP:20110613T212242Z
SEQUENCE:0
BEGIN:VALARM
ACTION:DISPLAY
TRIGGER;RELATED=START:-PT5M
DESCRIPTION:Reminder
END:VALARM
END:VEVENT
END:VCALENDAR
Meeting created in Outlook 2010
BEGIN:VCALENDAR
PRODID:Zimbra-Calendar-Provider
VERSION:2.0
METHOD:PUBLISH
BEGIN:VTIMEZONE
TZID:America/Anchorage
BEGIN:STANDARD
DTSTART:19710101T020000
TZOFFSETTO:-0900
TZOFFSETFROM:-0800
RRULE:FREQ=YEARLY;WKST=MO;INTERVAL=1;BYMONTH=11;BYDAY=1SU
TZNAME:AKST
END:STANDARD
BEGIN:DAYLIGHT
DTSTART:19710101T020000
TZOFFSETTO:-0800
TZOFFSETFROM:-0900
RRULE:FREQ=YEARLY;WKST=MO;INTERVAL=1;BYMONTH=3;BYDAY=2SU
TZNAME:AKDT
END:DAYLIGHT
END:VTIMEZONE
BEGIN:VEVENT
UID:040000008200E00074C5B7101A82E0080000000050A9EE87BB29CC010000000000000000100000003FF96DD71CB3114BAA3C5A0AA42D0B01
SUMMARY:test from outlook
LOCATION:not real, test only
ATTENDEE;CN=User One;ROLE=REQ-PARTICIPANT;PARTSTAT=ACCEPTED;RSVP=TRUE:mailto:user1@domain.com
ORGANIZER:mailto:user2@domain.com
DTSTART;TZID="America/Anchorage":20110613T150000
DTEND;TZID="America/Anchorage":20110613T153000
STATUS:CONFIRMED
CLASS:PUBLIC
X-MICROSOFT-CDO-INTENDEDSTATUS:BUSY
TRANSP:OPAQUE
LAST-MODIFIED:20110613T191750Z
DTSTAMP:20110613T191750Z
SEQUENCE:0
BEGIN:VALARM
ACTION:DISPLAY
TRIGGER;RELATED=START:-PT15M
DESCRIPTION:
END:VALARM
END:VEVENT
END:VCALENDAR
Below I pasted the original info for two meetings. One made in Outlook 2003, the other in 2010. I think it might make a difference, but 2003 does not include the TZ lines for Time Zone information. The 2010 meetings work and display correctly, while the 2003 schedule correctly but will not display in the message body correctly.
Meeting created in Outlook 2003
BEGIN:VCALENDAR
PRODID:Zimbra-Calendar-Provider
VERSION:2.0
METHOD:PUBLISH
BEGIN:VEVENT
UID:040000008200E00074C5B7101A82E00800000000406D85F9CC29CC010000000000000000100000005FA7F29E92A7714F90F0215095C871E2
SUMMARY:Test meeting
DESCRIPTION:
LOCATION:Here
ATTENDEE;CN=cu;ROLE=REQ-PARTICIPANT;PARTSTAT=ACCEPTED;RSVP=TRUE:mailto:user2@domain.com
PRIORITY:5
ORGANIZER:mailto:user1@domain.com
DTSTART:20110613T230000Z
DTEND:20110613T233000Z
STATUS:CONFIRMED
CLASS:PUBLIC
X-MICROSOFT-CDO-INTENDEDSTATUS:BUSY
TRANSP:OPAQUE
LAST-MODIFIED:20110613T212242Z
DTSTAMP:20110613T212242Z
SEQUENCE:0
BEGIN:VALARM
ACTION:DISPLAY
TRIGGER;RELATED=START:-PT5M
DESCRIPTION:Reminder
END:VALARM
END:VEVENT
END:VCALENDAR
Meeting created in Outlook 2010
BEGIN:VCALENDAR
PRODID:Zimbra-Calendar-Provider
VERSION:2.0
METHOD:PUBLISH
BEGIN:VTIMEZONE
TZID:America/Anchorage
BEGIN:STANDARD
DTSTART:19710101T020000
TZOFFSETTO:-0900
TZOFFSETFROM:-0800
RRULE:FREQ=YEARLY;WKST=MO;INTERVAL=1;BYMONTH=11;BYDAY=1SU
TZNAME:AKST
END:STANDARD
BEGIN:DAYLIGHT
DTSTART:19710101T020000
TZOFFSETTO:-0800
TZOFFSETFROM:-0900
RRULE:FREQ=YEARLY;WKST=MO;INTERVAL=1;BYMONTH=3;BYDAY=2SU
TZNAME:AKDT
END:DAYLIGHT
END:VTIMEZONE
BEGIN:VEVENT
UID:040000008200E00074C5B7101A82E0080000000050A9EE87BB29CC010000000000000000100000003FF96DD71CB3114BAA3C5A0AA42D0B01
SUMMARY:test from outlook
LOCATION:not real, test only
ATTENDEE;CN=User One;ROLE=REQ-PARTICIPANT;PARTSTAT=ACCEPTED;RSVP=TRUE:mailto:user1@domain.com
ORGANIZER:mailto:user2@domain.com
DTSTART;TZID="America/Anchorage":20110613T150000
DTEND;TZID="America/Anchorage":20110613T153000
STATUS:CONFIRMED
CLASS:PUBLIC
X-MICROSOFT-CDO-INTENDEDSTATUS:BUSY
TRANSP:OPAQUE
LAST-MODIFIED:20110613T191750Z
DTSTAMP:20110613T191750Z
SEQUENCE:0
BEGIN:VALARM
ACTION:DISPLAY
TRIGGER;RELATED=START:-PT15M
DESCRIPTION:
END:VALARM
END:VEVENT
END:VCALENDAR