Microsoft KB Archive Search

Notice: This website is an unofficial Microsoft Knowledge Base (hereinafter KB) archive and is intended to provide a reliable access to deleted content from Microsoft KB. All KB articles are owned by Microsoft Corporation. Read full disclaimer for more details.

  1. Home
  2. RemoteFX Licensing Incompatible with standard Remote Desktop Protocol (RDP) Security

RemoteFX Licensing Incompatible with standard Remote Desktop Protocol (RDP) Security

View products that this article applies to.

Symptoms

RDP Connection attempts to a RemoteFX enabled Terminal Server fail, resulting in the following error on the client:

"The remote computer disconnected the session because of an error in the licensing protocol.  Please try connecting to the remote computer again or contact your server administrator."

The Terminal Server logs the following event:

Event ID: 1152

Source: TerminalServices-RemoteConnectionManager

Message: The Remote Desktop Virtualization Host server cannot issue a client license.  It was unable to issue the license due to a changed (mismatched) client license, insufficient memory, or an internal error.

↑ Back to the top

Cause

This problem occurs when standard RDP security is used by the client to connect to the RemoteFX server.

This can occur under the following conditions:

  1. The client is a custom application using the Remote Desktop active control.  This control uses standard RDP security by default.
  2. The client is 3rd party or Windows Remote Desktop client that is configured to use standard RDP security.  Windows XP SP3 and newer Remote Desktop clients use Enhanced RDP security by default and will not exhibit this problem.  Older client operating systems use standard RDP security by default, and will exhibit the symptoms listed in this article.

↑ Back to the top

Resolution

The client must be configured to use Enhanced RDP security.

If the client is a custom application using the Remote Desktop ActiveX control, the client must use minimum control version IMsRdpClientAdvancedSettings4 interface and set the AuthenticationLevel property to either 1 or 2 (default level is 0).

Windows XP SP2 clients running MSTSC.exe can work around this licensing problem by using RDP enhanced security (by selecting the "Attempt authentication" Drop down in the security tab properties of the Remote Desktop Connection client.

↑ Back to the top

Keywords: vkball, kb

↑ Back to the top

Article Info
Article ID : 2590851
Revision : 2
Created on : 8/1/2019
Published on : 8/1/2019
Exists online : False
Views : 132