Cannot RDP using OSX. RpcOverHttpEndpointException: 2, Your connection was denied because of a Resource Access Policy (TS_RAP). Please contact your server administrator

remote-desktop

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)

/Users/username/Library/Containers/com.microsoft.rdc.mac/

Then the next time that you load the client, you get a completely fresh client version, including first run prompts etc. You will need to re-create the profile and gateway however.

After doing that, we no longer get the ‘login failed’ popup.

It seems that something in the version upgrade doesn’t correctly upgrade the settings files, causing the issue. But a fresh setup works.

We haven’t yet found out exactly which file causes the issue however we have tested and can confirm this fix allows the system to connect and work.

 

Credit: Tony “tbigby” Bigby

No audio device found in Remote Desktop Terminal Server client redirection on 2008 or 2012 server

no-audio-card-sound-on-2012

Having a problem getting audio sound redirected over terminal server or remote desktop server 2008 or 2012 to the client?

Here are a couple of things to check to enable audio redirect, even when server has no audio sound card.

When you connect the client to the server, it will redirect all sounds to be played via your local sound card however this may fail due to the following issues.

  1. Make sure the client has Audio enabled.
    • In the Remote Connection (MSTSC.EXE) , under LOCAL RESOURCES – > REMOTE AUDIO SETTINGS, make sure PLAY ON THIS COMPUTER is enabled
  2. Make sure that on the 2012 Server, DESKTOP EXPERIENCE is installed. This can be found under Server Manager under Roles and Features
  3. Right click the speaker icon and make sure you can test a PLAYBACK SOUND. There should also be a VIRTUAL SOUNDCARD listed
  4. If you still get NO AUDIO DEVICE FOUND at this stage, you will need to go back to server manager, under the SERVER COLLECTIONS, make sure that the REMOTE USER has Audio enabled.

If you require further assistance or more technical information, please make comment and we will be happy to further assist.

SBS 2011 Can’t connect to the remote computer because no certificate was configured – Remote workplace certificate error

Problem:
When connecting to Windows SBS 2011 Remote Web Access, the following error appears when trying to connect to a remote computer.

RWA-Cant-Connect

 

 

 

 

 

 

Your computer can’t connect to the remote computer because no certificate was configured to use at the
Remote Desktop Gateway server. Contact your network administrator for assistance.

Solution:
You need to repair the Remote Desktop Gateway (RD Gateway) service in the the RD Gateway Manager management console.

By default, SBS 2011 does not have the RD Gateway Manager management console enabled, The following command will properly install the RD Gateway Manager management console:

dism /online /Enable-Feature:Gateway-UI

Run this command from an elevated command prompt.

Then follow these steps

  1. Open the Remote Desktop Gateway Manager from Administrative Tools > Remote Desktop Services.
  2. Right-click your server name and choose properties.
  3. Select the SSL Certificate tab.
  4. Click the Import Certificate… button.
  5. Choose your trusted certificate and click Import.
  6. Click Ok.

RDCM-SSL-Certificate

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

note: you may need to assign a different certificate, then reassign the desired certificate to force RD Gateway Manager to take effect

See Also:
How to Install Your Existing Certificate into SBS Essentials

 

SOURCE: Thanks to stevehardie.com – This is used for reference and internal use.