Windows client uses the pc and the servers time and time zone to figure the time to show and send all items. Problems arise when there is an old client data meta file still inside of Windows. The client will then, after un-install or upgrade, use the wrong time basis to handle and display transmitted task... ie sent-items, task.
The Server can have the right time and time zone, but the upgraded client still will not change it's configuration and stays off in time, 1 or 2 hours, depending on DST or not.
Why not have Groupwise client have it's own NTP setting to verify time with the pc? Most Windows' pc's do not change from time.windows.com unless the admins have changed it.
Linux doesn't have a 2014 version, but the same problem exist from the 2012 and version 8. It no longer is the SATA issue.

by: Jerry B. | over a year ago | Windows Client