Event ID 1009 — RemoteApp and Desktop Connection Management Service Configuration

Applies To: Windows Server 2008 R2

The RemoteApp and Desktop Connection Management service is installed and configured on the RD Connection Broker server.

Event Details

Resolve

Identify and fix configuration issues with the RemoteApp and Desktop Connection Management service

To resolve this issue, do the following:

• Create the TS Web Access Computers group on the RD Connection Broker server.
• Ensure that the RD Connection Broker server is joined to the correct domain.
• Ensure that the RD Connection Broker server is available on the network.

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

Create the TS Web Access Computers group on the RD Connection Broker server

The TS Web Access Computers security group must exist on the RD Connection Broker server.

Note: If you are creating a TS Web Access Computers security group on a domain controller, you should use the procedure named "To create the TS Web Access Computers security group when using a domain controller."

To create the TS Web Access Computers security group on the RD Connection Broker server:

1. On the RD Connection Broker server, open Server Manager. To open Server Manager, click Start, point to Administrative Tools, and then click Server Manager.
2. Expand Configuration, expand Local Users and Groups, and then click Groups.
3. Right-click Groups, and then click New Group.
4. In the Group name box, type TS Web Access Computers.
5. Click Add to add the appropriate members, and then click Create.
6. Click Close.

If you need to create the TS Web Access Computers security group on a domain controller, you must create the group by using Active Directory Users and Computers.

To create the TS Web Access Computers security group when using a domain controller:

1. On the domain controller, click Start, point to Administrative Tools, and then click Active Directory Users and Computers.
2. Right-click Builtin, point to New, and then click Group.
3. In the Group name box, type TS Web Access Computers, and then click OK.
4. Close Active Directory Users and Computers.

Ensure that the RD Connection Broker server is joined to the correct domain

The RD Connection Broker server must be joined to the same domain as the other computers that are hosting Remote Desktop Services role services.

To ensure that the RD Connection Broker server is joined to the correct domain:

1. On the RD Connection Broker server, open the System console. To open the System console, click Start, right-click Computer, and then click Properties.
2. Under the Computer name, domain, and workgroup settings heading, ensure that the Domain value is in the same domain as the other computers that are hosting Remote Desktop Services role services.

Ensure that the RD Connection Broker server is available on the network

The RD Connection Broker must be available on the network to accept connection requests.

The following are some additional troubleshooting steps that you can perform to help identify the root cause of the problem:

• Ping other computers on the network to help determine the extent of the network connectivity issue.
• If you can ping other servers but not the RD Connection Broker server, try to ping the RD Connection Broker server from another computer. If you cannot ping the RD Connection Broker server from any computer, first ensure that the RD Connection Broker server is running. If the RD Connection Broker server is running, check the network settings on the RD Connection Broker server.
• Check the TCP/IP settings on the local computer by doing the following:
  1. Click Start, click Run, type cmd, and then click OK.
  2. At the command prompt, type ipconfig /all, and then press ENTER. Make sure that the information listed is correct.
  3. Type ping localhost to verify that TCP/IP is installed and correctly configured on the local computer. If the ping is unsuccessful, this may indicate a corrupt TCP/IP stack or a problem with your network adapter.
  4. Type ping IP_address, where IP_address is the IP address assigned to the computer. If you can ping the localhost address but not the local address, there may be an issue with the routing table or with the network adapter driver.
  5. Type ping DNS_server, where DNS_server is the IP address assigned to the DNS server. If there is more than one DNS server on your network, you should ping each one. If you cannot ping the DNS servers, this indicates a potential problem with the DNS servers, or with the network between the computer and the DNS servers.
  6. If the RD Connection Broker server is on a different subnet, try to ping the default gateway. If you cannot ping the default gateway, this might indicate a problem with the network adapter, the router or gateway device, cabling, or other connectivity hardware.
• In Device Manager, check the status of the network adapter. To open Device Manager, click Start, click Run, type devmgmt.msc, and then click OK.
• Check network connectivity indicator lights on the computer and at the hub or router. Check network cabling.
• Check firewall settings by using the Windows Firewall with Advanced Security snap-in.
• Check IPsec settings by using the IP Security Policy Management snap-in.

Verify

To verify that the RemoteApp and Desktop Connection Management service is configured correctly, you must start the RemoteApp and Desktop Connection Management service by using the Services console.

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 RemoteApp and Desktop Connection Management service:

1. On the RD Connection Broker server, 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. Verify that the service starts successfully.

Related Management Information

RemoteApp and Desktop Connection Management Service Configuration

Remote Desktop Services