If you do need a license, it will be much lighter on the wallet.ĪnyDesk works flawlessly without any installation required. Teamviewer became a lot more restrictive on what is considered to be "non commercial use", but Anydesk is secure, much smaller footprint, and if you can have a direct connection doesn't seem to care too much about usage. Not sure why microsoft rdp cannot have some simple, quick file manager like what ammyy admin AnyDesk has oh well.Īdd: Can also use AnyDesk or Teamviewer. This strategy is a bit more complex, but it should do the job. net, c#/c++, AutoIT, etc) to launch AnyDesk locally and automate the connecting and downloading specific files. You'd have to write your own scripts (java. But, if you only "browse files" (use only the file manager without streaming the desktop), CPU usage >0.3% idle and >1 avg% when transferring files (burst up to 5-6% when the file is finished uploading and the pieces are being finalized). This might decrease if there is more video ram or graphics processor on the target server. I am using 1280 x 2048 window with 4 cores and the CPU usage is 22-25% idle or moving things around. Also, the CPU usage might increase to stream the desktop screen, somewhat related to the size of the RDP window.
Note: Use portable mode only on the remote user's desktop Do NOT fully install AnyDesk.
The AnyDesk file manager is a bit crude, but it works.
Good idea to password protect your AnyDesk login and which IDs have access to unattended remote connections. Most vps servers have dedicated IP addresss or subdomain address so this should not be a problem.
AnyDesk can be free if you connect via direct IP connection. This includes using AnyDesk's file manager's ability to browse any folder you need and copy. Then use AmmyyAdmin AnyDesk on user1's desktop to connect and manipulate the desktop. Note that this does 'permanently' use 1 rdp session until you decide to close it.
This video should show you how to implement this 2 user setup on your server to hold an rdp session open. This will keep the user1's gui alive in the cloud without having to remain logged in to rdp locally. Remember, you can allow only certain folders to be synced on specific devices (you don't have to sync the entire dropbox, just the folders you need)Ģ) If you are allowed to setup more than one user on the remote server, have a 2nd user and then have user2 session connect rdp session to user1. Īnd yes, the mapping does seem to disallow access to the rest of the drive, although I wouldn't bet my life that it doesn't have chroot-like "vulnerabilities" (assuming it is supposed to be secure in the first place).ġ) Install dropbox or equivalent cloud storage product and sync needed files that way between computers. There are actually also other ways to do the mapping, see. Keep in mind that the subst mappings are not persistent across reboots, of course, so this is mostly convenient for a one-time session of file transfer. Type mstsc (which launches Remote Desktop).So I recommend to run everything from a single command prompt: Note that it's fairly easily to have problems with this method due to subst performing the mapping only for the user under which it is run.
You can very easily share a single folder by using subst to map it to a drive letter, and then selecting that drive in remote desktop. Eug wrote what I thing is an extremely useful comment that seems to have overlooked by everyone: