Partager via

Event ID 1016 — Connection Request Management

  • Article

Applies To: Windows Server 2008 R2

Connection requests in RD Connection Broker include user connection requests and redirection connection requests.

Event Details

Product: Windows Operating System
ID: 1016
Source: Microsoft-Windows-TerminalServices-SessionBroker
Version: 6.1
Symbolic Name: EVENT_FAIL_RPC_DENY_ACCESS
Message: RD Connection Broker service denied the remote procedure call (RPC) from an unauthorized computer %1.

Resolve

Add the computer account for the RD Session Host server or RD Virtualization Host server to the Session Broker Computers local group

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) server 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.

Verify

To verify that the RD Connection Broker server is managing connection requests successfully, examine Event Viewer logs and search for the following event message. This event message indicates that the RD Connection Broker server is managing connection requests successfully.

To perform this procedure, you do not need to have membership in the local Administrators group. Therefore, as a security best practice, consider performing this task as a user without administrative credentials.

To verify that the RD Connection Broker server is successfully managing connection requests:

  1. On the RD Connection Broker server, click Start, point to Administrative Tools, and then click Event Viewer.
  2. In the Event Viewer console tree, navigate to Application and Services Logs\Microsoft\Windows\TerminalServices-SessionBroker, and then search for the following events:
    • Event ID 801, Source TerminalServices-SessionBroker: This event indicates that the RD Connection Broker successfully managed a connection request.

Connection Request Management

Remote Desktop Services