Dear Licensing people at Microsoft.

Why does this process have to be so confusing and hard?

I am in the process of writing up a wiki post that will go step by step on how to install the RDS cals on a member server/premium server sku.  And yes, I know that I should be blogging about adding a MultiPoint server to a SBS 2011 box but I promised folks I’d do a step by step post on how to add a member server to a SBS network.  RDS first, then SQL next.

So tonight I go to blog the steps and because I have 5 TS cals in a VLSC that I can use for the demo/blog.  So I get to the screen where you are supposed to enter the Open value license/agreement number into the window and I put in my valid/current/non expired Open value agreement which currently is a V1234567 digit number (notice the V in the front).  And the window on the TS/RDS licensing refuses to take the V in the front.  Okay, says I, let’s try using the 1234567 part of the agreement number.  No go.

Okay.. so what number do you want? 

Hmmm let’s try my expired, Windows 2008 version of the open value license which is a 1234567 digit number but doesn’t have a V in the front.  And even though that old expired license is based on Server 2008 rds cals, let’s choose 2k8r2 cals in the drop down window and see if it likes my expired RDS agreement number.

The darn thing worked.

Mind you this is not the active agreement in my VLSC.  This is an expired agreement as of 1/31/2011.  It should not have activated like this… yet it did.

<sigh>  Why does licensing have to be so confusing?  This is why Charlie says forget TS/RDS in a member server and go with Multipoint instead.

 

 

 

One Response to Dear Licensing people at Microsoft.

  1. Dean says:

    “Dear Licensing people at Microsoft.

    Why does this process have to be so confusing and hard?”

    You could have just stopped right there.

    “And yes, I know that I should be blogging about adding a MultiPoint server to a SBS 2011 box”

    No, no you shouldn’t. 🙂