Event ID 13057 — Virtual Desktop Management

Published: January 8, 2010

Applies To: Windows Server 2008 R2

red

Virtual desktops assigned as personal virtual desktops or assigned to virtual desktop pools are managed by using Hyper-V Manager.

Event Details

Product: Windows Operating System
ID: 13057
Source: Microsoft-Windows-TerminalServices-TSV-VmHostAgent
Version: 6.1
Symbolic Name: EVENT_ERR_FAIL_REPORT_VM_CHANGE
Message: Failed to report VM info change to RD Connection Broker. VM=%1, Hr=%2

Resolve

Start the Remote Desktop Connection Broker service

To resolve this issue, do the following things:

  • Start the Remote Desktop Connection Broker service.
  • Identify and fix network connectivity issues between the RD Virtualization Host server and the RD Connection Broker server.

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

Start the Remote Desktop Connection Broker service

You can start the Remote Desktop Connection Broker service by using the Services console.

To start the Remote Desktop Connection Broker service:

  1. On the RD Connection Broker server, click Start, point to Administrative Tools, and then click Services.
  2. Right-click Remote Desktop Connection Broker, point to All Tasks, and then click Start.
  3. If the issue is not resolved, use the procedures in the section named "Identify and fix network connectivity issues between the RD Virtualization Host server and the RD Connection Broker server."

Identify and fix network connectivity issues between the RD Virtualization Host server and the RD Connection Broker server

The following are some 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 domain controller 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 domain controller 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 virtual desktops are configured correctly, you can connect to them by using RD Web Access.

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

To connect to a virtual desktop:

  1. On a client computer, open Internet Explorer. To open Internet Explorer, click Start, point to All Programs, and then click Internet Explorer.
  2. In the Address bar, type https://servername/RDWeb where servername is the fully qualified domain name of the RD Web Access server, and then press ENTER.
  3. In the Domain\user name box, type the name of a user account that has access to a virtual desktop.
  4. In the Password box, type the specified password, and then click Sign in.
  5. Click the appropriate virtual desktop, and then click Connect.
  6. Verify that the virtual desktop opens without error.

Related Management Information

Virtual Desktop Management

Remote Desktop Services

Community Additions

ADD
Show: