RD Connection Broker Migration: Post-Migration Tasks
Updated: July 19, 2010
Applies To: Windows Server 2008, Windows Server 2008 R2
This topic describes the steps to be taken after the migration is complete, including running a pilot program, retiring the source server, and rolling back the deployment by restoring the RD Connection Broker server.
Run a pilot program
Retire the RD Connection Broker server after migration
Restore the RD Connection Broker server
For more information, see Run a pilot program in the topic Remote Desktop Services Migration Overview: Post-Migration Tasks.
After you complete and verify the migration, the source server can be shut down or disconnected from the network.
In the event of migration failure, you can restore the original RD Connection Broker server or TS Session Broker server if the source server is still available in the state it was in after the migration was completed.
To roll back the migration of an RD Connection Broker server or a TS Session Broker server, return the source computer to service.
|If there is more than one role service on the server, after removing the source server from the domain, you will not have access to the other role services on the computer.|
Remote Desktop Connection Broker Role Service Migration
RD Connection Broker Migration: Preparing to Migrate
RD Connection Broker Migration: Migrating the RD Connection Broker Role Service
RD Connection Broker Migration: Verifying the Migration
RD Connection Broker Migration: Appendix A: Migration Data Collection Worksheets