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.

Installing RES Automation Manager 2011 on Windows Server 2008 (R2) x64 on SQL Server 2008 R2 Express With Tools x64

You’ll need an admin account. I used Server 2008, my guess is that the procedure won’t differ much when using Server 2008 R2 although I have not tested this.

Download SQLEXPRWT_X64_ENU.exe and start the install.

Enable all features and I recommend installing on a separate partition or disk. Let me rephrase: DON’T install on your system disk (C:).

Change the Instance root directory to somewhere else as your system disk.

Choose Mixed Mode (mandatory according to the RES install docs). I recommend adding the local machine Administrators group as SQL Server administrators.

Complete the setup.

We now need to create a 32-bit System DSN. Otherwise the (32-bit) RES software will not find the database. Start the ODBC Data Source Administrator (Administrative Tools -> Data Sources (ODBC)). Select the System DSN tab and click Add.

Select the SQL Server Native Client 10.0 and press Finish.

Fill in the values as shown in the screenshot below and press Finish.

Test your connection with the button that appears in the next screen.

Press OK and OK again. Your System DSN is now created.

Now open the SQL Server Configuration Manager from the Start Menu and enable Named Pipes and TCP/IP protocols for SQLEXPRESS.

Now, reboot your server.

Download RES-AM-2011.msi and start the install. I recommend not installing on your system disk. Launch the console at the end of the setup.

Press the Create button to create the new datastore for RES Automation Manager 2011.

If you have not create the 32-bit System DSN or have not rebooted, you will not see <ServerName>\SQLEXPRESS in the pulldown list.

Choose <YourServer>\SQLEXPRESS or fill this in yourself. Use the sa account to create the database.

Choose a logical database name. I recommend using the default name.

Choose the location of the datafile and the transaction log file as well as the initial sizes and growth sizes. If you don’t know what values to use, the defaults will probably be sufficient for your needs.

Choose the user and password to be created to login to the database.

Click Next and Finish. The database will be created.

Your done. When you start RES AM, you can check and verify the settings on the Information option in the tree.

Remove Help icon with popup description from Citrix Web Interface 5 logon page

I was handed the challenge of removing the help icon/picture from the Citrix Web Interface 5.3 as shown below.

Of course I couldn’t find any up tot date info on the citrix site, so I had to search for myself. What else is new.

I managed to find the part I was looking for in Inetpub\wwwroot\Citrix\XenApp\app_code\PagesJava\com\citrix\wi\pageutils\UIUtils.java and out commented the lines I didn’t want.

No need to reboot, just a refresh of the logon page and everybody is happy with this little Citrix WI hack =)

%d bloggers like this: