[Okta Webinar] Learn how to a build a cloud-first strategyRegister Now

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 590
  • Last Modified:

Upgrading from an MSDN to a Volume License


I have about 10 servers which are running Windows 2003 Server with MSDN licenses. I now want to move these servers into production and have purchased a volume license for all of them.
I've received conflicting information about whether I need to do a full reinstall or whether I can simply insert the new volume license CD and do an in-place "Upgrade".

Has anyone been down this road?

Any help would be appreciated.
0
Primedius
Asked:
Primedius
  • 4
  • 3
  • 3
2 Solutions
 
CarlWarnerCommented:
I'm not convinced you even need to do any kind of install.

I would think running a routine to change the product key is all you would need to do.

[Even though this talks about going from a leaked/illegal key to a good new one, the principles apply.]
How to change the Volume Licensing product key on a Windows XP or a Windows 2003-based computer
http://support.microsoft.com/kb/918342/en-us
0
 
PrimediusAuthor Commented:
Tried this and it does not work for an MSDN install....

As the article suggests, it only works on volume license installs.

Good idea had it worked.

0
 
atheluCommented:
here is a freeware utility that should do the trick:

http://www.magicaljellybean.com/keyfinder.shtml

Just click on the Options button and choose change windows key.
0
What does it mean to be "Always On"?

Is your cloud always on? With an Always On cloud you won't have to worry about downtime for maintenance or software application code updates, ensuring that your bottom line isn't affected.

 
PrimediusAuthor Commented:
Thanks for the try athelu but:

 FAQ:

Q. I see the 'change key' option, but it's grayed out. Why?

A. The Keyfinder only supports changing the keys in Windows 95, 98, ME, and XP. Windows 2000, NT, and Server 2003 aren't supported.
0
 
atheluCommented:
BAH!

The page said support for server 2003. Must be to reveal the key only.
0
 
atheluCommented:
0
 
PrimediusAuthor Commented:
Hi Athelu,

I am afraid not. This only works if the key now on was a volume license and not MSDN or retail.
0
 
CarlWarnerCommented:
I'm sorry that didn't work the way I thought it would.

Still, I don't believe an install is necessary just to change Product keys.

Since the process to do exactly what you want to do in the direction you need to do it doesn't seem to be common enough to be well-documented in the real world, I would strongly suggest cointacting MS suport and tell them what you want to do about changing the product key and that you don't want to re-install an in-place working operating system.  They have to have a real easy solution, even if they want to keep it close to the vest.
0
 
PrimediusAuthor Commented:
I finally got a reply back from Microsoft.

You must do an in-place install using the upgrade option on the volume license CD media.

This is the only way to convert an MSDN license to a volume license.

I am splitting points
0
 
CarlWarnerCommented:
Thanks.

I'm glad you have a solution.  

But, I still think an in-place install is awfully drastic just to change a darn product key.  Thanks, MS.
0

Featured Post

Vote for the Most Valuable Expert

It’s time to recognize experts that go above and beyond with helpful solutions and engagement on site. Choose from the top experts in the Hall of Fame or on the right rail of your favorite topic page. Look for the blue “Nominate” button on their profile to vote.

  • 4
  • 3
  • 3
Tackle projects and never again get stuck behind a technical roadblock.
Join Now