Home
  •  

Remote Procedure Call Communication

UIGeneratedMonitorec9ed86a3f0d44e6ad569047bb945888 (UnitMonitor)

This object monitors communication of the remote procedure call.

Knowledge Base article:

Configuration

The RemoteApp and Desktop Connection Management service must be able to communicate by using Remote Procedure Call (RPC) to query RD Session Host servers and RD Virtualization Host servers for information about RemoteApp programs, session-based desktops, and virtual desktops on your network.

Resolutions

To resolve this issue, ensure that the credentials are valid on the RD Web Access Web site by doing the following:

To perform these tasks, refer to the following sections.

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

Ensure that you can log on to the RD Web Access server by using domain credentials

The RD Web Access server that is configured to use the RD Connection Broker server must be available to communicate with the RD Connection Broker server.

To log on to the RD Web Access server that is configured to use the RD Connection Broker server:

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

2. In the Domain\user name box, type a valid domain and user account name.

3. In the Password box, type the password for the user account.

4. Verify that you can successfully log on to the RD Web Access server by using Remote Desktop Web Access Configuration.

Ensure that the domain credentials are formatted correctly in a non-Microsoft application

The RemoteApp and Connection Management service queries RemoteApp programs, session-based desktops, and virtual desktops that are available to a specific user. This error can occur in a non-Microsoft application if the domain credentials are not properly formatted. For more information about the RemoteApp and Connection Management service API reference, see http://msdn.microsoft.com/en-us/library/dd401668(VS.85).aspx.

Add the RD Connection Broker computer account to the Windows Authorization Access Group

The Windows Authorization Access Group is a security group included in the Active Directory Domain Services domain.

To add the RD Connection Broker computer account to the Windows Authorization Access Group:

1. On the domain controller, open Active Directory Users and Computers. To open Active Directory Users and Computer, click Start, point to Administrative Tools, and then click Active Directory Users and Computers.

2. Click Builtin, and then double-click Windows Authorization Access Group.

3. Click the Members tab, and then click Add.

4. In the Enter the object names to select box, type the name of the RD Connection Broker computer account, and then click OK.

Click OK to close the Windows Authorization Access Group dialog box.

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.SingleEventLogManualReset2StateMonitorType
RemotableTrue
AccessibilityPublic
Alert Message
Remote Procedure Call Communication Alert
Event ID: {0} -- Description: {1}
RunAsDefault

Source Code:

<UnitMonitor ID="UIGeneratedMonitorec9ed86a3f0d44e6ad569047bb945888" 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.SingleEventLogManualReset2StateMonitorType" ConfirmDelivery="true">

  <Category>Custom</Category>

  <AlertSettings AlertMessage="UIGeneratedMonitorec9ed86a3f0d44e6ad569047bb945888_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="UIGeneratedOpStateId6154b8913bbe461494c9ba99bbe1747a" MonitorTypeStateID="ManualResetEventRaised" HealthState="Success"/>

    <OperationalState ID="UIGeneratedOpStateId39c1b3c25f104a068eefd83eb619dcfc" MonitorTypeStateID="EventRaised" HealthState="Warning"/>

  </OperationalStates>

  <Configuration>

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

    <LogName>Microsoft-Windows-RemoteApp and Desktop Connection Management/Admin</LogName>

    <Expression>

      <And>

        <Expression>

          <SimpleExpression>

            <ValueExpression>

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

            </ValueExpression>

            <Operator>Equal</Operator>

            <ValueExpression>

              <Value Type="String">Microsoft-Windows-RemoteApp and Desktop Connection Management/Admin</Value>

            </ValueExpression>

          </SimpleExpression>

        </Expression>

        <Expression>

          <SimpleExpression>

            <ValueExpression>

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

            </ValueExpression>

            <Operator>Equal</Operator>

            <ValueExpression>

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

            </ValueExpression>

          </SimpleExpression>

        </Expression>

      </And>

    </Expression>

  </Configuration>

</UnitMonitor>