Symptoms
Consider the following scenario:
-
You enable the License Server Security Group Group Policy setting on a Terminal Server license server that is running Windows Server 2008. The Terminal Server Computers group is automatically created after the Group Policy setting takes effect.
-
You add a terminal server that is running Windows Server 2008 into the Terminal Server Computers group of the license server.
In this scenario, you encounter one of following issues:
Issue 1
The terminal server is running Windows Server 2008. This terminal server cannot obtain terminal licenses from the license server if the domain of the terminal server is in mixed mode. Therefore, users of this terminal server cannot create terminal sessions.
Issue 2
In the Terminal Services Configuration snap-in window of Microsoft Management Console (MMC) of the terminal server, is the Licensing Diagnosis tool. The Licensing Diagnosis tool cannot locate license servers that are in a disjointed namespace. When this occurs, you receive the following error message:
License Server cannot issue the Terminal Services Client Access Licenses (TS CALs) to the terminal server because the "License Server Security Group" is enabled
Cause
Cause of issue 1
The domain is in mixed mode, and the Network Service account starts the Terminal Services. In this scenario, the terminal server that is running Windows Server 2008 uses an anonymous token to access the license server.
The anonymous token cannot pass the remote procedure call (RPC) validation on the license server. Therefore, the terminal server that is running Windows Server 2008 cannot obtain terminal licenses.
Cause of issue 2
The Licensing Diagnosis tool assumes that the first part of the fully qualified domain names (FQDN) is equal to the NetBIOS domain name. However, this assumption is not true in a disjointed namespace. Therefore, the tool cannot locate license servers that are in a disjointed namespace.
Resolution
Hotfix information
A supported hotfix is available from Microsoft. However, this hotfix is intended to correct only the problem that is described in this article. Apply this hotfix only to systems that are experiencing the problem described in this article. This hotfix might receive additional testing. Therefore, if you are not severely affected by this problem, we recommend that you wait for the next software update that contains this hotfix.
If the hotfix is available for download, there is a "Hotfix download available" section at the top of this Knowledge Base article. If this section does not appear, contact Microsoft Customer Service and Support to obtain the hotfix.
Note If additional issues occur or if any troubleshooting is required, you might have to create a separate service request. The usual support costs will apply to additional support questions and issues that do not qualify for this specific hotfix. For a complete list of Microsoft Customer Service and Support telephone numbers or to create a separate service request, visit the following Microsoft Web site:
http://support.microsoft.com/contactus/?ws=supportNote The "Hotfix download available" form displays the languages for which the hotfix is available. If you do not see your language, it is because a hotfix is not available for that language.
Prerequisites
To apply this hotfix, your computer must be running Windows Server 2008 or Windows Server 2008 Service Pack 2 (SP2).
Restart requirement
You must restart the computer after you apply this hotfix.
Registry information
On a terminal server in a mixed mode domain, you must create the following registry entry, and then you must set its value to 1.Location: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Lsa
Name: UseMachineID
Type: REG_DWORD
Value: 1
File information
The English version of this hotfix has the file attributes (or later file attributes) that are listed in the following table. The dates and times for these files are listed in Coordinated Universal Time (UTC). When you view the file information, it is converted to local time. To find the difference between UTC and local time, use the Time Zone tab in the Date and Time item in Control Panel.
For all supported x86-based versions of Windows Server 2008
|
File name |
File version |
File size |
Date |
Time |
Platform |
SP requirement |
|---|---|---|---|---|---|---|
|
Lsdiag.dll |
6.0.6001.22443 |
262,144 |
04-Jun-2009 |
13:40 |
x86 |
SP1 |
|
Lsdiagres.dll |
6.0.0.0 |
2,048 |
04-Jun-2009 |
10:43 |
x86 |
SP1 |
|
Tsconfig.dll |
6.0.6001.22443 |
724,992 |
04-Jun-2009 |
13:44 |
x86 |
SP1 |
|
Tscfgwmi.dll |
6.0.6001.22443 |
164,352 |
04-Jun-2009 |
12:35 |
x86 |
SP1 |
|
Lsdiag.dll |
6.0.6002.22146 |
262,144 |
04-Jun-2009 |
13:47 |
x86 |
SP2 |
|
Lsdiagres.dll |
6.0.0.0 |
2,048 |
04-Jun-2009 |
10:52 |
x86 |
SP2 |
|
Tsconfig.dll |
6.0.6002.22146 |
724,992 |
04-Jun-2009 |
13:51 |
x86 |
SP2 |
|
Tscfgwmi.dll |
6.0.6002.22146 |
164,352 |
04-Jun-2009 |
10:52 |
x86 |
SP2 |
For all supported x64-based versions of Windows Server 2008
|
File name |
File version |
File size |
Date |
Time |
Platform |
SP requirement |
|---|---|---|---|---|---|---|
|
Tscfgwmi.dll |
6.0.6001.22443 |
204,288 |
04-Jun-2009 |
12:46 |
x64 |
SP1 |
|
Lsdiag.dll |
6.0.6001.22443 |
262,144 |
04-Jun-2009 |
13:49 |
x86 |
SP1 |
|
Lsdiagres.dll |
6.0.0.0 |
2,048 |
04-Jun-2009 |
11:00 |
x64 |
SP1 |
|
Tsconfig.dll |
6.0.6001.22443 |
724,992 |
04-Jun-2009 |
13:53 |
x86 |
SP1 |
|
Tscfgwmi.dll |
6.0.6002.22146 |
204,288 |
04-Jun-2009 |
14:28 |
x64 |
SP2 |
|
Lsdiag.dll |
6.0.6002.22146 |
262,144 |
04-Jun-2009 |
15:17 |
x86 |
SP2 |
|
Lsdiagres.dll |
6.0.0.0 |
2,048 |
04-Jun-2009 |
12:37 |
x64 |
SP2 |
|
Tsconfig.dll |
6.0.6002.22146 |
724,992 |
04-Jun-2009 |
15:21 |
x86 |
SP2 |
For all supported Itanium-based versions of Windows Server 2008
|
File name |
File version |
File size |
Date |
Time |
Platform |
SP requirement |
|---|---|---|---|---|---|---|
|
Tscfgwmi.dll |
6.0.6001.22443 |
411,648 |
04-Jun-2009 |
12:30 |
IA-64 |
SP1 |
|
Lsdiag.dll |
6.0.6001.22443 |
262,144 |
04-Jun-2009 |
13:22 |
x86 |
SP1 |
|
Lsdiagres.dll |
6.0.0.0 |
2,048 |
04-Jun-2009 |
10:53 |
IA-64 |
SP1 |
|
Tsconfig.dll |
6.0.6001.22443 |
724,992 |
04-Jun-2009 |
13:25 |
x86 |
SP1 |
|
Tscfgwmi.dll |
6.0.6002.22146 |
411,648 |
04-Jun-2009 |
14:13 |
IA-64 |
SP2 |
|
Lsdiag.dll |
6.0.6002.22146 |
262,144 |
04-Jun-2009 |
14:53 |
x86 |
SP2 |
|
Lsdiagres.dll |
6.0.0.0 |
2,048 |
04-Jun-2009 |
12:39 |
IA-64 |
SP2 |
|
Tsconfig.dll |
6.0.6002.22146 |
724,992 |
04-Jun-2009 |
14:55 |
x86 |
SP2 |
Status
Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.
More Information
For more information about possible licensing problems on terminal servers, visit the following Microsoft Web site:
http://technet.microsoft.com/en-us/library/cc730675(WS.10).aspxFor more information, click the following article number to view the article in the Microsoft Knowledge Base:
824684 Description of the standard terminology that is used to describe Microsoft software updates
