JP2005301379A - Software resources management method and system - Google Patents

Abstract

<P>PROBLEM TO BE SOLVED: To provide a software resources management method offering a means for detecting software, which is installed but not used, and supporting removal of it for removing unused software for more effective license use and optimization of a purchased license. <P>SOLUTION: Installed software information and using software information are gathered from a plurality of information processing devices, and an input of an optional condition including designation of a period is received. Idle software is determined from the installed software information, the using software information, and the optional input condition including period designation, an uninstalling instruction to the idle software is received, and an instruction for uninstalling the idle software is transmitted to the information processing device. <P>COPYRIGHT: (C)2006,JPO&NCIPI

Description

  The present invention relates to a software asset management method and system for managing idle software assets.

  Conventional software license management methods include a method of managing software with an installation license (installation is permitted within a range not exceeding the number of licenses held for each license) (see, for example, Patent Document 1). There is a method (for example, refer to Patent Document 2) for managing software of a contract execution license (which is permitted to be used simultaneously as long as the number of licenses does not exceed the number of licenses held).

  Patent Document 1 is a method for managing software of the above-described installation license contract method, and is actually installed on a computer in an organization and means for storing and managing the number of software licenses owned by a company, organization or group as a whole. Means for automatically collecting inventory information, including software, over the network, the number of software licenses held by the entire organization, and the number of software licenses actually used calculated based on the collected software inventory information To calculate the difference between software licenses, and to output the license usage status related to the excess or shortage of software licenses or the additional purchase information on the number of software licenses, enabling appropriate purchase of software licenses throughout the organization That.

  Patent Document 2 is a method for managing the software of the simultaneous execution license contract method. Since the license management server issues a license and distributes it to the user terminal via the network, the user has a plurality of user terminals. Even in such a case, the software can be used on a plurality of terminals without purchasing a license for each terminal.

JP 2001-222424 A JP 2003-84852 A

  The main purposes of software license management are as follows.

(1) Compliance with the number of software purchase licenses (2) Optimization of the number of software purchase licenses The present invention is an invention mainly related to the above (2) regarding software license management of the installation license contract method.

  The software management method of the installation license contract method generally compares the total number of software actually installed on the computer with the number of software licenses held, as disclosed in the prior art. By this method, it is possible to realize the purchase of an appropriate software license that does not cause illegal copying or excessive purchase.

  However, it is not possible to confirm the presence of software that has been installed and is not used, but is wasting software licenses and machine resources.

  Also, in the software management method of the concurrent execution license contract method, since the number of purchased licenses is set according to the number actually used, there is no waste in the purchased license, but like the above management method, machine resources, etc. It is not possible to confirm the existence of software that is installed but not used.

  In the software management method of the installation license contract method, if there is software that is installed but not used, and the number of installations exceeds the purchased license number due to new usage requests, etc. Must be purchased additionally, but a certain period of time is required to purchase a license, and during that time, even if you want to use the software, you cannot use it.

  Uninstalling software that is installed but not used solves the problem. However, software that is frequently used has high recognition, but software that is not used has low recognition. Since it is not even known that it is installed, it is left as it is without being uninstalled. Or, if you decide not to use it and uninstall it, software that you use frequently may stop working.

  The present invention has been made in view of the above circumstances, and detects software that has been installed but is not used, and provides a means for supporting the removal of software that has not been used. It is an object of the present invention to provide a software resource management method and system capable of eliminating and more effectively utilizing licenses or realizing appropriate purchase licenses.

  In the software asset management method of the present invention in which an asset management server and a plurality of information processing devices are connected via a network and the information of the plurality of information processing devices is managed by the asset management server, the installed software information is used from the plurality of information processing devices. Software information is collected, input of an arbitrary condition including a period designation is accepted, idle software is determined from the installed software information, used software information, and an arbitrary input condition including the period designation, and an instruction to uninstall the idle software And transmits an instruction to uninstall the idle software to the information processing apparatus.

  The present invention not only can easily detect software that is installed but not used, but also can efficiently eliminate software that is not used, optimize the number of software purchased licenses, and TCO (Total Cost of Ownership) can be reduced.

  In addition, flexible license operations such as uninstalling infrequently used software and allocating it to a new usage request within the scope of the owned license are possible, and the owned license can be used more effectively.

  Hereinafter, it demonstrates using drawing.

  FIG. 1 is a diagram showing a system configuration of a computer in the software resource management system. This software resource management system has an asset management server 100 and is connected to a plurality of asset agents 110 via a network. A terminal 120 for operation by an operator is connected to the asset management server 100. Further, databases 151, 152, 153, 154, 155, 156, 157, 158, and 159 are connected to the asset management server 100.

  Software to be managed by the software resource management system is a communication function for communicating with the asset management server 100, a storage function such as a memory, and an OA device such as a computer having a processing function such as a CPU (Central Processing Unit) ( Hereinafter, these are collectively referred to as “information processing apparatus”). An information processing apparatus in which software to be managed in this system is installed has a program called an asset agent incorporated therein.

  In this system, the asset management server determines whether the software is installed but not used based on the software information transmitted from the asset agent 110, the usage status of the software, etc., and selects the corresponding software. Can be uninstalled. This enables software resource management that matches the actual usage, detects software that is installed but not used, and prompts uninstallation to reduce unnecessary software licenses and hard disk resources, thereby helping to reduce costs. It is possible.

  In this example, “idle software” is software that is not used by software installed in the information processing apparatus.

  Next, the operation of the entire system will be described.

  In the system shown in FIG. 1, the asset management server 100 is a server that collects software information installed from the information processing apparatus and determines whether it is idle software. If it is determined as idle software, information for prompting uninstallation. Is a server that provides asset managers with

  Hereinafter, the asset management server 100 and the asset agent 110 will be described.

  The asset management server 100 is a server for managing information on information processing devices and software information installed on the information processing devices and determining whether the software is idle software. Information on information processing devices and installed software Asset information registration unit 101 for registering information in databases 151, 152, 153, 154, 155, 156, 157, 158, 159, idle software determination unit 102 for determining whether the software is idle software, and asset agent 110 And an instruction receiving unit 103 for processing an instruction to uninstall. The operation of each part will be described later.

  Further, in the asset management server 100, databases 151, 152, 153, 154, 155, 156, 157, 158 for registering information on information processing apparatuses, installed software, used software, and the like, and a database 159 for registering idle conditions, etc. Is connected. Each database stores the following information. Details of each database are shown in FIGS.

