Event ID 11 — RD Web Access Configuration

Applies To: Windows Server 2008 R2

When the Remote Desktop Web Access (RD Web Access) role service is installed, a default Web site is automatically created. By default, the Web site is located at https://server_name/RDWeb, where server_name is the name of the RD Web Access server.

To populate the Web page with a list of available RemoteApp programs or virtual desktops, you must specify a Remote Desktop Session Host server or Remote Desktop Connection Broker server for RD Web Access to use. Any RemoteApp programs on the specified RD Session Host server or RD Connection Broker server that are configured to show in RD Web Access will appear on the Web page.

Event Details

Resolve

Ensure that the server is configured as an RD Session Host server or RD Connection Broker server, and that the server is available on the network

To resolve this issue, do the following:

• Determine the source that the RD Web Access server is configured to use.
• Ensure that the source specified is configured as either an RD Session Host server or an RD Connection Broker server.
• Identify and fix any network connectivity problems between the RD Web Access server and the source.

To perform these tasks, refer to the following sections.

Determine the source that the RD Web Access server is configured to use

To perform this procedure, you must be logged on with the local Administrator account or have membership in the local TS Web Access Administrators group on the RD Web Access server.

To determine the source that RD Web Access is configured to use:

1. Connect to the RD Web Access Web site. To do this, use either of the following methods:

   • On the RD Web Access server, click Start, point to Administrative Tools, point to Remote Desktop Services, and then click Remote Desktop Web Access Administration.
   • Use Internet Explorer to connect to the RD Web Access Web site. By default, the Web site is located at https://server_name/RDWeb, where server_name is the name of the RD Web Access server.

2. Log on to the site by using either the local Administrator account, or an account that is a member of the local TS Web Access Administrators group. If you are already logged on to the computer as one of these accounts, you are not prompted for credentials.

3. On the title bar, click the Configuration tab.

   Note:  If you access the RD Web Access Web site by using the RD Web Access Administration option, the page automatically opens to the Configuration tab.

4. In the Select source to use area, select the An RD Connection Broker server option if you are using an RD Connection Broker server. If you are using one or more RD Session Host servers, select the One or more RemoteApp sources option.

5. In the Source name box, enter the name of the RD Connection Broker server or RD Session Host server that you want to use as the data source.

   Note: If you are using multiple RD Session Host servers, enter each RD Session Host server in the Source name box separated by a semicolon.

6. Click Apply to apply the changes.

Ensure that the source specified is configured as either an RD Session Host server or an RD Connection Broker server

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

To check that the server is configured as an RD Session Host server:

1. On the server, open Server Manager. To open Server Manager, click Start, point to Administrative Tools, and then click Server Manager.
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 left pane, expand Roles. If listed, click Remote Desktop Services. If Remote Desktop Services is not listed, the server is not configured as an RD Session Host server.
4. Under Role Services, the status of **Remote Desktop Session Host **should be listed as Installed. If the status is listed as Not installed, the server is not configured as an RD Session Host server.
5. If the server is not configured as an RD Session Host server, do either of the following:
   • Add (install) the Remote Desktop Session Host role service onto the server.
   • Configure RD Web Access to use another server that is already configured as an RD Session Host server. To configure RD Web Acesss to use a different RD Session Host server, navigate to the Configuration tab of the RD Web Access Web site. In the Select source to use area, select the One or more RemoteApp sources option. In the Source name box, type the name of the Remote Desktop Session Host server, and then click Apply.

To check that the server is configured as an RD Connection Broker server:

1. On the server, open Server Manager. To open Server Manager, click Start, point to Administrative Tools, and then click Server Manager.
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 left pane, expand Roles. If listed, click Remote Desktop Services. If Remote Desktop Services is not listed, the server is not configured as an RD Connection Broker server.
4. Under Role Services, the status of Remote Desktop Connection Broker should be listed as Installed. If the status is listed as Not installed, the server is not configured as an RD Connection Broker server.
5. If the server is not configured as an RD Connection Broker server, do either of the following:
   • Add (install) the Remote Desktop Connection Broker role service onto the server.
   • Configure RD Web Access to use another server that is already configured as an RD Connection Broker server. To configure RD Web Acesss to use a different RD Connection Broker server, navigate to the Configuration tab of the RD Web Access Web site. In the Select source to use area, select the An RD Connection Broker option. In the Source name box, type the name of the RD Connection Broker server, and then click Apply.

Identify and fix any network connectivity problems between the RD Web Access server and the source

To identify and fix any network connectivity problems between the RD Web Access server and the source, do the following:

• Determine if there is a network connectivity problem by using the ping command.
• Perform additional troubleshooting steps, if necessary, to help identify the cause of the problem.

To perform these tasks, refer to the following sections.

Note:  The following procedures include steps for using the ping command to perform troubleshooting. Therefore, before performing these steps, check whether the firewall or Internet Protocol security (IPsec) settings on your network allow Internet Control Message Protocol (ICMP) traffic. ICMP is the TCP/IP protocol that is used by the ping command.

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

Determine if there is a network connectivity problem

To determine if there is a network connectivity problem between the RD Web Access server and the source:

1. On the RD Web Access server, click Start, click Run, type cmd, and then click OK.

2. At the command prompt, type ping server_FQDN, where server_FQDN is the fully qualified domain name (FQDN) of the source (for example, server1.contoso.com), and then press ENTER.

   If the ping was successful, you will receive a reply similar to the following:

   Reply from IP_address: bytes=32 time=3ms TTL=59

   Reply from IP_address: bytes=32 time=20ms TTL=59

   Reply from IP_address: bytes=32 time=3ms TTL=59

   Reply from IP_address: bytes=32 time=6ms TTL=59

3. At the command prompt, type ping IP_address, where IP_address is the IP address of the source, and then press ENTER.

If you can successfully ping the source by IP address, but not by FQDN, this indicates a possible issue with DNS host name resolution.

If you cannot successfully ping the source by IP address, this indicates a possible issue with network connectivity, firewall configuration, or IPsec configuration.

Perform additional troubleshooting steps

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 source, try to ping the source from another computer. If you cannot ping the source from any computer, first ensure that the source is running. If the source is running, check the network settings on the source.
• 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 source 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 RD Web Access server is correctly configured to make RemoteApp programs or virtual desktops available through RD Web Access, do the following:

1. Use Internet Explorer to connect to the RD Web Access Web site. By default, the Web site is located at https://server_name/RDWeb, where server_name is the name of the RD Web Access server.
2. Under RemoteApp Programs, click a program that is listed.
3. If the RemoteApp program opens, the RD Web Access server and the RD Session Host server are correctly configured to make RemoteApp programs available through RD Web Access.

Related Management Information

RD Web Access Configuration

Remote Desktop Services