To fight piracy, Microsoft tightens MSDN and TechNet terms again
1–10 of 14 posts
Re: To fight piracy, Microsoft tightens MSDN and TechNet terms again
#2Re: To fight piracy, Microsoft tightens MSDN and TechNet terms again
#3[deleted]
Re: To fight piracy, Microsoft tightens MSDN and TechNet terms again
#4Re: To fight piracy, Microsoft tightens MSDN and TechNet terms again
#5Getting a Technet or MSDN subscription used to be enjoyable since you just got freedom to test what you wanted when you wanted and on what machines (or VMs) you wanted.
Now every time you activate you will have to think "Is this installation worth an activation?" Because what the article fails to mention is that each key has an activation limit (so 3 * 10 = 30 total activations per product).
Even on my retail copy of Windows 7 Pro I constantly hit the activation limit and need to call them. Which you would know is damn annoying as you have to type in and type back like sixty digit strings of nonsense.
I thought activation was originally meant to stop pirates not harass paying customers? Where did Microsoft lose it's way?
Re: To fight piracy, Microsoft tightens MSDN and TechNet terms again
#6Re: To fight piracy, Microsoft tightens MSDN and TechNet terms again
#7Re: To fight piracy, Microsoft tightens MSDN and TechNet terms again
#8Ouch; they've really taken something fun and made it a pain in the neck to use. Getting a Technet or MSDN subscription used to be enjoyable since you just got freedom to test what you wanted when you wanted and on what machines (or VMs) you wanted. Now every time you activate you will have to think "Is this installation worth an activation?" Because what the article fails to mention is that each key has an activation…
Same goes for a VM, just make a copy of the fresh installed VM.
Re: To fight piracy, Microsoft tightens MSDN and TechNet terms again
#9Ouch; they've really taken something fun and made it a pain in the neck to use. Getting a Technet or MSDN subscription used to be enjoyable since you just got freedom to test what you wanted when you wanted and on what machines (or VMs) you wanted. Now every time you activate you will have to think "Is this installation worth an activation?" Because what the article fails to mention is that each key has an activation…
This really seems at odds with "Developers, developers, developers."