This monitor checks whether the Remote Desktop Connection Broker service is running.
The Remote Desktop Connection Broker server is unavailable because the Remote Desktop Connection Broker service is not running.
An unhealthy state of this monitor indicates that the Remote Desktop Connection Broker service is set to start Automatically, but is not running. A service can stop for many reasons, including:
The service was stopped by an administrator.
The service could not allocate the required memory.
The service was prevented from starting because the user account could not be authenticated.
To resolve this issue, try to start the Remote Desktop Connection Broker service. If the problem persists, restart the RD Connection Broker server. After the server has restarted, confirm that the Remote Desktop Connection Broker service has started.
To perform this procedure, you must have membership in the local 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 snap-in. 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 Continue.
3. In the Services pane, right-click Remote Desktop Connection Broker, and then click Properties.
4. On the General tab, ensure that Startup type is set to Automatic. If it is not, click Automatic, and then click Apply.
5. Under Service status, click Start.
6. Click OK to close the Remote Desktop Connection Broker dialog box.
Confirm that the Status column for the Remote Desktop Connection Broker service displays Started.
| Target | Microsoft.Windows.Server.2012.R2.RemoteDesktopServicesRole.Service.RDConnectionBroker | ||
| Parent Monitor | System.Health.AvailabilityState | ||
| Category | AvailabilityHealth | ||
| Enabled | True | ||
| Alert Generate | True | ||
| Alert Severity | Error | ||
| Alert Priority | High | ||
| Alert Auto Resolve | True | ||
| Monitor Type | Microsoft.Windows.CheckNTServiceStateMonitorType | ||
| Remotable | True | ||
| Accessibility | Public | ||
| Alert Message |
| ||
| RunAs | Default |
Home<UnitMonitor ID="Microsoft.Windows.Server.2012.R2.RDConnectionBroker.ServiceStateMonitor" Accessibility="Public" Enabled="true" Target="Microsoft.Windows.Server.2012.R2.RemoteDesktopServicesRole.Service.RDConnectionBroker" ParentMonitorID="SystemHealth!System.Health.AvailabilityState" Remotable="true" Priority="Normal" TypeID="Windows!Microsoft.Windows.CheckNTServiceStateMonitorType" ConfirmDelivery="false">
<Category>AvailabilityHealth</Category>
<AlertSettings AlertMessage="Microsoft.Windows.Server.2012.R2.RDConnectionBroker.ServiceStateMonitor_AlertMessageResourceID">
<AlertOnState>Error</AlertOnState>
<AutoResolve>true</AutoResolve>
<AlertPriority>High</AlertPriority>
<AlertSeverity>Error</AlertSeverity>
<AlertParameters>
<AlertParameter1>$Target/Host/Host/Property[Type="Windows!Microsoft.Windows.Computer"]/NetbiosComputerName$</AlertParameter1>
</AlertParameters>
</AlertSettings>
<OperationalStates>
<OperationalState ID="Running" MonitorTypeStateID="Running" HealthState="Success"/>
<OperationalState ID="NotRunning" MonitorTypeStateID="NotRunning" HealthState="Error"/>
</OperationalStates>
<Configuration>
<ComputerName>$Target/Host/Host/Property[Type="Windows!Microsoft.Windows.Computer"]/NetworkName$</ComputerName>
<ServiceName>tssdis</ServiceName>
<CheckStartupType>false</CheckStartupType>
</Configuration>
</UnitMonitor>