After spending many hours trying to resolve a Mac OSX system remoting to a 2012 R2 RDS/TS Server, we have found the fix.
When remoting in you may get the following error: Cannot RDP using OSX. RpcOverHttpEndpointException: 2, Your connection was denied because of a Resource Access Policy (TS_RAP). Please contact your server administrator
This error is with Microsoft Remote Desktop on a Mac with version 8.0.28 that had been upgraded from 8.0.26.
Interestingly we didn’t have the problem on a fresh client that had 8.0.28 installed fresh and not upgraded from an earlier version.
Navigate and delete or move the following folder: (NOTE: doing so will delete all your preconfigs saved currently)
If you are wanting to use your printer on a Terminal Server (TS) or Remote Desktop Server (RDS), ensure you have allowed your connection to redirect your printers or they will not been seen on the remote server.
To set your remote session default printer, please ensure that if you want a local printer to be the default printer on the server, it must be set to the DEFAULT printer on your computer.
To select a default printer
Open Devices and Printers by clicking the Start button , and then, on the Start menu, clicking Devices and Printers.
Right-click the printer you want to use, and then click Set as default printer. (You’ll see a check mark on the printer’s icon signifying that it’s now your default printer.)
If you are running a Thin Client device, you will need to either have a VPN setup or the printer needs to have its port and IP address open to the internet. Setting default printers on Thin clients, (unless there is an OS or is capable of seeing the local printer in its OS), is a little more complex and not discussed here.
Watch out – the old OS X Microsoft Remote Desktop (version 2.1.1) that comes with Mac Microsoft Office 2011 no longer works with Windows 2012 R2 (it does work with plain old Windows 2012). For me it fails with the following error message:
Remote Desktop Connection cannot verify the identity of the computer that you want to connect to.
A (regular) Windows 2012 Remote Desktop client doesn’t have this problem.
(Brief aside – Microsoft have a little note that says the 2.1.1 client is not supported on OS X v10.7 or later. Who knew and why did it make me report all those crashes?)
The good news is that the new OS X Microsoft Remote Desktop 8.0.24091 (Mac App store only though – grr) does work with Windows 2012 R2 . Why this information isn’t listed on the What’s New in 2012 R2 Remote Services page I don’t know…