RD Connection Broker Availability

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

This object monitors availability of the RD Connection Broker server.

Knowledge Base article:

Summary

The RD Connection Broker server must be available to accept connection requests from user sessions, RD Session Host servers in a farm, and RD Session Host servers running in redirection mode.

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: 901

To resolve this issue, you must restart the Remote Desktop Connection Broker service.

To perform this procedure, you must be a member of the Administrators group, or you must have been delegated the appropriate authority.

To restart the Remote Desktop Connection Broker service:

1. On the RD Connection Broker server, open the Services console. To open the Services console, click Start, point to Administrative Tools, and then click Services.

2. Right-click RD Connection Broker, point to All Tasks, and then click Restart.

Resolution steps for the following event ID: 898

To resolve this issue, you should start the Remote Desktop Connection Broker service.

To perform this procedure, you must be a member of the Administrators group, or you must have been delegated the appropriate authority.

To start the Remote Desktop Connection Broker service:

1. On the RD Connection Broker server, open the Services console. To open the Services console, click Start, point to Administrative Tools, and then click Services.

2. Right-click RD Connection Broker, point to All Tasks, and then click Start.

Resolution steps for the following event ID: 833

Resource and filter plug-ins are stored in the Windows registry. Resource plug-ins are stored in HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\Tssdis\Parameters\Resource, and filter plug-ins are stored in HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\Tssdis\Parameters\Filter.

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

To ensure that the plug-in is configured correctly:

1. On the RD Connection Broker server, open Registry Editor. To open Registry Editor, click Start, click Run, type regedit.exe and then press ENTER.

2. Navigate to HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\Tssdis\Parameters\Plugins.

3. For filter plug-ins, click Filter. For resource plug-ins, click Resource.

4. Click the plug-in name.

5. Double-click IsEnabled.

6. In the Value data box, type 1 and then click OK.

7. Ensure that the Name, Provider, and CLSID registry settings exist and have values assigned to them.

8. Close Registry Editor.

Note: If you are unsure which plug-in is not configured correctly, a resource plug-in that is not configured correctly will return an Hresult of 0x88130010, and a filter plug-in that is not configured correctly will return an Hresult of 0x88130011.

Resolution steps for the following event ID: 902

To resolve this issue, add the computer account for the Remote Desktop Session Host (RD Session Host) server or the Remote Desktop Virtualization Host (RD Virtualization Host) computer to the Session Broker Computers local group on the Remote Desktop Connection Broker (RD Connection Broker) server.

Important: If the computer that was denied access is not part of an RD Session Host server farm that is serviced by the RD Connection Broker server where the condition was logged, no further action is required.

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 RD Session Host server or RD Virtualization Host server to the Session Broker Computers local group:

1. On the RD Connection Broker 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.

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 Groups.

4. In the right pane, right-click the Session Brokers Computers group, and then click Properties.

5. Click Add.

6. In the Select Users, Computers, or Groups dialog box, click Object Types.

7. Select the Computers check box, and then click OK.

8. Locate and then add the computer account for the RD Session Host server or RD Virtualization Host server that will use the RD Connection Broker server.

9. Click OK to close the Select Users, Computers, or Groups dialog box, and then click OK to close the Session Brokers Computers Properties dialog box.

Resolution steps for the following event ID: 834

The filter plug-in priority must be a positive integer and is set by using Registry Editor. The registry path is as follows: HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\Tssdis\Parameters\Filter\<priority>, where <priority> is replaced with a positive integer.

Element properties:

TargetMicrosoft.Windows.Server.10.0.RemoteDesktopServicesRole.Service.RDConnectionBroker
Parent MonitorSystem.Health.AvailabilityState
CategoryCustom
EnabledTrue
Alert GenerateTrue
Alert SeverityMatchMonitorHealth
Alert PriorityHigh
Alert Auto ResolveTrue
Monitor TypeMicrosoft.Windows.2SingleEventLogManualReset3StateMonitorType
RemotableTrue
AccessibilityPublic
Alert Message
RD Connection Broker Availability Alert
Event ID: {0} -- Description: {1}
RunAsDefault

Source Code:

