Migrating Terminal Server Licenses from Windows Server 2003 to Windows Server 2008 R2 using the Remote Desktop Licensing Manager

Here’s a step-by step guide to migrate your Terminal Server licenses from a Windows Server 2003 server to a Windows Server 2008 R2 server.

Why 2008 R2? Because it has a kind of transfer wizard that isn’t present in 2008. If you want to transfer your licenses to 2003 or 2008 server, you’ll have to get on the phone with Microsoft. In both situations you’ll need the authorization and/or license codes, so keep them at hand. If you can’t find them anymore, you can ask Microsoft to send you a license report for your company. You’ll also need a connection to the Internet so the wizard can contact the Microsoft Clearinghouse server to register your transfer.

Start the Remote Desktop Licensing Manager

Add your servers to the overview screen to the left by right clicking on All servers and choosing Connect

You’ll end up with something like this:

Right click your new server and choose Manage Licenses

The Manage licenses Wizard will start. Click Next on the welcome screen

The wizard will try to contact the Microsoft Clearinghouse server

Now choose your action. I’ll choose the first option because this a a migration and not a disaster recovery

Put in the source license server’s DNS name

I had to put in the IP address because our source license server had a name with an underscore and the wizard did not like that

Agree to discontinue using the source license server

Choose you license program

I chose Open License which required me to input the Authorization number and License number

Choose your product version, license type and the quantity

The licenses will be migrated

You’re done

If you receive the error “The Microsoft Clearhouse server could not be contacted. Ensure that you have Internet connectivity …..”, you can try to first open a browser windows to http://microsoft.com and (repeatedly) try the last step (press Back and Next) of the migration again right after the Microsoft website appears. This resolved this weird problem in my case.


About Yuri de Jager
Technology Addict

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out /  Change )

Google+ photo

You are commenting using your Google+ account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )


Connecting to %s

%d bloggers like this: