Greetings from the Macintosh Business Unit at Microsoft! We appreciate the interest many of you have shown about the new RDC client for Mac. As announced on Mac Mojo blog a couple of weeks ago, we released a public beta version of Microsoft Remote Desktop Connection (RDC) Client for Mac 2.0 on Tuesday July 31st. RDC for Mac lets you connect to a Microsoft Windows-based computer and work with programs and files on that computer from your Macintosh computer. The 2.0 Beta includes the following new features:
Currently, RDC for Mac 2.0 (Beta) is only available in English, and supports only US English keyboards. Technical support is not available for this beta release.
For more information, including a list of known issues, see the Read Me for this application. After you install RDC for Mac 2.0 (Beta), open it, and then on the Help menu, click Read Me.
This Beta release expires on March 31, 2008.
Go to this download page to get the RDC 2.0 for Mac beta build, which comes in .dmg format. After opening the disk image, double-click the Install Remote Desktop Connection package to start the installer and follow the install steps. Note that this is the same build as the pre-beta, and you do not need to reinstall if you already have the pre-beta build.
We want to read your bug reports and suggestions! Please submit feedback at the RDC Connect site https://connect.microsoft.com/macrdc. You will need to sign in with a Windows Live ID to submit feedback. Read these tips for submitting bugs & suggestions, then click the Feedback link on the left. To discuss RDC beta issues with your fellow beta testers, please use the RDC public newsgroup microsoft.public.mac.rdc. You can access the newsgroup either by a newsreader or a browser.
Please remember all bugs must be filed through the MS Connect site. Due to limited resources on the MacBU RDC team, we will not be able to respond to all the public beta feedback. But rest assured that we will review all that you send our way!
Again, thanks for your interest. We cannot wait to hear about your impression of the new Mac client!
-David Liu and the MacBU RDC team
Where do I get the needed TS CAL?! (And don't tell me to ask my networking guy internally, they do not support the Mac.)
Forgot to mention that the VPN freezes are only happening with Vista as remote client. W2K3, W2K and XP working fine via VPN tunnel. Too bad if your main workstation runs a Vista..
I use Windows Vista (and before that, XP) to administer more than 100 Windows 2003 servers in various data centers. One problem that has plagged me for almost 8 years is that copy/paste intermittently stops working between my local workstation and the remote machine. Access to the clipboard is definitely enabled, and it works briefly but then stops. I've researched it more than a dozen times, and it doesn't seem to be caused by software locking, then failing to unlock, the clipboard. It seems to happen most often when I'm copying from Office or pasting to Office on the local machine, but does affect Notepad and all other apps. I just did a clean rebuild of Vista Business + Office 2007 Ent + McAfee + Windows Updates with NO OTHER SOFTWARE installed, and I had 10 joyous hours of productivity before copy/paste stopped working (2 hours after starting my machine up this morning). I'm at my wit's end and frankly feel like dumping Windows.
Sorry to hear about the difficulties you have been experiencing. The shared clipboard has been a source of frustration over the years. Take a look at:
This posting explains why the system clipboard chain (which it the mechanism through which TS components are notified of clipboard updates) breaks so easily and what has been done in Vista and later to resolve this issue.
Can I use Terminal Services to install Timbuktu then use Timbuktu on its own later?
It appears that if TS is disconnected it stops Timbuktu from sharing the screen although the file exchange still functions.
Can anybody clarify this?
I need to be able to run Tmbktu w/o TS on occasions in order to run single copy of Filemaker Pro.
Please help! I'm trying to connect to Windows Server 2003 through my MacBook Pro 10.5.2 and I always get this error.
The mac cannot connect to the Windows-based computer. The problem might be temporary. Try connecting to the windows-based computer again, or contact your administrator.
It works fine when I try and connect from a windows computer to the server but I can't get it to work on my mac.
Fix the black and white printing!; why are we still unable to print in color from a remote session?
Does the mac 2.0 Beta client support "Start a program" like the windows remote desktop connection? I am trying to publish a application instead of the desktop. In the windows remote desktop connection (mstsc), this featuture can be found under the "Options" tab and then selecting "Programs"
The Beta expires on March 31st which is 3 days from now. Will there be an update before then?
The Beta is telling me to download the Final version -- but there doesn't appear to be a Final version...
So... today is March 31st. The beta "expires" today, and I can't seem to find any word on when (or if) the final version will be ready. Anyone able to find it?
(When I first got the message the beta was "expiring", and the page the link took me to didn't have what it said it was supposed to have, the fist thought that popped into my head was "How very Microsoft...".)
Folks, I posted about the beta2 expiration on Mac Mojo blog. Please take a look of it at http://www.officeformac.com/blog/. Or here is the direct link: http://www.officeformac.com/blog/RDC-Beta-Users--Beta2-is-Expiring--But-DonAt-Panic
I really like LogMeIn (http://www.logmein.com) to go from windows to my Mac... The nice thing is that it is accessible either through your LAN or even over the net.
Any plans or ideas on when there will be a RDC for Mac that can connect to a Terminal Server 08? I just tried ver.2 Beta 3 with no luck.
Are you connecting directly to WS2008 server and have issues with it, or attempting to connect via TSG?