Remote Desktop Connection Client for Mac 2.0 Beta Available Now

Remote Desktop Connection Client for Mac 2.0 Beta Available Now

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:

  • Universal Binary
    Runs natively on both Intel-based and PowerPC-based Macs.
  • Remote Desktop Protocol 6.0
    Provides better compatibility with Windows Vista, improved security features, and many other improvements.
  • Multiple Sessions
    Lets you connect to multiple Windows-based computers at the same time.
  • Improved User Experience
    Provides a true Mac experience and improved usability.
  • Improved Customization Options
    Lets you change application preferences, including keyboard shortcuts, while you are running a session. Changes take effect the next time that you connect.
  • Dynamic Screen Resizing
    Lets you resize your session window or switch to full-screen mode during a session.
  • Improved Printing Support
    Supports all configured printers on your Mac. No longer limited to PostScript printers.

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.

Downloading

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.

Submitting Feedback

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

 

Leave a Comment
  • Please add 6 and 6 and type the answer here:
  • Post
  • I need the TS Gateway support too for our MAC computers. We don't want to open 389 ports to the internet, but are almost forced into it now... :( Is there any development going on on this?

  • Please add TS Gateway option on the Mac RDC!!!

  • Another big vote for adding TS Gateway support! We want to get rid of Citrix but can't because of this.

  • Again, please add support for TS / RD Gateway to the Mac RDC client! Doctors tend to like Macs, and they are angry they can't connect to the RDS server I just built up for them. Opening 3389 to the outside world is crazy, and not an option! Please, please, please fix this!

  • If you have a single Terminal Server, why is opening port 3389 to the outside world so crazy?!  

  • Another vote for TSG support!! It's crazy that I need VMWare to run a windows client to connect to my employers virtual machines!

  • VMWare is one method ($$), another option is to deploy a VPN for Mac clients.  Once they connect to the VPN (which can be port restricted to 3389) then they can connect to a terminal server bypassing the gateway.

    Having said that, I completely agree that this is taking far too long to get a compatible Mac client.

  • Another vote for TS Gateway support!

  • and another vote for TS Gateway support in Mac RDP client. ... It's getting more common that employees have Mac at home as they are gaining ground ... Businesses want's go have that connection working on Mac ... oh yes and perhaps even in other browsers too!

  • One more vote for TS Gateway support. PLEASE!!!

  • When will the Mac TS client support TS Gateway.

    I think it's pretty shoddy that Microsoft are releasing client software that doesn't work with its own server software with no ETA on when the problem will be fixed.

  • Sometimes what is built comes at the request of a specific customer, with specific requirements.  It's possible that RD Gateway support was not in scope with the customer requirements.  If you do need secure remote access from Mac/Linux to RDSH or VDI both Quest vWorkspace and Citrix XenDesktop add this functionality to the Microsoft platform. (Disclaimer, I work for Quest).

  • Shocked that MS didn't include support for the TS Gateway. Please add it ASAP.

  • Here´s another vote for TS Gateway support for Mac!

  • I am currently rolling out Remote Desktop Gateway R2 with Windows Server 2008 R2 which is to become a key component to Remote Desktop solution providing secure encrypted Remote Desktop solutions. We have around 35-40 MACs and have now discovered these won't support TS Gateway. How can Microsoft build such systems without enabling them to support other clients like MACs? It looks like I may have to open up standard ports for just 5% of my user base. Please add this functionality ASAP.

Page 5 of 12 (179 items) «34567»