Our company is old 2X ThinClient Server users (from v6.0). Now we use 2XRAS for PXE booting and connecting to Windows Terminal Servers. We have about 150 HDD-less thin clients. And everything was OK until we update OS on our terminals. Just now we use Windows Server 2016 as Terminal Server, and 2XThinClient cannot connect to them because of old RDP Client version in 2XThinClient OS. We have ThinClientOS v7.3.13015 with embedded RDP 5.2 client (Build 3790). But Windows Server 2016 supports only RDP 6.1 and higher. And when 2XOSThinClent tries to connect, he receive error 86. Could you help us to resolve this problem? May be we can download new version of ThinClientOS from anywhere? Thanks.
@EvgenyG1 Unfortunately, the following lifecycle announcements states that 2X OS is not supported anymore and that 7.3 was the last version. http://2x.helpserve.com/Knowledgebase/Article/View/199/1/lifecycle-announcement-for-2x-products http://2x.helpserve.com/Knowledgeba...bove---how-do-i-regain-access-to-this-feature The 2X Client that shipped with 2XOS v7.3.13015 is build 1959 should support NLA which is an RDP 6.0 feature, so not all hope is lost. Ref: https://web.archive.org/web/20140913015909/http://2x.com:80/downloads/os/2XOS-ChangeLog.txt Since you recently upgraded your Windows Server, I would first suggest to check your RDP licensing servers to confirm that everything is in order (maybe test with the latest Linux client on an Ubuntu installation). If that does not help, and your support license is still valid, I would contact Parallels Support to see what options you have available for you. Otherwise, you might want to try your luck with one of the following self-service approaches: Check the RDP server's event logs for any RDP-related errors Attempt upgrading the ISO used for PXE booting with the latest client. Alternatively, you could look for a PXE-bootable Ubuntu and set it up with latest Parallels client installed in kiosk mode Use the HTML5 Gateway functionality in RAS v16 (just needs a browser or a PXE-bootable OS with Firefox or Chromium in kiosk mode) Use RAS managed devices (needs windows OS installation/PXE bootup)
Hello, jpc Thanks for your response! RDP License Server is OK. Because users can connect to Terminal Server using Windows Workstations (Windows 10 or Windows 7) but cannot connect throw 2X ThinClient OS. I tried to find any error messages in Terminal Server Logs... But nothing. May be I tried to find in wrong place... But I looked throw all views in Event Viewer. Using another ISO for PXE-booting is not possible, I think. Because we tried to use alternative ISO and cannot add it to 2XRAS. 2XRAS can use only his own ZIP-files. May be this ZIP-files use some specific format or specific data... Using 2XRAS PXE-booting is very important for us because we have different thinClients and can attach different 2XOS to different Hardware. And Microsoft AD Authorization is very comfortably. After entering "username" and "password" user will be connected to specific terminal server. And we cannot install OS on every thinClients in our organization because they have not HDD Even if they had HDDs, after OS installing, we can use RDP-Client embedded in Windows. And 2XRAS will not be required. I hope Support Team can explain me how we can update RDP-Clinet in ZIP-files or something alse... Thank you!
