Mouse does not work with Remote Desktop

Thanks for the link to that other question @quack quixote, the first answer lead me to this post - where the answer goes as follows:

...The following command can be run on the remote computer and it will leave the system unlocked with the account that was used during the remote session logged on.

tscon.exe 0 /dest:console

I connect remotely to my XP Pro system using the credentials of the main account on that machine. I created a batch file that runs that command and placed it in the C:\Windows folder of the remote computer. The batch file is named Disconnect.bat. I then put a shortcut to the batch file in the All Users\Desktop folder. I also changed the shortcut's icon to match the one for "Turn Off Computer" on the Start menu.

Instead of closing the remote desktop connection on my local computer, I double click the shortcut on the remote computer to end the session.

Works great!

Edit: As per the question quack linked: If you get the error: "Could not connect sessionID 0 to sessionname console, Error code 5 Error [5]:Access is denied." - Your sessionID may be another number. In the comments @yossis suggests a script as follows to remedy this:

I managed to make it work by trying different session numbers. The session number is different every time I use remote desktop. So I wrote a small script to try out 10 session numbers: for %%i in (0 1 2 3 4 5 6 7 8 9) do ( tscon %%i /dest:console ) It should be executed as administrator.

From here: https://community.wyse.com//forum/showthread.php?2398-Additional-buttons-on-mouse-don-t-work

Those buttons are not HID based. They require a driver. Usually that driver is built into Windows, so you don't see it install. Regular RDP cannot tunnel USB devices that are not HID. HID devices, like mouse and keyboard, are directed into the remote session, but the extra buttons aren't. You will need a USB tunnel for that.

So, a driver will be part of your solution, but a USB tunnel will be necessary as well because the Remote Desktop protocol doesn't even send the necessary information the driver will need.

A quick Google search returned this promising result: http://www.usb-over-network.com/

However, I have not used this solution and so cannot speak to its efficacy.