I have installed Windows server 2012 RDS license on a new Windows server 2012 R2 machine. We need the ability to RDP in from mobile handhelds (Motorola mc 9090 and mc 9100) running CE 5.0 and 6.0. I need to connect my newly purchased Motorola/Zebra MC2180 Handheld Data Collector with Windows CE 6.0. I could not find the Remote Client or Remote Desktop RDP in the system. Where can I find the the RDP Client in my device.
A reddit dedicated to the profession of Computer System Administration. Community members shall conduct themselves with professionalism.
Do not expressly advertise your product. More details on the may be found. For IT career related questions, please visit Please check out our, which includes lists of subreddits, webpages, books, and other articles of interest that every sysadmin should read!
Checkout the Users are encouraged to contribute to and grow our Wiki. So you want to be a sysadmin? Official IRC Channel - #reddit-sysadmin on Official Discord -. I work for a nonprofit organization that has been given 20 thin clients which are the old HP T5000 model thin clients. I am thinking whoo hooo, I can use these. Well not so fast. The RDP client on these thin clients appears to not play along well with a Win Srv 2012R2 with RDS deployed.
I am thinking this pretty well stinks, but was thinking maybe there is a way around this limitation? I know at some point equipment is just completely outdated and it's time to run it over, but perhaps there is still an idea on how to fix it?
I am not too worried about RDP that doesn't negotiate with Network Level Authentication because it's local RDP behind a decent firewall, simple SSL/TLS would do but I have already tried to downscale it from the RDS side and it hasn't worked. My first thought was a Live Linux USB that has a higher version of RDP on it, but was curious if anyone has tried that. If not, at least it was worth a try.
This may not be the case. I went back and found my old email about this issue and here it is (all of this is text copied out of someone else's forum post) Ok, here's what I had to do and this fixed the issue on all 3 of our servers. Go to RD Licensing Manager. Right click on your Licensing Server name and select properties. Change Connection Method to 'Web Browser'. Go back to the Licensing Server and right click on your server. Select Advanced - 'Reactivate Server'.
Reactive server via the given Wizard + web browser. Delete the following registry keys (they will be reset when you reboot) HKEYLOCALMACHINE SYSTEM CurrentControlSet Control Terminal Server RCM. Certificate.
X509 Certificate. X509 Certificate ID. X509 Certificate2. Reboot After doing the above steps, I was able to log in using RD Mobile. We have several Windows Server 2008 R2 Remote Desktop Servers, and a Windows Server 2008 R2 License server. We did have the problem that Windows XP clients, without Service Pack 3 & Remote Desktop Protocol 7 could not log in.
![Windows ce 6.0 rdp client error Windows ce 6.0 rdp client error](/uploads/1/2/5/4/125451486/859834840.jpg)
Also a lot of HP Thin Clients which did not support Windows Server 2008 R2 could not connect to our Remote Desktop Servers. We first did your 7 steps on our License server, then we did step 6 on each Remote Desktop Server, and we also removed the License Server entry on each Remote Desktop Server in the RD Session Host Configuration.
Then added the License Server entry again, then restarted the Remote Desktop Servers. Now we can connect with the older clients again. Thanks for the tips. Then I read this: We had the same problem with older terminals after cloning a 2008R2 rds server and sysprep it. The original rds server worked fine but when the old terminals connect to the new 1 they come up with the error: Because of a security error, the client could not connect to the remote computer. Verify that you are logged onto the network and then try connecting again' After reading all of the postings about this issue and tried the reactivate solution of the license server, I was sure that it had something to do with the x509 certificates that are generated the first time you connect to a valid license server. What I did, I installed a new license server activate it but did not install licenses on it.
I pointed the defective rds server to the newly installed license server and deleted the following registry keys: HKEYLOCALMACHINE SYSTEM CurrentControlSet Control Terminal Server RCM. Certificate. X509 Certificate. X509 Certificate ID. X509 Certificate2 Then reboot. After the reboot all old terminals can connect fine again.
As final step I pointed the rds server to the same license server as the other ones, reboot and all worked fine. So conclusion is that when you pont a rds server to a license server that has the new type of licenses on it it will generate the wrong x509 certificates that are not supported by the older clients, by pointing it first to 1 without any rds calls on it, it generates the older x509 certificates which are compatible with the older rdp clients then the switch to new license server will then not regenerate the x509 certs so it keeps working. I hope this helps someone This issue was driving me crazy so very happy that it is resolved now Cheers Frits.