| Event Information | According to Microsoft :
Diagnose :
This error might be caused by one of the following conditions:- The licensing mode for the terminal server does not match the type of TS CALs installed on the license server
To perform this procedure,must have membership in the local Administrators group, or you must have been delegated the appropriate authority.
To determine the licensing mode for the terminal server:- On the terminal server, open Terminal Services Configuration. To open Terminal Services Configuration, click Start, point to Administrative Tools, point to Terminal Services, and then click Terminal Services Configuration.
- If the User Account Control dialog box appears, confirm that the action it displays is what wanted, and then click Continue.
- In the left pane, click Licensing Diagnosis.
- Review the following information in Licensing Diagnosis:
- Under Terminal Server Configuration Details, note the licensing mode for the terminal server.
- Under Terminal Services License Server Information,note the type of TS CALs installed on any license server that is listed as discovered. Information about the type of TS CALs installed on a license server is listed under License Server Configuration Details, which is displayed when click a license server listed as discovered under Terminal Services License Server Information.
- If the licensing mode for the terminal server does not match the type of TS CALs installed on the license server
- The RDP encryption levels on the terminal server and the client are not compatible
To perform this procedure,must have membership in the local Administrators group or must have been delegated the appropriate authority.
To determine the RDP encryption level compatibility:- On the terminal server, open Terminal Services Configuration.To open Terminal Services Configuration, click Start, point to Administrative Tools, point to Terminal Services, and then click Terminal Services Configuration.
- If the User Account Control dialog box appears, confirm that the action it displays is what wanted, and then click Continue.
- Under Connections, right-click the connection, and then click Properties.
- On the General tab, note the value of Encyption level.
- On the client computer, start Remote Desktop Connection.To start Remote Desktop Connection, click Start, click Run, type mstsc.exe, and then press ENTER.
- Click the icon in the upper-left corner of the Remote Desktop Connection dialog box, and then click About. Look for the phrase "Maximum encryption strength" in the About Remote Desktop Connection dialog box. This value is the maximum encryption strength supported by the version of Remote Desktop Connection running on the computer.
- If the maximum encryption strength supported by the version of Remote Desktop Connection running on the client computer is not supported by the encryption level configured on the terminal server
- The certificate on the terminal server is corrupted
If the licensing 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 the client are compatible, the certificate on the terminal server might be corrupted.
To resolve this issue, use the resolution that corresponds to the cause you identified in the Diagnose section. After performing resolution,Verify section to confirm that the feature is operating properly
Cause :
The licensing mode for the terminal server does not match the type of TS CALs installed on the license server
Resolution :
Specify the licensing mode for the terminal server
To resolve issue, specify the Terminal Services licensing mode on the terminal server.
Important : The Terminal Services licensing mode configured on a terminal server must match the type of TS CALs available on the license server.
To perform this procedure, you must have membership in the local Administrators group, or you must have been delegated the appropriate authority.
To specify the Terminal Services licensing mode:- On the terminal server, open Terminal Services Configuration.To open Terminal Services Confiiguration, click Start, point to Administrative Tools, point to Terminal Services, and then click Terminal Services Configuration.
- If the User Account Control dialog box appears, confirm that the action it displays is what wanted, and then click Continue.
- Under Licensing, double-click Terminal Services licensing mode.
- Select either Per Device or Per User, depending on environment.Click OK, and then click OK.
Note : Can also specify the Terminal Services licensing mode for a terminal server by using Group Policy.
Cause :
The RDP encryption levels on the terminal server and the client are not compatible
Resolution :
Change the RDP encryption level on the terminal server
To resolve this issue, change the RDP encryption level on the terminal server to a level that is supported by the version of Remote Desktop Connection that is running on the client computer.
To perform this procedure,must have membership in the local Administrators group, or must have been delegated the appropriate authority.
To change the RDP encryption level:- On the terminal server, open Terminal Services Configuration.To open Terminal Services Configuration, click Start, point to Administrative Tools, point to Terminal Services, and then click Terminal Services Configuration.
- If the User Account Control dialog box appears, confirm that the action it displays is what wanted, and then click Continue.
- Under Connections, right-click the connection, and then click Properties.
- On the General tab, change the value of Encyption level to a level that is appropriate for the version of Remote Desktop Connection that is running on the client computer.
Note : Can also change the RDP encryption level on the terminal server by using Group Policy.
Cause :
The certificate on the terminal server is corrupted
Resolution :
Delete the appropriate registry subkey
To resolve issue, delete the MSLicensing registry subkey on the client computer, restart the client computer and then try again to connect remotely to the terminal server from the client computer. If the issue 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 again to connect to the terminal server from the client computer.- Delete the MSLicensing registry subkey
To perform this procedure on the client computer, must have membership in the local Administrators group, or must have been delegated the appropriate authority.
Caution : Incorrectly editing the registry might severely damage your system. Before making changes to the registry,should back up any valued data.- Delete the appropriate registry entries on the terminal server
If the issue persists, delete the Certificate, X509 Certificate, X509 Certificate2, and X509 Certificate ID registry entries on the terminal server.
To perform this procedure on the terminal server,must have membership in the local Administrators group, or must have been delegated the appropriate authority.
Caution : Incorrectly editing the registry can severely damage system. Before making changes to the registry,should back up any valued data on the computer. |