Anyone know of a hardware RDP client that works with Win10?

dbwillis

dbwillis

[H]F Junkie
Joined
Jul 9, 2002
Messages
8,932
I have a customer Im planning to upgrade from Win7 to WIn10 before January.
This is a harsh environment.....auto body shop (dusty) and auto repair (hot, muggy, dirty)
Right now, and for the last 5 yrs, Ive used thin clients from Devon IT, mounted on the wall along with the monitor to connect to a VM (on ESXi) via RDP.

As a test I built a Win10 VM, but the thin clients wont connect due to a 'protocol error' for RDP.
I assume W10 has a newer protocol that doesnt work well with the old clients. (yes, I did turn off NLA on the W10 VM)
Flashing the client to a newer firmware, removes the RDP option

I cant seem to find any RDP clients out there for Win10, anyone?

http://www.devonit.com/support/legacy-products/tc10-thin-client
 
what is the protocol error? Is it that Oracle encyption error or something? If so that's an easy fix through a local group policy change.
 
the thin client gets the error, not much in the way of logs on them, they are old, so I assume dont support the RDP10 protocol
 
Yes, it's the client that gets the error. It doesn't display the error when it fails?

This is the issue I'm talking about, and the fix you can make on the windows 10 box to disable the extra security to see if the thinclient can connect:

  1. On the client has the CredSSP update installed, run gpedit.msc, and then browse to Computer Configuration > Administrative Templates > System > Credentials Delegation in the navigation pane.
  2. Change the Encryption Oracle Remediation policy to Enabled, and then change Protection Level to Vulnerable.
Source: https://support.microsoft.com/en-us...cle-remediation-error-when-to-rdp-to-azure-vm
 
Thanks for the tip Biznatch, no luck though.
Th wording of the error seems to me, to mean the RDP client in the zero client, isnt compatable
It connects for about 3 seconds, then disconnects. I cleared the logs and did a connect try, this was in the log:

2d,14:38:59.170> Connecting with host (******-Bay1VM.******.local, 00-00-00-00-00-00)
2d,14:38:59.190> Using resolution 1280 x 1024 at 60 Hz on DVI port 0
2d,14:38:59.210> CONNECTED (172.16.1.135, 00-00-00-00-00-00)
2d,14:38:59.210> Setting host power state to: S0
2d,14:39:00.150> SESSION ACTIVE
2d,14:39:00.150> (MGMT_RDP): dec_core_block: Unsupported RDP version (0xC)
2d,14:39:00.150> (MGMT_RDP): mgmt_rdp_sec_recv: sec_dec_security_open call failed
2d,14:39:00.150> Connection dropped (detected RDP protocol error)
2d,14:39:00.230> Session lost!
2d,14:39:00.230> Ready to connect with host
2d,14:39:00.230> (MGMT_RDP): INIT: Received unrecognized event 0x20!
 
I had seen that, but thats for the thin client connecting to Win10, I cant change the firmware on these zero clients.
I had checked again, but in the C:\Program Files\Windows Apps, there isnt a folder with 'remote desktop' in the name at all.

Best thing Ive come up with so far is:
A-cheap old Mac Mini, just put an RDP icon in the middle of the screen (requirements are DVI, wired LAN and 2 USB for mouse/kb)
B-some sort of other thin client
 
dbwillis said:
I had seen that, but thats for the thin client connecting to Win10, I cant change the firmware on these zero clients.
I had checked again, but in the C:\Program Files\Windows Apps, there isnt a folder with 'remote desktop' in the name at all.

Best thing Ive come up with so far is:
A-cheap old Mac Mini, just put an RDP icon in the middle of the screen (requirements are DVI, wired LAN and 2 USB for mouse/kb)
B-some sort of other thin client
Click to expand...


Are those instructions not to downgrade the RDP version running on windows 10, so you can connect with your older thin client version? That's what I thought they were for, and what I was looking for. I assumed no changes can be made to the TC itself.
 
yeh, those are to downgrade an RD client, not the host/Windows 10 machine
 
dbwillis said:
I had seen that, but thats for the thin client connecting to Win10, I cant change the firmware on these zero clients.
I had checked again, but in the C:\Program Files\Windows Apps, there isnt a folder with 'remote desktop' in the name at all.

Best thing Ive come up with so far is:
A-cheap old Mac Mini, just put an RDP icon in the middle of the screen (requirements are DVI, wired LAN and 2 USB for mouse/kb)
B-some sort of other thin client
Click to expand...

Or a raspberry Pi running Linux and Remmina.
 
