Hi I have recently added a new 2007 exchange server into an exisiting exchange 2003 enviroment. I have having a problem where the emails deliver with the incorrect time stamp. The server time is set correctly, however when an email is received it stamps it 2 hours ahead. Hardware is set to the correct time. Is there a settting within exchange that overrides the system time? Emails delivering to the old 2003 server still show the correct time. Thanks

Is your exchange 2007 SP2? Make sure that exchange 2007 is fully updated.Also try to restart the Windows time service. Is your exchange 2003 getting the time from PDC or some external time source? How about exchange 2007??Raj

Take a look at:http://social.technet.microsoft.com/forums/en-US/exchangesvrclients/thread/baa337f5-fff3-466a-b1fa-6b478188a9d4/

I have been looking around and it looks like some of the rollups, especially 5 and 6, seem to fix this issue. Have you applied all the update rollups for Exchange 2007?http://www.tech-archive.net/Archive/Exchange/microsoft.public.exchange.setup/2008-06/msg00046.html

Hi Sorry, I should have mentioned I am already running SP2. 2003 and 2007 are both syncing their time from the PDC, which is giving out the correct time. If I set the Time zone to Athens (where the 2007 server is) the time is correct. Then when the server is rebooted it adds a further 2 hours, and the info store will not start. All the other servers in the domin are set to the Athens time zone. Thanks Chris

It is now resolved. It was the time sync service. It was trying to sync time from time.windows.com and then adding on a further 2 hours. Do a w32tm /config and make the time source the domheir. Thanks

I am always amazed how many problems are fixed by getting time sync working. Congradulations!Make sure that the PDC emulator for your domain is set to get it's time from a reliable time source...I usually pick one from this list:http://tf.nist.gov/tf-cgi/servers.cgi(I don't think that time.windows.com is all that reliable.) Copy the following into a batch file then run it on the PDC emulator:@echo offw32tm /config /manualpeerlist:time-b.nist.gov /syncfromflags:manual /reliable:yes /updatepausenet stop w32timenet start w32timepause(change the manualpeerlist to whatever you want)Then after setting the right time zone and time (use the local timezone and time)on any machine, run the following to fix a broken machine (or even just a suspect machine):@echo offnet stop w32timew32tm /unregisterw32tm /registernet start w32timenet time /domain:%userdomain% /set /yw32tm /resync /rediscoverpauseThe above works on ANY domain machine (any windows ver.).Hope this helps...sorry for the after-the-factness of the reply!