Three questions:
S. Todd Stevens said:
Bill,
1. Yes.
2. Yes.
3. Yes.
Thoughts?
I've seen this before with one of my folks on the East coast. Our server
is Central. He had a shared calendar he used for posting vacation times
and had the same issue. It stemmed from Outlook on the East coast
reading the calendar from the Central time zone. The event was scheduled
in Outlook on the East coast as an all-day event but this was treated as
11:00 p.m. to 10:59 p.m. when read from the server. Essentially, the
one-day event now appeared as a two-day event.
While I was troubleshooting I determined that my Entourage was
up-to-date and therefore dismissed that as the cause of the problem.
However, my user's Outlook was older than mine. I asked him to have his
local IT person update him but he never followed through. So, dead end
on that idea.
Unfortunately, it wasn't a huge problem for him and he worked around it
somehow. But I think this is somehow related to a misconfigured time
zone on on a client workstation or the client application (Outlook and
Entourage both have time zone settings) or possibly the server. This
could also be an Exchange setting but I'm not sure how Exchange deals
with time zones.
I'm sorry that this isn't much to go on but it's a problem I would love
to know how to resolve in case I see it again. Play around with
Outlook's time zone setting. Setting it to match your server's time zone
may be the answer.
Good luck! bill