I tried a RPI the other night after the biz closed, it was OK, the screen had lag though when opening apps and browsers.

Wyse 5010 ($60ish) and there are some teeny Win10 PC boxes on Amazon for $100, then there is an NComputing RX-RDP, which looks promising, but its $120
 
dbwillis said:
I tried a RPI the other night after the biz closed, it was OK, the screen had lag though when opening apps and browsers.

Wyse 5010 ($60ish) and there are some teeny Win10 PC boxes on Amazon for $100, then there is an NComputing RX-RDP, which looks promising, but its $120
Click to expand...

Really? What variant was the Pi?

I wouldn't have thought RDP was that demanding..
 
Ethernet based KVM and get a rugged LCD panel. Keyboards and mice are cheap enough to replace every few months if you have to.
 
Mazzspeed said:
Really? What variant was the Pi?

I wouldn't have thought RDP was that demanding..
Click to expand...

This is such an easy solve... I've done RDP to Windows 10 from [name your distro] and from Windows 10 back multiple times in a day, while doing other setup and troubleshooting. I don't even really know what I'm doing.

To the OP: look for fanless x86 miniPCs on Amazon. You don't need much, obviously, but you can get up to desktop-class hardware in a small enclosure that is its own heatsink, and with VESA mounts. Can get with WiFi if needed too.

The new RPI is an example of one of these as well, just running their own version; cheaper, but you can put anything on the above. Including just putting Windows 10 on it.
 
"Ethernet based KVM and get a rugged LCD panel. Keyboards and mice are cheap enough to replace every few months if you have to."

How would you connect the KVM to a Virtual machine?
Yeh, Ive seen some of the fanless units on amazon
 
dbwillis said:
"Ethernet based KVM and get a rugged LCD panel. Keyboards and mice are cheap enough to replace every few months if you have to."

How would you connect the KVM to a Virtual machine?
Yeh, Ive seen some of the fanless units on amazon
Click to expand...
But could it be setup on a bare-metal install? Would be a simpler solution IMO.
 
it could be....
- would need power / circuit ran to server room as there is one circuit there now and 3 of the 4 outlets are used (2 battery backups-1 for each server, then 1 for the monitor)
- would need KVM cables run to server room from monitors/station out in shop
- would need network cables run from server room to data closet in the middle of the shop for the new machines (there are 3 cables run a few yrs back, 2 are used, 1 is a spare)
 
You can even use an Android tablet if you want with the Microsoft remote desktop app.

I use it all the time on my phone.
 
I could, but can I connect a USB keyboard, USB mouse and plug in the network and the DVI or HDMI monitor?
 
I tried an rpi. Although a 3w, but the screen would be slow to refresh.
I just ordered a 10zig thin client (not zero client) from ebay, will try it out Friday at the client since im off that day tip work in the demo derby car.
 
dbwillis said:
And still be able to plug in a keyboard and mouse?
Click to expand...

Wouldn't the keyboard and mouse be Bluetooth? Compute sticks have 2 x USB ports, install Ubuntu and Reminia and you have a cheap RDP client.

You could use Windows 10 if that's what you're comfortable with, but with 2 - 4GB of ram it's going to be a slower experience than Linux.
 
Mazzspeed said:
A Raspberry Pi 4 running Ubuntu Mate and Remmina should handle these duties just fine..?
Click to expand...
Doubtful. That's a lot of overhead from the OS, not to mention the likely lack of hardware acceleration would make for a less than ideal machine to act as a thin client.
 
Lunar said:
Doubtful. That's a lot of overhead from the OS, not to mention the likely lack of hardware acceleration would make for a less than ideal machine to act as a thin client.
Click to expand...

So run a thin client OS such as WTWare.

https://www.makeuseof.com/tag/raspberry-pi-windows-thin-client/

dbwillis said:
Keyboard and mouse are wired usb
Click to expand...

Which should be fine regarding a compute stick as it has two usb ports. Get a keyboard with inbuilt USB like an apple clone keyboard.
 
the 10Zig thin client came in and was able to go from out of box to connected in about 10 minutes.
Its embedded Win7, but I should be able to get the Win10 IOT since I have an account for 10Zig
 
Lunar said:
Doubtful. That's a lot of overhead from the OS, not to mention the likely lack of hardware acceleration would make for a less than ideal machine to act as a thin client.
Click to expand...

Remoting in to my Pi 3b+ using RDP over WiFi- bought on the cheap with the Pi 4 release- and for what it is, it works. Far better than expected. A 4GB Pi 4 should fly.
 
You must log in or register to reply here.
Back
Top