Groupwise 6.5 client only time stamp one hour ahead

[pete...@mustangps.org]

Need help with the problem
Problem started after daylight saving time change
All my servers are in time sink with the correct time
In groupwise web access the time is correct
But in Groupwise client time stamp is one hour ahead.
So in a nut shall when receiving a e-mail the time stamp shows one hour
ahead in the groupwise client only

[al...@field.com]

I'm still having the same problem also. But only with workstation installed
clients.

[Danita Zanre]

pete...@mustangps.org wrote:

> So in a nut shall when receiving a e-mail the time stamp shows one hour
> ahead in the groupwise client only

Have you looked at this?

https://secure-support.novell.com/KanisaPlatform/Publishing/741/3802376_f.SAL_Public.html

--
Danita Zanre
Novell Support Forums Volunteer
Are you a GroupWise PowerUser?
http://caledonia.net

[in...@intsol.net]

Yes - I have; all these actions have been taken. The confusing part is
that all the documentation indicates the clients pull the info from the
workstations, which are correct.

[in...@intsol.net]

We're seeing this problem on every Groupwise system - those on Netware
servers, Small Business Servers, and Windows Servers. All timestamps are
1 hour off.

CindyB.

[Danita Zanre]

in...@intsol.net wrote:

> The confusing part is that all the documentation indicates the clients
> pull the info from the workstations, which are correct.

Well, they do, but the POA is what stamps the delivered time on the email.
If it isn't correct, then it will stamp the wrong time. So, after you
updated the timezones in ConsoleOne, you restarted the POA, right?

[Danita Zanre]

in...@intsol.net wrote:

> We're seeing this problem on every Groupwise system - those on Netware
> servers, Small Business Servers, and Windows Servers. All timestamps are
> 1 hour off.
>
> CindyB.

Need to know a bit more what you have and haven't done already. However, one
thing that is forgotten a lot is to change the timezone designations in
ConsoleOne and restart all of the agents.

[pete...@mustangps.org]

Yes I did Today. I got a e-mail that told me a work around Disable DST on
the windows Station and set the time manually. When
this is done the time stamps on the emails (even ones already
received) change back to normal. I have messed with allot of windows
and netware settings to no avail,

[i...@comalt.org]

On Mar 14, 5:25 pm, peters...@mustangps.org wrote:

I've had this issue as well. Microsoft released an interim patch last
week (KB932590) that is supposed to correct tz information in
applications not recognizing the original windows DST patch released
back in November. When I apply this patch and restart, GW client
timestamp is back to normal. The next day, however, it reverts back to
the original behavior of 1 hour + on the timestamp. Apply the patch
again, same results -- ok for 24 hours. I am investigating whether
disabling the "Internet time" auto-synchronization may allow this
patch to persist, as it is obviously a better solution than ignoring
DST. I've set up two workstations, one in each configuration, and will
report results tomorrow.

Environment: Groupwise 6.5 SP6 - dstshift applied, java patched.
Windows XP SP2, GW client 6.5.7

[i...@comalt.org]

On Mar 15, 9:06 am, i...@comalt.org wrote:
> On Mar 14, 5:25 pm, peters...@mustangps.org wrote:
>
>
>
> > > i...@intsol.net wrote:
>
> > > > The confusing part is that all the documentation indicates the clients
> > > > pull the info from the workstations, which are correct.
>
> > > Well, they do, but the POA is what stamps the delivered time on the
> > email.
> > > If it isn't correct, then it will stamp the wrong time. So, after you
> > > updated the timezones in ConsoleOne, you restarted the POA, right?
>
> > > --
> > > Danita Zanre
> > > Novell Support Forums Volunteer
> > > Are you aGroupWisePowerUser?
> > >http://caledonia.net
>
> > Yes I did Today. I got a e-mail that told me a work around DisableDSTon
> > the windows Station and set the time manually. When
> > this is done the time stamps on the emails (even ones already
> > received) change back to normal. I have messed with allot of windows
> > and netware settings to no avail,
>
> I've had this issue as well. Microsoft released an interim patch last
> week (KB932590) that is supposed to correct tz information in

> applications not recognizing the original windowsDSTpatch released

> back in November. When I apply this patch and restart, GW client
> timestamp is back to normal. The next day, however, it reverts back to
> the original behavior of 1 hour + on the timestamp. Apply the patch
> again, same results -- ok for 24 hours. I am investigating whether
> disabling the "Internet time" auto-synchronization may allow this

> patch to persist, as it is obviously a better solution than ignoringDST. I've set up two workstations, one in each configuration, and will
> report results tomorrow.
>
> Environment:Groupwise6.5 SP6 - dstshift applied, java patched.

> Windows XP SP2, GW client 6.5.7

The solution seems to be applying the MS patch and disabling autosync
on the Internet Time tab, leaving DST enabled. All tests here give
correct mail time stamps in the Groupwise client.

[Paul]

I had the same problem untill I changed the timezones in C1

and restarted all agents.

Everything seemed to get fixed after that.