Event ID 804 — Connection Request Management

Applies To: Windows Server 2008 R2

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

Event Details

Resolve

Identify and fix personal virtual desktop configuration issues

To resolve this issue, do the following:

• Start the RemoteApp and Desktop Connection service.
• Ensure that the personal virtual desktop is assigned by using Active Directory Users and Computers.
• Ensure that the virtual machine name is the same as the fully qualified domain name (FQDN) of the guest operating system.

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

Start the RemoteApp and Desktop Connection service

The RemoteApp and Desktop Connection service must be started on the RD Connection Broker service so that users can connect to their assigned personal virtual desktops.

To start the RemoteApp and Desktop Connection service:

1. On the RD Connection Broker server, start the Services console.  To start the Services console, click Start, point to Administrative Tools, and then click Services.
2. Right-click RemoteApp and Desktop Connection Management, point to All Tasks, and then click Start.
3. If the service was already started, follow the steps in the section named "Ensure that the personal virtual desktop is assigned by using Active Directory Users and Computers."

Ensure that the personal virtual desktop is assigned by using Active Directory Users and Computers

You can assign personal virtual desktops to users by using the user account properties dialog box in Active Directory Users and Computers.

Note: To see the Personal Virtual Desktop tab in the user account properties dialog box, the functional level of your domain must be at Windows Server 2008 R2. If your functional level is at Windows Server 2008, you cannot use Active Directory Users and Computers.

To ensure that the personal virtual desktop is assigned by using Active Directory Users and Computers:

1. On the domain controller, open Active Directory Users and Computers. To open Active Directory Users and Computers, click Start, point to Administrative Tools, and then click Active Directory Users and Computers.
2. Navigate to and then right-click the desired user account object, and then click Properties.
3. Click the Personal Virtual Desktop tab.
4. Ensure that the Assign a personal virtual desktop to this user check box is selected.
5. In the Computer Name box, ensure that the computer name matches the fully qualified domain name of the virtual machine assigned as the personal virtual desktop.
6. If the personal virtual desktop was already assigned, follow the steps in the section named "Ensure that the virtual machine name is the same as the fully qualified domain name of the guest operating system."

Ensure that the virtual machine name is the same as the fully qualified domain name of the guest operating system

The fully qualified domain name of the personal virtual desktop must match the name of the virtual machine. You can change this name by using Hyper-V Manager.

To ensure that the virtual machine name is the same as the fully qualified domain name of the guest operating system:

1. On the RD Virtualization Host server, open Hyper-V Manager. To open Hyper-V Manager, click Start, point to Administrative Tools, and then click Hyper-V Manager.
2. Under Virtual Machines, right-click the virtual machine that is assigned as the personal virtual desktop, and then click Settings.
3. Under the Management heading, click Name.
4. In the You can edit the name of this virtual machine box, ensure that the name of the virtual machine matches the fully qualified domain name of the personal virtual desktop.

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.

Related Management Information

Connection Request Management

Remote Desktop Services