To resolve this issue, create the Terminal Server Computers local group on the Terminal Services license server or, add the computer account for the terminal server to the Terminal Server Computers local group on the Terminal Services license server.
Create the Terminal Server Computers local group on the Terminal Services 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 create the Terminal Server Computers group:
On the license server, open the Local Users and Groups snap-in. To open Local Users and Groups, click Start, click Run, type lusrmgr.msc, and then click OK.
If the User Account Control dialog box appears, confirm that the action it displays is what you want, and then click Continue.
In the left pane, right-click Groups, and then click New Group.
In Group name, type Terminal Server Computers, click Create, and then click Close.
Note: If the license server is installed on an Active Directory Domain Services (AD DS) domain controller, use the Active Directory Users and Computers snap-in to create the Terminal Server Computers group. To create the Terminal Server Computers group on a domain controller, you must have membership in the Domain Admins group in AD DS, or you must have been delegated the appropriate authority. To open Active Directory Users and Computers, click Start, click Run, type dsa.msc, and then click OK.
Note: When the License server security group Group Policy setting is enabled and applied to a license server, the license server will respond only to license requests from terminal servers whose computer accounts are a member of the Terminal Server Computers local group. This Group Policy setting can be found in Computer Configuration\Administrative Templates\Windows Components\Terminal Services\TS Licensing.
Add the computer account for the terminal server to the Terminal Server Computers local group on the Terminal Services 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 add the computer account for the terminal server to the Terminal Server Computers group:
On the license server, open the Local Users and Groups snap-in. To open Local Users and Groups, click Start, click Run, type lusrmgr.msc, and then click OK.
If the User Account Control dialog box appears, confirm that the action it displays is what you want, and then click Continue.
In the left pane, click Groups.
In the right pane, right-click the Terminal Server Computers group, and then click Properties.
Click Add.
In the Select Users, Computers, or Groups dialog box, click Object Types.
Select the Computers check box, and then click OK.
Locate and then add the computer account for the terminal server that you want to add.
Click OK to close the Select Users, Computers, or Groups dialog box, and then click OK to close the Terminal Server Computers Properties dialog box.
Note: If the license server is installed on an Active Directory Domain Services (AD DS) domain controller, use the Active Directory Users and Computers snap-in to add the computer account for the terminal server to the Terminal Server Computers group. To add the computer account for the terminal server to the Terminal Server Computers group on a domain controller, you must have membership in the Domain Admins group in AD DS, or you must have been delegated the appropriate authority. To open Active Directory Users and Computers, click Start, click Run, type dsa.msc, and then click OK.
| Target | Microsoft.Windows.Server.2008.TerminalServicesRole.Service.TSLicensing | ||
| Category | EventCollection | ||
| Enabled | True | ||
| Event Source | Microsoft-Windows-TerminalServices-Licensing | ||
| Alert Generate | True | ||
| Alert Severity | Error | ||
| Alert Priority | Normal | ||
| Remotable | True | ||
| Alert Message |
| ||
| Event Log | System |
| ID | Module Type | TypeId | RunAs |
|---|---|---|---|
| DS | DataSource | Microsoft.Windows.EventProvider | Default |
| Alert | WriteAction | System.Health.GenerateAlert | Default |
Home
ENU <Rule ID="Microsoft.Windows.Server.2008.TerminalServicesRole.Service.TSLicensing.71.4140.4141" Enabled="onStandardMonitoring" Target="Microsoft.Windows.Server.2008.TerminalServicesRole.Service.TSLicensing" ConfirmDelivery="true" Remotable="true" Priority="Normal" DiscardLevel="100">
<Category>EventCollection</Category>
<DataSources>
<DataSource ID="DS" TypeID="Windows!Microsoft.Windows.EventProvider">
<ComputerName>$Target/Host/Host/Property[Type="Windows!Microsoft.Windows.Computer"]/NetworkName$</ComputerName>
<LogName>System</LogName>
<Expression>
<And>
<Expression>
<RegExExpression>
<ValueExpression>
<XPathQuery Type="UnsignedInteger">EventDisplayNumber</XPathQuery>
</ValueExpression>
<Operator>MatchesRegularExpression</Operator>
<Pattern>^(71|4140|4141)$</Pattern>
</RegExExpression>
</Expression>
<Expression>
<SimpleExpression>
<ValueExpression>
<XPathQuery Type="String">PublisherName</XPathQuery>
</ValueExpression>
<Operator>Equal</Operator>
<ValueExpression>
<Value Type="String">Microsoft-Windows-TerminalServices-Licensing</Value>
</ValueExpression>
</SimpleExpression>
</Expression>
</And>
</Expression>
</DataSource>
</DataSources>
<WriteActions>
<WriteAction ID="Alert" TypeID="SystemHealth!System.Health.GenerateAlert">
<Priority>1</Priority>
<Severity>2</Severity>
<AlertName/>
<AlertDescription/>
<AlertOwner/>
<AlertMessageId>$MPElement[Name="Microsoft.Windows.Server.2008.TerminalServicesRole.Service.TSLicensing.71.4140.4141.AlertMessage"]$</AlertMessageId>
<AlertParameters>
<AlertParameter1>$Data/EventDescription$</AlertParameter1>
</AlertParameters>
<Suppression>
<SuppressionValue>$Data/EventDescription$</SuppressionValue>
</Suppression>
<Custom1/>
<Custom2/>
<Custom3/>
<Custom4/>
<Custom5/>
<Custom6/>
<Custom7/>
<Custom8/>
<Custom9/>
<Custom10/>
</WriteAction>
</WriteActions>
</Rule>