Remote Desktop use of local Space Navigator
Moderator: Moderators
-
- Posts: 4
- Joined: Thu Apr 02, 2020 6:48 am
Re: Remote Desktop use of local Space Navigator
I have been going back and forth with 3D on this subject.
Was told no drivers are to be loaded on the home computer.
Still haven't gotten anything to work.
I'm not a computer tech.
With all the people at home now, thousands.
That 3D wouldn't create a patch to allow remote access,
as easy as the keyboard or mouse which would prompt hundreds to buy their product for home use.
I know of CAD operators where I work who purchased 3D devices only to
find they won't work at home.
What an enormous loss of revenue.
Was told no drivers are to be loaded on the home computer.
Still haven't gotten anything to work.
I'm not a computer tech.
With all the people at home now, thousands.
That 3D wouldn't create a patch to allow remote access,
as easy as the keyboard or mouse which would prompt hundreds to buy their product for home use.
I know of CAD operators where I work who purchased 3D devices only to
find they won't work at home.
What an enormous loss of revenue.
-
- Posts: 1
- Joined: Mon Dec 21, 2020 9:47 am
Re: Remote Desktop use of local Space Navigator
Here's what finally worked for me when I was in the same boat of it wouldn't show up in the RDP Local resources section no matter what I did.
It looks like a new windows update may have added a new item under RemoteFX USB Device Redirection. See below for modified instructions. Original instructions are not mine.
(Install the same version driver on the host and client PC. I used 64-bit fine.)
These settings need to be changed on both (host and client) systems.
RemoteFX does not work with the universal receiver. You need to connect your wireless device via cable.
Run gpedit.msc
In the group policy editor open
Computer Configuration ->
Administrative Templates ->
Windows Components ->
Remote Desktop Services ->
Remote Desktop Connection Client ->
RemoteFX USB Device Redirection.
Enable: "Allow RDP redirection of other supported RemoteFX USB devices "
THIS IS THE KICKER ====> And set USB redirection rights to "Administrators and Users"
Remote Desktop Services ->
Remote Desktop Session Host ->
Connections
Enable: "Allow user to connect remotely by using Remote Desktop Services ".
Remote Desktop Services ->
Remote Desktop Session Host ->
Device and Resource Redirection
Disable: "Do not allow supported Plug and Play device redirection".
Remote Desktop Services ->
Remote Desktop Session Host ->
Remote Session Environment ->
RemoteFX for Windows Server 2008
Enable: "Configure RemoteFX".
Now open the command prompt with administrative rights.
run "gpupdate /force"
Next restart the machine.
After the restart right click the RDP connection and press edit.
Go to the “Local Resources” tab
Click on “More” on the bottom of the window (section "Local devices and resources").
You should see "Other supported RemoteFX USB devices".
Open it - it shows the connected SpaceMouse device.
Activate the checkbox for the SpaceMouse device.
The device will be forwarded to your target system next time when you connect via RDP.
It looks like a new windows update may have added a new item under RemoteFX USB Device Redirection. See below for modified instructions. Original instructions are not mine.
(Install the same version driver on the host and client PC. I used 64-bit fine.)
These settings need to be changed on both (host and client) systems.
RemoteFX does not work with the universal receiver. You need to connect your wireless device via cable.
Run gpedit.msc
In the group policy editor open
Computer Configuration ->
Administrative Templates ->
Windows Components ->
Remote Desktop Services ->
Remote Desktop Connection Client ->
RemoteFX USB Device Redirection.
Enable: "Allow RDP redirection of other supported RemoteFX USB devices "
THIS IS THE KICKER ====> And set USB redirection rights to "Administrators and Users"
Remote Desktop Services ->
Remote Desktop Session Host ->
Connections
Enable: "Allow user to connect remotely by using Remote Desktop Services ".
Remote Desktop Services ->
Remote Desktop Session Host ->
Device and Resource Redirection
Disable: "Do not allow supported Plug and Play device redirection".
Remote Desktop Services ->
Remote Desktop Session Host ->
Remote Session Environment ->
RemoteFX for Windows Server 2008
Enable: "Configure RemoteFX".
Now open the command prompt with administrative rights.
run "gpupdate /force"
Next restart the machine.
After the restart right click the RDP connection and press edit.
Go to the “Local Resources” tab
Click on “More” on the bottom of the window (section "Local devices and resources").
You should see "Other supported RemoteFX USB devices".
Open it - it shows the connected SpaceMouse device.
Activate the checkbox for the SpaceMouse device.
The device will be forwarded to your target system next time when you connect via RDP.
-
- Posts: 1
- Joined: Sun Jan 03, 2021 12:03 pm
Re: Remote Desktop use of local Space Navigator
In addition to pockybum522 :
After the restart right click the RDP connection and press edit.
Go to the “Local Resources” tab
Click on “More” on the bottom of the window (section "Local devices and resources").
I experienced the following complication:
I already had several Remote desktop files name-1.rpd , name-2.rpd, name-3.rpd etc saved om my desktop.
It didn't work starting a session with clicking this saved configuration (s).
The supported RemoteFX USB devices didn't appear.
Instead, I had to make a new connection from scrap.
Type under left next to START "remote" The app appears. Right click the app and choose "start as a administrator' Now, fill in the address or host name and go to the “Local Resources” tab
Click on “More” on the bottom of the window (section "Local devices and resources"
Now the supported RemoteFX USB devices did appear.
Saving this as new connection. RDP om my desktop. didn’t work.
Ending and restarting the session gave me the same problem again.
So this is what i did:
Type next to START "remote". The app appears. Right click the app and choose "open file Location"
A link in C:\ProgramData\Microsoft\Windows\Start Menu\Programs\Accessories appears.
Right click the link and choose again "open file Location"
C:\Windows\system32\mstsc.exe
Right click mstsc.exe and choose : copy to ... Desktop ( make link)
Now you can right click this newly made link on your desktop and run it as an administrator.
:
After the restart right click the RDP connection and press edit.
Go to the “Local Resources” tab
Click on “More” on the bottom of the window (section "Local devices and resources").
I experienced the following complication:
I already had several Remote desktop files name-1.rpd , name-2.rpd, name-3.rpd etc saved om my desktop.
It didn't work starting a session with clicking this saved configuration (s).
The supported RemoteFX USB devices didn't appear.
Instead, I had to make a new connection from scrap.
Type under left next to START "remote" The app appears. Right click the app and choose "start as a administrator' Now, fill in the address or host name and go to the “Local Resources” tab
Click on “More” on the bottom of the window (section "Local devices and resources"
Now the supported RemoteFX USB devices did appear.
Saving this as new connection. RDP om my desktop. didn’t work.
Ending and restarting the session gave me the same problem again.
So this is what i did:
Type next to START "remote". The app appears. Right click the app and choose "open file Location"
A link in C:\ProgramData\Microsoft\Windows\Start Menu\Programs\Accessories appears.
Right click the link and choose again "open file Location"
C:\Windows\system32\mstsc.exe
Right click mstsc.exe and choose : copy to ... Desktop ( make link)
Now you can right click this newly made link on your desktop and run it as an administrator.
Re: Remote Desktop use of local Space Navigator
Hi pockybum522 and the 3Dconnexion Community,pockybum522 wrote: ↑Mon Dec 21, 2020 9:49 am Here's what finally worked for me when I was in the same boat of it wouldn't show up in the RDP Local resources section no matter what I did.
It looks like a new windows update may have added a new item under RemoteFX USB Device Redirection. See below for modified instructions. Original instructions are not mine.
(Install the same version driver on the host and client PC. I used 64-bit fine.)
These settings need to be changed on both (host and client) systems.
RemoteFX does not work with the universal receiver. You need to connect your wireless device via cable.
Run gpedit.msc
In the group policy editor open
Computer Configuration ->
Administrative Templates ->
Windows Components ->
Remote Desktop Services ->
Remote Desktop Connection Client ->
RemoteFX USB Device Redirection.
Enable: "Allow RDP redirection of other supported RemoteFX USB devices "
THIS IS THE KICKER ====> And set USB redirection rights to "Administrators and Users"
Remote Desktop Services ->
Remote Desktop Session Host ->
Connections
Enable: "Allow user to connect remotely by using Remote Desktop Services ".
Remote Desktop Services ->
Remote Desktop Session Host ->
Device and Resource Redirection
Disable: "Do not allow supported Plug and Play device redirection".
Remote Desktop Services ->
Remote Desktop Session Host ->
Remote Session Environment ->
RemoteFX for Windows Server 2008
Enable: "Configure RemoteFX".
Now open the command prompt with administrative rights.
run "gpupdate /force"
Next restart the machine.
After the restart right click the RDP connection and press edit.
Go to the “Local Resources” tab
Click on “More” on the bottom of the window (section "Local devices and resources").
You should see "Other supported RemoteFX USB devices".
Open it - it shows the connected SpaceMouse device.
Activate the checkbox for the SpaceMouse device.
The device will be forwarded to your target system next time when you connect via RDP.
I'm new to this forum because I have a problem like everybody here
First things first:
Windows 10
computers connected via VPN
Inv2019
3Dconnexion driver 10.7 (on both machines)
I got the SpacePilot Pro (connected with cable) and it also shows up in the RDP. I checked the box, but it won't forward the signal to the work computer. (only like a zooming in/out).
So I checked every gpedit setting (home- and work-computer) and found one little mistake i made on the work computer. As you mentioned "set USB redirection rights to "Administrators and Users"".
I thought: THIS IS IT and now it has to work, but unfortunately it doesn't.
Am I missing there something? I tried to read every post in this forum, but maybe i oversaw something. If it is so, please point me out in the right direction.
I'm desperate.
Thanks a lot
Regards,
J
-
- Posts: 1
- Joined: Fri Jan 29, 2021 2:23 pm
Re: Remote Desktop use of local Space Navigator
RemoteFX vGPU will be removed from all applicable Windows platforms in the February 2021 Windows security updates (February 9, 2021)
https://support.microsoft.com/en-us/hel ... -component
so on to the next potential Software solution i suppose....
https://support.microsoft.com/en-us/hel ... -component
so on to the next potential Software solution i suppose....
Re: Remote Desktop use of local Space Navigator
Hallo Zusammen,
habe hier eine bebilderte Anleitung geschrieben:
https://sites.google.com/view/remotefx/startseite
Funktioniert ohne Zusatzsoftware etc...
Viel Erfolg
habe hier eine bebilderte Anleitung geschrieben:
https://sites.google.com/view/remotefx/startseite
Funktioniert ohne Zusatzsoftware etc...
Viel Erfolg
Re: Remote Desktop use of local Space Navigator
Hello
i tried multiple suggestions but i'm a little stuck
product i have is : spacemouse enterprise
driver version: 10.7.1
problem: ctrl/alt/enter/etc. not working with remote desktop
the button bar 1 to 12 and turning etc works fine with remote
with adjusting de base.xml i cannot get it to work
what am i missing or did i do wrong ?
ideally i want to use it aat work computer and on remote computer the same
thnx in advance
i tried multiple suggestions but i'm a little stuck
product i have is : spacemouse enterprise
driver version: 10.7.1
problem: ctrl/alt/enter/etc. not working with remote desktop
the button bar 1 to 12 and turning etc works fine with remote
with adjusting de base.xml i cannot get it to work
what am i missing or did i do wrong ?
ideally i want to use it aat work computer and on remote computer the same
thnx in advance
-
- Posts: 36
- Joined: Tue Mar 29, 2011 12:47 am
Re: Remote Desktop use of local Space Navigator
Hello,
I use this global.xml file that I tidied up with notepad++ and allows the other keys to work.
Located in:
C:\Users\username\AppData\Roaming\3Dconnexion\3DxWare\Cfg
First create a fresh global.xml file and then looking at whats differnt between the two.
Also I'm not sure what will happen if you use the same spacemouse at home or in the office as you may need two differnt global.xml files.
Button actions area probably be the same for whichever CAD software is used.
Button bank area will change depending on what the CAd package alls each mode.
Bit cut/copy/paste maye solve the issue.
Good luck.
I use this global.xml file that I tidied up with notepad++ and allows the other keys to work.
Located in:
C:\Users\username\AppData\Roaming\3Dconnexion\3DxWare\Cfg
First create a fresh global.xml file and then looking at whats differnt between the two.
Also I'm not sure what will happen if you use the same spacemouse at home or in the office as you may need two differnt global.xml files.
Button actions area probably be the same for whichever CAD software is used.
Button bank area will change depending on what the CAd package alls each mode.
Bit cut/copy/paste maye solve the issue.
Good luck.
- Attachments
-
- Global.zip
- (793 Bytes) Downloaded 326 times
Re: Remote Desktop use of local Space Navigator
Hi, I'm Liks, French user.
I'm a new user of space mouse enterprise. My drivers are Ok
I work with a remote desktop, and I've a a similar problem. After using this protocol : https://3dconnexion.com/fr/wp-content/u ... moteFX.pdf, my space mouse detect my different software in the remote desktop.
On my desk, all buttons work fine, however, no one work one the remote desktop. Just the main button (don't know the word for the big one ) works correctly.
Some of you has got a solution ?
Thanks for all
I'm a new user of space mouse enterprise. My drivers are Ok
I work with a remote desktop, and I've a a similar problem. After using this protocol : https://3dconnexion.com/fr/wp-content/u ... moteFX.pdf, my space mouse detect my different software in the remote desktop.
On my desk, all buttons work fine, however, no one work one the remote desktop. Just the main button (don't know the word for the big one ) works correctly.
Some of you has got a solution ?
Thanks for all
Re: Remote Desktop use of local Space Navigator
After more research, that was not exactly what I say.
The spacemouse works in rdp.
But some function not.
If i use a macro or a key form keyboard on spacemouse, it doesn't work.
But if I associate a software on a key of the space mouse... it works....
So why this result ?
Thanks in advance for your help
The spacemouse works in rdp.
But some function not.
If i use a macro or a key form keyboard on spacemouse, it doesn't work.
But if I associate a software on a key of the space mouse... it works....
So why this result ?
Thanks in advance for your help
Re: Remote Desktop use of local Space Navigator
This is a known problem with the RDP environment.
We are working with Microsoft to see if they have a solution.
In general macros won't work. But some SpaceMouse Enterprise KB modifier keys (Shift, Control, Alt, Tab, Space, Esc, Enter) can be made to work with some XML editing.
We are working with Microsoft to see if they have a solution.
In general macros won't work. But some SpaceMouse Enterprise KB modifier keys (Shift, Control, Alt, Tab, Space, Esc, Enter) can be made to work with some XML editing.
Re: Remote Desktop use of local Space Navigator
Hello there,
trying to use severel approches of changing the Group Policies and related regestry entries I just figured, even with 3'ird-party software it seems not to be possible using Windows Home on the Client?
The Server has Windows Professional and it works from other Windows Professional machines.
Group pilicy settings i used
https://sites.google.com/view/remotefx/startseite
Regisrty settings I changed:
[HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Windows NT\Terminal Services]
"fDenyTSConnections"=dword:00000000
"fDisablePNPRedir"=dword:00000000
"fEnableVirtualizedGraphics"=dword:00000001
[HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Windows NT\Terminal Services\Client]
"fEnableUsbBlockDeviceBySetupClass"=dword:00000001
"fEnableUsbNoAckIsochWriteToDevice"=dword:00000050
"fEnableUsbSelectDeviceByInterface"=dword:00000001
"fUsbRedirectionEnableMode"=dword:00000002
[HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Windows NT\Terminal Services\Client\UsbBlockDeviceBySetupClasses]
"1000"="{3376f4ce-ff8d-40a2-a80f-bb4359d1415c}"
[HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Windows NT\Terminal Services\Client\UsbSelectDeviceByInterfaces]
"1000"="{6bdd1fc6-810f-11d0-bec7-08002be2092f}"
Has anybody made it work usind Windows Home on the client?
Thanks for Help or Input.
trying to use severel approches of changing the Group Policies and related regestry entries I just figured, even with 3'ird-party software it seems not to be possible using Windows Home on the Client?
The Server has Windows Professional and it works from other Windows Professional machines.
Group pilicy settings i used
https://sites.google.com/view/remotefx/startseite
Regisrty settings I changed:
[HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Windows NT\Terminal Services]
"fDenyTSConnections"=dword:00000000
"fDisablePNPRedir"=dword:00000000
"fEnableVirtualizedGraphics"=dword:00000001
[HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Windows NT\Terminal Services\Client]
"fEnableUsbBlockDeviceBySetupClass"=dword:00000001
"fEnableUsbNoAckIsochWriteToDevice"=dword:00000050
"fEnableUsbSelectDeviceByInterface"=dword:00000001
"fUsbRedirectionEnableMode"=dword:00000002
[HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Windows NT\Terminal Services\Client\UsbBlockDeviceBySetupClasses]
"1000"="{3376f4ce-ff8d-40a2-a80f-bb4359d1415c}"
[HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Windows NT\Terminal Services\Client\UsbSelectDeviceByInterfaces]
"1000"="{6bdd1fc6-810f-11d0-bec7-08002be2092f}"
Has anybody made it work usind Windows Home on the client?
Thanks for Help or Input.
Re: Remote Desktop use of local Space Navigator
Thank you jwick for your answer.jwick wrote: ↑Thu Apr 22, 2021 8:15 am This is a known problem with the RDP environment.
We are working with Microsoft to see if they have a solution.
In general macros won't work. But some SpaceMouse Enterprise KB modifier keys (Shift, Control, Alt, Tab, Space, Esc, Enter) can be made to work with some XML editing.
What means KB ?
So I have no solution today to use my space mouse strongly . If I correctly understand, even if i find someone who can edit my xml file... macros won't work, correct ?
That's frustrating
Re: Remote Desktop use of local Space Navigator
Hi Guido LT,
To me, you have to be on windows pro to modify Group Policies.
Using the protocol https://3dconnexion.com/fr/wp-content/u ... moteFX.pdf with windows pro allow spacemouse in remote environement.
However it's not full use
But if you want absolutely on windows home, i've never seen a solution.
To me, you have to be on windows pro to modify Group Policies.
Using the protocol https://3dconnexion.com/fr/wp-content/u ... moteFX.pdf with windows pro allow spacemouse in remote environement.
However it's not full use
But if you want absolutely on windows home, i've never seen a solution.
Guido LT wrote: ↑Thu Apr 22, 2021 10:27 pm Hello there,
trying to use severel approches of changing the Group Policies and related regestry entries I just figured, even with 3'ird-party software it seems not to be possible using Windows Home on the Client?
The Server has Windows Professional and it works from other Windows Professional machines.
Group pilicy settings i used
https://sites.google.com/view/remotefx/startseite
Regisrty settings I changed:
[HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Windows NT\Terminal Services]
"fDenyTSConnections"=dword:00000000
"fDisablePNPRedir"=dword:00000000
"fEnableVirtualizedGraphics"=dword:00000001
[HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Windows NT\Terminal Services\Client]
"fEnableUsbBlockDeviceBySetupClass"=dword:00000001
"fEnableUsbNoAckIsochWriteToDevice"=dword:00000050
"fEnableUsbSelectDeviceByInterface"=dword:00000001
"fUsbRedirectionEnableMode"=dword:00000002
[HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Windows NT\Terminal Services\Client\UsbBlockDeviceBySetupClasses]
"1000"="{3376f4ce-ff8d-40a2-a80f-bb4359d1415c}"
[HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Windows NT\Terminal Services\Client\UsbSelectDeviceByInterfaces]
"1000"="{6bdd1fc6-810f-11d0-bec7-08002be2092f}"
Has anybody made it work usind Windows Home on the client?
Thanks for Help or Input.
Re: Remote Desktop use of local Space Navigator
General macros that you create will not work.
The only thing that can be made to work are the keyboard (KB) modifiers that have predefined keys (Shift, Control, Esc, Tab, ...).
The only thing that can be made to work are the keyboard (KB) modifiers that have predefined keys (Shift, Control, Esc, Tab, ...).