Remote Desktop License Server Discovery

Microsoft.Windows.Server.10.0.RemoteDesktopServices.NewUnitMonitor_23 (UnitMonitor)

This object monitors the discovery of Remote Desktop license servers.

Knowledge Base article:

Summary

An RD Session Host server must be able to contact a Remote Desktop license server to request Remote Desktop Services client access licenses (RDS CALs) for users or computing devices that are connecting to the RD Session Host server.

Resolutions

To resolve this issue, check the event ID, and then view the troubleshooting information for that event in the sections below.

Resolution steps for the following event ID:1128

This error might be caused by one of the following conditions:

There is a network connectivity problem between the RD Session Host server and the license server.
The license server is not correctly configured to be automatically discovered.
The RD Session Host server cannot automatically contact a Remote Desktop license server.
The Remote Desktop Licensing service is not running on the license server.

There is a network connectivity problem between the RD Session Host server and the license server

To determine if there is a network connectivity problem between the RD Session Host server and the license server, use the ping command.

Note: The following procedures include steps for using the ping command to perform troubleshooting. Therefore, before performing these steps, check whether the firewall or Internet Protocol security (IPsec) settings on your network allow Internet Control Message Protocol (ICMP) traffic. ICMP is the TCP/IP protocol that is used by the ping command.

To perform this procedure, you must have membership in the local Administrators group, or you must have been delegated the appropriate authority.

To determine if there is a network connectivity problem between the RD Session Host server and the license server:

1. On the RD Session Host server, click Start, click Run, type cmd, and then click OK.

2. At the command prompt, type ping server_FQDN, where server_FQDN is the fully qualified domain name (FQDN) of the license server (for example, server1.contoso.com), and then press ENTER.

If the ping was successful, you will receive a reply similar to the following:

Reply from IP_address: bytes=32 time=3ms TTL=59

Reply from IP_address: bytes=32 time=20ms TTL=59

Reply from IP_address: bytes=32 time=3ms TTL=59

Reply from IP_address: bytes=32 time=6ms TTL=59

3. At the command prompt, type ping IP_address, where IP_address is the IP address of the license server, and then press ENTER.

If you cannot successfully ping the license server by IP address or by FQDN, see the section titled "Identify and fix network connectivity issues".

The license server is not correctly configured to be automatically discovered

To perform this procedure, you must have membership in the local Administrators group, or you must have been delegated the appropriate authority.

To determine if the license server is correctly configured:

1. Open RD Licensing Manager on the license server. To open RD Licensing Manager, click Start, point to Administrative Tools, point to Remote Desktop Services, and then click Remote Desktop Licensing Manager.

2. If the User Account Control dialog box appears, confirm that the action it displays is what you want, and then click Yes.

3. In the left pane, click All Servers, click the name of the license server, and then on the Action menu, click Review Configuration.

4. In the Configuration dialog box, if there is a message indicating that RD Session Host servers will not be able to automatically discover this license server, see the section titled "Configure the discovery scope for the Remote Desktop license server".

The RD Session Host server cannot automatically discover (contact) a Remote Desktop 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 determine if the RD Session Host server can discover a license server:

1. Open Remote Desktop Session Host Configuration on the RD Session Host server. To open Remote Desktop Session Host Configuration, click Start, point to Administrative Tools, point to Remote Desktop Services, and then click Remote Desktop Session Host Configuration.

2. If the User Account Control dialog box appears, confirm that the action it displays is what you want, and then click Yes.

3. In the left pane, click Licensing Diagnosis. Under Remote Desktop Services License Server Information, if at least one license server is not listed as discovered, see the section titled "Specify a Remote Desktop license server for the RD Session Host server to use".

The Remote Desktop Licensing service is not running 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 determine if the Remote Desktop Licensing service is started:

1. Open the Services snap-in on the license server. To open the Services snap-in, click Start, point to Administrative Tools, and then click Services.

2. If the User Account Control dialog box appears, confirm that the action it displays is what you want, and then click Yes.

3. In the Services pane, if the Status column for the Remote Desktop Licensing service does not display Started, see the section titled "Start the Remote Desktop Licensing service on the license server".

Resolution steps for the following event ID: 1129

To resolve this issue, specify a Remote Desktop license server for the RD Session Host server to use.

To perform this procedure, you must have membership in the local Administrators group, or you must have been delegated the appropriate authority.

To specify a license server to use:

1. On the RD Session Host server, open Remote Desktop Session Host Configuration. To open Remote Desktop Session Host Configuration, click Start, point to Administrative Tools, point to Remote Desktop Services, and then click Remote Desktop Session Host Configuration.

2. If the User Account Control dialog box appears, confirm that the action it displays is what you want, and then click Yes.

3. Under Licensing, double-click Remote Desktop licensing mode.

4. Under Specified license servers, click Add.

5. In the License server name or IP address box, type the license server name or IP address, and then click OK.

6. Click OK.

Note: You can also specify a Remote Desktop license server for the RD Session Host server to use by using Group Policy.

To specify a Remote Desktop license server for the RD Session Host server to use, enable the Use the specified Remote Desktop license servers Group Policy setting. This Group Policy setting is located in Computer Configuration\Administrative Templates\Windows Components\Remote Desktop Services\Remote Desktop Session Host\Licensing. Note that the Group Policy setting will take precedence over the setting configured in Remote Desktop Session Host Configuration.

