Remote Desktop : Why should I log out and whats the difference between disconnect and sign out / log off?

Is your RDS / TS server running slow when only a couple of people are logged in?
Do you find things such as printers stop working for no reason but a restart fixes this?

We sometimes get these question and it is related to how users EXIT their Remote Desktop Services (RDS or RDP) and Terminal Services sessions. There are two options when closing a client session: you can either “Sign Out/Log Off” or “Disconnect“.

Sign Out/Log Off – Ends the session running on the remote computer or server. Any applications running within the session will be closed and unsaved changes made to open files will be lost. The next time you log onto the remote computer or server, a new FRESH session is created and printers restored.

Disconnect – Leaves the session running on the remote computer or server. You can reconnect to the remote computer or server and resume the session. This is good if switching computers or if you are running a time consuming task , you can start the task and disconnect from the session. Later, you can log back onto the remote computer or server, reenter the session, and check the results.

What are our recommendations?
A: To ALWAYS SIGN OUT or LOG OFF.  Even if going to lunch as whilst you are disconnected, other users are being slowed down due to your session taking up unnecessary resources.
It will also refresh the memory for that session as well (especially with Google Chrome)

Show me the differences?

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.

How to make printer default in terminal server ( TS ) / remote desktop server ( RDS )

Commodore_Printer-64Whiz-Kid-predators-bbs_MPS-802

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

  1. Open Devices and Printers by clicking the Start button Picture of the Start button, and then, on the Start menu, clicking Devices and Printers.

  2. 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.

If you still need assistance, please contact Sterling IT via our contact form or call our office.