Migrate Microsoft Remote Desktop Version 10

| Posted on by

-->

You have three options to migrate your RDS CALs:

Download & install the latest offline installer version of Chrome Remote Desktop for Windows PC/laptop. It works with both 32-bit & 64-bit of Windows 7 / Windows 7 64 / Windows 8 / Windows 8 64 / Windows 10 / Windows 10 64. Safe & Free Download for Windows PC/laptop – 4.1 MB. Safety (Virus) Test. Microsoft's Remote Desktop Connection is a convenient program for accessing and working with remote Windows workstations and servers. The tool is built into Windows but is also available as a.

  1. Automatic connection method: This recommended method communicates via internet directly to the Microsoft Clearinghouse outbound over TCP port 443.
  2. Using a web browser: This method allows migration when the server running the Remote Desktop Licensing Manager tool does not have internet connectivity, but the administrator has internet connectivity on a separate device. The URL for the Web migration method is displayed in the Manage RDS CALs Wizard.
  3. Using a telephone: This method allows the administrator to complete the migration process over the phone with a Microsoft representative. The appropriate telephone number is determined by the country/region that you chose in the Activate Server Wizard and is displayed in the Manage RDS CALs Wizard.

In this article, the Establish RDS CAL migration method highlights the general steps common across any RDS CAL migration method, while Migrate RDS CALs highlights the steps specific to each migration method.

Regardless of migration method, you must, at a minimum, be a member of the local Administrators group to perform the migration steps.

Establish RDS CAL migration method

  1. On the license server, open Remote Desktop Licensing Manager. (Click Start > Administrative Tools. Enter the Remote Desktop Services directory, and launch Remote Desktop Licensing Manager.)
  2. Verify the connection method for the Remote Desktop license server: right-click the license server to which you want to migrate the RDS CALs, and then click Properties. On the Connection Method tab, verify the Connection method - you can change it in the dropdown menu. Click OK.
  3. Right-click the license server to which you want to migrate the RDS CALs, and then click Manage RDS CALs.
  4. Follow the steps in the wizard to the Action Selection page. Click Migrate RDS CALs from another license server to this license server.
  5. Choose the reason for migrating the RDS CALs, and then click Next. You have the following choices:
    • The source license server is being replaced by this license server.
    • The source license server is no longer functioning.
  6. The next page in the wizard depends on the migration reason that you chose.

    • If you chose The source license server is being replaced by this license server as the reason for migrating the RDS CALs, the Source License Server Information page is displayed.

      On the Source License Server Information page, enter the name or IP address of the source license server.

      If the source license server is available on the network, click Next. The wizard contacts the source license server. If the source license server is running an operating system earlier than Windows Server 2008 R2 or the source license server is deactivated, you are reminded that you must remove the RDS CALs manually from the source license server after the wizard has completed. After you confirm that you understand this requirement, the Obtain Client License Key Pack page appears.

      If the source license server is not available on the network, select The specified source license server is not available on the network. Specify the operating system that the source license server is running, and then provide the license server ID for the source license server. After you click Next, you are reminded that you must remove the RDS CALs manually from the source license server after the wizard has completed. After you confirm that you understand this requirement, the Obtain Client License Key Pack page appears.

    • If you chose The source license server is no longer functioning as the reason for migrating the RDS CALs, you are reminded that you must remove the RDS CALs manually from the source license server after the wizard has completed. After you confirm that you understand this requirement, the Obtain Client License Key Pack page appears.

The next step is to migrate the CALs - use the information below to complete the wizard. Note that what you see in the wizard depends on the connection method you identified in Step 2 above.

Migrate RDS CALs

There are three mechanisms to migrate licenses to the destination license server; continue the steps corresponding to the Connection method verified in Step 2:

Automatic connection method

  1. On the License Program page, select the appropriate program through which you purchased your RDS CALs, then click Next.
  2. Enter the required information (typically a license code or an agreement number, depending on the License program), and then click Next. Consult the documentation provided when you purchased your RDS CALs.
  3. Select the appropriate product version, license type, and quantity of RDS CALs for your environment based on your RDS CAL purchase agreement, and then click Next.
  4. The Microsoft Clearinghouse is automatically contacted and processes your request. The RDS CALs are then migrated onto the license server.
  5. Click Finish to complete the RDS CAL migration process.

Using a web browser

  1. On the Obtain Client License Key Pack page, click the hyperlink to connect to the Remote Desktop Services Licensing Web site.If you are running Remote Desktop Licensing Manager on a computer that does not have Internet connectivity, note the address for the Remote Desktop Services Licensing Web site, and then connect to the Web site from a computer that has Internet connectivity.

  2. On the Remote Desktop Services Licensing Web page, under Select Option, select Manage CALs, and then click Next.

  3. Provide the following required information, then click Next:

    • Target License Server ID: A 35-digit number, in groups of 5 numerals, which is displayed on the Obtain Client License Key Pack page in the Manage RDS CALs Wizard.
    • Reason for recovery: Choose the reason for migrating the RDS CALs.
    • License Program: Choose the program through which you purchased your RDS CALs.

  4. Provide the following required information, then click Next:

    • Last name or surname

    • First name or given name

    • Company name

    • Country/region

      You can also provide the optional information requested, such as company address, e-mail address, and phone number. In the organizational unit field, you can describe the unit within your organization that this license server serves.

  5. The License Program that you selected on the previous page determines what information you need to provide on the next page. In most cases, you must provide either a license code or an agreement number. Consult the documentation provided when you purchased your RDS CALs. In addition, you need to specify which type of RDS CAL and the quantity that you want to migrate to the license server.

  6. After you have entered the required information, click Next.

  7. Verify that all of the information that you have entered is correct, then click Next to submit your request to the Microsoft Clearinghouse. The web page then displays a license key pack ID generated by the Microsoft Clearinghouse.

    Important

    Keep a copy of the license key pack ID. Having this information with you facilitates communications with the Microsoft Clearinghouse, should you need assistance with recovering RDS CALs.

  8. On the same Obtain Client License Key Pack page, enter the license key pack ID, and then click Next to migrate the RDS CALs to your license server.

  9. Click Finish to complete the RDS CAL migration process.

