The quick and easy way to connect to a Windows remote desktop from your tablet, PC, or smartphone. Seamlessly connect to and support your macOS computers from any location or device. Powerful and fast access to your remote desktops in Linux.
Microsoft Remote Desktop Connection Client V2.1.1 Mac OS XIt is expected to come to new and existing Windows Phone 8 phones starting this summer. Our fully managed desktop as a service (DaaS) solution provides business owners and IT managers more time to focus on core business initiatives. Our DaaS offering is cost-efficient, fast, and scalable.It will disable TLS 1.0 and 1.1 which may break client connections to your website. Please make sure that RDP will continue to function as Windows 2008 R2.Many Windows Phone users were none too happy that Microsoft delivered Remote Desktop apps for Android phones and iPhones last fallWith no word on when it planned to introduce a Windows Phone version. In March, Microsoft updated the Remote Desktop apps for Android, iOS and Mac OS X, still with no word as to when or how it would provide remoting for Windows Phone.Remote Desktop allows users to connect to remote Windows PCs and access resources from those machines. Microsoft announced this week that has deprecated Remote Desktop Connection Manager (RDCMan) due to security concerns.Lots of lag and just generally a little flaky in my use.Conversely, Microsoft’s offering is fairly straightforward if you are used to the Windows RDP clients. However, overall the perfomance was pretty bad in my setup. Here is the short version of my results:CoRd has some cool features like automatic screen resizing when you resize the window and it has a nice interface for adding and saving connections. ITap mobile mobile RDP is the most powerful RDP client +fast and optimized RDP implementation with RemoteFX +secureby supporting NLA and TS Gateway +handy 3 different cursor modes +convenient gesture control +universalbinary for iPad, iPhone and iPod +available on Android as wellThe first option is Microsoft’s official RDC client for Mac OSX.The second option is CoRD, an open source alternative RDC client for Mac OSX.I installed both and tested them from my MacBook Air to my Dell M6500 laptop and a variety of other systems over the course of a workweek. The licensing requirements for these apps are complex. Client-access licenses and supporting back-end infrastructure are required to make Remote Desktop work on Windows and non-Windows devices.Like the other existing Remote Desktop apps, the Windows Phone 8.1 preview version is free.Then either let it save as default (not really recommended), or save off a connection.I have an update on my mac RDP experience, but no solution. I am looking for a permanent solution (so you don’t have to press “Continue” every time)…UPDATE 1: Commenter Zachary suggested I just fix any certificate errors, but alas this is not always an option for me.UPDATE 2: you can see how the Windows based Remote Desktop Client handles this situation:It seems an ideal solution to me… it notifies you once, but you can turn off subsequent notifications.UPDATE 3: Commenter Dustin has the easy solution for auto-bypassing certificate errors when connecting to Windows machines from Macs, awesome work Dustin!If you’re working with saved connections…“Always connect, even if authentication fails.”The authentication they speak of is machine authentication, not user account authentication.If its not a saved one, go from RDP -> Preferences. Do you want to connect to this computer anyway?” You can bypass this message and still connect to the computer by clicking Continue. Those two clients are definitely worth taking a look at as unfortunately MS seems to be letting their MS RDP client languish □*Note, there is one minor annoyance: when connecting to some Windows based PC, Microsoft’s Remote Desktop Connection Client for Mac may display a warning message: “The server name on the certificate is incorrect. It performs smoothly even on slow connections and did I not notice any deal-breaking* issues.UPDATE: Some commenters have suggested that CoRD performance has progressed nicely over since this article was first written and iTap for desktop has also come online as a nice option for those willing to pay money for a RDP cleint.I figured the RDP keyboard latency was because of this (that MS just needed to fix their client, and possibly CoRD needed to catch up too). I decided to get a Windows 7 ISO and install VMWare Fusion. A few hours after my last post, I saw this message on the MS site and decided to give up on any mac client – RDC or CoRD. To my surprise, all of the describe the same experience. I went around the office asking other people using mac rdp. After all, its not the client. I started mstsc.exe … and … SLLLOW!At this point, I started to suspect something more fundamental – something is up with the mac os itself. The virtual itself behaves very well – very responsive. SonicWall has a mac client, but its not free. This network requires the use of the SonicWall VPN client. Dual booting is quite different.BUT – (one more wrinkle) – I decided to use the mac to connect to another network I do development on. (right?) I was willing to accept the virtual because I could run the virtual full screen in another desktop and just slide to it whenever I want – in other words, I would have the best of both worlds. Use mac for windows usersBUT, the mac, running Windows 7 virtual, running SonicWall VPN client, then RDP to server = fast!I’ll let you know if I learn anything else… hopefully there is a resolution before I shoot myself in the face. It doesn’t do me a lot of good since I only use this connection for a small part of my work.I have no idea why this works – the mac, running Windows 7 virtual, normal RDP to server = slow. To my surprise, the keyboard latency vanished! I get wonderful performance in this one special case. After installing the client, I RDP into the development server located in this network. I haven’t been able to identify a sequence of events leading to the problem, so without establishing that pattern, there is little hope of understanding or fixing it since it happens relatively rarely, it isn’t a show-stopper.I have used the 2.1.1 client to connect to Win 7 and Win XP systems on my local LAN, and to a Win XP system at work using the Cisco AnyConnect VPN client.Now that I know about the official incompatibility statement, I may think twice about upgrading to Mountain Lion, and I hope that perhaps Microsoft will eventually provide an update (pretty please!)For those having trouble with memory leaks in MS’s RDC for Mac app, try disabling the Drives Redirection – set it to None. The only trouble I have is that I will occasionally be unable to establish a connection, and only a reboot will restore normal function. I’m surprised at my good fortune to have avoided the problems so many others have had, since I don’t usually find myself to be especially lucky regarding technological ease, as I’m usually spending an uncomfortable amount of time resolving one problem or another.I have not experienced any sluggish behavior such as the keyboard lags reported by others. I would not even have known about the purported incompatibility, except that I was advising a friend how to get set up on his new Macbook Air, and while hunting for a link to the RDP client to send him, I happened to notice the statement from Microsoft. When deciding to upgrade to Lion, I was not aware of Microsoft’s advisory about incompatibility, and I never experienced any noticeable trouble. So the only other thing I could think of was when I moved to using the Mac Mini, I lost that binary clipboard capability and so started using share folders.I’ve now disabled folder redirection in all my. Also, copy’n’paste a large file didn’t result in increased memory use.I then thought back to some time ago when using MS’s RDC for Mac, before I got the Mini or started using CoRD on the MacBook Pro, as I was sure I didn’t have this problem with Snow Leopard and probably not with Lion either.
0 Comments
Leave a Reply. |
AuthorMartha ArchivesCategories |