We’re looking for a replacement for the Mac RDP client. We have one client whose clock is off no matter what in Outlook. Using a Windows PC is not an option for various reasons. Using parallels isn’t really an option. This was tried and it created more calls for us than using something more native to OS X. This user is on an x86 Macbook Pro laptop. She has limited technical skills. We are trying to make her life easier and simplify the process for her to connect to the terminal server farm where all of their data lives. RDP6 for Mac (Remote Desktop Connection 2) is the best solution we have so far, but it still sometimes has issues with the timezone for her. Lastly, using Entourage 2004/2008 or Mail is also not an option – the business owner does not want any local data to reside on any PC due to security concerns.
What we want to do is run the Windows binary of RDP5 or RDP6 on a Mac or more easily run the Linux rdesktop command with a GUI wraper. I run this tool frequently from the command line or the GUI wrapper in Ubuntu or other distros and it works great.
Can someone with an Intel Mac try this: http://desktopecho.com/iMKS/ and let me know how easy it is to setup and use? It replaces TSClientX, an opensource GUI wrapper of the opensource RDP client. TSClientX was awesome – a GUI wrapper to rdesktop. Unfortunately it isn’t supported in 10.5 and the 10.5.5 or 10.5.4 update broke it (changes to the x11 environment I believe). We want to see how easy it is to setup and use RDP, either the Linux tool or the Windows binary for RDP5 or RDP6.
The other thing we’d like to try is WINE: http://wiki.winehq.org/MacOSX with a walkthrough here: http://davidbaumgold.com/tutorials/wine-mac/.
The last time I looked, the Windows RDP5 binary worked. RDP6 was not. This may have changed as that was six months ago.
We have tried CoRD – http://cord.sourceforge.net/ – but it feels slower than Microsoft’s RDP method or rdesktop.
My feeling is strongly that the time zone issues are not a function of the method of access. It wouldn’t matter if you used RDP or VNC.
The profile you access with the client is where the time and time zone issues need to be resolved. It’s possible the system clock on the remote system is significantly off?
Am I misunderstanding the issue?
Time and time zone are not set in the RDP client, nor are the MacBook Pro’s settings carried to the remote system.