

- REMOTE DESKTOP FOR MAC OS X MOUNTAIN LION SOFTWARE
- REMOTE DESKTOP FOR MAC OS X MOUNTAIN LION LICENSE
As long as the server works for the users I am now happy. To be honest I don't really know where to point the finger either to place blame and I really don't care. So in the end, neither Microsoft nor Apple will own up to the cause of the issue nor offer a solution that actually works. I am not affiliated with them but boy did they help me out.

If you want to read more back and forth banter about this issue and where I found most of my information, check out the following site. (I just reactivated online though and it worked just fine.) Reactivate the Terminal Services Licensing server by using the Telephone connection method in the Licensing Wizard. Quit Registry Editor, and then restart the server.

Right-click each of the following values, click Delete, and then click Yes to confirm the deletion: ** Make a backup if you want to but it should not be needed HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Terminal Server\RCM Locate and then click the following registry subkey: Follow the steps below then return to the above client steps: If you still encounter the licensing error you will need to follow the steps outlined to correct the certificates. you should be able to reconnect easily at this point with no licensing error Reconnect with the MS RDC Client v2.1.2 and verify creation of the files f. Change the permissions of the Microsoft folder as well to Everyone -> Read and Write e. Change the permissions of this folder to Everyone -> Read and Write d. Macintosh HD > Users > Shared > Microsoft > RDC Crucial Server Information b. Here are short and to the point steps to fix the Mac client: So this seems simple enough right? It is once you find the area where the permissions issues happened.
REMOTE DESKTOP FOR MAC OS X MOUNTAIN LION LICENSE
Due to permissions on the Mac client, the new license information was unable to be downloaded to the client. When I finally got the licensing server to work, that's when the Macs lost their ability to connect. When connecting to the RDS server, the MS RDC client pulled down licensing information related to the grace period. When the RDS server was set up initially, I didn't have the licensing server correctly configured and licensed so the users were running in the Grace Period. In the end it is a MAC issue, not a Microsoft issue, however the only way the issue is evident is through the Microsoft RDC Client.Ĭause: This is the short version. So I solved this issue with lots of trial, error, and searching for bits of info in all dark alleys of the internet. I am hoping someone here may have a better solution available or maybe has run into the same issues as I. We have staff coming back on Monday and students in 2 weeks. I am at my wits end and am looking for a last straw to get our district to connect to the new server. I know this, but was lookign for an alternative or a direction for a solution, not the blanket not supported statement. All they said was RDC for Mac is not supported on Mountain Lion. I proposed the same question there, basically a copy and paste of my original question. I sent in a ticket to MS Technet support for 2012 Remote Desktop Services and the only answer they gave me was talk to the MS Office for Mac community. It doesn't work consistently and complains of a licensing protocol issue where no issue exists. MS RDC 2.1.2 - Not really released yet, but is available on a randon guy's dropbox account online in many forums. This may be a network issue and not thinomenon though, but other apps seem to handle it better if it is a network issue. It has the same effect if you were to unplug from the network and disconnect from the server. Thinonemnon - This solution connects fine but has proven to be unreliable as the connection drops often. It is hard to predict, but easy to reproduce. The Microsoft RDC Client for Mac has not been updated and is no longer supported as far as I can tell.ĬORD - This one tends to make the cursor disappear and become unusable. I have tried using a few different solutions to connect with the Mac and nothing so far has worked well.

The server runs great when connecting to it from a PC. In an effort to get the terminal server into a current OS, I built a new server as 2012 enterprise and configured Remote Desktop Services. In order to accomplish this we have been running terminal services.
REMOTE DESKTOP FOR MAC OS X MOUNTAIN LION SOFTWARE
We are a Mac school district with the need to run certain PC only software for students and staff members. Is there a good alternative to the Microsoft RDC Client provided with MS Office for Mac?
