Server Fault

Return to Question

added 54 characters in body
Source Link
Jozef
Jozef
  • 79
  • 1
  • 2
  • 7

Windows 7Have Windows7 workstation with a USB COM port device installed.

From this Windows7 workstation I RDP to Windows Server 2012 terminal server and all devices are redirected through RDP correctly.

If I RDP from same workstation Windows7 to Windows Server 2019 terminal server, using the same GPO in domain, I do not get these COM ports redirected.

Both RDP connections have the COM port redirection checked ON, and I see the device on the workstation OK. (MSTSC.msc/Local resources/ Other Supported RemoteFX devices/COM3).

Seems likeDoes Windows Server 2019 has changed somethingneed to allow anytjhing special in acceptingGPO to accept COM port redirectionports redirected. Windows 7 clientWindows7 workstation is using RDP 8.1 RDP version, as on Windows Server 2012 it works OK.

Or it requires something additional in GPO to be allowed. Any ideas?

Windows 7 workstation with a USB COM port.

From this workstation I RDP to Windows Server 2012 terminal server and all devices are redirected through RDP correctly.

If I RDP from same workstation to Windows Server 2019 terminal server, using the same GPO in domain, I do not get these COM ports redirected.

Both RDP connections have the COM port redirection checked ON, and I see the device on the workstation OK. (MSTSC.msc/Local resources/ Other Supported RemoteFX devices/COM3).

Seems like Windows Server 2019 has changed something in accepting COM port redirection. Windows 7 client using RDP 8.1 RDP version, as on Windows Server 2012 it works OK.

Or it requires something additional in GPO to be allowed. Any ideas?

Have Windows7 workstation with a USB COM port device installed.

From this Windows7 workstation I RDP to Windows Server 2012 terminal server and all devices are redirected through RDP correctly.

If I RDP from same workstation Windows7 to Windows Server 2019 terminal server, using the same GPO in domain, I do not get these COM ports redirected.

Both RDP connections have the COM port redirection checked ON, and I see the device on the workstation OK. (MSTSC.msc/Local resources/ Other Supported RemoteFX devices/COM3).

Does Windows Server 2019 need to allow anytjhing special in GPO to accept COM ports redirected. Windows7 workstation is using RDP 8.1 RDP version, as on Windows Server 2012 it works OK.

Or it requires something additional in GPO to be allowed. Any ideas?

Formatting
Source Link
Greg Askew
Greg Askew
  • 36.3k
  • 6
  • 55
  • 82

Windows Server 2019 RemoteFX COM port redirection to WIN2019 doesntdoes not work, toWindows Server 2012 it works

have WorkstationWindows 7 workstation with old WIn7, into which a a USB device is coonected (it creates a COM port).

From this Win7 stationworkstation I RDP to WIN2012 (Terminal)Windows Server 2012 terminal server and all devices are forwardedredirected through RDP correctly. BUT if

If I RDP from same WIN7 stationworkstation to WIN2019 (Terminal tooWindows Server 2019 terminal server, using the same GPO in domain), I do not get these COM ports redirected. Both

Both RDP connections have the COM port redirection checked ON, and I see the device on the workstation OK. (MSTSC.msc/Local resources/ Other Supported RemoteFX devices/COM3) Seems.

Seems like WIN2019Windows Server 2019 has changed something in accepting COM port redirection (Win7. Windows 7 client using RDP 8.1 RDP version), as on win2012 allWindows Server 2012 it works OK.....or

Or it requires something additional in GPO to be allowed. Any ideas?

COM port redirection to WIN2019 doesnt work, to 2012 it works

have Workstation with old WIn7, into which a USB device is coonected (it creates a COM port)

From this Win7 station I RDP to WIN2012 (Terminal) and all devices are forwarded through RDP correctly. BUT if I RDP from same WIN7 station to WIN2019 (Terminal too, using the same GPO in domain) I do not get these COM ports redirected. Both RDP connections have the COM port redirection checked ON, and I see the device on the workstation OK (MSTSC.msc/Local resources/ Other Supported RemoteFX devices/COM3) Seems like WIN2019 has changed something in accepting COM port redirection (Win7 client using RDP 8.1 RDP version) as on win2012 all works OK.....or it requires something additional in GPO to be allowed. Any ideas?

Windows Server 2019 RemoteFX COM port redirection does not work, Windows Server 2012 it works

Windows 7 workstation with a USB COM port.

From this workstation I RDP to Windows Server 2012 terminal server and all devices are redirected through RDP correctly.

If I RDP from same workstation to Windows Server 2019 terminal server, using the same GPO in domain, I do not get these COM ports redirected.

Both RDP connections have the COM port redirection checked ON, and I see the device on the workstation OK. (MSTSC.msc/Local resources/ Other Supported RemoteFX devices/COM3).

Seems like Windows Server 2019 has changed something in accepting COM port redirection. Windows 7 client using RDP 8.1 RDP version, as on Windows Server 2012 it works OK.

Or it requires something additional in GPO to be allowed. Any ideas?

Source Link
Jozef
Jozef
  • 79
  • 1
  • 2
  • 7

COM port redirection to WIN2019 doesnt work, to 2012 it works

have Workstation with old WIn7, into which a USB device is coonected (it creates a COM port)

From this Win7 station I RDP to WIN2012 (Terminal) and all devices are forwarded through RDP correctly. BUT if I RDP from same WIN7 station to WIN2019 (Terminal too, using the same GPO in domain) I do not get these COM ports redirected. Both RDP connections have the COM port redirection checked ON, and I see the device on the workstation OK (MSTSC.msc/Local resources/ Other Supported RemoteFX devices/COM3) Seems like WIN2019 has changed something in accepting COM port redirection (Win7 client using RDP 8.1 RDP version) as on win2012 all works OK.....or it requires something additional in GPO to be allowed. Any ideas?

Your privacy

By clicking “Accept all cookies”, you agree Stack Exchange can store cookies on your device and disclose information in accordance with our Cookie Policy.