Using a telephone

  1. On the Obtain Client License Key Pack page, use the displayed telephone number to call the Microsoft Clearinghouse. Give the representative your Remote Desktop license server ID and the required information for the licensing program through which you purchased your RDS CALs. The representative then processes your request to migrate the RDS CALs, and gives you a unique ID for the RDS CALs. This unique ID is referred to as the license key pack ID.

    Important

    Keep a copy of the license key pack ID. Having this information with you facilitates communications with the Microsoft Clearinghouse should you need assistance with recovering RDS CALs.

  2. On the same Obtain Client License Key Pack page, enter the license key pack ID, and then click Next to migrate the RDS CALs to your license server.

  3. Click Finish to complete the RDS CAL migration process.

-->Desktop

Migrate Microsoft Remote Desktop Version 10 To Ios

Files and application settings can be migrated to new hardware running the Windows® operating system, or they can be maintained during an operating system upgrade on the same computer. This topic summarizes the Microsoft® tools you can use to move files and settings between installations in addition to special considerations for performing an upgrade or migration.

Migrate Microsoft Remote Desktop Version 10 Windows

Upgrade from a previous version of Windows

You can upgrade from an earlier version of Windows, which means you can install the new version of Windows and retain your applications, files, and settings as they were in your previous version of Windows. If you decide to perform a custom installation of Windows instead of an upgrade, your applications and settings will not be maintained. Your personal files, and all Windows files and directories, will be moved to a Windows.old folder. You can access your data in the Windows.old folder after Windows Setup is complete.

Migrate files and settings

Migration tools are available to transfer settings from one computer that is running Windows to another. These tools transfer only the program settings, not the programs themselves.

For more information about application compatibility, see the Application Compatibility Toolkit (ACT).

The User State Migration Tool (USMT) 10.0 is an application intended for administrators who are performing large-scale automated deployments. For deployment to a small number of computers or for individually customized deployments, you can use Windows Easy Transfer.

Migrate with Windows Easy Transfer

Windows Easy Transfer is a software wizard for transferring files and settings from one computer that is running Windows to another. It helps you select what to move to your new computer, enables you to set which migration method to use, and then performs the transfer. When the transfer has completed, Windows Easy Transfer Reports shows you what was transferred and provides a list of programs you might want to install on your new computer, in addition to links to other programs you might want to download.

With Windows Easy Transfer, files and settings can be transferred using a network share, a USB flash drive (UFD), or the Easy Transfer cable. However, you cannot use a regular universal serial bus (USB) cable to transfer files and settings with Windows Easy Transfer. An Easy Transfer cable can be purchased on the Web, from your computer manufacturer, or at an electronics store.

Note

Windows Easy Transfer is not available in Windows 10.

Migrate Microsoft Remote Desktop Version 10

Migrate with the User State Migration Tool

You can use USMT to automate migration during large deployments of the Windows operating system. USMT uses configurable migration rule (.xml) files to control exactly which user accounts, user files, operating system settings, and application settings are migrated and how they are migrated. You can use USMT for both side-by-side migrations, where one piece of hardware is being replaced, or wipe-and-load (or refresh) migrations, when only the operating system is being upgraded.

Upgrade and migration considerations

Whether you are upgrading or migrating to a new version of Windows, you must be aware of the following issues and considerations:

Application compatibility

For more information about application compatibility in Windows, see Use Upgrade Readiness to manage Windows upgrades.

Multilingual Windows image upgrades

When performing multilingual Windows upgrades, cross-language upgrades are not supported by USMT. If you are upgrading or migrating an operating system with multiple language packs installed, you can upgrade or migrate only to the system default user interface (UI) language. For example, if English is the default but you have a Spanish language pack installed, you can upgrade or migrate only to English.

If you are using a single-language Windows image that matches the system default UI language of your multilingual operating system, the migration will work. However, all of the language packs will be removed, and you will have to reinstall them after the upgrade is completed.

Errorhandler.cmd

When upgrading from an earlier version of Windows, if you intend to use Errorhandler.cmd, you must copy this file into the %WINDIR%SetupScripts directory on the old installation. This makes sure that if there are errors during the down-level phase of Windows Setup, the commands in Errorhandler.cmd will run.

Data drive ACL migration

During the configuration pass of Windows Setup, the root access control list (ACL) on drives formatted for NTFS that do not appear to have an operating system will be changed to the default Windows XP ACL format. The ACLs on these drives are changed to enable authenticated users to modify access on folders and files.

Changing the ACLs may affect the performance of Windows Setup if the default Windows XP ACLs are applied to a partition with a large amount of data. Because of these performance concerns, you can change the following registry value to disable this feature:

This feature is disabled if this registry key value exists and is configured to 1.

Related topics

User State Migration Tool (USMT) Overview Topics
Windows 10 upgrade paths
Windows 10 edition upgrade