Sep 12, 2016 - 02:55 AM
Sep 12, 2016 - 03:33 AM
From a Microsoft Review perspective:
Visual Studio is licensed per User - so each user accessing that server would require the appropriate Visual Studio license (back to above, why would you have this installed in a production environment?).
For the MSDN part (i.e. the "free to dev" software) - MSDN have their own licensing keys. These are not valid within a production environement and will need to be updated to a full VL key if located or the user charge above applies.
Sep 30, 2016 - 10:44 AM
Many Visual Studio subscribers use a computer for mixed use—both design, development, testing, and demonstration of your programs (the use allowed under the Visual Studio subscription license) and some other use. Using the software in any other way, such as for doing email, playing games, or editing a document is another use and is not covered by the Visual Studio subscription license. When this happens, the underlying operating system must also be licensed normally by purchasing a regular copy of Windows such as the one that came with a new OEM PC.
The "restriction" comes in to play only when you want to exempt the device's other MS titles from licensing by leveraging MSDN product benefits. In that case, the device must be used solely for dev.
For example if you wanted to exempt the Windows license, Office license, you could do so with the appropriate MSDN subscription if it is a dev machine. Also, all other users accessing it would have to have the approriate level active MSDN subscriptions. (See https://download.microsoft.com/downlo...)
So if you are using VS on a production machine, you must have a valid license for it and all other software on the machine. Thats it!
Oct 11, 2016 - 11:03 AM
You can use VS on Prod with a valid license keys though it would be little costly since MSDN offering is specifically for Development devices.
How it works is: MSDN user subscription is bought by an organization...mentioning the machines is optional(though it is a good proactive approach in terms of compliance)...Respective users can use the software on their machines...CMDB process has to be there to determine the user to device relationship and also the environment of Device(Dev, QA, Prod etc)....if the device is Dev then it is covered under MSDN subscription bought but if it is plugged into Production environment and being used for business then VS has to be licensed seperately.
I hope it helps!!!