It is currently not possible to directly map a drive letter to a redirected folder when connecting to a server using Microsoft RDP. Most programs do not require a drive letter but in case you do need a "local path", you can create a symlink in order to achieve this.
MKLINK /D C:\MyFolder \\tsclient\MyFolder
This will create a "symlinked" folder on your C-drive, which you can then use to work with files and folders of the redirected folder. The symlink is persistent across reboots.
If you're running Internet Explorer 10 or later, you may get this error when trying to log on to a computer using RDP through Remote Web Workplace:
You can resolve the issue by adding RWW to the Compatibility View list in Internet Explorer.
You can add RDS servers to the list of computers in Remote Web Workplace, making them available to anyone with access to RWW. The process is simple, requires no reboot and is immediately active.
Note that this will only work if your RDS server is inside the SBSServers OU or a sub-OU (i.e. you're allowed to create other OU's inside the SBSServers OU).
When performing RDS shadowing, by default, the user whose session is being shadowed has to consent to viewing and/or controlling his/her session. This behaviour can be changed with a group policy.
In your group policy (local or through domain), navigate to:
Computer Configuration\Policies\Administrative Templates\Windows Components\Remote Desktop Services\Remote Desktop Session Host\Connections
Find the policy called Set rules for remote control of Remote Desktop Services user sessions and configure it:
By default, only users with local admin rights on an RDS server can do session shadowing on that server.
To allow a particular user or group to allow shadowing, run this from a command prompt on the RDS server:
wmic /namespace:\\root\CIMV2\TerminalServices PATH Win32_TSPermissionsSetting WHERE (TerminalName="RDP-Tcp") CALL AddAccount "domain\group",2
In the command, replace domain\group with settings of your own. It's recommended to create a group specific for the job (e.g. RDS Shadowing) so you can run this command only once, and then add users to the group to allow them to shadow.
An Asterisk TAPI driver, which is actually usable on Terminal Server:
It's not freeware, but is absolutely affordable, and is usable on Terminal Server (multi-user profiles).
When running a Windows 2008 (R1) Terminal Services, and you connect with a RDP 7.1 client and try to shadow another session, it may happen that both clients get disconnected.
KB2523307 tells us that this is caused by RemoteFX being active when a new client is used.
A hotfix is available to address the issue, and can be requested via the KB.
EDIT: for your convenience, I've attached the hotfix (English only!), at least until Microsoft requests its removal...