Mocha Remote Desktop - Windows 200x Server

Windows 200x Servers are not supported. Only Workstations.

As the Server patent license is very expensive, there are no plans for such an option in a future releases. Microsoft has a patent on the remote protocol (RDP), and to sell clients, a company must purchase a patent license from Microsoft. We have "only" a patent license for workstations.  
 
 

Upgrade to RDP 4.8 and Windows Servers

With version 4.7, mocha rdp uses TLS 1.2 and Cipher AES. Older servers, or a server, which has not been updated may only support TLS 1.0. Notice , because another system on your server uses TLS 1.2, does not indicate TLS 1.2 is build into the RDP server part in your OS.


It is only possible to use rdp 4.7 with protocol version 5 for access to a Windows 200x server admin console, but the server must not be  configured (in roles) as a  terminal (TS) server.

It is possible to use TLS 1.0 Cipher AES in mocha rdp version 4.8, with option menu - configure - use only TLS 1.0. Notice this is not 100% as older mocha rdp versions, as less secure cipher RC4 has been removed, and now AES is used.

It is possible to run an older v 4 protocol (and not TLS 1.2) in mocha rdp:

  - in mocha rdp, menu - configure, select option use old protocol v 4

but:

Windows 200x Servers are not supported. Only Workstations, as we also write in the App Store product description. If you connect to a server type 2000/2003, you will get only the console session. As the Server patent license is very expensive, there is no plans for such an option in a future releases. Microsoft has a patent on the remote protocol (RDP), and to sell clients, a company must purchase a patent license from Microsoft. We have "only" a patent license for workstations.

Upgrade to RDP 3.0 and VMWare/Oracle VirtualBox

These servers cannot handle Unicode keyboard data, select another type in mocha rdp, menu - configure - keyboard

Upgrade to RDP 3.0 and very old Windows OS types

RDP v 3.0 uses as default protocol TSL1. Some older systems does not know this protocol. Select OFF in rdp, menu - configure - check for NLA , and the older rdp protocol (SSL) will be active.