Windows CE Programming Blog Archive Windows Server 2. RDS and Windows Mobile connection error. For whatever reason MS decided to make Windows 2. RDS former Terminal Services, now Remote Desktop Services not compatible with Windows Mobile 6. Windows CE 5. 0 based handheld devices. Fortunately, if you activated Remote Desktop License Server using Web Browser method, you simply have to change the Collections Security settings and disable Allow only Network Level Authentication NLA. The following can also apply for Windows 2. R2 Terminal Server. Check if you activate the Licensing server via Web Browser connection or directly. My 2. 00. 8 R2 server is running OK for Windows Mobile, as a stand alone server, with 1. Web Browser. But let start at the beginning. Basic RDS setup. When you installed Windows 2. Server within an existing or new Active Directory and then add the Remote Desktop Server role, you have different choices You may go on with Remote Desktop Services scenario based installation and then just follow the wizard after selecting Quick Start. The wizard will install everything onto one server. Virtual Desktop Infrastructure makes no sense for Windows Mobile clients. They do not need a full virtual windows machine based on a virtual machine. So we select Session Virtualization. The wizard will then deploy all the services and roles and create one default Session Collection and Remote Apps. At the end you should get following screen Now check the setup and look at the RDS Overview You see we have RD Web Access unused by Windows Mobile but cannot be removed, no RD Gateway not needed here, no RD Licensing we will install that later, the RD Connection Broker, no RD Virtualization Host as we do not provide virtual machines here and a RD Session Host with a Quick. Get help, support, and tutorials for Windows productsWindows 10, Windows 8. Windows 7, and Windows 10 Mobile. Tell me about the issue and Ill help you find the solution you need. Session Collection. At this stage we can not connect using Windows Mobile client. The NLA setting dis allows that and we get an error in Remote Desktop Mobile. Just change the NLA setting of the Collection and your Windows Mobile clients can connect. NOTE that there is no License server and we are in the 1. RDS You can access the above Properties using the TASKS menu of Remote Desktop Services Collections Collection. Name and selecting Edit Properties. Android-RealVNC_Screenshot.png' alt='Windows Ce 6 0 Rdp Client Windows' title='Windows Ce 6 0 Rdp Client Windows' />If there is no Collection, we can not change the setting Windows Desktop PCs can connect to that RDS without a Collection installed. We Windows Mobile client need a collection to disable NLA. Setup Remote Desktop License Server. Now setup a Remote Desktop License server, activate it or better read my later note about the activation method see RD License Server Activation Connection Method and install some CALs or DALs licenses per User or Device. Ensure the License Manager shows your License Server without any error. And also check with RD License DiagnoserTelecommuting is pretty easy now. Skype, Slack, and good ol Gchatexcuse me, Google Hangoutsmake communicating with your colleagues down the hall or around. The licensing mode must match the general Collections properties setting If everything is in place and activated and licensed Windows Mobile Clients can no longer connect The certificates generated by the License Server are not compatible with Remote Desktop Mobile. They use 4. 09. 6 bit key length and SHA2. The certificates are stored in the registry at HKEYLOCALMACHINESYSTEMCurrent. Control. SetControlTerminal ServerRCM. Extracted and converted these certs look like this Certificate. Version 3 0x. 2. Serial Number. Signature Algorithm sha. Windows Update 7. For whatever reason MS decided to make Windows 2012 RDS former Terminal Services, now Remote Desktop Services not compatible with Windows Mobile 6. Historique. Bas sur le protocole ITU T. T. 128, la premire version de RDP version 4. With. RSAEncryption. Issuer CUS, STWashington, LRedmond, OMicrosoft Corporation, CNMicrosoft Assurance Designation Root 2. Validity. Not Before Mar 2. GMT. Not After Mar 2. GMT. Subject CUS, STWashington, LRedmond, OMicrosoft Corporation, CNMicrosoft Assurance Designation Root 2. Subject Public Key Info. Consequences Of Not Activating Software Developer'>Consequences Of Not Activating Software Developer. Public Key Algorithm rsa. Encryption. Public Key 4. Modulus. 0. 0 a. Exponent 6. X5. 09v. 3 extensions. X5. 09v. 3 Key Usage. Digital Signature, Certificate Sign, CRL Sign. X5. 09v. 3 Basic Constraints critical. CA TRUE. X5. 09v. Subject Key Identifier. A A9 5. 3 4. 5 3. E D0 6. E 2. 2 5. E FF 7. 9 1. 4 4. Signature Algorithm sha. With. RSAEncryption. RD License Server Activation Connection Method. To fix that and get compatible certificates re activate the RD Licensing Server using the Web method. In RD Licensing Manager right click the server name and select Properties. Change the Connection Method to Web Browser. Close Properties with OK and again right click the server and then Advanced Reactivate. Follow the process to reactivate the server using the web browser. After reactivation delete the following registry keys and reboot the server HKEYLOCALMACHINESYSTEMCurrent. Control. SetControlTerminal ServerRCM. X5. 09 Certificate. X5. 09 Certificate ID. X5. 09 Certificate. These registry keys will rebuild with lower security after reboot see also. And, surprise, after reboot Remote Desktop Mobile Windows CE5, Windows Mobile 6. Windows Embedded Handheld 6. If you extract and convert the new web based certificates you see the difference Certificate. Version 3 0x. 2. Serial Number. Signature Algorithm sha. With. RSA. Issuer Lx. Wx. 00. 2x. 00. Kx. CNx. 00. Wx. 00. Kx. Hx. 00. Gx. 00. O. Not Before Mar 1. GMT. Not After Mar 1. GMT. Subject Lx. Wx. Kx. 00. 1x. 00. CNx. Wx. 00. Kx. 00. 1x. Hx. 00. Gx. 00. O. Subject Public Key Info. Public Key Algorithm rsa. Encryption. Public Key 2. Exponent 6. 55. 37 0x. X5. 09v. 3 extensions. X5. 09v. 3 Basic Constraints. CA TRUE, pathlen 0. Q. G. K. 8. V. 3. W. 2. K. H. P. D. W. 4. V. M. Q. 2. G. 3. T. H. 3. K. C. 8. J. W. K. W. D. M. 4. Y. Signature Algorithm sha. With. RSA. 3a 1d 9. The key length is only 2. SHA1. If you had activated the Web browser Connection method before Activating the server the first time, you do not need to touch the registry and reactivate the serverConclusion. Windows Mobiles Remote Desktop Mobile RDM application connects fine if the right certificates are generated when Activating the RD License Server. RDM will not connect, if SHA2. RDM does not support NLA nor SSLTLS What MS says. RDS 2. R2, and 2. RDP 5. To get around this add the following registry key to the RDS Session Host. Subkey HKEYLOCALMACHINESYSTEMCurrent. Control. SetControlTerminal ServerRCM. Registry entry Use. Len. Prop. Cert. Data type REGDWORD. This is far less secure 5. RDP protocol, but older clients will be able to connect. What wonders me about that, is that it says no support of 2. Possibly they mean, does not support 4. Use. 51. 2Len. Prop. Cert. Test your installation. If you like to check the certificates of your installation you may use the attached demo application RDS2. It will just read the registry and show the certificates data. The code included in the attachment just reads the registry and extracts the certification data. The data is stored binary with some extra data at the beginning. There are twelve bytes to remove to get the raw certificate all these certs start with 0x. So the reg might look like this X5. Certificatehex 0. Then the tool has to remove the first 1. Here is the simple code that does this in csharp and then initializes a new X5. Certificate. 2 object const string rdmain. Reg. Key SYSTEMCurrent. Control. SetControlTerminal ServerRCM. Value. Names new string X5. Certificate, X5. Certificate. X5. 09. Certstring s. Value. Name. byte buf null. Registry. Key rk Registry. Download Update. Star Update. Star. Download the. Double click the downloaded file. Update. Star is compatible with Windows platforms. Update. Star has been tested to meet all of the technical requirements to be compatible with. Windows 1. 0, 8. 1, Windows 8, Windows 7, Windows Vista, Windows Server 2. Windows. XP, 3. 2 bit and 6. Simply double click the downloaded file to install it. Update. Star Free and Update. Star Premium come with the same installer. Update. Star includes support for many languages such as English, German, French, Italian, Hungarian, Russian and many more. You can choose your language settings from within the program. Bible In Plain Text Or Html.