Home News
36
0

 

This error can be caused by one of the following conditions: The terminal server licensing mode does not match the type of TS CALs installed on the license server. RDP encryption levels are incompatible on the terminal server and on the client. The certificate on the terminal server is corrupted.

 

 

Event Information According to Microsoft:

Diagnostics: This error can be caused by one of the following conditions:

  • The terminal server licensing mode does not match the type of TS CALs installed on the license server.

To complete this procedure, you must be a member of the Local Administrators group, or be assigned the appropriate permissions.
How to determine the license mode for a terminal server:

  1. Open Terminal Services Configuration on the Terminal Server. To open Terminal Services Configuration, click Start, select Administrative Tools, Terminal Services and click Terminal Services Configuration.
  2. If the User Account Control dialog box appears, make sure the displayed action matches your requirements and click Next.
  3. In the left pane, click License Diagnostics.
  4. Check the following information in the license diagnostics:
    • Pay attention to the license mode for the terminal server in the terminal session configuration details Faith.
    • In the “About Terminal Services License Server” section, note the type of TS CALs installed on the license server that is listed as recognized. For more information about the type of TS CALs installed on the license server, see License Server Configuration Information. They appear when you click the license server listed in the “Terminal Services License Server Information” section.
  5. If the terminal server licensing mode does not match the type of TS CALs installed on the license server.
  • The RDP encryption levels on the terminal server and on the client are incompatible.

You must be a member of the local Administrators group, or have the appropriate permissions to complete this procedure.
How to determine the compatibility of the RDP encryption level:

  1. Open Terminal Services Configuration on the Terminal Server. To open Terminal Services Configuration, click Start, select Administrative Tools, Terminal Services, and click ToTerminal Services Configuration “.
  2. If the User Account Control dialog box appears, make sure the displayed action matches your requirements and click Next.
  3. In the Connections section, right-click the connection and select Properties.
  4. On the General tab, note the encryption level value.
  5. Start a Remote Desktop Connection on the client computer. To start Remote Desktop Connection, click Start, click Run, type mstsc.exe, and then press ENTER.
  6. Click the icon in the upper left corner of the Remote Desktop Connection dialog box, then click About. In the Remote Desktop Connection Information dialog box, look for the phrase “Maximum encryption strength.” This value represents the maximum encryption strength supported by the version of Remote Desktop Connection running on the computer.
  7. When the maximum encryption strength supported by the connection versionI am accessing Remote Desktop running on a client computer is not supported by the encryption level configured on the terminal server.
  • The certificate on the terminal server is corrupted.

If the license mode for the terminal server matches the type of TS CALs installed on the license server and the RDP settings on the terminal server, and if the client is compatible, the certificate for the terminal server might be corrupted.
To resolve this issue, use the solution that matches the cause listed in the Diagnostics section. After completing the section, check the Verification section to make sure the feature is working correctly.

Cause: The license mode for the terminal server does not match the type of TS CALs installed on the license server

Solution: Specify the terminal server licensing mode. To resolve this issue, specify the Terminal Services licensing mode on the terminal server.

Film Important. The Terminal Services Licensing Mode configured on the Terminal Server must match the Terminal Services CAL Type.RC terminals available on the license server.
You must be a member of the local Administrators group, or be delegated to complete this procedure.
To set Terminal Services Licensing Mode:

  1. Open Terminal Services Configuration on the Terminal Server. To open Terminal Services Configuration, click Start, select Administrative Tools, Terminal Services and click Terminal Services Configuration.
  2. If the User Account Control dialog box appears, make sure the displayed action matches your requirements and click Next.
  3. Under Licensing, double-click Terminal Services Licensing Mode.
  4. Select by device or user based on your environment. Click OK, then OK.

Note. Group Policy can also be used to set the Terminal Services licensing mode for a Terminal Server.

Reason: RDP encryption levels on the terminal server and on the client are incompatible

Solution. Change the RDP encryption level on the serverterminals. To resolve this issue, change the RDP encryption level on the terminal server to a level supported by the Remote Desktop Connection version. runs on a client computer.

You must be a member of the local Administrators group, or have the appropriate permissions to complete this procedure.
To change the RDP encryption level:

  1. Open Terminal Services Configuration on the Terminal Server. To open Terminal Services Configuration, click Start, select Administrative Tools, Terminal Services and click Terminal Services Configuration.
  2. If the User Account Control dialog box appears, make sure the displayed action matches your requirements and click Next.
  3. In the Connections section, right-click the connection and select Properties.
  4. On the General tab, change the encryption level to match the version of Remote Desktop Connection running on the client computer.

Note. You can also use grUPP policy to change the RDP encryption level on the terminal server.
error 1004 the terminal server cannot issue a client license

Cause: The certificate on the terminal server is corrupted

Solution: Delete the appropriate registry subkey. To resolve this issue, delete the MSLicensing registry subkey on the client computer, restart the client computer, and then try to connect to the terminal server remotely from the client computer. If the problem persists, delete the Certificate, X509 Certificate, X509 Certificate2, and X509 Certificate ID registry entries on the terminal server, restart the terminal server, and then try connecting to the terminal server from the computer again. customer.

  • Delete the MSLicensing registry subkey.

To perform this procedure on a client computer, you must be a member of the local Administrators group, or have appropriate rights.
Warning: Incorrectly editing the registry can seriously damage your system. Before making any changes to the registry, you must back up any important data.

  • Delete the corresponding registry entries on the term serverfishing.

If the problem persists, remove the certificate, X509 certificate, X509 registry entries for certificate2, and X509 certificate ID from the terminal server.
To perform this procedure on a terminal server, it must be a member of the local Administrators group, or have the appropriate permissions.
Warning: Improper Processing The registry can seriously damage the system. Before changing the registry, back up any important data on your computer.

Reason-1

The event log does not indicate the client device that provided an invalid license. Insufficient permissions have been applied to the Microsoft license key in the registry for a group of authenticated users. When testing, try to establish an RDP connection after deleting the MSLicense key from the registry as a user (not a domain administrator or power user group). The RDP connection also doesn’t work.

Resolution

To resolve this issue, back up and delete the registry keys for the X509 certificate. Restart your computer and reactivateSet the Terminal Services License Server. To do this, follow these steps.

  1. Make sure the Terminal Server registration is saved correctly.

  2. Start Registry Editor.

  3. Find and click the following registry subkey:
    HKEY_LOCAL_MACHINE SYSTEM CurrentControlSet Services TermService Parameters

  4. From the Registry menu, select Export Registry File.

  5. Enter the exported parameters in the fieldIn the File name box, click Save.

    Note

    If you need to restore this registry subkey later, double-click the Exported-parameters.reg file that you saved in this step.

  6. Below parameter entry