Outlook 2003 -- Booking of our Board room displayed different time
Hi, recently, I found out when we tried to book our Conference room resource for meetings, the booking showed up a different time than we setup. E.g when I booked for 12pm to 1pm, the booking showed up as 1pm to 2pm instead. It did display the correct time zone.
Now, I recently performed an offline defrag on our database. Has this defrag got to do with this booking problem?
Now, I recently performed an offline defrag on our database. Has this defrag got to do with this booking problem?
ASKER
Seriously? If this happened 3yrs ago, why would I only notice it now? Strange.
check your time zones and other time setting in Exchange server, if you are using it...
ASKER
Dandraka, I checked Windows 2000 server, my Outlook 2003 and my WinXP Pro machine and they looked correct. Is there a specific settings in Exchange 2000? If so, where can I locate this setting?
There is no setting for the time zone in Exchange. As I mentioned previously, DST patches need to be applied to Exchange if you haven't already obtained and applied them.
JJ
JJ
In your email account check the Tools --> options, Preferences tab, click on Calendar options and then on Time Zones...check to see if the machine you are booking the meeting from is on a different time zone than the correct one.
For exchange settings see the links below:
(1) http://support.microsoft.com/kb/931667
(2) http://support.microsoft.com/gp/cp_dst (http://support.microsoft.com/gp/cp_dst)
hope these help...
For exchange settings see the links below:
(1) http://support.microsoft.com/kb/931667
(2) http://support.microsoft.com/gp/cp_dst (http://support.microsoft.com/gp/cp_dst)
hope these help...
ASKER
Ok, I'm getting a little confused. Is the problem with Exchange 2000 running on Windows Server 2000 box or is this a workstation running WinXP Pro with Outlook 2003 problem?
Dandraka: Yes, I have checked the time zone on my computer. It was the first thing I checked.
Dandraka: Yes, I have checked the time zone on my computer. It was the first thing I checked.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
If you are running Exchange 2000, the problem is likely due to the fact that it isn't patched for the 2007 DST update. Unfortunately, Exchange 2000 is under "extended support" so you need to contact Microsoft and pay them to get the fix.
JJ