Hi ppl. I'm not sure if this has been answered but I need to try get some sort of concrete answer on this issue. My users have found when sending appointments to different external recipients that some receive the appointment for one hour earlier than scheduled. We have an exchange 2003 server with various outlook clients and workstation os versions. We are in a non time zone country and are testing with local recipients in the same country. What I have done to try resolve the problem. 1) Have set the Domain controller to sync with a time server on the internet. 2) Set the time server in DNS to point to the domain controller. 3) checked the time zones on the domain controller the exchange server and my work station. (all (UTC+02:00) Harare, Pretoria) 4) I have tested with both outlook 2003 and 2007. Windows xp and windows 7 5) I've installed KB951072-v2 on the exchange 2003 server. 6) I’ve made sure that all the time patches are release through wsus to the clients. Yet my time is still out, at the recipient. Does anyone have something I can try to resolve this.

On Wed, 26 May 2010 07:34:36 +0000, Jihad123 wrote: > > >Hi ppl. > >I'm not sure if this has been answered but I need to try get some sort of concrete answer on this issue. > >My users have found when sending appointments to different external recipients that some receive the appointment for one hour earlier than scheduled. > >We have an exchange 2003 server with various outlook clients and workstation os versions. > >We are in a non time zone country and are testing with local recipients in the same country. > >What I have done to try resolve the problem. > >1) Have set the Domain controller to sync with a time server on the internet. > >2) Set the time server in DNS to point to the domain controller. > >3) checked the time zones on the domain controller the exchange server and my work station. (all (UTC+02:00) Harare, Pretoria) > >4) I have tested with both outlook 2003 and 2007. Windows xp and windows 7 > >5) I've installed KB951072-v2 on the exchange 2003 server. > >6) I?ve made sure that all the time patches are release through wsus to the clients. > >Yet my time is still out, at the recipient. > >Does anyone have something I can try to resolve this. Are you sure that the time zones are correct on the machines where there's a one hour difference? Your machines may be sending the the time correctly, but that time is adjusted for the time zone at the recipient's machine. If the time zone is incorrect on the recipient's machine you can't fix the problem. --- Rich Matheisen MCSE+I, Exchange MVP --- Rich Matheisen MCSE+I, Exchange MVP

Double checked with 2 external people that are recieving the appointment an hour earlier and they both have the correct time and timezone +02:00) Harare, Pretoria

On Thu, 27 May 2010 13:17:39 +0000, Jihad123 wrote: >Double checked with 2 external people that are recieving the appointment an hour earlier and they both have the correct time and timezone +02:00) Harare, Pretoria And if you send the same meeting request to several people, some internal and some external, do all the internal people see the correct time? And do only some of the external people see a different time? If *some* of the external people see a different time then it's a pretty sure thing that it's not your side that's the source of the problem since all of the external people will receive the same information. --- Rich Matheisen MCSE+I, Exchange MVP --- Rich Matheisen MCSE+I, Exchange MVP

Yeah I tend to lean that way as well, but my managment doesnt see it that way. They want me to make sure it defnitly on our side. So my next step will be to apply the below hotfix http://support.microsoft.com/kb/956398 and see if that doesn't make a diffrence. I have tried to find out from one of the company's on the out side if they have this issue all the time and they say it is only from a few clients of thiers, so it isn't even constant at thier exchange server.

Ok Looks like this is now sorted. After applying the hot fix on the main exchange server, I saw that there was supposed to be a decomissioned server that has never been switched off. Applied hot Fix and all out standing security patches on that server and that seems to have resolved the issue. The joys of joining a new environment and still having to learn about past issues.