151: Hardware information 152: Network information 153: Installed software information 154: Software management information (corresponding to installation and purchased software)
155: Purchased software management information 156: Software asset management information 157: Software usage history information 158: Software management information (corresponding to installation and used software)
159: Idle software determination condition FIG. 2 shows the contents of the database 151. In this database, hardware information related to the information processing apparatus managed by the asset management server 100 is registered. In this database, device number 201, user 202, department 203, installation location 204, amount 205, product name 206, manufacturer 207, model name 208, CPU 209, memory 210, and HDD 211 are registered. The device number 201 is a number for specifying the information processing apparatus, and is unique on the asset management system. The HDD 211 is a hard disk drive.

  FIG. 3 shows the contents of the database 152. In this database, network information related to the information processing apparatus managed by the asset management server 100 is registered. In this database, a device number 301, a host name 302, an IP address 303, and a MAC address 304 are registered.

  FIG. 4 shows the contents of the database 153. In this database, software information installed in the information processing apparatus managed by the asset management server 100 is registered. In this database, a device number 401, an installed software ID 402, a product key 403, a CD key 404, a serial number 405, a status flag 406, and the number of uninstalls 407 are registered. The installed software ID 402 is an ID for specifying the installed software, and is unique on the asset management system. The status flag 406 represents the status of the installed software, and 0 (installed) and 1 (uninstalled) are registered. The number of uninstalls 407 is for monitoring the state in which the user has illegally installed the software. If the administrator has uninstalled the software that has been illegally installed, the number of uninstalls is uninstalled. It is highly possible.

  FIG. 5 shows the contents of the database 154. Information for associating installed software information with purchased software information is registered in this database. In this database, an installed software ID 501, an installed software name 502, a version 503, a GUID (Globally Unique IDentifier) 504, and a purchased software ID 505 are registered. The GUID 504 is a unique ID assigned to the installation software. The purchased software ID 505 is an ID for specifying the purchased software, and is unique on the asset management system, and is associated with a database 155 of FIG. 6 to be described later.

  FIG. 6 shows the contents of the database 155. Purchased software information is registered in this database. In this database, a purchased software ID 601, a purchased software name 602, and a manufacturer 603 are registered.

  FIG. 7 shows the contents of the database 156. In this database, software asset information purchased in the organization is registered. In this database, a purchased software ID 701, a department 702, the number of purchased licenses 703, an amount 704, and a purchase date 705 are registered.

  FIG. 8 shows the contents of the database 157. In this database, a history of software information actually used by the information processing apparatus managed by the asset management server 100 is registered. In this database, a device number 801, a use software ID 802, a use start time 803, a use end time 804, a memory usage 805, a page fault 806, an I / O count 807, and an acquisition date 808 are registered. The used software ID 802 is an ID for specifying the used software, and is unique on the asset management system. The I / O count 807 is the number of times the software has input / output to / from the file. All of this information is registered as a history. As a result, the administrator can know how much the software has been used in the past.

  FIG. 9 shows the contents of the database 158. In this database, information for associating used software information with installed software information is registered. In this database, used software ID 901, used software name 902, file name 903, file version 904, file size 905, file creation date 906, and installed software ID 907 are registered.

  FIG. 10 shows the contents of the database 159. In this database, idle conditions for determining that the software is idle software are registered. In this database, a condition name 1001, a usage time 1002, a memory usage amount 1003, a page fault 1004, and an I / O count 1005 are registered.

  Next, the operation of each unit of the asset management server 100 will be described.

  FIG. 11 shows the processing of the asset information registration unit 101.

  The asset information registration unit 101 collects hardware information (FIG. 2), network information (FIG. 3), installed software information (FIGS. 4 and 5), and used software information (FIG. 8) collected by using the asset agent. 9) is registered in the databases 151, 152, 153, 154, 157, 158.

  First, the asset management server transmits (1201) an information collection execution instruction to the asset agent. The message to be transmitted is shown in FIG. This message includes a flag, an IP address, a software name, a version, and a GUID. The flag represents an execution instruction, where 1 is information collection of both installed software information and used software information, 2 is collection of installed software information, 3 is collection of used software information, and 4 is uninstallation. The IP address is the IP address of the information processing apparatus to be executed. The software name, version, and GUID areas are used only when the flag is an uninstall instruction.

  The asset agent analyzes the received message (1202), and if the instruction is software information collection, extracts the software information (1203). On the other hand, if the analyzed message is instructed to be uninstalled, a process for uninstalling the corresponding software is executed. The uninstall process will be described later. After the asset agent extracts the software information, a list is created (1204). The list created here is shown in FIG. This list includes IP address of hardware information and network information, host name, MAC address, model name, CPU, memory, HDD, installed software name of installed software information, version, GUID, product key, CD key, serial number, It consists of the file name, version, size, creation date, use start time, use end time, memory usage, page fault, and I / O count of used software information. Since some software cannot obtain a GUID, the GUID may be empty. When the collection instruction does not collect the installed software information, the installed software name, version, GUID, product key, CD key, and serial number are empty. When the used software information is not collected, the file name, version, size, The creation date, use start time, use end time, memory usage, page fault, and I / O count are empty. This list has multiple records for the corresponding number, and the installed software information is sorted by installed software name and version, and the used software information is sorted in ascending order by file name, version, size, and creation date. It is. This list is empty when there is no data to acquire.

  The asset agent transmits the created list (hereinafter referred to as “list”) to the asset management server (1205).

  The asset management server receives the list of FIG. 18 from the asset agent (1206), and registers the hardware information and network information of the list as the initial update (1207).

  Next, the asset management server allocates a device number from the database 152 (FIG. 3) based on the IP address or host name of the received list, and extracts an existing list related to installed software information (1208). In the existing list of installed software information, the installed software name 502, version 503, installed software ID 501, and status flag 406 are extracted from the databases 153 (FIG. 4) and 154 (FIG. 5) based on the installed software ID 402 of the corresponding device number. Is. This existing list has a plurality of records corresponding to the number, and is sorted in ascending order by installed software name and version. Further, an existing list other than the corresponding information is not generated by the execution instruction transmitted from the asset management server to the asset agent. The existing list is empty when there is no data to acquire.

  The following processing is processing performed on the list related to installed software information. The process for the list regarding the used software information will be described later. Lists that have not been generated are not processed.

  Existing data is data extracted from an existing list, and list data is data extracted from a list. The data to be extracted is the installed software name and version. If there is no data to be acquired next in the existing list and list, there is no data in the existing data and list data, respectively.

  The comparison between the existing data and the list data is a size comparison. First, the installed software name of the existing data and the installed software name of the list data are compared. If the size determination is given, the size of existing data and list data is determined. If the installed software names are the same, the version of the existing data is compared with the version of the list data. If the size determination is given, the size of existing data and list data is determined. If the versions are also the same, it is the same installed software, and the size determination of the existing data and the list data is made = (same) determination.

  In processing 1209, the top data of the existing list is substituted into the existing data, and the top data in the list is substituted into the list data, and processing 1210 is executed.

  In process 1210, when there is no existing data and no list data (Y), the process of the asset information registration unit is terminated. Otherwise (N), processing 1211 is executed.

  In process 1211, if there is no existing data and there is list data (Y), process 1225 is executed. Otherwise (N), process 1212 is executed. Processing 1225-1227 is processing when there is list data, but this is not reflected in the existing data.

  In process 1212, if there is existing data and there is no list data (Y), process 1228 is executed. Otherwise (N), processing 1213 is executed. Processing 1228-1232 is processing when the list data is uninstalled, but this is not reflected in the existing data.

  In process 1213, the existing data and the list data are compared. When this size determination is “existing data = list data” determination (Y), processing 1214 is executed. Otherwise (N), process 1218 is executed. Processes 1218-1224 are processes in the middle of comparing list data with existing data.

  In the process 1214, if the status flag 406 of the record that is the installation software ID of the existing data with the corresponding device number is 0 (installed) (Y), the process 1215 is executed. Otherwise (N), processing 1217 is executed.

  In process 1215, corresponding software information is acquired from the list based on the list data, registered in the database, and process 1216 is executed. The product key 403, CD key 404, and serial number 405 in the database 153 are updated.

  In process 1216, the next data in the existing list is substituted into the existing data, and the next data in the list is substituted into the list data, and the process returns to process 1210.

  In process 1217, corresponding software information is acquired from the list based on the list data, registered in the database, and process 1216 is executed. The product key 403, CD key 404, and serial number 405 in the database 153 are updated. Since the status flag 406 is 1 (uninstalled), it is updated to 0 (installed).

  In process 1218, the existing data is compared with the list data. When this magnitude determination is “existing data <list data” (Y), processing 1219 is executed. Otherwise (N), process 1223 is executed. (Y) indicates that the data corresponding to the existing data is actually deleted from the list data, that is, uninstalled. Therefore, in the following process 1220, the number of uninstalls 407 is added.

  In the process 1219, if the status flag 406 of the record that is the installation software ID of the existing data with the corresponding device number is 0 (install) (Y), the process 1220 is executed. Otherwise (N), process 1222 is executed.

  In process 1220, the number of uninstalls 407 of the record that is the installed software ID of the existing data with the corresponding device number is acquired, 1 is added, and process 1221 is executed.

  In process 1221, the corresponding software information is acquired from the existing list based on the existing data, registered in the database, and process 1222 is executed. The status flag 406 of the database 153 is updated to 1 (uninstall), and the number of uninstalls 407 is updated to the value added in the process 1220.

  In process 1222, the next data in the existing list is substituted into the existing data, and the process returns to process 1210.

  In process 1223, corresponding software information is acquired from the list based on the list data, registered in the database, and process 1224 is executed. A status flag 406 of 0 (installed) is added to the database 153. That is, since new software information that is not present in the existing data is stored in the list data, this new software information is registered in step 1223.

  In process 1224, the next data in the list is substituted into the list data, and the process returns to process 1210.

  In process 1225, if there is no list data (N), the process returns to process 1210. On the other hand, if there is list data (Y), processing 1226 is executed.

  In process 1226, corresponding software information is acquired from the list based on the list data, registered in the database, and process 1227 is executed. A status flag 406 of 0 (installed) is added to the database 153.

  In process 1227, the next data in the list is substituted into the list data, and the process returns to process 1225. That is, this process is repeated until there is no list data.

  In process 1228, if there is no existing data (N), the process returns to process 1210. On the other hand, if there is existing data (Y), processing 1229 is executed.

  In process 1229, if the status flag 406 of the record that is the installation software ID of the existing data with the corresponding device number is 0 (installed) (Y), process 1230 is executed. Otherwise (N), processing 1232 is executed.

  In the process 1230, the number of uninstalls 407 of the record that is the installed software ID of the existing data with the corresponding device number is acquired, 1 is added, and the process 1231 is executed. By this processing, the software that has been uninstalled is reflected in the existing data in the list data.

  In process 1231, the corresponding software information is acquired from the existing list based on the existing data, registered in the database, and process 1232 is executed. The status flag 406 of the database 153 is updated to 1 (uninstalled), and the number of uninstalls 407 is updated to the value added in the process 1230.

  In process 1232, the next data in the existing list is substituted into the existing data, and the process returns to process 1228. That is, this process is repeated until there is no existing data.

  The above processing is repeated until there is no target data, and the installed software information is registered.

  Regarding registration of used software information, all used software information in the list is added to the database 157.

  FIG. 12 shows the processing of the idle software determination unit 102.

  The idle software determination unit 102 displays an idle software search condition input screen (FIG. 13), and searches for idle software under an arbitrary condition including a period designation input by the asset manager. Here, if it is below the specified condition, it is determined as idle software. After the search, a list (FIG. 14) of information processing apparatuses in which idle software is installed is displayed. Further, when uninstalling idle software, the asset manager can select and determine an uninstall target from the search result, so that the idle software determination unit 102 can issue an uninstall instruction to the instruction receiving unit 103.

  First, the idle software determination unit 102 displays a search condition input screen (FIG. 13) (1301). Here, the operator inputs a search condition using the terminal 120 connected to the asset management server and presses the search button. The input of the search condition is accepted and processing 1302 is executed.

  In process 1302, if no period is specified in the search condition (N), the process returns to process 1301. On the other hand, if there is a period designation (Y), the period condition is added to the search condition (1303), and the process 1304 is executed.

  In process 1304, if there is no department designation in the search condition (N), process 1306 is executed. On the other hand, if there is a department designation (Y), the department condition is added to the search condition (1305), and processing 1306 is executed.

  In process 1306, if the software name is not specified in the search condition (N), process 1308 is executed. On the other hand, if there is a software name designation (Y), the software name condition is added to the search condition (1307), and the process 1308 is executed.

  In process 1308, when the idle condition is read from the idle condition list (Y), the idle condition selected from the list is added to the search condition (1317), and the process 1318 is executed. On the other hand, when the idle condition is not read from the list (N), processing 1309 is executed.

  In process 1309, if the use time is not specified in the search condition (N), process 1311 is executed. On the other hand, if there is a usage time designation (Y), the usage time is added to the search condition (1310), and processing 1311 is executed.

  In process 1311, if there is no memory usage designation in the search condition (N), process 1313 is executed. On the other hand, if the memory usage is specified (Y), the memory usage is added to the search condition (1312), and the process 1313 is executed.

  In process 1313, if there is no page fault designation in the search condition (N), process 1315 is executed. On the other hand, if there is a page fault designation (Y), the page fault is added to the search condition (1314), and processing 1315 is executed.

  In process 1315, if the I / O count is not specified in the search condition (N), process 1318 is executed. On the other hand, if there is an I / O count designation (Y), the I / O count is added to the search condition (1316) and processing 1318 is executed.

  By examining the memory usage, page fault, and I / O count added in the above process, it is distinguished whether the software was just loaded into memory, or loaded into memory and actually executed (used) be able to.

  The search is executed within the range of the specified condition including the period specification or less (1318), the result is obtained (1318), the search result is displayed on the screen (FIG. 14) (1319), and the process 1320 is executed. At that time, based on the usage history of the database 157 of FIG. 8, the total usage time within the period specified by the condition is checked.

  In process 1320, when the operator selects software to be uninstalled from the search result list and presses the uninstall button (Y), an uninstall instruction is transmitted to the asset agent (1321), and process 1322 is executed. The message to be transmitted is shown in FIG. The asset agent analyzes the received message, and if it is an uninstall instruction, executes processing for uninstalling the corresponding software. The uninstall process will be described later. On the other hand, when the process 1320 does not uninstall (N), the process 1322 is executed.

  In process 1322, in order to save the idle condition of the search result, when the save condition button is pressed (Y), the idle condition is registered in the database 159 (1323), and the process of the idle determination unit is terminated. On the other hand, when the idle condition is not saved (N), the process of the idle determination unit is terminated.

  If you want to save the search conditions used at the time of the search as a history, press the Save Condition button in FIG. 13 to save the usage time, memory usage, page fault, and I / O condition values in the database 159. can do.

  The idle software search method uses software usage time, memory usage, page fault and I / O as idle conditions (FIG. 13) and displays a list (FIG. 14). For example, display as shown in FIGS. 15 and 16 is also possible.

  FIG. 15 is a diagram showing the number of unused software (number of installed licenses with no usage time) by expanding the normal number of licenses. You can display a list of installed devices based on the number of unused devices and correct idle software.

  FIG. 16 is a diagram showing that the software whose usage time is less than or equal to a certain value is determined to be idle and displayed by a counting method based only on the software usage time. It is possible to correct the device list determined to be idle software.

  Further, by adding the uninstall count 407 of the database 153 to the output items of the idle software list, it becomes a judgment material when selecting the uninstall instruction.

  Next, the asset agent 110 will be described.

  The asset agent 110 is an agent for monitoring the installed software information and used software information of the information processing device and transmitting the asset information to the asset management server 100, and the installed software for monitoring the installed software information of the information processing device. An information monitoring unit 111, a used software information monitoring unit 112 for monitoring used software information of the information processing apparatus, an information communication unit 113 for transmitting / receiving information to / from the asset management server 100, and an uninstall processing unit 114 for uninstalling And have. The installed software information monitoring unit 111 and the used software information monitoring unit 112 can be realized by using existing technology, and thus description thereof is omitted.

  FIG. 20 shows processing of the uninstall processing unit 114.

  The uninstall processing unit 114 analyzes the message (FIG. 19) transmitted from the asset management server, and performs processing only when the flag is an uninstall instruction.

  First, the uninstall processing unit extracts the software name, version, and GUID from the uninstall instruction message received from the server (2002), and executes the process 2003.

  In process 2003, if there is a GUID (Y), process 2004 is executed. On the other hand, when there is no GUID (N), processing 2005 is executed.

  In a process 2005, using the extracted software name and version, a matching item is searched in the registry, an uninstall execution path of the corresponding item is extracted, and a process 2004 is executed.

  In process 2004, the generated uninstall execution path is executed, and process 2006 is executed.

  In process 2006, the end status of the uninstall process is transmitted to the asset management server.

  As described above, the corresponding software is uninstalled.

