Changing a Windows Server product key

If people need “productivity software,” they might usefully consider free, open source alternatives to proprietary software. I personally find it disgraceful that educational institutions help lock users in to the wares of certain large software companies by insisting on the use of those wares. I’m aware of the excuse that, “But that’s what they’ll use when they start work. The proprietary versions change from version to version, necessitating retraining in any case. A spreadsheet’s a spreadsheet.
msdn licence keys

To fight piracy, Microsoft tightens MSDN and TechNet terms again

The reasoning behind the change is to cut down on software piracy by rogue subscribers who sell or pass on their product keys to other people. Changes have been made to this article in response to information provided by Microsoft. Microsoft has already tightened the terms for subscribers, reducing the product keys a TechNet subscriber gets from ten per product down to three, while MSDN subscribers are now limited to five keys per product and three keys for older products – however keys can be used in multiple activations..

The products covered by the product keys include most client and server operating systems, the Office suite, and Visual Studio. The problem faced by Microsoft was that of fraudulent businesses selling the keys on, sometimes to innocent customers who did not realise they were buying keys not intended for commercial use. Microsoft also points out that subscribers can request additional keys if needed.

Alongside the new restriction comes a reduction in the number of product keys that can be downloaded per day by Technet subscribers to For MSDN the limit is roughly 55 keys per 24 hour period, and for some subscription levels this is being reduced to seven.

When your subscription concludes, you will no longer have access to the software or any associated benefits and must discontinue your use of the software. As a Microsoft spokesperson told us: Microsoft reserves the right to suspend or terminate your subscription, without any notice or obligation to you, if Microsoft detects suspicious activity related to keys or activations It has to be admitted that exactly what Microsoft will do isn’t made plain and we have asked for clarification – so look out for an update.

Microsoft has also clarified the terms of use of the software in the new subscription agreement to make it more obvious that the software is for evaluation rather than being a cut-price way to acquire licenses.

The simpler TechNet subscription contains the following key points: You may not use the software if you do not have an active subscription. You may install and use the software on your devices only to evaluate the software. You may not use the software in a live operating environment, in a staging environment, or with data that has not been backed up. You may not use the software for software development or in an application development environment. MSDN subscribers can still use the software for design, development, testing, and demonstration of your programs.

While it is understandable that Microsoft wants to prevent rogue subscribers misusing the software, many long term subscribers will be unsettled by the changes.

TechNet and MSDN have provided a way for many people to get to know Microsoft software, and anything that constitutes a barrier will increase the numbers of people moving to open source alternatives. If Microsoft moves to enforcing the limitation of use by cancelling keys automatically at the end of the license period, then a stronger reaction is likely. In the case of MSDN the license is still one that allows you to use the software for the range of purposes specified in perpetuity.

This is exactly what is required and Microsoft would have to think very hard before changing this license condition. Notice that the TechNet license specifically rules out using it for software development or testing and now with the “time out” clause it becomes unattractive to even think about bending the rules.

We often create VMs for testing and then simply archive them in case they are needed at a later date. If the license key were to time out then the chances are the test setup wouldn’t work when it was needed. More Information.

You are here:

July 06, – 21 comments Microsoft, in an attempt to fight piracy, has tightened the terms for MSDN and TechNet subscribers once again. Back in March we reported that Microsoft reduced the number of keys that TechNet subscribers received with their subscription from five to 3. Today ZDNet reports that the company has revised its policies again to fight piracy. Subscribers up until recently received ten product keys for nearly every Microsoft client and server product available, including Microsoft Windows and the company’s Office suite. Counterfeit businesses took the keys and resold them to customers who often were not aware that they did receive keys that were not intended for retail channels. For a single annual subscription fee of a few hundred Dollars, subscribers would get keys that they could resell for a multitude. Even with three keys, it can still a profitable business due to the sheer size of products Microsoft is making available.

VIDEO: Microsoft Developer Network

Using MSDN at home is not just a dream its a right that you have today. to download software and product keys ends when the subscription. Microsoft has altered the TechNet license so that subscribers will no longer For MSDN the limit is roughly 55 keys per 24 hour period, and for. What are MSDN Keys and how do they work with regards staying valid? system Microsofts stance is that anyone using an MSDN licence like.

Leave a Reply

Your email address will not be published. Required fields are marked *