Remote Desktop Services Migration Overview: Post-Migration Tasks
Applies To: Windows Server 2008, Windows Server 2008 R2
This topic contains general post-migration steps that can be performed after the migration of the Remote Desktop Services role services. Steps specific to each role service are included in the migration guide for the role service.
Post-migration tasks for Remote Desktop Services role services
See the following sections for post migration procedures:
Run a pilot program
Retire the source servers after migration
Restore the Remote Desktop Services role services
Run a pilot program
Always test migration by using test accounts. Use an Administrator account and an account for a valid user.
We recommend creating a pilot project in the production environment to ensure that the migration of all role services was successful. We suggest running a pilot on the servers before you put the migrated role services into production to verify that your deployment works as you expect. Depending on the role service that you are migrating, you should limit connections at first, and slowly increase the number of users or connections.
Retire the source servers after migration
Warning
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.
In each case, the source server is retired by removing it from the domain. Most of the Remote Desktop Services role services must be removed from the domain before the destination server is joined to it. Any additional requirements for specific role services are discussed in the topics for those role services.
After you complete and verify the migration, the source server can be shut down or disconnected from the network.
Restore the Remote Desktop Services role services
You can restore the Remote Desktop Services role services in the event of migration failure by rolling back the migration.
Roll back the migration
Most of the servers can be rolled back if the source server is still available in the state it was in after the migration was completed.
Note
If there is more than one role service on the migrated server, you will not have access to the other role services on that server after removing it from the domain.
The following procedure can be used to roll back the migration of these role services:
RD Session Host
RD Virtualization Host
RD Connection Broker
RD Web Access
The rollback of the migration of RD Licensing and RD Gateway role services is covered in the Post-Migration Tasks topics for those role services.
To roll back the migration of a role service
Remove the destination server from the domain.
Join the original source server to the domain.
To verify that the rollback was successful, follow the verification steps in the migration guide for each role service.