Microsoft Remote Desktop Connection For Mac
Have you ever wondered why your Remote Desktop Connection on your Mac works well on one system but not on another? I was testing out my connectivity to some of my customers’ network using n on my MacBook Pro.
Microsoft Remote Desktop Connection For Mac
This used to work on one of their environments but now it doesn’t. I was under the impression that there must be something that changed on my system. So I did a quick check but couldn’t find anything that has changed on my MacBook Pro (it simply means that I rely so much on VMs that my host machines – whether PC or Macs – don’t get changed that often.) What’s even more frustrating is that it works on one environment but not on another.
This clearly means that there must be something that was changed on my customer’s environment. After asking a bunch of questions, it appears that they have upgraded their server operating system from Windows Server 2003 to Windows Server 2008 R2. Since Windows Server 2008 R2 is secure by default, some of the security policies in place may be preventing the Remote Desktop Connection for Mac client from establishing a connection. But here’s where my confusion lies. The error message does not tell me anything related to those security policies.
You were disconnected from the Windows-based computer because of problems during the licensing protocol. I mean, seriously, how does that error message help me? The reason I ask is because I have configured a Windows Server 2008 R2 Terminal Services server in the past and I was able to connect from a MacBook using the Remote Desktop Connection for Mac client.
Because I cannot do anything on the server to fix this issue, I decided to dig deeper ( a.k.a do a Google search.) It seems that there are a lot of people who are experiencing this same issue. A very popular forum post regarding this issue is from where the thread kept going for more than a year. Somebody pointed out a that outlines the steps that you need to do on the Terminal Server.
Maybe they shouldn't be ignored. Maybe calling attention to this is a good thing. Drunk assholes are usually still assholes when they sober up, IME. Student known for 'mac-and-cheese tirade set to return to. That is the whitest sentence I've seen lately.
Microsoft Remote Desktop Connection For Mac Os X 10.8.5
As I mentioned, this is not the path that I can take unless I’m the server administrator. One thing did work for me:. I have searched for it on the Microsoft Download Center but could not find it anywhere.
Technically, this is still an unsupported product so be aware that you might not get any help from Microsoft when using this. Install it on your Mac, run it and test your connectivity to a Windows Server 2008 (or higher) Terminal Server. NOTE: Please remove the PDF file extension from the file after downloading. I know this is an old thread, but it is still among the top listings for what is a current issue. Version 2.1.1 of the Microsoft Remote Desktop Connection Client for Mac fails to work with a Remote Desktop Server (aka Terminal Services server). It will work with an Admin remote desktop session (i.e. 2 user limit) to a Windows server but not an actual Remote Desktop Server.
The above mentioned licensing problem occurs. A resolution appears to be using the newer Microsoft Remote Desktop v 8.0.14 app from the App store.