How to configure, use and troubleshoot Asset Management 6.5 Win32 Licenses
Last Updated February 12, 2013
This key article discusses common questions for Asset Management 6.5 Win32 License configuration, usage and troubleshooting.
Question: What is an Asset Management Win32 License? Answer: A Win32 License records license data about software applications, such as Microsoft Office, to which you own purchased licenses. Win32 Licenses tie in with Software Purchases to provide license compliancy on client computers. Instructions for how to create a Win32 License can be found in the Asset Management Solution 6.5 Product Guide starting on page 29.
Question: How does a Win32 License differ from the other Asset Management license types, such as a Software License? Answer: Asset Management provides several different pre-set license types, such as Win32 Licenses, Software Licenses, OS Licenses, etc. For example:
Win32 License. This is the primary license type used when referring to Asset Management licensing.
Software License. The Software license resource type records data about a particular version of an application to which you own licenses.
OS License. The OS license resource type records data about particular versions of operating systems.
Other types of licenses are described in detail in the Asset Management Solution 6.5 Product Guide starting on page 65.
Note: Because of the redundancy of how different Asset license types work, many of these license types can be more or less used interchangeably. For example, an OS License could be used instead of setting up an Win32 License. An OS License merely has additional fields for an operating system, but a Win32 License could still be used instead.
Question: Does Asset Management track my license keys for my software applications? Answer: Asset Management does not have any out of box ability to track which client computers use which license keys for specific software applications or to even record a list of license keys that can be used. Asset Management tracks license usage based on how the Software Purchase is configured and what is found on client computers by a software inventory. This then becomes license compliancy. Note: A custom data class can be added by the user to record specific license keys that client computers use. The following article describes how to do this:
Question: How does license compliancy work? Answer: License compliancy works by tying a Software Purchase to a Win32 License. The Win32 License is then configured to use what is found on client computers as software inventory for the software application in question, which can be from Core (Windows Add or Remove Programs data), Inventory Solution software inventory (physical files) and/or Application Metering Solution (software usage data). For example:
* A Software Purchase is created for ten Microsoft Word 2010 purchases. This is understood to be ten valid licenses that can be used. * A Win32 License is created for the Software Purchase. This is based on software inventory from "word.exe" version 2010, found by software inventory, from Inventory Solution. * When the Win32 License summary is calculated, it finds that there are twenty client computers that have "word.exe" version 2010 installed on them, as reported by Inventory Solution. This then looks like the following:
Total Licenses: 10 In Use: 20 Compliancy: -10
There are therefore ten unauthorized installations of "word.exe" version 2010 in the environment. Note: It is outside of the scope of Asset Management to enforce the user's license compliancy in the user's environment. Reports are provided that help the user to track down which computers have "word.exe" version 2010 installed. The user would then have to make a determination on what to do about it, such as creating a network group policy (GPO) to force the uninstall of unauthorized software installations, an email asking users to do this, purchasing additional licenses, etc.
Question: How do I set up a Win32 License to use software inventory for license compliancy? Answer: Win32 Licenses use a search rule to tie in the software inventory. The following article describes how this is configured: