Some customers are reporting that the Omni Mobile client produces calendar items that show up in the GroupWise client calendar as one hour earlier.  Please review this post if you believe this is related to Omni Mobile and Daylight Savings Time.

There are 6 key elements that can affect time with Omni Mobile.  They are:

•  Server Time - the WebAccess Agent and all other GroupWise agents read the server time to calculate timestamps.

• Agent Time Zone Setting - all GroupWise Objects (Domain, PO, GWIA and WebAccess objects have a field to specify time zone settings.  If one of those are set different from the others, you may see different timestamps for mail items, e.g. if the PO is set to MST and WebAccess is set to PST, you may see a one hour difference on the timestamps for calendar items depending where they are being viewed from.

• WebAccess client time – while logged into WebAccess, each user has their working time zone information saved into their client options.  If you notice that calendar items created in WebAccess are off when they appear in the GroupWise client calendar, the WebAccess client options may have the wrong timezone “foot-printed” into the time zone value.  Even though the correct time zone may be displaying, an incorrect value may be saved in the background.  To correct the problem, the user needs to set the time zone value in “Options” to a different time zone and save the change.  Then the user changes that value back to the correct time zone value and saves the changes again.

• Local computer time - the GroupWise client uses the local computer time to timestamp all email/calendar items.  If the local computer is set for MST and WebAccess is set in the browser for PST, you will see a difference in the timestamps for items when viewed in the gW client versus the WebAccess client.

• Mobile device time - may have an effect on email/calendar items originated from the device.
  

• OM client options time zone setting - which DOES NOT respect daylight savings time (DST) ... this explains why New Zealand times were out by one hour.  Although the device will respect DST the OM client will not.  If the local time is in DST, then the OM  In the New Zealand example, when the Time Zone in the OM client was reset to +13 hours, all timings matched between calendar items as viewed on the OM device and in WebAccess and the GW client. Client options need to be adjusted to what the real difference is between local time and UTC.

TIPS and SUGGESTIONS:

1.       Always set time zones for the GroupWise objects and the hosting server times/time zone settings to match.

2.       Always ensure that user’s local computer time and time zone settings are correct.

3.       Always ensure that the mobile device time and time zone settings are correct.

4.       When actual time is Daylight Savings Time (DST), adjust the time zone settings in the OM client options to reflect the actual time difference between local time and UTC.

DAYLIGHT SAVINGS TIME:

The current release of the Omni Mobile client has a bug relating to Daylight Saving Time. Refer to "Time Sync Out By 1 Hour" for more information on how to correct the problem.  

For more information about Omni Mobile, please go to www.omni-ts.com/mobile-groupwise