Hi,
When setting up a Visual Studio (With MSDN) License you should either create it from the Purchase, using the SKU you have, or create the License from scratch and choose the Visual Studio Application, at which point you will have the choice of choosing a Product Use Rights Template – just be sure to choose the appropriate Edition (Enterprise, Professional etc). Either of these approaches will auto-create your License with the correct Use Rights and Applications.
Please note:
- The License will be a Named User License. This means that it will only be consumed by users who are allocated. Therefore in addition to setting up the License you will need to allocate the users from your MSDN Portal.
- Wherever a User is allocated, any of the included Visual Studio and MSDN Applications found on that User’s device/s will consume the Visual Studio License, as desired.
I would also recommend setting up a Device License to catch Visual Studio only for any installs on devices of users who are not allocated to the Named User License (This is a good indication of users who should have an MSDN subscription, but do not).
To allocate large numbers of users you can use an Excel template and the Business Adapter Studio.
An alternative approach would be to change the Named User License to a User License and let Flexnet consume the license naturally, but then the big risk is that any of the included Applications will consume the Visual Studio License instead of their own license (Like SQL Server for example). You could avoid this by changing all of the included Products to Supplementary status in the Use Rights tab of the License, but this:
- Will take time
- Will mean consumption includes the devices of Users who may not have Vis. Studio and MSDN Subscriptions (But do have Visual Studio installed).
Kind Regards,
Stewart
