Cause: The terminal server might not be able to locate the license server.
Solution: Perform the following steps:
|
1.
|
Verify that the license server is correctly installed.
|
|
2.
|
Verify that the Terminal Server Licensing service is running on the license server.
|
|
3.
|
Verify that the client, the terminal server, and the license server can communicate by ensuring that Domain Name System (DNS) is configured correctly on each computer. To do this, run the ping command from each computer to each computer using the IP address, FQDN, and the NetBIOS name. If any of the ping commands fail, verify the DNS configuration on the network.
|
|
4.
|
On the terminal server, set a preferred licensing server to connect to. You can do this by using the registry, a Windows Management Instrumentation (WMI) script, or, in Windows Server 2003 with Service Pack 1, you can use Group Policy settings or Terminal Server Configuration.
|
Cause: The client might have exceeded its Terminal Server Licensing grace period, and a license server has not yet been installed or activated to issue the client a CAL.
Solution: Install Terminal Server Licensing, activate the license server, and then install and purchase a sufficient number of CALs to support the clients in your organization.
Forums
Contact Us
Business Desktop Deployment (BDD) 2007
Windows 2003
Email
Print
Add Comment