MSDN and MVLS activation

Hi
I'm having a hell of a time getting exact information out of our Microsoft reseller and am hoping someone can clear it up. This question mainly concerns applications such as Visual Studio and not client or server OS.

We have around 100 MSDN subscriptions and access to the same software through the volume licensing site. The advantages of the VL site software is that the application software generally doesn't require activation. We use mass deployment tools to rollout upgrades when requried. All fairly standard.

We obviously want to remain compliant. The problem is, to do so it seems that we have to assign each MSDN subscription to an individual's .NET passport and have them log in to the MSDN site and retrieve their keys for the application. We want to make sure the users aren't abusing this privilege (such as activating MSDN software at home). Therefore we generally don't give them access to download their own licenses and software.

One solution is we generate 100 dummy email addresses and assign one to each MSDN subscription but this is an administrative overhead we don't want to absorb. The natural solution would appear to be to use the MVLS software instance that shouldn't require activation and then roll that out to the users. But I can't see anywhere any information about whether or not this is a supported and legally compliant route to take.

Has anyone crossed this bridge themselves and what was the outcome?

Thanks

AdoBeebo
LVL 3
AdoBeeboAsked:
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

Jian An LimSolutions ArchitectCommented:
I have access to the MSDN and it seems to me that all visual studio product's product keys are pre-pidded to the file.

The Keys for application depends on cases.
If it is retail, you only have maximum of 10 in an organisation (even though you have 100 MSDN subscription), they share between users.

Alot of the products offers Static Activation or VA licence.
Retail edition should not be deployed in automated rollout.

So, to remain compliant, you need to know what level you have purchased.
http://msdn.microsoft.com/en-au/subscriptions/subscriptionschart.aspx

Only certain product can be used in production use, and others in development and testing phase.



also you would like to compare the MSDN and technet plus subscriptions
http://msdn.microsoft.com/en-au/subscriptions/dd362338.aspx


if you need any help on product key, you can contact the msdn customer service center.
http://msdn.microsoft.com/en-au/subscriptions/cc137104.aspx


 

0

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Microsoft Applications

From novice to tech pro — start learning today.

Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.