Export (0) Print
Expand All

RD Connection Broker Migration: Migrating the RD Connection Broker Role Service

Updated: November 15, 2010

Applies To: Windows Server 2008, Windows Server 2008 R2

This topic presents the procedures for the migration of the RD Connection Broker role service and the TS Session Broker role service.

Membership in the local Administrators group, or equivalent, on the RD Connection Broker server that you plan to configure, is the minimum required to complete this procedure. Review details about using the appropriate accounts and group memberships at Local and Domain Default Groups (http://go.microsoft.com/fwlink/?LinkId=83477).

To migrate the RD Connection Broker role service, refer to the data that you added to the RD Connection Broker Migration: Appendix A: Migration Data Collection Worksheets and perform the following steps:

  1. Remove the source server from the domain.

  2. Join the destination server to the domain.

    ImportantImportant
    If there is more than one role service on the server, after removing the server from the domain, you will not have access to the other role services on the computer.

  3. Migrate the security groups for the RD Connection Broker server. For detailed steps, see Migrating the security groups for the RD Connection Broker server.

  4. Migrate the RD Connection Broker role service or the TS Session Broker role service to an RD Connection Broker server.

To migrate the security groups, perform the following procedures:

  • Add members to the Session Broker Computers local group on the RD Connection Broker server.

  • Add the RD Connection Broker server to the TS Web Access Computers security group on the RD Session Host server.

First, add the members from the data worksheet to the Session Broker Computers local group on 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, and then click Computer Management.

  3. Expand Local Users and Groups, and then click Groups.

  4. Double-click Session Broker Computers, and then click Add.

  5. Click Object Types, select Computers, and then click OK.

  6. In the Enter the object name to select box, type the domain and computer name of the first computer, and then click Check Names.

  7. Continue until all the computers from the data worksheet have been added to the list, and then click OK twice to close the Session Broker Computers Properties dialog box.

Finally, add the RD Connection Broker server name to the TS Web Access Computers security group on the RD Session Host server. This is required if you are using RemoteApp sources.

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

  2. Click Start, point to Administrative Tools, and then click Computer Management.

  3. Expand Local Users and Groups, and then click Groups.

  4. Double-click TS Web Access Computers, and then under Members, click Add.

  5. In the Select Users, Computers, or Groups dialog box, click Object Types.

  6. In the Object Types dialog box, select Computers, and then click OK.

  7. In the Select Users, Computers, or Groups dialog box, in the Enter the object names to select box, enter the name of the new RD Connection Broker server, and then click OK.

  8. After the Select Users, Computers, or Groups dialog box closes, verify that your computer appears in the Members list.

To migrate the RD Connection Broker role service, perform the following steps:

  • Import the RemoteApp and Desktop Connection settings.

  • Add the RD Virtualization Host servers to the RD Connection Broker server.

  • Begin importing virtual desktop settings.

  • Continue importing virtual desktop settings.

  • Import the personal virtual desktop settings.

  • Create the virtual desktop pools.

  • Import the settings for the virtual desktop pools.

  • Import the RD Connection Broker farm settings.

  • Connect the RD Session Host server for the RemoteApp source to the RD Connection Broker server.

First, import the RemoteApp and Desktop Connection settings.

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

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

  3. Right-click Remote Desktop Connection Manager, and then click Properties.

  4. In RemoteApp and Desktop Connection Properties, on the Connection Settings tab, enter the values for Display name and Connection ID from the data collection worksheet.

  5. On the RD Web Access tab, in the Server name box, enter the fully qualified domain name (FQDN) of the RD Web Access server from the data collection worksheet, and then click OK.

Next, add the RD Virtualization Host servers to the RD Connection Broker server.

  1. On the RD Connection Broker server, click Start, point to Administrative Tools, point to Remote Desktop Services, and then click Remote Desktop Connection Manager.

  2. Right-click RD Virtualization Host Servers, and then click Add RD Virtualization Host Server.

  3. Enter the name of the RD Virtualization Host server, and then click Add.

Next, begin importing virtual desktop settings.

  1. Log on to the destination server as a member of the local Administrators group.

  2. On the RD Connection Broker server, click Start, point to Administrative Tools, point to Remote Desktop Services, and then click Remote Desktop Connection Manager.

  3. In the console tree, right-click the Remote Desktop Connection Manager node, and then select Configure Virtual Desktops.

  4. In the Configure Virtual Desktops Wizard, on the Specify an RD Virtualization Host Server page, type the NetBIOS name or FQDN of the RD Virtualization Host server, click Add, and then click Next.

  5. On the Configure Redirection Settings page, in the Server name box, type the NetBIOS name or FQDN of the RD Session Host server, and then click Next.

  6. On the Specify an RD Web Access Server page, enter the name of the RD Web Access server, and then click Next.

  7. On the Confirm Changes page, click Apply.

  8. Ensure that the Assign personal virtual desktop check box is cleared, and then click Finish.

Next, continue importing virtual desktop settings.

  1. Log on to the destination server as a member of the local Administrators group.

  2. In the console tree, right-click the RD Virtualization Host Servers node, and then click Properties.

  3. On the Redirection Settings tab, in the Server name box, type the name of the RD Session Host server running in virtual machine redirection mode. If you have an RD Session Host server running in redirection mode for previous versions of Remote Desktop Connection (RDC), select Enable redirection for earlier RDC versions. In the Alternative server name box, enter the server name that you want to use for earlier RDC versions.

  4. On the RD Gateway Settings tab, select the same RD Gateway settings that you noted on the data worksheet. If Use these RD Gateway server settings is selected, enter the Server name and Logon method, and then select Use the same user credentials for RD Gateway and virtual desktops or Bypass RD Gateway server for local addresses to match what was noted on the data worksheet.

    noteNote
    Do not migrate the values from the worksheet to the Digital Signature tab. Digital certificates will be configured at the end of the deployment. For more information about migrating certificates, see Remote Desktop Services Migration Overview: Migrating Certificates.

Next, import the personal virtual desktop settings.

  1. Log on to the destination server as a member of the local Administrators group.

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

  3. Right-click Personal Virtual Desktops, and then click Properties.

  4. On the General tab, if the check box is selected on the Personal Virtual Desktops Properties data worksheet, select the Show in RemoteApp and Desktop Connection check box.

  5. If the Automatically save virtual machines check box was selected on the data worksheet, select it and enter the value from the worksheet in the Wait for box.

  6. On the Common RDP Settings tab, select all the values for the check boxes from the data collection worksheet.

  7. On the Custom RDP Settings tab, if any custom RDP settings exist, transfer them from the data worksheet, and then click OK.

Next, create the virtual desktop pools.

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

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

  3. On the console tree, right-click RD Virtualization Host Servers, and then click Create Virtual Desktop Pool.

  4. In the Create Virtual Desktop Pool Wizard, on the Welcome to the Create Virtual Desktop Pool Wizard page, click Next.

  5. On the Select Virtual Machines page, do not select any virtual machines. Click Next.

  6. In the Remote Desktop Connection Manager alert box, click Yes to continue.

  7. On the Set Pool Properties page, enter the Display name and Pool ID from the <virtual_desktop_pool> Properties data worksheet. Click Next.

  8. Verify the virtual machines displayed in the list, and then click Next.

  9. On the Results page, click Finish.

  10. Repeat steps 3–8 for each virtual desktop pool.

Next, import the settings for the virtual desktop pools.

  1. Log on to the destination server as a member of the local Administrators group.

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

  3. Right-click the first virtual desktop pool, and then click Properties.

  4. On the General tab, enter the values for Display name and Pool ID that you recorded on the data worksheet If the Show in RemoteApp and Desktop Connection check box is selected on the data worksheet, select it on the General tab.

  5. If the Automatically save virtual machines check box was selected on the data worksheet, select it on the General tab, and then enter the value from the worksheet in the Wait for box.

  6. On the Common RDP Settings tab, select all the values for the check boxes from the data collection worksheet.

  7. On the Custom RDP Settings tab, if any custom RDP settings exist, transfer them from the data worksheet, and then click OK.

  8. Repeat steps 3–7 for each virtual desktop pool.

Next, import the RD Connection Broker farm settings.

If RD Session Host servers are deployed in a farm configuration, configure farm settings to point to the new RD Connection Broker server. To configure farm settings, see Add Each RD Session Host Server in the Farm to the Session Broker Computers Local Group (http://go.microsoft.com/fwlink/?LinkId=193001).

Finally, connect the RD Session Host server for the RemoteApp source to the RD Connection Broker server.

  1. Log on to the RD Session Host server as a member of the local Administrators group.

  2. Click Start, point to Administrative Tools, point to Remote Desktop Services, and then click Remote Desktop Session Host Configuration.

  3. In the RD Connection Broker section, double-click Member of farm in RD Connection Broker. On the RD Connection Broker tab, verify the RD Connection Broker and Farm name computer names.

  4. Go to https://<servername>/rdweb where <servername> is the name of the RD Web Access server. Log on as a member of the Administrators security group.

  5. On the Configuration tab, select the An RD Connection Broker option, and then enter the name of the server.

To migrate a TS Session Broker role service, perform the following procedures:

  • Back up the registry on the RD Connection Broker server.

  • Import the registry keys from the TS Session Broker server to the RD Connection Broker server.

  • Connect to the source that RD Web Access uses for RemoteApp and Desktop Connection.

First, back up the registry on the RD Connection Broker server. For detailed information about migrating registry keys, see Registry Editor.

CautionCaution
You should back up the registry on the RD Connection Broker server before making any changes to the registry. You can find more information at Back up your source server.

Next, import the registry keys from the TS Session Broker server to the RD Connection Broker server.

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

    CautionCaution
    Incorrectly editing the registry may severely damage your system. Before making changes to the registry, you should back up any valued data on the computer.

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

  3. Double-click the NumberFailedPingsBeforePurge registry entry.

  4. Enter the new value in the Value data box, and then click OK.

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

  6. On the File menu, click Exit to close the registry editor.

Finally, connect to the source that the RD Web Access role service uses for RemoteApp and Desktop Connection.

  1. Log on with a user account that is a member of the local Administrators security group.

  2. Click Start, point to Administrative Tools, point to Remote Desktop Services, and then click Remote Desktop Web Access Configuration.

    noteNote
    If you see a warning that there is a problem with the certificate for this website, and a link that says Continue to this website (not recommended), it indicates that there is a problem with the SSL certificate. If your client and server are behind a firewall, you might choose to click the link to gather the information; however, you should use a trusted certificate when deploying RD Web Access in a production environment. For more information, see Remote Desktop Services Migration Overview: Migrating Certificates.

  3. In the Domain\user name box, type the name of a valid user account on the domain who is also a member of the local Administrators security group.

  4. In the Password box, type the password, and then click Sign in.

  5. On the Configuration page, click An RD Session Host server.

Was this page helpful?
(1500 characters remaining)
Thank you for your feedback

Community Additions

ADD
Show:
© 2014 Microsoft