Remote Desktop Services: Migrate Remote Desktop Services Role Services

  • Artikel

 

Applies To: Windows Server 2012 R2

Migration for a Remote Desktop Services deployment is supported from source servers running Windows Server 2012 or Windows Server 2012 R2 to destination servers running Windows Server 2012 R2. Migration from any other major or minor releases to Windows Server 2012 R2 is not supported.

Following are the steps for migrating a Remote Desktop Services deployment:

  1. Migrate the RD Connection Broker server

  2. Migrate session collections

  3. Migrate virtual desktop collections

  4. Migrate RD Web Access servers

  5. Migrate RD Gateway servers

  6. Migrate RD Licensing servers

  7. Migrate standalone Remote Desktop Services servers

  8. Migrate certificates

Migrate the RD Connection Broker server

This is the first and most important step for migrating to a destination server running Windows Server 2012 R2.

  • The Remote Desktop Connection Broker (RD Connection Broker) destination server must be configured for high availability to support migration.

    For more information, see RD Connection Broker High Availability in Windows Server 2012.

  • If you have more than one RD Connection Broker server in the high availability setup, remove all the RD Connection Broker servers except the one that is currently active.

  • Upgrade the remaining RD Connection Broker server to Windows Server 2012 R2.

  • After the server is upgraded, add it to the high availability deployment.

Note

A mixed high availability configuration with Windows Server 2012 and Windows Server 2012 R2 is not supported for RD Connection Broker servers. An RD Connection Broker running Windows Server 2012 R2 can serve session collections with RD Session Host servers running Windows Server 2012, and it can serve virtual desktop collections with RD Virtualization Host servers running Windows Server 2012.

Migrate session collections

Follow these steps to migrate a session collection in Windows Server 2012 to a session collection in Windows Server 2012 R2.

Important

Migrate session collections only after successfully completing the previous step, Migrate the RD Connection Broker server.

  1. Upgrade the session collection from Windows Server 2012 to Windows Server 2012 R2.

  2. Add the new RD Session Host server running Windows Server 2012 R2 to the session collection.

    Tip

    Use drain mode when you are setting the RD Session Host servers. For more information about drain mode, see Introducing Terminal Services Server Drain Mode.

  3. Sign out of all sessions in the RD Session Host servers, and remove the servers that require migration from the session collection. 

Note

If the UVHD template (UVHD-template.vhdx) is enabled in the session collection and the file server has been migrated to a new server, update the User Profile Disks: Location collection property with the new path. The User Profile Disks must be available at the same relative path in the new location as they were on the source server. A session collection of RD Session Host servers with a mix of servers running Windows Server 2012 and Windows Server 2012 R2 is not supported.

Migrate virtual desktop collections

Follow these steps to migrate a virtual desktop collection from a source server running Windows Server 2012 to a destination server running Windows Server 2012 R2.

Important

Migrate virtual desktop collections only after successfully completing the previous step, Migrate the RD Connection Broker server.

  1. Upgrade the virtual desktop collection from the server running Windows Server 2012 to Windows Server 2012 R2.

  2. Add the new Windows Server 2012 R2 RD Virtualization Host servers to the session collection.

    Tip

    Use drain mode when you set the RD Session Host servers that need to be migrated.

  3. Migrate all virtual machines in the current virtual desktop collection that are running on RD Virtualization Host servers to the new servers.

  4. Remove all RD Virtualization Host servers that required migration from the virtual desktop collection in the source server.

Note

If the UVHD template (UVHD-template.vhdx) is enabled in the session collection and the file server has been migrated to a new server, update the User Profile Disks: Location collection property with the new path. The User Profile Disks must be available at the same relative path in the new location as they were on the source server. A session collection of RD Session Host servers with a mix of servers running Windows Server 2012 and Windows Server 2012 R2 is not supported.

Migrate RD Web Access servers

To migrate the RD Web Access servers, see Remote Desktop Web Access Role Service Migration.

Migrate RD Gateway servers

To migrate the RD Gateway Servers, see Remote Desktop Gateway Role Service Migration.

Migrate RD Licensing servers

Follow these steps to migrate an RD Licensing server from a source server running Windows Server 2012 or Windows Server 2012 R2 to a destination server running Windows Server 2012 R2.

  1. Migrate the Remote Desktop Services client access licenses (RDS CALs) from the source server to the destination server.

    For more information, see Migrate Remote Desktop Services Client Access Licenses (RDS CALs).

  2. Use the Deployment Properties Wizard to list the new RD Licensing servers on the server running Windows Server 2012 R2.

  3. Remove the RDS CALs from the source RD Licensing server.

    For more information, see Remove Remote Desktop Services Client Access Licenses.

  4. Remove the source RD Licensing servers from the deployment.

Migrate standalone Remote Desktop Services servers

The following list contains the complete migration guides for each role service. Each guide include information about preparing to migrate, verifying the migration, and post-migration tasks:

Migrate certificates

Migrating certificates simply requires updating certificate information in Deployment Properties: Manage certificates

Remote Desktop Services features that use certificates

Although this guide does not describe how to migrate Remote Desktop Services features, the following list of features that use certificates is included for reference. Each of the following features uses certificates for at least one role service:

  • Single sign-on (SSO) for RemoteApp and Desktop Connection

  • Web Single Sign-On (Web SSO)

  • HTTPS connections to RD Web Access

  • Digital signing of Remote Desktop Protocol (.rdp) files for personal virtual desktops and virtual desktop pools

  • Digital signing of Remote Desktop Protocol files for Remote App programs

  • RD Gateway connections to Remote Desktop Services

  • RD Session Host server connections in a farm configuration

Preparing certificates for migration

In most cases, the migration of certificates for Remote Desktop Services requires you to export the certificate with the private key. After export, you should store the certificate in a safe location.

A certificate with a private key can be migrated by using the following steps:

  1. To export the certificate to a PFX file, see Export a certificate with the private key.

  2. To import the certificate from a PFX file, see Import a certificate.

After you have imported the certificate to the certificate store on the destination server, follow the instructions for configuring the certificate for the specific role service.

Additional references