November 2, 2011 at 7:52 am
I have a situation where a client needs to change the license key in an installation of SQL Server 2008. He does not want to reinstall. Is there a way to update the license key without a reinstall?
November 2, 2011 at 9:50 am
Fred Woolverton-442598 (11/2/2011)
I have a situation where a client needs to change the license key in an installation of SQL Server 2008. He does not want to reinstall. Is there a way to update the license key without a reinstall?
You should be able go to the registry and change it, but I don't recommend doing this. Can I ask why they need to change the key? If they have the licenses and the software is not asking for it, I believe they should be fine. Although, I have been known to be wrong before 🙂
Jared
Jared
CE - Microsoft
November 2, 2011 at 9:54 am
He assigns KEY numbers by CLIENT. Then he charges his clients based on number of licenses. Apparently when this instance was installed six months ago the installer used the wrong key. Now they want to change the key without bringing down the instance.
Already tried the registry thing without success.
November 2, 2011 at 10:09 am
Fred Woolverton-442598 (11/2/2011)
He assigns KEY numbers by CLIENT. Then he charges his clients based on number of licenses. Apparently when this instance was installed six months ago the installer used the wrong key. Now they want to change the key without bringing down the instance.Already tried the registry thing without success.
Looks like your only option is to call Microsoft. Here is the results of one of those calls: http://stackoverflow.com/questions/1942595/changing-a-sql-server-2005-installed-product-key
I assume then that this is not a worry about actual Licensing with Microsoft, but with record keeping for this client?
Jared
Jared
CE - Microsoft
November 2, 2011 at 10:20 am
I think we may be over-thinking this. Licensing is a function of paperwork. I have 5 SQL 2008 Standard servers and 5 SQL 2008 Standard licenses. The fact that I used the same key on all 5 is not important. The fact I have enough licenses IS.
CEWII
November 2, 2011 at 10:24 am
Elliott Whitlow (11/2/2011)
I think we may be over-thinking this. Licensing is a function of paperwork. I have 5 SQL 2008 Standard servers and 5 SQL 2008 Standard licenses. The fact that I used the same key on all 5 is not important. The fact I have enough licenses IS.CEWII
I'm going to half +1 on this.
I've heard of a review here that went along those lines. I bought 300 offices licenses and I have 280 computers. that audit pretty much ended there on that point.
November 2, 2011 at 10:31 am
Going back a couple of employers, I have to agree. We purchased multiple licenses of SQL Server 2005 and later SQL Server 2008 that we installed on multiple servers. The license key was burned into the install media so the same key was used on multiple servers. We had the paperwork to show we were compliant if (when) audited.
November 2, 2011 at 10:33 am
Elliott Whitlow (11/2/2011)
I think we may be over-thinking this. Licensing is a function of paperwork. I have 5 SQL 2008 Standard servers and 5 SQL 2008 Standard licenses. The fact that I used the same key on all 5 is not important. The fact I have enough licenses IS.CEWII
Yes, but in THIS case the OP is talking about monitoring which client has which license. In this case, the installed product is mismatched with the recorded license. I believe that is the issue.
Thanks,
Jared
Jared
CE - Microsoft
November 2, 2011 at 10:43 am
jared-709193 (11/2/2011)
Elliott Whitlow (11/2/2011)
I think we may be over-thinking this. Licensing is a function of paperwork. I have 5 SQL 2008 Standard servers and 5 SQL 2008 Standard licenses. The fact that I used the same key on all 5 is not important. The fact I have enough licenses IS.CEWII
Yes, but in THIS case the OP is talking about monitoring which client has which license. In this case, the installed product is mismatched with the recorded license. I believe that is the issue.
While that may be true I am suggesting that he is over thinking it. And because somebody screwed up he is going to have to work around it, so he probably needs to push for better controls in the future to prevent the problem.
Also, how is he lining up licenses to clients? Reg Key? Its not directly stored in the registry. So how?
I am 99% sure that you can't change the data without a re-install.
It might be as simple as tweaking his data which would probably make more sense.
CEWII
November 2, 2011 at 11:17 am
Elliott Whitlow (11/2/2011)
jared-709193 (11/2/2011)
Elliott Whitlow (11/2/2011)
I think we may be over-thinking this. Licensing is a function of paperwork. I have 5 SQL 2008 Standard servers and 5 SQL 2008 Standard licenses. The fact that I used the same key on all 5 is not important. The fact I have enough licenses IS.CEWII
Yes, but in THIS case the OP is talking about monitoring which client has which license. In this case, the installed product is mismatched with the recorded license. I believe that is the issue.
While that may be true I am suggesting that he is over thinking it. And because somebody screwed up he is going to have to work around it, so he probably needs to push for better controls in the future to prevent the problem.
Also, how is he lining up licenses to clients? Reg Key? Its not directly stored in the registry. So how?
I am 99% sure that you can't change the data without a re-install.
It might be as simple as tweaking his data which would probably make more sense.
CEWII
I don't think anybody is overthinking, the OP is just trying to see if there is an easy way to keep things orderly. Yes the product key it is directly stored in the registry and there are several tools/scripts to return it.
OP: No, you cannot change the key without reinstalling.
Thanks,
Jared
EDIT: product key is not hex
Jared
CE - Microsoft
November 2, 2011 at 12:46 pm
Alright Jared, I stand corrected on the reg key.
Personally I have never needed to retrieve it after I did an install. But YMMV..
CEWII
Viewing 11 posts - 1 through 10 (of 10 total)
You must be logged in to reply to this topic. Login to reply