1.3.7 License management of various license types
Asset Console allows you to manage various types of software licenses.
This subsection describes the typical license types and the license management methods, and the license management method used by Asset Console.
- Organization of this subsection
(1) License types
There are many types of licenses, but the main ones are as follows.
-
Installation license
This license permits installation on a single device.
-
User license
This license permits use by a single user. It permits installation on multiple devices that are owned by the same user.
-
Pre-installed
This license covers installation on a purchased device.
-
Server license
This is a license for server products. Server products normally have additional licenses, such as for the permitted number of times the server can be accessed (client access license), the permitted number of CPUs (CPU license), or the permitted number of manageable nodes (managed node license).
-
Second license
This license permits installation on a specific second device, such as a portable device. It is typically together with an installation license that permits installation on only a single device.
-
Concurrent execution license
This license might be necessary, depending on the number of software programs that are to be concurrently executed or reside on a device.
-
Volume license
This license allows you to freely purchase any number of licenses within the predefined range. The purchaser can choose the desired combination and number of licenses, but both the minimum and maximum number of points that can be used during the contract period are predetermined.
In addition to the above types of licenses, there are various options, such as whether software is upgradeable or downgradable.
(2) License management methods
The two main license management methods are total count management and per-license management. You can select the method that is best for your asset management system (or is appropriate for your software programs).
- Total count management
-
This method manages licenses by comparing the total number of software licenses owned by the company or a group to the number of licenses in use. It eliminates the need for allocating individual licenses, thereby making management tasks comparatively easy.
However, if licenses are not used properly, it is difficult to identify a specific device or user where a license violation is occurring. Even with the same license, if permitted options depend on purchase contract terms, it is difficult to determine whether the license is being used properly by each device or user.
You cannot clearly determine which devices downgrade software licenses are being used for.
- Per-license management
-
This method manages licenses by associating each owned license with a specific device or user. This method allows you to accurately determine the usage status according to each license's terms of purchase. It is also easy to identify devices or users that are illegally using licenses.
However, this method requires that each license be associated with a device or a user.
(3) License management via Asset Console
Asset Console provides you with the flexibility to create license information appropriate to the types of licenses you have and the management method you are already using, thereby making it possible to manage licenses on a very detailed level.
For example, you can efficiently manage licenses by using the appropriate management method for each license, such as employing total count management for licenses that are used throughout the entire company and per-license management for licenses that are individually purchased.
In addition to the volume license management method, this section describes total count management and per-license management, which are license management methods supported by Asset Console.
(a) Managing licenses based on the number of owned licenses and the number of used licenses
This is the total count management method.
This method registers the number of licenses you own when a license is purchased, obtains the number of licenses being used from the licenses installed on devices, and then compares these numbers.
The following figure shows the concept of managing licenses on the basis of the number of owned licenses and the number of used licenses.
|
For an example of total count management, see 2.4.1 Checking the operation status by comparing the number of owned licenses to the number of used licenses.
(b) Managing licenses by assigning them to devices or users
This is the per-license management method.
- Managing licenses by assigning them to devices
-
This method manages licenses that are required for each device, such as installation licenses and second licenses, by assigning them to devices.
A license's acquisition method, such as part of a package or pre-installed, can be managed as an attribute within the license information.
The following figure shows the concept of managing licenses by assigning them to devices.
Figure 1‒9: Concept of managing licenses by assigning them to devices - Managing licenses by assigning them to users
-
This method manages licenses as User licenses by assigning them to users who are managed by Asset Console.
The following figure shows the concept of managing licenses by assigning them to users.
Figure 1‒10: Concept of managing licenses by assigning them to users
Second and concurrent execution licenses are managed as follows:
-
You can manage second licenses by adding and assigning them to devices, or by managing them as User licenses without adding the licenses.
-
Managing concurrent execution licenses
You can manage concurrent execution licenses by registering the number of licenses that can be executed concurrently as the number of owned licenses, or you can manage the number of copies that can be executed concurrently as a license attribute.
For an example of per-license management, see 2.4.2 Accurately managing targets according to the assigned licenses.
(c) Managing downgrade software
When you use a purchased license for an older version of some software, the older version of the software is called downgrade software. For example, if you use Windows 7 with a license purchased for Windows 8, Windows 7 is downgrade software. To manage downgrade software, you must perform per-license management as described in subsection (b) above.
The following figure shows the concept of managing downgrade software by assigning licenses for each device and managing them as installation licenses.
|
Managing downgrade software requires specifying a number of settings in addition to performing per-license management. For details, see 4.6.9 Adding downgrade software assets in the Administration Guide.
(d) Managing volume license points
You can manage the status of the number of accrued points by registering the volume license information and associating it with the applicable licenses.
Options for volume licenses (such as whether software is upgradeable) are managed as part of the license information for software.
The following figure shows the concept of managing volume license points.
|