It is the figure which showed the structure of the software resource management system. It is the figure which showed the contents of the database of hardware information. It is the figure which showed the content of the database of network information. It is the figure which showed the contents of the database of installed software information. It is the figure which showed the content of the database of software management information (correspondence of installation, purchase software). It is the figure which showed the contents of the database of purchased software management information. It is the figure which showed the contents of the database of software asset management information. It is the figure which showed the content of the database of software use history information. It is the figure which showed the content of the database of software management information (correspondence of installation and use software). It is the figure which showed the content of the database of idle software determination conditions. It is the figure which showed the process of the asset information collection part. It is the figure which showed the process of the idle determination part. It is the figure which showed the screen which sets idle software search conditions. It is the figure which showed the screen of the list list of idle software candidates. It is the figure which showed the screen of the list list of a license number total result. It is the figure which showed the screen of the list list of idle software candidates by use time. It is the figure which showed the information transmitted / received by a communication part. It is the figure which showed the information transmitted / received by a communication part. It is the figure which showed the information transmitted / received by a communication part. It is the figure which showed the process of the uninstallation process part.

Explanation of symbols

100: Asset management server 110: Asset agent 120: Terminal

Claims (5)

In a software asset management system in which an asset management server and at least one information processing device are connected by a network, and the asset management server manages software information of the information processing device,
The resource management server
An asset information registration unit for registering installed software information and used software information sent from the information processing apparatus;
An idle software determination unit for determining idle software from the installed software information and used software information;
An instruction receiving unit that transmits an instruction for uninstalling the idle software;
The information processing apparatus includes:
An installed software information monitoring unit for monitoring software installed in the information processing apparatus;
A used software information monitoring unit for monitoring software used in the information processing apparatus;
A software asset management system comprising: an uninstallation processing unit that uninstalls installation software of the information processing apparatus. A software asset management method in which an asset management server and at least one information processing device are connected via a network, and the asset management server manages software information of the information processing device,
Collect installed software information and used software information from the information processing device,
Accept input of predetermined conditions including period specification,
Determine idle software from predetermined input conditions including the installed software information, used software information, and the period designation,
Receiving an uninstall instruction for the idle software;
A software asset management method comprising transmitting an instruction for uninstalling idle software to the information processing apparatus. A software asset management method in which an asset management server and at least one information processing device are connected via a network, and the asset management server manages software information of the information processing device,
Receiving a software information collection instruction from the asset management server;
Information of software installed in the information processing apparatus and information of software used in the information processing apparatus are transmitted to the asset management server;
Receiving an instruction to uninstall idle software from the asset management server;
A software asset management method comprising: uninstalling installation software of the information processing apparatus based on the instruction.   The asset management server uses at least one of the use start time, use end time, memory usage, page fault, and I / O count of the collected software information to determine that it is idle software if it is less than a specified condition. The software asset management system according to claim 1, wherein:   The software information management system according to claim 1, wherein the information processing apparatus receives an uninstall instruction from the resource management server and uninstalls software installed in the information processing apparatus.

Images