If you are a user of any sort of RDP technology, where you are looking to copy/paste, or even save files on the local machine (i.e: \tsclient) , you will immediately notice that this is the pain in the side of most IT admins. And chances are, if you’re on this post, you’re trying to find a solution to speed things up.
There are a lot of thoughts on this on the inter-webs. Unfortunately, what you will find is a unanimous “File transfer over RDP SMB sucks”.
I have recently had clients complain about the slowness of browsing to their C: drive to save a file from their RDP session. So, here’s a solution that I found that is very easy to setup, and works. It won’t speed up access \tsclient, but it will certainly help to prevent the need of drilling down 6 folder before getting to the one you need.
By default, RDP will map every mapped drive to \tsclient. For example: \tsclient\c , and \tsclient\m , etc … so, what if we were to simply create another drive letter on the client that points to the folder where the user would want to save locally? Here’s how:
- On the local workstation, create a .bat file
- This would be the content of the .bat file:
@echo off c:\windows\system32\subst.exe q: "%USERPROFILE%\Desktop"
- Place the file in their startup folder.
Of course, you can make this script a bit more intelligent, by checking for existing mapped drives, so that there is no conflict, but you get the idea.
Now, when you’re logged in to an RDP session, you’re going to get the Q: drive mapped as a \tsclient\q drive. Simply go to it, and you will land directly on the desktop, without having to navigate through all the folders. This same thing can be done with any folder, or you can have multiples as well.