I'm currently using extended coverage per machine, per application to assign Non-Production use rights (MSDN).
How does everyone else approach this task?
Is there a better, more efficient way of doing this?
I have done this as follows:
1. Add all non-production machines to an Organisation in Snow (e.g. YourCo/Server/NonProductionServers) - you can set up rules to auto-populate this organisation based on machine name patterns
2. Add Site licenses for all MSDN license entitlements. You can do a batch import of these licenses to speed up this process.
3. Assign the site licenses to the YourCo/Server/NonProductionServers organisation you set up in step 1
4. Ensure that you add your MSDN subscriptions (e.g. Visual Studio Pro) to your Production organisations as that is where you need to count those and also track maintenance/renewal information.
You can also do this for non-MS software which has "free" non-production licensing. For example, Tableau offer two non-prod licenses for each Tableau Server core/user.
By doing the above and ensuring that your non-prod licenses are ring-fenced to your non-prod organisation you can quickly & accurately track non-prod vs prod installs/uses of the same application.
Caveat: You need a robust rule set up to ensure that only non-prod machines can be added to the non-prod site. Particularly important for MSDN. However, in the case of MSDN you should probably have something similar in place in AD - create a non-prod OU and non-prod user accounts, and give those accounts to those users who have MSDN subscriptions assigned to them. This is acceptable proof to MS in the event of an audit. You need to prove that only users with an MSDN subscription are able to access those servers.
Retrieving data ...