msdn.microsoft.com/subscriptions/faq/default.aspx
EULA) allows each person with an MSDN license to use all of the software that is included in the subscription for development, test, and demonstration purposes only. everyone who uses the products within an MSDN Subscription must have an MSDN Subscriptions license. In other words, one license must be purchased for each user. Customers do not have to purchase media for each licensed user. MSDN subscription media can be shared with all individuals who have an MSDN Subscriptions license of the same level or higher. it is not a single-user license and can be freely shared within an organization. You need to purchase the MSDN Library, but the information on the Library is available for use by anyone in your organization.
When a subscription expires, do the licenses terminate or are the y still valid? MSDN Subscriptions have a perpetual license, so subscribers can still use the products received with their MSDN Subscription after their subscription has expired.
Everyone who uses products within MSDN Subscriptions must have an MSDN Subscriptions license. The contents of MSDN Subscriptions cannot be shared with non-subscribers or subscribers with a lower subscription level.
May I use MSDN Subscriptions software to install software for day -to-day (production) use? Software in your MSDN Subscription comes with a development, test, and demonstration license. Examples of prohibited use include: + You may not install Exchange Server from your MSDN Universal Subscription and use it to send and receive personal or business-related e-mail. For example, you can use Project to manage a development project, use Visio to diagram your application, etc. Again, only persons with an MSDN Universal Subscription license can use these Microsoft Office products in this manner.
By "production" we mean any activity that is personal, for general business use, or not directly related to the testing and development of software applications. Examples of (prohibited) production use include: + Installing Windows 98 to play games for entertainment. You may not use your MSDN Subscription as a substitute for purchasing a retail license for an operating system if you do more than develop and test on your computer. Examples of development and testing use include: + Testing to see if a program in development works equally well with various different operating systems.
Can I use the operating systems in my MSDN subscription to instal l or upgrade my development PCs? MSDN-licensed operating systems (OS) can be used as the primary OS as long as the computer is used only for development and testing purposes, and as long as every individual using that computer for development or testing purposes has a separate MSDN license: MSDN is licensed on a per user model, unlike normal OS licensing which is based on a per device model. If a computer using an MSDN-licensed OS is used for any purpose other than development and testing (for example, a developer's primary computer which is also used for corporate email), then a production-use OS license for the computer is required.
Can I use the Visual Studio product to create an executable file and distribute this file for sale? Applications, utilities, and executables you develop using Visual Studio, Access, or Office Developer can be distributed to customers royalty-free, pursuant to the terms of the corresponding End-User License Agreement (EULA). In addition, there are many redistributable components included with Visual Studio, which you are welcome to incorporate into your applications and distribute for free pursuant to the terms of the Visual Studio EULA. Please note there is a royalty for Microsoft server products that are distributed with applications.
Can I use Office, Project, and Visio for development and testing of applications? Office Professional Enterprise Edition 2003, Project Standard and Visio Standard can be used for business use directly related to the design, development, testing and demonstration phases of building applications. In addition, one copy of Office Professional Enterprise Edition 2003 can be used for general business use by each licensed MSDN Universal subscriber. Project Professional 2003, Project Server 2003 and Microsoft Office Project Server 2003 Client Access License are not currently available for business purposes under the MSDN licensing agreement.
Do all users also need an MSDN license to test applications? MSDN licenses are required for testers who do progressive test, configuration testing, debugging and maintenance programming. MSDN licenses are not required for user acceptance testing or stress testing, provided that that the testers will not be doing any debugging, configuration, or maintenance.
My organization has many different MSDN subscriptions, are we lic ensed to use the same software? Customers are licensed for the software in their subscription. For example, an MSDN Professional Subscriber has a license to all the products in the MSDN Professional subscription. An MSDN Professional Subscriber is not licensed for products in MSDN Universal subscription.
Yes, as long as your use falls within the scope of the MSDN Subscriptions End-User License Agreement (EULA). You can only use the software for development and testing purposes.
In general, you can install MSDN software on any number of machines. However: + Only persons with MSDN Subscription licenses can use the software on any of the machines + Some products, such as Windows XP, require product activation, which may limit the number of machines on which you can install software. See the section on Product Activation for more information.
I've had an MSDN Subscription for some time now and have many old discs that are duplicates or that I simply don't use. You may only sell or transfer your MSDN Subscription as a whole, and you must transfer all materials received with the subscription to the new owner.
What licensin g terms apply to products I received in the past? If you have been an MSDN Subscriber for many years, you probably have older products which no longer ship in MSDN. Older products follow the licensing terms (from the End User License Agreement) that governed your MSDN subscription at the time you received those products.
I notice that occasionally Microsoft changes the end user license agreement for MSDN. What license terms apply to products that I had previously received? Occasionally we change the licensing terms for MSDN or for specific products. If the licensing terms change, the new terms apply to products you receive in your current subscription. A new MSDN end user license agreement does not apply to products which no longer ship in MSDN. You will receive a new End User License Agreement, if the terms change. For your convenience, you may want to keep copies of all the MSDN End User License Agreement with your MSDN shipments.
At this time MSDN subscriptions purchased in the United States and Canada are not transferable to countries outside of the North American region. If you live outside of the US and Canada, you cannot purchase MSDN from the US or Canada. If you purchased and activated an MSDN subscription in the US or Canada and are moving to a country outside of the North America, please cancel your subscription for which you will receive prorated refund, and purchase a new subscription in that country.
MSDN Volume License Registration site is for Open, Select, and Enterprise Agreement customers. Customers who register their licenses will receive access to MSDN Subscriber Downloads, technical support, an MSDN Subscriber ID. Customers who ordered their licenses through the Software Assurance program will also receive complimentary media, based on number of licensees ordered. All customers who register at the site will need to establish a unique Passport email address. The registration site will prompt all customers to enter their Passport email address. Customers who already have a Passport address may use their current address. Customers who do not have a Passport address will be prompted to create one.
I am receiving errors when I try to register at the site. There are a few reasons why you might be receiving er...
|