Share via

Remote Desktop Connection Broker Role Service Migration

  • Article

Applies To: Windows Server 2008, Windows Server 2008 R2

This guide describes how to migrate the Remote Desktop Connection Broker (RD Connection Broker) role service or the Terminal Services Session Broker (TS Session Broker) role service.

The result of the migration of the RD Connection Broker server is different from the migration of the TS Session Broker server.

When you follow the steps to migrate the RD Connection Broker server, the result is a fully functioning RD Connection Broker server that replaces the one you retire from the deployment. You do not need to perform any additional steps to use the RD Connection Broker server.

Important

If you are migrating an RD Connection Broker server that is part of a Windows Server 2008 R2 Failover Cluster, see the Migration Paths for Migrating to a Failover Cluster Running Windows Server 2008 R2 (https://go.microsoft.com/fwlink/?LinkID=182156).

When you follow the steps to migrate the TS Session Broker server, you must finish deploying the server by creating a custom deployment plan. For more information about deploying RD Connection Broker servers, see Remote Desktop Services Deployment Guide (https://go.microsoft.com/fwlink/?LinkId=192601).

Note

In Windows Server 2008 R2, the TS Session Broker role service is now called the RD Connection Broker role service. In this guide, the TS Session Broker role service and the RD Connection Broker role service are discussed separately. References to the RD Connection Broker role service or server do not include the TS Session Broker role service or server. The security group names have not changed in Windows Server 2008 R2.

Overview of the migration process for the RD Connection Broker role service

The RD Connection Broker role service migration process includes the following topics:

What is migrated by using this guide

The Remote Desktop Connection Broker Migration Guide contains steps to migrate RD Connection Broker servers and TS Session Broker servers. Preparation and verification steps are also included in this guide.

Migrating RD Connection Broker includes migrating connection strings and settings for the following features:

  • RD Virtualization Host servers, personal virtual desktops, and virtual desktop pools

  • RemoteApp sources, RD Session Host servers, and terminal servers

  • RD Web Access sources for RemoteApp and Desktop Connection

  • Session Broker Computers security group members

Certificates for RD Connection Broker are also migrated in this guide. For general information about migrating certificates, see RD Connection Broker server certificates in Remote Desktop Services Migration Overview: Migrating Certificates. Steps to migrate certificates in RD Connection Broker are included in RD Connection Broker Migration: Preparing to Migrate.

Migrating TS Session Broker includes migrating the following:

  • Registry settings

  • TS Web Access sources for RemoteApp and Desktop Connection

Important

During the migration process, the name of the source server is given to the destination server. This allows you to migrate a role service without changing the connection strings for any of the other role services in the deployment. After you remove a source server from the domain, you will not have access to any role services on that computer.

What is not migrated

This guide references the Remote Desktop Services Migration Overview topic, which contains information that applies to the migration of all role services such as the order of migration, expected downtime, impact of migration on other role services, and permissions required for migration. In addition, the overview explains how to migrate SSL, code signing, and digitally signed certificates. The steps documented in the overview are not repeated in the guides for the individual role services.

See also