Configure Windows 10, 11, Server 2016, 2019 or 2022 to accept Remote Desktop Connections from Windows CE

Applies To

• Windows CE 2.11
• Windows CE 3.0
• Windows CE .net 4.0, 4.1, 4.2
• Windows CE 5.0
• Windows CE 6.0, 6.0 R2, 6.0 R3
• Windows Embedded CE 7.0
• Windows 10 Professional, Windows 11 Profesional
• Windows Server 2016, 2019, 2022

Overview

This article discusses the security changes necessary to allow Remote Desktop Connection requests from the Windows CE Terminal Service / Remote Desktop client to be accepted by Windows 10 / Windows Server 2016 or newer Remote Desktop Session Host servers.

More Info

The secure-by-default model for later Windows releases means that the legacy Terminal Services / Remote Desktop clients of Windows CE are now incompatible with the default security configuration of Remote Desktop Session Hosts (RDP servers).

Before you can connect a Windows CE client to a newer RDP server, you must modify its security configuration to permit the connection.

How To

1. In the Windows start menu / taskbar search, search for:
   gpedit.msc
2. Click on the search result to open the Local Group Policy Editor
   Note: If you are on an Active Directory Domain and wish to make the change using Group Policy, use the Domain Group Policy editor instead of Local Group Policy editor
3. In the left hand navigation pane, navigate to:
4. Computer Configuration > Administrative Templates > Windows Components > Remote Desktop Services > Remote Desktop Session Host > Security
5. Set the following group policies:
   1. 'Set client connection encryption level': [Enabled] Encryption Level: Client Compatible
   2. 'Require use of specific security layer for remote (RDP) connections': [Enabled] Security Layer: Negotiate
   3. 'Require user authentication for remote connections by using Network Level Authentication': [Disabled]
6. Reboot the computer to apply the configuration changes
7. Retry the connection from the Handheld PC
   NB: Without WINS resolution, Windows CE's ability to search for network hosts using NetBIOS is poor. If you do not have the use of a local DNS alias for your host, use the IP address instead of the NetBIOS hostname when connecting to your RDP server.