Super User is a question and answer site for computer enthusiasts and power users. Join them; it only takes a minute:

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

I have a logitech MX518 that has nice forward and back buttons built onto the mouse directly. They work great locally. However anytime over remote desktop these buttons do nothing. This happens both with the Windows Remote Desktop and the Windows Store / Windows Metro Remote Desktop.

The computer I'm remoting to at work has the same mouse, which when at my desk physically the forward and back buttons work fine.

Is there any way to get remote desktop to respect these commands properly?

share|improve this question
up vote 2 down vote accepted

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.

share|improve this answer
    
Stupid as this may be, i guess this is reality, as unfortunate as it may be. – Chris Marisic Jan 3 '14 at 16:10
    
Yea, it would be nice if RDP/VNC supported non-HID inputs, even just as an option. But it would probably take more resources and would require additional drivers to be loaded on the host machine. – music2myear Jan 3 '14 at 16:14
    
As mentioned, these drivers already exist on the host. or do you mean additional drivers to translate known action X over transport back to known action X? Wouldn't this be similar to how printers are shared over RDC anyway (which personally i think is wrong for it do so)? – Chris Marisic Jan 3 '14 at 17:22

For what it's worth, I currently use AutoHotKey to do this. Just like with other hotkeys, when the RDP window is active, I cause the XButton2, for example, to Send {XButton2}. Of course, if you're not already using AHK, then it might be too much trouble to get a script together. For whatever reason, it works.

I have a Logitech M510 mouse and luvz it to pieces!

share|improve this answer

You must log in to answer this question.

Not the answer you're looking for? Browse other questions tagged .