Operates fine under stand alone Winxp, fails to operate durint Terminal server sessions to Win2003 r2 server. Toggles numlock instead. Machine: dell Inspiron 6000 to Dell Poweredge1950 server.
Turns out it in fact was a setting on Terminal Services clients. Seems as if default behavior is to pass windows keys on full screen mode. Leaving windows key combinations on the local device solved the problem (unless one needed to pass windows key combinations, which is unlikely.
I don?t have the equipment to test your setup; however, I suspect your problem is in redirecting the device to the terminal server session. Check the terminal server system event log file to see if you are generating any messages when you connect. When my users have issues, typically with printers, they will be listed in the log as *Errors* and the source will be *TermServDevices*. If you?re using the latest Remote Desktop Client there is a tab in options called Local Resources which is used to deal with configuring your workstation sounds, keyboard, printer, and other local resources to redirect to the terminal server. Click on the More button at the bottom and you will be taken to the more generic section of resource redirection that deals with other items. Your device is probably USB so if it is going to work is would fall under the scope of the section labeled *Supported Plug and Play devices*. You would start by placing a check in that box, reconnect and see if you keypad works now or if anything shows up in the event log. Let us know how this turns out and if you have any other questions. As always please don?t forget to rate this post.
Usually answered in minutes!