<UnitMonitor ID="Microsoft.Windows.Server.10.0.RemoteDesktopServices.NewUnitMonitor_2" Accessibility="Public" Enabled="true" Target="Microsoft.Windows.Server.10.0.RemoteDesktopServicesRole.Service.RDConnectionBroker" ParentMonitorID="SystemHealth!System.Health.AvailabilityState" Remotable="true" Priority="Normal" TypeID="Windows!Microsoft.Windows.2SingleEventLogManualReset3StateMonitorType" ConfirmDelivery="true">
<Category>Custom</Category>
<AlertSettings AlertMessage="Microsoft.Windows.Server.10.0.RemoteDesktopServices.NewUnitMonitor_2_AlertMessageResourceID">
<AlertOnState>Warning</AlertOnState>
<AutoResolve>true</AutoResolve>
<AlertPriority>High</AlertPriority>
<AlertSeverity>MatchMonitorHealth</AlertSeverity>
<AlertParameters>
<AlertParameter1>$Data/Context/EventDisplayNumber$</AlertParameter1>
<AlertParameter2>$Data/Context/EventDescription$</AlertParameter2>
</AlertParameters>
</AlertSettings>
<OperationalStates>
<OperationalState ID="UIGeneratedOpStateId49c63be8d969421d895a4218f14ed1df" MonitorTypeStateID="ManualResetEventRaised" HealthState="Success"/>
<OperationalState ID="UIGeneratedOpStateIdf93cd6c512474dae9cf7f917bb8e5a1c" MonitorTypeStateID="SecondEventRaised" HealthState="Warning"/>
<OperationalState ID="UIGeneratedOpStateIda1dd81d385c84ec1ac783bc8dd21f0c9" MonitorTypeStateID="FirstEventRaised" HealthState="Error"/>
</OperationalStates>
<Configuration>
<FirstComputerName>$Target/Host/Host/Property[Type="Windows!Microsoft.Windows.Computer"]/NetworkName$</FirstComputerName>
<FirstLogName>Microsoft-Windows-TerminalServices-SessionBroker/Admin</FirstLogName>
<FirstExpression>
<And>
<Expression>
<SimpleExpression>
<ValueExpression>
<XPathQuery Type="String">Channel</XPathQuery>
</ValueExpression>
<Operator>Equal</Operator>
<ValueExpression>
<Value Type="String">Microsoft-Windows-TerminalServices-SessionBroker/Admin</Value>
</ValueExpression>
</SimpleExpression>
</Expression>
<Expression>
<Or>
<Expression>
<SimpleExpression>
<ValueExpression>
<XPathQuery Type="UnsignedInteger">EventDisplayNumber</XPathQuery>
</ValueExpression>
<Operator>Equal</Operator>
<ValueExpression>
<Value Type="UnsignedInteger">898</Value>
</ValueExpression>
</SimpleExpression>
</Expression>
<Expression>
<SimpleExpression>
<ValueExpression>
<XPathQuery Type="UnsignedInteger">EventDisplayNumber</XPathQuery>
</ValueExpression>
<Operator>Equal</Operator>
<ValueExpression>
<Value Type="UnsignedInteger">901</Value>
</ValueExpression>
</SimpleExpression>
</Expression>
</Or>
</Expression>
</And>
</FirstExpression>
<SecondComputerName>$Target/Host/Host/Property[Type="Windows!Microsoft.Windows.Computer"]/NetworkName$</SecondComputerName>
<SecondLogName>Microsoft-Windows-TerminalServices-SessionBroker/Admin</SecondLogName>
<SecondExpression>
<And>
<Expression>
<SimpleExpression>
<ValueExpression>
<XPathQuery Type="String">Channel</XPathQuery>
</ValueExpression>
<Operator>Equal</Operator>
<ValueExpression>
<Value Type="String">Microsoft-Windows-TerminalServices-SessionBroker/Admin</Value>
</ValueExpression>
</SimpleExpression>
</Expression>
<Expression>
<Or>
<Expression>
<SimpleExpression>
<ValueExpression>
<XPathQuery Type="UnsignedInteger">EventDisplayNumber</XPathQuery>
</ValueExpression>
<Operator>Equal</Operator>
<ValueExpression>
<Value Type="UnsignedInteger">834</Value>
</ValueExpression>
</SimpleExpression>
</Expression>
<Expression>
<SimpleExpression>
<ValueExpression>
<XPathQuery Type="UnsignedInteger">EventDisplayNumber</XPathQuery>
</ValueExpression>
<Operator>Equal</Operator>
<ValueExpression>
<Value Type="UnsignedInteger">833</Value>
</ValueExpression>
</SimpleExpression>
</Expression>
<Expression>
<SimpleExpression>
<ValueExpression>
<XPathQuery Type="UnsignedInteger">EventDisplayNumber</XPathQuery>
</ValueExpression>
<Operator>Equal</Operator>
<ValueExpression>
<Value Type="UnsignedInteger">902</Value>
</ValueExpression>
</SimpleExpression>
</Expression>
</Or>
</Expression>
</And>
</SecondExpression>
</Configuration>
</UnitMonitor>