To configure the Group Policy setting in Active Directory Domain Services (AD DS), use the Group Policy Management Console (GPMC). To configure the Group Policy setting locally on an RD Session Host server, use the Local Group Policy Editor. For more information about configuring Group Policy settings, see either the Local Group Policy Editor Help ( http://go.microsoft.com/fwlink/?LinkId=143317) or the GPMC Help ( http://go.microsoft.com/fwlink/?LinkId=143867) in the Windows Server Technical Library.

Element properties:

Target

Microsoft.Windows.Server.10.0.RemoteDesktopServicesRole.Service.RDSessionHost

Parent Monitor

System.Health.ConfigurationState

Category

Custom

Enabled

True

Alert Generate

True

Alert Severity

MatchMonitorHealth

Alert Priority

Normal

Alert Auto Resolve

True

Monitor Type

Microsoft.Windows.2SingleEventLogManualReset3StateMonitorType

Remotable

True

Accessibility

Public

Alert Message

Remote Desktop License Server Discovery Alert

Event ID: {0} -- Description: {1}

RunAs

Default

Source Code:

<UnitMonitor ID="Microsoft.Windows.Server.10.0.RemoteDesktopServices.NewUnitMonitor_23" Accessibility="Public" Enabled="true" Target="Microsoft.Windows.Server.10.0.RemoteDesktopServicesRole.Service.RDSessionHost" ParentMonitorID="SystemHealth!System.Health.ConfigurationState" Remotable="true" Priority="Normal" TypeID="Windows!Microsoft.Windows.2SingleEventLogManualReset3StateMonitorType" ConfirmDelivery="true">

  <Category>Custom</Category>

  <AlertSettings AlertMessage="Microsoft.Windows.Server.10.0.RemoteDesktopServices.NewUnitMonitor_23_AlertMessageResourceID">

    <AlertOnState>Warning</AlertOnState>

    <AutoResolve>true</AutoResolve>

    <AlertPriority>Normal</AlertPriority>

    <AlertSeverity>MatchMonitorHealth</AlertSeverity>

    <AlertParameters>

      <AlertParameter1>$Data/Context/EventDisplayNumber$</AlertParameter1>

      <AlertParameter2>$Data/Context/EventDescription$</AlertParameter2>

    </AlertParameters>

  </AlertSettings>

  <OperationalStates>

    <OperationalState ID="UIGeneratedOpStateId8a8e4aa64b5240cfb29aba264c2cec95" MonitorTypeStateID="ManualResetEventRaised" HealthState="Success"/>

    <OperationalState ID="UIGeneratedOpStateId9c200af92fe148f79279efa51f2ad3a2" MonitorTypeStateID="SecondEventRaised" HealthState="Warning"/>

    <OperationalState ID="UIGeneratedOpStateId10a325caa5c64bb9af9dfc5e8bf5f07b" MonitorTypeStateID="FirstEventRaised" HealthState="Error"/>

  </OperationalStates>

  <Configuration>

    <FirstComputerName>$Target/Host/Host/Property[Type="Windows!Microsoft.Windows.Computer"]/NetworkName$</FirstComputerName>

    <FirstLogName>System</FirstLogName>

    <FirstExpression>

      <And>

        <Expression>

          <SimpleExpression>

            <ValueExpression>

              <XPathQuery Type="UnsignedInteger">EventDisplayNumber</XPathQuery>

            </ValueExpression>

            <Operator>Equal</Operator>

            <ValueExpression>

              <Value Type="UnsignedInteger">1128</Value>

            </ValueExpression>

          </SimpleExpression>

        </Expression>

        <Expression>

          <SimpleExpression>

            <ValueExpression>

              <XPathQuery Type="String">PublisherName</XPathQuery>

            </ValueExpression>

            <Operator>Equal</Operator>

            <ValueExpression>

              <Value Type="String">Microsoft-Windows-TerminalServices-RemoteConnectionManager</Value>

            </ValueExpression>

          </SimpleExpression>

        </Expression>

      </And>

    </FirstExpression>

    <SecondComputerName>$Target/Host/Host/Property[Type="Windows!Microsoft.Windows.Computer"]/NetworkName$</SecondComputerName>

    <SecondLogName>System</SecondLogName>

    <SecondExpression>

      <And>

        <Expression>

          <SimpleExpression>

            <ValueExpression>

              <XPathQuery Type="UnsignedInteger">EventDisplayNumber</XPathQuery>

            </ValueExpression>

            <Operator>Equal</Operator>

            <ValueExpression>

              <Value Type="UnsignedInteger">1129</Value>

            </ValueExpression>

          </SimpleExpression>

        </Expression>

        <Expression>

          <SimpleExpression>

            <ValueExpression>

              <XPathQuery Type="String">PublisherName</XPathQuery>

            </ValueExpression>

            <Operator>Equal</Operator>

            <ValueExpression>

              <Value Type="String">Microsoft-Windows-TerminalServices-RemoteConnectionManager</Value>

            </ValueExpression>

          </SimpleExpression>

        </Expression>

      </And>

    </SecondExpression>

  </Configuration>

</UnitMonitor>