Remote Desktop Virtualization Host Role Service Migration
Applies To: Windows Server 2008, Windows Server 2008 R2
This guide describes how to migrate the RD Virtualization Host role service. It also explains how to use Hyper-V to migrate the virtual machines.
Following the steps to migrate the RD Virtualization Host role service will result in a fully functional RD Virtualization Host server with the same server name and virtual machines as the source server.
Overview of the migration process for the RD Virtualization Host role service
The RD Virtualization Host role service migration process includes the following topics:
What is migrated by using this guide
The RD Virtualization Host Migration Guide provides guidance for migrating the RD Virtualization Host role service between servers running Windows Server 2008 R2. The following are migrated by following the steps in the RD Virtualization Host Migration Guide:
RD Virtualization Host server
During the migration process, the name of the source server is given to the destination server. This permits migration of 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.
When the virtual machines are exported from Hyper-V, the machine ID is also exported. The virtual machine ID must be unique, and as a result, the virtual machines must be deleted from the source server migration.
What is not migrated
This guide does not cover migration of clustered RD Virtualization Host servers. For more information about migrating clustered Hyper-V servers, see Migrating Clustered Virtual Machines to Windows Server 2008 R2 (http://go.microsoft.com/fwlink/?LinkId=195978).
This guide references the Remote Desktop Services Migration Overview guide, which contains information that applies to the migration of all role services such as order of migration, expected downtime, SSL and code signing certificates, impact of migration on other role services, and permissions required for migration. Any steps required to migrate every role service are also documented in the overview. The steps documented in the overview are not repeated in the guides for the individual role services.