Isn't about time that the Mac Remote Desktop Client finally understands how
to connect to Terminal Servers in other Time Zones other than GMT?
Across the country, we have several dozen Mac desktops and laptops running
all versions of Mac OS X and all of them are running version 1.0.3 of the
RDC. Even though the Macs are all correctly configured for the time zones
(Eastern through Pacific) where they are located, they always connect to
their local Win 2003 Terminal servers as if they were in the GMT time
zone.
We just downloaded the 2.0 Beta and tested it on a few Macs in different
time zones, and Mac RDC is STILL using GMT for the time zone, rather than
the
'local' time zone of the TermServer.
Its a simple test: RDC into your favourite TermServer; logon; open the CMD
prompt; type TIME at the prompt.
On Windows RDC connections, you will get the 'local' time of the
TermServer
regardless of what time zone the Term Server is in, or what time zone
your
host PC/Laptop is in.
On mac RDC connections, you will get the 'GMT' time of the TermServer
regardless of what time zone the Term Server is in, or what time zone
your
desktop /Laptop Mac is in.
Yes I'm aware of the 'fix' by turning off the 'allow time zone
redirection'
in the GPO, but this only works if all the Macs and Windows machines are
in
the same time zone as the TermServer. Why should we turn off a setting
that
works correctly for Windows RDC across time zones to correct a problem
with
Mac RDC?
This has been an issue for most of this decade. Will it get fixed soon?
----------------
This post is a suggestion for Microsoft, and Microsoft responds to the
suggestions with the most votes. To vote for this suggestion, click the "I
Agree" button in the message pane. If you do not see the button, follow
this
link to open the suggestion in the Microsoft Web-based Newsreader and then
click "I Agree" in the message pane.
http://www.microsoft.com/communities/newsgroups/list/en-us/default.aspx?mid=ff946a4b-5750-41e9-b431-bfcc18e5b1d1&dg=microsoft.public.mac.rdc
|
