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?