Share via

RD Connection Broker Migration: Verifying the Migration

  • Article

Applies To: Windows Server 2008, Windows Server 2008 R2

Verify the migration of the RD Connection Broker server by using Remote Desktop Connection Manager to verify that the destination RD Connection Broker server contains all the RD Virtualization Host servers and RemoteApp sources that you expected to migrate. To verify the migration of the RD Connection Broker server, see Verifying the migration of the RD Connection Broker server.

Verify the migration of the TS Session Broker server registry key settings by checking to see that the destination RD Connection Broker registry displays the registry key values that you migrated. To verify the migration of the TS Session Broker server registry key settings, see Verifying the migration of the TS Session Broker server registry keys to the RD Connection Broker registry.

Verifying the migration of the RD Connection Broker server

Refer to the following sections to verify that the migration of the RD Connection Broker server was successful:

  • Verify the location of the personal virtual desktops and virtual desktop pools

  • Verify the location of the RD Session Host servers and farms

  • Verify that the RD Session Host servers are communicating with the RD Connection Broker server

Verify the location of the personal virtual desktops and virtual desktop pools

Check that all the personal virtual desktops and virtual desktop pools that you expected to migrate are present in the correct location under the RD Virtualization Host node.

To check that all the personal virtual desktops and virtual desktop pools are present

  1. Log on to the RD Connection Broker server as a member of the local Administrators group.

  2. Click Start, point to Administrative Tools, click Remote Desktop Services, and then click Remote Desktop Connection Manager.

  3. In the left pane, under Remote Desktop Connection Manager: <server_name>, expand the RD Virtualization Host Servers node.

  4. Click the Personal Virtual Desktop node. Compare the list of servers in the Personal Virtual Desktop section of the results pane to the list of servers that you expected to migrate from the data worksheet at RD Connection Broker Migration: Appendix A: Migration Data Collection Worksheets.

  5. For each Pooled Virtual Desktops node, compare the list of servers in the Pooled Virtual Desktops section of the results pane to the list of servers that you expected to migrate from the data worksheet in Appendix A.

Verify the location of the RD Session Host servers and farms

Check that all the RD Session Host servers and farms for RemoteApp sources and additional RD Web Access sources are in the list in the results pane.

To check that all RD Session Host servers and farms are present

  1. Log on to the RD Connection Broker server as a member of the local Administrators group.

  2. Click Start, point to Administrative Tools, click Remote Desktop Services, and then click Remote Desktop Connection Manager.

  3. In the left pane, under Remote Desktop Connection Manager:<server_name>, click RemoteApp sources.

  4. Compare the list of servers in the RemoteApp sources section of the results pane to the list of servers in the data worksheet in Appendix A.

Verify that the RD Session Host servers are communicating with the RD Connection Broker server

Make sure that all the RD Session Host servers are properly communicating with the RD Connection Broker server by attempting to connect to an RD Session Host server through an RD Session Host server running in redirection mode.

To make sure that all the RD Session Host servers are properly communicating with the RD Connection Broker server

  1. Log on to the RD Connection Broker server as a member of the local Administrators group.

  2. Click Start, point to Administrative Tools, click Remote Desktop Services, and then click Remote Desktop Services Manager.

  3. In the left pane, right-click Remote Desktop Services Manager, and then click Import from RD Connection Broker. Specify the name or IP address of the destination RD Connection Broker server, and then click OK.

  4. In the left pane, right-click Remote Desktop Services Manager, and then click Connect to Computer. Specify the name or IP address of an RD Session Host server that is connected through the destination RD Connection Broker server, and then click OK.

  5. Specify credentials for a member of the local Administrators group.

  6. In Select Computer, in the Enter the object name to select box, specify the name or IP address of an RD Session Host server that is connected through the destination RD Connection Broker server, and then click OK.

  7. Check that the server name or IP address that you specified is in the list in the left pane of Remote Desktop Services Manager.

Verifying the migration of the TS Session Broker server registry keys to the RD Connection Broker registry

Verify the migration of the TS Session Broker registry keys by comparing the values for registry key settings migrated from the TS Session Broker server to the values for the same registry keys on the RD Connection Broker server.

Compare the values for the registry keys in the TS Session Broker table in the data worksheet in Appendix A with those in the exported file. The values for the registry keys should be the same.

To compare the registry key values on the RD Connection Broker server with the ones migrated from the TS Session Broker Computer

  1. Click Start, and in the Search programs and files box, type regedit.exe and then press ENTER.

  2. Navigate to HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Tssdis\Parameters.

  3. Double-click the NumberFailedPingsBeforePurge registry entry. Compare the entry in the Value box to the corresponding entry in the data worksheet in Appendix A.

  4. Click Cancel.

  5. Repeat steps 3–4 for each registry setting.

  6. Click File, and then click Exit to close the Registry Editor.

See also