The Community is now in read-only mode to prepare for the launch of the new Flexera Community. During this time, you will be unable to register, log in, or access customer resources. Click here for more information.
What is the correct way to link a Visual Studio App to a Visual Studio license in Flexera. For example, ours was set up for us. Under applications, Visual studio components show the usage, not the commercial Visual Studio license. This is deceiving for when I run a VS license report.
Do you add the components to the VS commercial license application and then create the usage as all my users state they are using the full VS app?
Thank you for any help on this so we can make sure we are tracking this license appropriately
Feb 13, 2023 06:01 AM
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:
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:
Kind Regards,
Stewart
Feb 24, 2023 03:18 AM
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:
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:
Kind Regards,
Stewart
Feb 24, 2023 03:18 AM
Thank you Stewart! I have decided that it is a lot less work to just manage the license from the MS Visual Studio Portal than in Flexera. Maybe one day Flexera can integrate with this. Appreciate the time you took to respond.
Feb 24, 2023 04:53 AM
The following Idea in Flexera Ideas is potentially related to what you're doing here: FXONE-I-127: SaaS Manager to support Microsoft Visual Studio.
Please vote on that Idea if it would be useful for you.
Feb 24, 2023 05:13 AM
Hi, you are welcome.
See Chris's note about the potential for a Saas Manager integration to the Visual Studio Portal.
Please note that managing the VS licenses in Flexera is less about the VS Licenses themselves and more about licensing the related software you may find on your developer's Laptops or Development VMs (Like SQL Server for example). Therefore I would encourage you to consider allocating your VS Portal users one way or another.
Regards,
Stewart
Feb 24, 2023 05:52 AM