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?

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.

Microsoft Remote Desktop on Apple mac OSX and Windows 2012 – How to fix & get updated software

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…

Another alternative is a product called CoRD – Home Page of CoRD