M
mcandy72
I have one Exchange (2003) Server in Arizona that is accessed by users
in Phoenix as well as users in Boise. I am trying to figure out how
to deal with the two different time zones as it relates to scheduling
appointments.
Some of our Boise users connect via Remote Desktop and run Outlook
2003 (installed on the server in Phx) over RDP. I have enabled the
"Allow Time Zone Redirection" group policy, so Boise users connecting
to RDP sessions get the correct time on the sys tray clock, but when
they schedule appointments with the Phoenix users the time reflects
Phoenix time, not Boise time.
Example: User 'A' is in Boise and schedules a 3:00 PM conference call
with user 'B' in Phoenix. User 'B' shows the appointment (on their
schedule) as being for 3:00, but it SHOULD be for 2:00 as Phoenix is
currently one hour behind Boise.
Some of our Boise users access the Exchange server directly from their
laptops (Outlook 2003) and they do not have this problem, scheduled
appointments show the appropriate time on Pheonix users' calendars.
It is only the RDP users (in Boise) who have the problem. Again, the
system clock in their RDP session DOES show the correct time, but it
seems that Outlook is pulling the time from the server, not the RDP
session.
I have looked online as well as in several Exchange books to find how
to address this, to no avail. I know we are not the first people to
run across this, but the only online results I can find are relating
to the DST issue which does not help us.
Thanks in advance for any help!
in Phoenix as well as users in Boise. I am trying to figure out how
to deal with the two different time zones as it relates to scheduling
appointments.
Some of our Boise users connect via Remote Desktop and run Outlook
2003 (installed on the server in Phx) over RDP. I have enabled the
"Allow Time Zone Redirection" group policy, so Boise users connecting
to RDP sessions get the correct time on the sys tray clock, but when
they schedule appointments with the Phoenix users the time reflects
Phoenix time, not Boise time.
Example: User 'A' is in Boise and schedules a 3:00 PM conference call
with user 'B' in Phoenix. User 'B' shows the appointment (on their
schedule) as being for 3:00, but it SHOULD be for 2:00 as Phoenix is
currently one hour behind Boise.
Some of our Boise users access the Exchange server directly from their
laptops (Outlook 2003) and they do not have this problem, scheduled
appointments show the appropriate time on Pheonix users' calendars.
It is only the RDP users (in Boise) who have the problem. Again, the
system clock in their RDP session DOES show the correct time, but it
seems that Outlook is pulling the time from the server, not the RDP
session.
I have looked online as well as in several Exchange books to find how
to address this, to no avail. I know we are not the first people to
run across this, but the only online results I can find are relating
to the DST issue which does not help us.
Thanks in advance for any help!