Your terminal services temporary client license will expire in "x" days. why it occurs when login to a windows 2003 server and what will be solution

A quick fix i used was

regedit

Delete the registry folder

HKEY_LOCAL_MACHINE\\SOFTWARE\\Microsoft\\MSLicensing

then relogin as administrator

certificate error... and login issues 

If you are running Terminal Server Licensing in a Windows Server 2003 environment and the licensing mode on the terminal server is set to Per Device but the license server is configured to issue only Per User CALs, then only temporary Per Device licenses are issued from the available pool of licenses. These licenses cannot be upgraded. When the temporary licenses are close to expiration, the following message appears on the terminal server: "Your terminal services temporary client license will expire in N days. Please contact your system administrator to get a permanent license." In this case, Event ID26, Source: Application Pop-up appears in the application event log.

Similarly, Terminal Server clients that run Windows XP or Windows 2000 might receive the following error message, if the client cannot connect to the terminal server for this reason: "The remote session was disconnected because the local computer client access license could not be upgraded or renewed." In this case, Event ID1011, Source:TermService appears in the application event log on the terminal server, with the following message: "The terminal services client has been disconnected because its temporary license has expired."

Do one of the following, based on the requirements of your environment and license agreement:

• Call the Microsoft Clearinghouse and reactivate the license server in the correct mode. For more information, see Locate the Microsoft Clearinghouse telephone number for your country or region(http://go.microsoft.com/fwlink/?LinkId=48885).
• Change the Terminal Server Licensing mode.

The terminal server might not be able to locate the license server.

To resolve this issue, perform the troubleshooting procedures described in The terminal server cannot locate the license server.

1. Review configuration requirements and considerations for implementing Terminal Server Licensing in different environments.
2. Verify that the client, the terminal server, and the license server can communicate.
3. Set a preferred license server.
4. Attempt again to verify whether the terminal server can discover the license server.

If the terminal server still cannot discover the license server, then perform the following steps.

1. Verify RDP-tcp connection settings.
2. Verify the license server role.
3. Verify that the Remote Registry service is started on the license server and that the startup type is set to Automatic.
4. Verify permissions on the Domain Controllers organizational unit.
5. Verify the value of the RestrictAnonymous registry key.
6. Verify that the administrative shares are shared on the license server.
7. Verify that File and Printer Sharing is bound to the network adapter and that the internal network adapter is at the top of the binding order.
8. Verify that the Terminal Server Licensing service is started on the license server and that the startup type is set to Automatic.
9. Verify that Terminal Server Licensing is correctly installed on the license server.
10. Verify that the license server is activated.
11. Remove the MSLicensing registry key on the client and verify permissions on the rebuilt key.

Do one of the following, based on the requirements of your environment and license agreement:

• Call the Microsoft Clearinghouse and reactivate the license server in the correct mode. For more information, see Locate the Microsoft Clearinghouse telephone number for your country or region (http://go.microsoft.com/fwlink/?LinkId=48885).
• Change the Terminal Server Licensing mode