Link to home
Start Free TrialLog in
Avatar of Swamp_Thing
Swamp_ThingFlag for United States of America

asked on

MSDN: Using a Windows Server 2003 license in a "production" envirnment... or is it a "developement" environment?

Hey guys, I just want to get some opions/facts from you.  I was searching around the knowledgebase here and came accross some MSDN questions.  I know that with each MSDN title that comes in under our subscription, there is a license associated with it.  For example, I was looking through our binder of MSDN CDs and came accross a "Windows Server 2003 Standard" CD.  I have a Ghost server that I'm in the process of refining and would like to put Server 2003 on it.  Instead of using one of our purchased licenses (we're on a server 2000 network and purcased a handful of keys ahead of time in anticipation of upgrading to '03) I figured I would just use the MSDN license/product key.  

Now I know the licenses that come with the MSDN titles are said to be "for developement use only". such as if I wanted to deploy SQL 2005 on a server I could install an MSDN copy on a test server, use the MSDN key, and when no conflicts emerged, buy a regular license and install it on the company's SQL server.  BUT... what about in my case.  I had planned on using an old server to run Ghost on it in which I would be testing the functionality of Ghost as well as the benefits of Server 2003, and in the future possibly purchasing a more up to date server in which Server 2003 would be installed with a regular license.  Am I in a gray area here or would you say that if ever questioned about it, I would be OK?
ASKER CERTIFIED SOLUTION
Avatar of PeterMac
PeterMac

Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
Avatar of Swamp_Thing

ASKER

Ok, thanks.  I just wanted to get a second opinion.