JP2016157323A - Management program, management method, and management device - Google Patents

Abstract

PROBLEM TO BE SOLVED: To provide a management program, a management method, and a management device which automate update of an environmental condition of checking a terminal.SOLUTION: A cloud server 100 transmits a precondition of terminals 3a-3d and 3m for executing specific software, managed by a precondition table 156, to each of the terminals, receives the result of inconsistency from a terminal determined not to satisfy the precondition through a communication interface, stores the result in an inconsistency information result table 159, changes the precondition regarding a condition which satisfies a reference value among conditions which have determined to be inconsistent in the terminals managed by the inconsistency information result table 159, updates the precondition table 156, and transmits an acquired new precondition to each terminal through the communication interface.SELECTED DRAWING: Figure 10

Description

  The present invention relates to a management program, a management method, and a management apparatus.

  2. Description of the Related Art In recent years, various efforts have been made to maintain the security of each terminal related to a business in a computer network so as not to hinder business operations.

  For example, the server receives information such as the setting environment collected by self-inspection by the terminal, the technology that checks the IT (Information Technology) usage environment, and the work result that indicates the change of the network environment for synchronization by the terminal. A technique for reporting, a technique in which a server transmits a check list to a terminal, and the like are known.

JP 2008-304968 A JP-T-2007-520760 JP 2006-318244 A

  However, in each terminal, the OS and various software are automatically updated individually, and the update timing is different for each terminal. Moreover, even if the terminal performs the same business, the terminal environment is different for each terminal.

  In the above-described conventional technology, there is no mechanism for automatically changing the environmental conditions for checking the environment of each terminal, so an administrator with knowledge must perform update work based on the results of investigating changes in the terminal environment . It is a very burdensome task for an administrator to grasp the differences and changes in the terminal environment of each terminal in a timely manner and update the environmental conditions of the terminal.

  Accordingly, in one aspect, the present invention is directed to automating the updating of environmental conditions for checking a terminal.

  According to one aspect, an environmental condition of a terminal for executing specific software is transmitted to a plurality of computers, and a report on the environment is received via a communication interface from a computer that is determined not to satisfy at least the environmental condition. If the result of the report on the environment from the computer that does not satisfy the environmental condition satisfies the condition for reviewing the environmental condition based on the received report, the environment is determined based on the received report on the environment. There is provided a management program characterized in that a new environmental condition obtained by changing a condition is transmitted to the plurality of computers via the communication interface, causing the computer to perform processing.

  In addition, as a means for solving the above-described problems, a management method and a management apparatus can be used.

  Automatic update of environmental conditions for checking terminals.

It is a figure explaining the example of basic operation in a present Example. It is a figure which shows the hardware constitutions of a cloud server. It is a figure which shows the function structural example of a cloud server. It is a figure which shows the function structural example of a terminal. It is a figure which shows the process sequence of basic operation | movement. It is a figure which shows the example of a table structure regarding the basic operation process in a cloud server. It is a figure explaining a precondition check process. It is a figure which shows the processing sequence of a precondition check. It is a figure which shows the example of a table structure regarding the precondition check process in a cloud server. It is a figure which shows the mechanism in which a precondition check result is made known. It is a flowchart figure for demonstrating the provision process of the collection result report 9 by a precondition check process part. It is a figure which shows the example of a description of a prerequisite file. It is a figure for demonstrating the example by which a mismatch check result is reported to a cloud server. It is a figure which shows the example of a description of a precondition check result. It is a figure which shows the example of a display of the result of a precondition check. It is a figure which shows the processing sequence of precondition review. It is a figure which shows the example of a table structure regarding the precondition review process in a cloud server. It is a flowchart figure for demonstrating the automatic update process by a precondition review process part. It is a figure which shows the example of a description of the updated precondition file. It is a figure for demonstrating the example in which the newest prerequisite file is provided. It is a figure which shows the example of a display of the collection result report after an update.

  Hereinafter, embodiments of the present invention will be described with reference to the drawings. FIG. 1 is a diagram for explaining an example of basic operation in the present embodiment. In the security system 1000 shown in FIG. 1, the cloud server 100 is connected to each terminal 3m, 3a, 3b, etc. serving as end points via the Internet or the like. Hereinafter, the terminals 3m, 3a, 3b, etc. may be collectively referred to as the terminal 3. In the example illustrated in FIG. 1, 3 a, 3 b, and the like are collectively referred to as a terminal 3, but a plurality of terminals 3 may include the terminal 3 m.

  The cloud server 100 is a server that manages the terminals 3 having various terminal environments 5 based on a policy 4p that defines the settings of each terminal 3 so that the A system, the B service, and the like are securely operated. The cloud server 100 includes a storage unit 130a that stores various data related to the implementation of the policy 4p.

  The policy 4p is a rule relating to information processing established in a company so that proper operation is performed in any of various operations using a computer system. For example, in the policy 4p, various rules regarding information processing are defined for each type such as security, ecology, asset control, and system operation.

  The security includes, for example, making it mandatory to set a password for the terminal 3, specifying an application that is prohibited from being installed, an application that cannot be started during the work, and the like in order to securely execute the work.

  Eco includes control of power supply, control for limiting paper printing, and the like. Asset control includes management of software inventory, licenses, and the like. System operation includes remote distribution of correction patches.

  In the present embodiment, the cloud server 100 will be described as an example of a server, but is not limited to a cloud server.

  In the example shown in FIG. 1, an outline of a basic operation for implementing the policy 4p is shown. In FIG. 1, a terminal 3a is a terminal on which a Windows (registered trademark) agent is installed, and a terminal 3b is a terminal on which an Android (registered trademark) agent is installed, and operations are performed in different terminal environments 5.

  It is assumed that user A performs a business using the A system on the terminal 3a, and user B performs a business using the B service on the terminal 3b. Performing business by the A system on the terminal 3a means that the business application for the A system is operated on the terminal 3a. Similarly, performing the business by the B service on the terminal 3b means operating the business application for the B service on the terminal 3b.

  The terminal 3m is a terminal used by the system administrator M. The terminal 3m can access the cloud server 100, and the policy file 4 and the like determined by the system administrator M based on the policy 4p are stored in the cloud server 100 so that the users A, B, etc. store.

  Specifically, first, the system administrator M creates a policy file 4 that defines the terminal environment 5 for each job based on the policy 4p so that each job can be performed securely at the terminal 3m. The policy file 4 is a data file and is stored in the storage unit 130a of the cloud server 100. When the system manager M instructs the cloud server 100 to distribute a policy from the terminal 3m, the policy 4p corresponding to the business is distributed to each terminal 3.

  In this embodiment, when each terminal 3 receives the policy 4p, each terminal 3 performs a security check that automatically checks whether the terminal environment 5 of the terminal 3 complies with the policy 4p, and a security check result indicating the result. 6 is returned to the cloud server 100.

  The terminal 3a using the A system performs a security check in response to the reception of the policy file 4a, and returns a security check result 6a indicating the result to the cloud server 100. The terminal 3b using the B service performs a security check in response to the reception of the policy file 4b, and returns a security check result 6b indicating the result to the cloud server 100.

  The cloud server 100 creates a collection result report 9 obtained by counting the security check results 6 collected from each terminal 3. The system administrator M can refer to the collection result report 9 created by the cloud server 100 with the terminal 3m.

  FIG. 2 is a diagram illustrating a hardware configuration of the cloud server. In FIG. 2, a cloud server 100 is an information processing device controlled by a computer, and includes a CPU (Central Processing Unit) 11a, a main storage device 12a, an auxiliary storage device 13a, an input device 14a, and a display device 15a. And a communication I / F (interface) 17a and a drive device 18a, which are connected to the bus B1.

  The CPU 11a corresponds to a control unit that controls the cloud server 100 according to a program stored in the main storage device 12a. A RAM (Random Access Memory), a ROM (Read Only Memory), or the like is used as the main storage device 12a. The program is executed by the CPU 11a, the data necessary for processing by the CPU 11a, and is obtained by processing by the CPU 11a. Store or temporarily store the data.

  The auxiliary storage device 13a uses an HDD (Hard Disk Drive) or the like, and stores data such as programs for executing various processes. A part of the program stored in the auxiliary storage device 13a is loaded into the main storage device 12a and executed by the CPU 11a, thereby realizing various processes.

  The input device 14 a has a mouse, a keyboard, and the like, and is used by a server administrator such as the system administrator M to input various information necessary for processing by the cloud server 100. The display device 15a displays various information necessary under the control of the CPU 11a. When the server administrator connects a server administrator terminal (for example, terminal 3m) to the cloud server 100 by communication and inputs and displays information, the input device 14a and the display device 15a are omitted. Is possible.

  The communication I / F 17a performs communication through a wired or wireless network. Communication by the communication I / F 17a is not limited to wireless or wired communication.

  A program for realizing the processing performed by the cloud server 100 is provided to the cloud server 100 by a storage medium 19a such as a CD-ROM (Compact Disc Read-Only Memory).

  The drive device 18a performs an interface between the cloud server 100 and a storage medium 19a (for example, a CD-ROM) set in the drive device 18a.

  In addition, the storage medium 19a stores a program that realizes various processes according to the present embodiment, which will be described later, and the program stored in the storage medium 19a is installed in the cloud server 100 via the drive device 18a. The The installed program can be executed by the cloud server 100.

  The storage medium 19a for storing the program is not limited to a CD-ROM, and one or more non-transitory tangible media having a structure that can be read by a computer. If it is. As a computer-readable storage medium, in addition to a CD-ROM, a portable recording medium such as a DVD disk or a USB memory, or a semiconductor memory such as a flash memory may be used.

  Since the hardware of the terminal 3 has the same configuration as described above, the description thereof is omitted. In order to facilitate the distinction between the cloud server 100 and the terminal 3, in the case of the terminal 3, an alphabetic subscript is distinguished by “b”.

  FIG. 3 is a diagram illustrating a functional configuration example of the cloud server. In FIG. 3, the cloud server 100 includes a basic operation processing unit 141, a precondition check processing unit 142, and a precondition review processing unit 143. The processing units 141 to 143 are realized by the CPU 11a executing a corresponding program.

  In addition, the cloud server 100 stores the terminal basic information table 151, the policy management table 152, the security check result table 153, the OS (Operating System) information table 154, the software information table 155, the precondition table 156, and the preconditions in the storage unit 130a. A check result table 157, a precondition check result history table 158, a mismatch information result table 159, and the like.

  The basic operation processing unit 141 is a processing unit that performs the basic operation as described with reference to FIG. 1, and transmits a policy file 4 corresponding to a job performed by the terminal 3 to each terminal 3 via the communication I / F 17a. And collect and manage security check results 6.

  The precondition check processing unit 142 is a processing unit that checks whether or not each terminal 3 satisfies the preconditions of software for operating the system and the service. The precondition corresponds to the environmental condition of the terminal 3 for executing specific software. The precondition check processing unit 142 transmits the precondition file 7 in which the precondition is described to each terminal 3 via the communication I / F 17a, and displays the precondition check result 8 indicating the result checked by each terminal 3. collect.

  The precondition check processing unit 142 can obtain the result of confirming the precondition for each piece of business software from each terminal 3. In this case, the collection result report 9 includes a result of collecting the precondition check result 8. For example, a situation in which software that does not satisfy the precondition is operating is indicated by statistical information, a graph, or the like.

  The system administrator M can grasp the existence of the terminal 3 having software that does not satisfy the preconditions in each business without operating the individual terminals 3.

  The precondition review processing unit 143 is a processing unit that reviews a condition that does not match the precondition in the terminal 3 after a predetermined period and automatically updates the precondition file 7. In the case of software that is automatically updated by each terminal 3 such as a browser version, the updated software may operate on the terminal 3 before verification by the system administrator M or the like in each business application.

  If there is no problem with the updated software for a certain period, it is determined that it can be considered as a precondition, and a new version is added to the precondition file 7 and updated. The precondition review processing unit 143 can reduce the burden required for verification by the system administrator M or the like.

  The terminal basic information table 151 is a table for managing basic information of each terminal 3. The policy management table 152 is a table for managing information of each policy file 4. The security check result table 153 is a table for managing the security check result performed according to the contents of the policy file 4 for each terminal 3.

  The OS information table 154 is a table for managing OS information of the terminal 3. The software information table 155 is a table for managing software information for each terminal 3.

  The precondition table 156 is a table for managing information of each precondition file 7. The prerequisite check result table 157 is a table for managing the latest prerequisite check result 8. The prerequisite check result history table 158 is a table for managing past prerequisite check results 8.

  The mismatch information result table 159 is a table for managing the conditions of the terminal 3 that are not defined by the precondition file 7. Information (mismatch information) indicating the condition of the terminal 3 that does not match (not match) any of a tag <support> and a tag <not_support> as will be described later is held for a predetermined period. The predetermined period is, for example, two weeks.

  Next, the functional configuration of the terminal 3 will be described with reference to FIG. FIG. 4 is a diagram illustrating a functional configuration example of the terminal. In FIG. 4, the terminal 3 includes a security check unit 61, a precondition check unit 62, and a post-review check unit 63. Each of the security check unit 61, the precondition check unit 62, and the post-review check unit 63 is realized by the CPU 11a executing a corresponding program.

  When the security check unit 61 receives the policy file 4 from the cloud server 100, the security check unit 61 stores the policy version 4v of the policy file 4 in the storage unit 130b so that its own terminal 3 conforms to each security item indicated by the policy file 4. Judge whether or not. For each security item, the security check unit 61 creates a security check result 6 in which OK is set if it is compliant, and NG is set if it is not compliant, and transmits the result to the cloud server 100.

  When the prerequisite check unit 62 receives the prerequisite file 7 from the cloud server 100, the prerequisite check unit 62 stores the prerequisite version 7 v of the prerequisite file 7 in the storage unit 130 b, and executes the prerequisite on the software in its own terminal 3. It is verified whether any of the conditions indicated in the file 7 is met.

  The precondition file 7 indicates at least one condition supported by at least the business application for each diagnosis item. Furthermore, conditions that are not supported by the business application may be indicated. The diagnosis item specifies software or middleware. In the present embodiment, the diagnosis item is described as software, but it is assumed that middleware is included.

  For each diagnostic item specified in the precondition file 7, the precondition check unit 62 sets the matched condition when the supported condition matches, and sets the condition of the terminal 3 when no matching condition exists. The indicated precondition check result 8 is created and transmitted to the cloud server 100 via the communication I / F 17b. Even if it matches an unsupported condition, the matched condition is indicated by the precondition check result 8 in the same way as when it matches the supported condition.

  The cloud server 100 can manage each current terminal environment 5 by collecting the precondition check result 8 from each terminal 3.

  The post-review checking unit 63 acquires the precondition file 7 of the new precondition version 7v from the cloud server 100 and performs a precondition check. For example, the software of the terminal 3 may update the version automatically. In such a case, the latest version is added to the preconditions after a certain period of time. In this case, the terminal 3 can confirm that the software of the terminal 3 for which it was unknown whether the software is supported is supported.

  First, regarding the basic operation shown in FIG. 1, a processing sequence of the basic operation and a table configuration example will be described. The basic operation is performed by the security check unit 61 of the terminal 3 and the basic operation process 141 of the cloud server 100.

  FIG. 5 is a diagram showing a processing sequence of basic operations. In FIG. 5, when the terminal 3 periodically executes the agent at a predetermined frequency, a basic operation described below is started between the terminal 3 and the cloud server 100. The predetermined frequency may be, for example, once every 3 hours.

  The security check unit 61 of the terminal 3 acquires the policy version 4v from the storage unit 130b and notifies the cloud server 100 of it (step S311). Information including the policy version 4v and the device management ID of the terminal 3 is transmitted to the cloud server 100 via the communication I / F 17b. The device management ID is identification information uniquely given to the terminal 3 in advance in the security system 100.

  In the cloud server 100, when the policy version 4v is received from the terminal 3, the basic operation processing unit 141 determines whether or not it matches the latest policy version in the cloud server 100 (step S111).

  The basic operation processing unit 141 refers to the terminal basic information table 151 and the policy management table 152 stored in the storage unit 130a, and based on the policy ID associated with the device management ID of the terminal 3, the terminal 3 Get policy version for security check with. The acquired policy version corresponds to the latest policy version.

  If it matches the latest policy version, the basic operation processing unit 141 notifies the terminal 3 that it is the latest policy version via the communication I / F 17a (step S112). When the notification that the policy version is the latest policy version is received from the cloud server 100 (step S312), the security check unit 61 of the terminal 3 ends the security check process.

  On the other hand, when the cloud server 100 determines that the policy version received from the terminal 3 does not match the latest policy version in the cloud server 100, the basic operation processing unit 141 transmits the policy file 4 of the latest policy version to the terminal 3. (Step S113). Then, the basic operation processing by the basic operation processing unit 141 ends.

  In the terminal 3, when the security check unit 61 receives the policy file 4 via the communication I / F 17b (step S313), the security check unit 61 performs a security check according to the contents of the policy file 4 (step S314). The security check unit 61 uploads the security check result 6 to the cloud server 100 via the communication I / F 17b (step S315). And the security check process by the security check part 61 of the terminal 3 is complete | finished.

  The basic operation processing unit 141 of the cloud server 100 stores the security check result 6 received from the terminal 3 in the security check result table 153 (step S114). Then, the basic operation processing by the basic operation processing unit 141 ends.

  The security check result table 153 may store the latest security check result 6 of the terminal 3, and the security check result 6 received in the past may be stored as a history in a separately prepared security check result history table. .

  FIG. 6 is a diagram illustrating a table configuration example regarding basic operation processing in the cloud server. In FIG. 6, the terminal basic information table 151 is a table in which basic information is associated with each terminal 3, and includes items such as a device management ID, a device management number, a policy ID, a device user ID, and a terminal deletion flag.

  The device management ID indicates identification information for uniquely identifying each terminal 3. The device management ID associates the terminal basic information table 151 with each of the security check result table 153, the OS information table 154, and the software information table 155.

  The device management number indicates the management number of the basic information of the terminal 3. The policy ID indicates the ID of a policy applied to the terminal 3. The terminal basic information table 151 and the policy management table 152 are associated with each other by the policy ID.

  The device user ID indicates the ID of the user of the terminal 3. The terminal deletion flag indicates that the terminal 3 has been excluded from the security system 1000.

  The policy management table 152 is a table for managing the policy file 4 and includes items such as policy ID, policy name, policy version, and policy type.

  The policy ID indicates identification information of the policy file 4, and the policy name indicates the file name of the policy file 4. The policy version indicates the policy version of the policy ID. The policy type indicates the type of policy such as security, ecology, asset control, and system operation.

  Since the policy file 4 may be stored in the storage unit 130a, the policy management table 152 does not store the policy file 4 but identifies the policy file 4 by the policy ID. The policy file 4 includes rules regarding security setting information, middleware setting information, and the like.

  The security check result table 153 is a table in which the security check result 6 is associated with each terminal 3, and includes items such as a device management ID, OSID, category ID, item ID, and check result.

  The device management ID indicates a device management ID registered in the terminal basic information table 151. The OSID indicates OS identification information in the security system 1000. The category ID indicates category identification information. The item ID indicates identification information of the category item. The check result indicates the result of the security check for the item. Based on the security check result 6 received from the terminal 3, the result for each item is shown.

  The OS information table 154 is a table in which OS information is associated with each terminal 3 and includes a device management ID, an OSID, an OS type, an OS name, a computer name, and the like.

  The device management ID indicates a device management ID registered in the terminal basic information table 151. The OSID indicates OS identification information in the security system 1000. The OS type indicates the type of OS such as Windows (registered trademark) or Android (registered trademark). The OS name indicates an OS name such as Windows XP (registered trademark) or Windows 7 (registered trademark). The computer name indicates the computer name of the terminal 3.

  The software information table 155 is a table in which software information is associated with each terminal 3 and includes a device management ID, an OS type, a software ID, a software name, version information, and the like.

  The device management ID indicates a device management ID registered in the terminal basic information table 151. The OS type indicates the type of OS such as Windows (registered trademark) or Android (registered trademark). The software ID indicates identification information of software used for business. The software name indicates the name of software used for business. The version information indicates version information of software used for business.

  FIG. 7 is a diagram for explaining the precondition check process. In FIG. 7, the cloud server 100 distributes the policy file of the A system to the terminal 3a in the environment where the A system is introduced via the communication I / F 17a (step S1-1), and the B service is introduced. The policy file for the B service is distributed to the terminal 3b in the environment (step S1-2).

  Each of the terminal 3a and the terminal 3b automatically performs a precondition check (step S2), and automatically transmits the precondition check result 8 to the cloud server 100 via the communication I / F 17b (step S3).

  The cloud server 100 updates the mismatch information result table 159 using the precondition check result 8 collected from the terminals 3a and 3b (step S4).

  FIG. 8 is a diagram showing a processing sequence of the precondition check. In FIG. 8, when the terminal 3 periodically executes the agent at a predetermined frequency, a precondition check described below is started between the terminal 3 and the cloud server 100. The predetermined frequency may be, for example, once every 3 hours.

  The prerequisite check unit 62 of the terminal 3 uploads the software information 9f of the terminal 3 to the cloud server 100 (Step S321). Information including the software information 9f and the device management ID of the terminal 3 is transmitted to the cloud server 100 via the communication I / F 17b.

  The software information 9f includes software ID and is information indicating software installed in the terminal 3.

  In the cloud server 100, when the software information 9f is received from the terminal 3 via the communication I / F 17a, the precondition check processing unit 142 adds the received software information 9f to the software information table 155 (step S121).

  The prerequisite check processing unit 142 determines whether or not the software ID indicated by the received software information 9f exists in the software ID defined in the prerequisite table 156 (step S122).

  If it exists, the precondition check processing unit 142 transfers the precondition file 7 to the terminal 3 via the communication I / F 17a (step S123). The precondition file 7 transferred to the terminal 3 is a file in which preconditions corresponding to business applications (A system, B service, etc.) operating on the terminal 3 are defined.

  When the terminal 3 receives the precondition file 7 via the communication I / F 17b (step S322), the precondition check unit 62 automatically relates to the software of the terminal 3 according to the contents of the received precondition file 7. A precondition check is performed (step S323). The prerequisite check unit 62 uploads the prerequisite check result 8 to the cloud server 100 via the communication I / F 17b (step S324). Then, the precondition check process by the precondition check unit 62 of the terminal 3 ends.

  When the precondition check processing unit 142 of the cloud server 100 receives the precondition check result 8 from the terminal 3, the check result stored in the precondition check result table 157 is stored in the precondition check result history table 158 (step S124) The received precondition check result 8 is stored in the precondition result table 157 (step S125).

  In addition, the precondition check processing unit 142 stores the mismatch result from the received precondition check result 8 in the mismatch information result table 159, and the precondition check process by the precondition check processing unit 142 ends.

  FIG. 9 is a diagram illustrating a table configuration example related to the precondition check process in the cloud server. In FIG. 9, tables related to the precondition check process are a terminal basic information table 151, a policy management table 152, a software information table 155, a precondition table 156, and a precondition check result table 157. Here, only the precondition table 156 and the precondition check result table 157 that are not described in FIG. 6 will be described.

  The precondition table 156 is a table for managing information related to each precondition file 7, and includes items such as a precondition ID, a precondition name, a precondition version, and a software ID.

  The precondition ID indicates identification information of the precondition file 7. The precondition name indicates the name of the precondition defined by the precondition file 7. The precondition version indicates a precondition version defined by the precondition file 7. As the version of the precondition, the version of the precondition file 7 may be used. The software ID indicates identification information of software used for business.

  Since the entity of the prerequisite file 7 may be held in the storage unit 130a, the policy management table 152 does not hold the entity of the prerequisite file 7, but identifies the prerequisite file 7 by the prerequisite ID. The precondition file 7 includes rules regarding the contents of the system setting file, middleware setting information, and the like.

  A mechanism for making the related information of the precondition check result 8 collected from each terminal 3 by the cloud server 100 known will be described with reference to FIG. FIG. 10 is a diagram showing a mechanism for disseminating the precondition check result.

  In FIG. 10, when the cloud server 100 collects the precondition check result 8 from each terminal 3, the precondition check processing unit 142 creates a collection result report 9 including the software status of each terminal 3 in the security system 1000. Then, the collection result report 9 is sent to the help desk D and the system administrator M (step S6-1). The help desk D and the system administrator M may be notified that the collection result report 9 is accessible, and the cloud server 100 may be accessed by itself to display the collection result report 9 on the respective terminals 3d and 3m. The help desk D confirms the collection result report 9 displayed on the terminal 3d. The system administrator M confirms the collection result report 9 displayed on the terminal 3m.

  Also, the precondition check processing unit 142 creates a diagnostic result 81 indicating a state of the terminal 3 with respect to the software precondition based on the precondition check result 8 for the terminal 3 that has transmitted the precondition check result 8. To the user (step S5-2).

  For example, the user A can know the state with respect to the preconditions for each software related to the A system of his / her terminal 3a by checking the diagnosis result 81 displayed on the terminal 3a. Similarly, the user B can know the state with respect to the preconditions for each software related to the B service of the terminal 3b by checking the diagnosis result 81 displayed on the terminal 3b.

  User A does not need to recognize whether or not his terminal 3a is a Windows (registered trademark) agent. Also, the user B does not need to recognize whether or not the terminal 3a of the user B is an Android (registered trademark) agent.

  On the other hand, in the cloud server 100, the precondition review processing unit 143 periodically checks the mismatch information result table 159 (step S6), and the terminal 3 managed by the mismatch information result table 159 has found a mismatch. The precondition table 156 is updated with respect to the condition that satisfies the reference value among the conditions (step S7).

  FIG. 11 is a flowchart for explaining the collection result report 9 providing process by the precondition check processing unit. In FIG. 11, the precondition check processing unit 142 of the cloud server 100 collects the software information 9f installed in each terminal 3 from each terminal 3 (step S331).

  The precondition check processing unit 142 performs the following steps S332 to S336 for each terminal 3 that has received the software information 9f.

  The precondition check processing unit 142 determines whether or not the software ID indicated by the software information 9f exists in the precondition table 156 (step S332). If the software ID indicated by the software information 9f does not exist in the precondition table 156, the precondition check for this terminal 3 is not performed, so the precondition check process for this terminal 3 is terminated.

  On the other hand, when the software ID indicated by the software information 9f exists in the precondition table 156, the precondition check processing unit 142 stores the precondition file 7 corresponding to the business performed in the terminal environment 5 and the terminal 3 of the terminal 3 in the terminal. 3 (step S333).

  The precondition check processing unit 142 receives the precondition check result 8 indicating the result of the precondition check performed on the terminal 3 from the terminal 3 (step S334). The received prerequisite check result 8 is stored in the prerequisite check result table 157.

  Then, the precondition check processing unit 142 transmits the diagnosis result 81 showing the environment different from the motion compensation in an easy-to-understand manner to the terminal 3 to display it on the terminal 3 (step S335). By displaying the diagnosis result 81, it is possible to understand the presence / absence of an environment different from the operation guarantee, and even a user who is unfamiliar with the security when using the terminal 3 can identify a location that may cause a problem in the terminal 3.

  The precondition check processing unit 142 transmits an e-mail indicating a URL (Uniform Resource Locator) of the diagnosis result 81 of the terminal 3 to the terminal 3, and causes the user to access the URL so that the diagnosis result 81 is displayed. May be.

  On the other hand, in the cloud server 100, when receiving the precondition check result 8 from the terminal 3 (step S334), the precondition check processing unit 142 updates the collection result report 9 (step S336). Then, the updated collection result report 9 can be displayed on the terminal 3m such as the system administrator M (step S337). The collection result report 9 may be displayed on the terminal 3d of the help desk D. The display of the collection result report 9 can reduce the troubleshooting time.

  Next, a flow of the precondition check process will be described, and a precondition review process performed in association with the precondition check process will be described.

  First, a description example of the precondition file 7 transmitted from the precondition check processing unit 142 of the cloud server 100 to the terminal 3 will be described with reference to FIG. FIG. 12 is a diagram illustrating a description example of the precondition file.

  FIG. 12 shows a description example of the precondition file 7a-1 for the terminal 3a that performs business in the A system. The precondition file 7a-1 indicates that it is a precondition for the A system by the description 75a. The description 75b indicates that the precondition version 7v of the description precondition file 7a-1 is “1.0.0.1”.

  When the terminal 3 receives the precondition file 7a-1, the terminal 3 acquires the precondition version 7v from the description 75b of the precondition file 7a-1, and stores it in the storage unit 130b of the terminal 3.

  The description 75c, the description 75d, and the description 75e indicate the support status for each software for which operation compensation is performed in the A system. In the description 75c, the tag <OS> indicates the support status of the software "OS", and the tag <support> indicates "Windows XP", "Windows Vista", "Windows 7", "Windows 8", and Indicates that “Windows 8.1” is supported.

  In the description 75d, the tag <browser> indicates that the software supports “browser”, and the tag <support> indicates “Internet Explore 8,” “Internet Explore 9,” “Internet Explore 10,” and “Internet.” Indicates that Explore 11 is supported. The tag <not_support> indicates that “Safari” and “Fire Fox” are not supported.

  In the description 75e, the tag <adobe> indicates that the software supports “Adbe”, and the tag <support> indicates that “Adbe Acrobat Reader 11.0” is supported.

  A tag that identifies the software and a tag that indicates a supported and / or unsupported version indicate an environment that can operate in the A system, an environment that cannot be used in the A system, or an environment that does not guarantee the operation. A tag <not_support> indicates that the component conflicts with the A system.

  For example, in the terminal environment 5 of the terminal 3a, when the OS is “Windows 8”, the OS is “supported” by the precondition check in the terminal 3a. On the other hand, in the terminal environment 5 of the terminal 3a, when the OS is “Windows 2000”, “Windows 2000” is not specified in the tag <support> or the tag <not_support> by the precondition check in the terminal 3a. It is judged that.

  In this case, it is not always necessary to switch to the version specified by the tag <support>, and if there is no report of a defect or a failure as a result of monitoring the state for a certain period, it can be a supported version. When it becomes a support target, it is specified by a tag <support>. If it is not supported, the tag <not_support> may be used.

  Further, in the terminal environment 5 of the terminal 3a, when the browser is “Internet Explore 10”, it is determined as a support target by the precondition check in the terminal 3a.

  On the other hand, in the terminal environment 5 of the terminal 3a, when the browser is “Internet Explore 12,” “Internet Explore 12” is designated as the tag <support> and the tag <not_support> by the precondition check in the terminal 3a. It is judged that there is no condition.

  In this case, it is not always necessary to switch to the version specified by the tag <support>, and if there is no report of a defect or a failure as a result of monitoring the state for a certain period, it can be a supported version. When it becomes a support target, it is specified by a tag <support>. If it is determined that the tag is not supported, the tag <not_support> may be specified.

  Also, in the terminal environment 5 of the terminal 3a, when the browser is “Safari”, it is clearly not supported because it is specified by the tag <not_support> by the precondition check in the terminal 3a, and the tag <support Switching to a product or version specified with> is recommended.

  The product name or version that does not match either the tag <support> or the tag <not_support> is indicated as mismatch information in the precondition check result 8 by the tag <other>, for example, and transmitted to the cloud server 100.

  FIG. 13 is a diagram for explaining an example in which a mismatch check result is reported to the cloud server. In FIG. 13, in the terminal 3a having a Windows (registered trademark) agent, the OS is “Windows 7”, the Adobe is “Adbe Acrobat Reader 11.0”, and the browser is “Internet Explore 12”.

  As a situation, “Internet Explore 11” was previously used (that is, the browser was supported), but the browser was updated on the terminal 3a, so that “Internet Explore 12” was used. ”And so on.

  In the terminal 3a using the A system, the precondition check is performed by the precondition check unit 62 based on the precondition file 7a-1 (FIG. 12) for the A system and Windows (registered trademark) agent received from the cloud server 100. Performed (step S3a).

  By the precondition check, the terminal 3a creates a precondition check result 8 for the purpose of notifying the cloud server 100 of the terminal environment 5 of the terminal 3a.

  That is, when it matches the supported condition of the precondition file 7, it is indicated as <support> Windows 8 </ support>.

  In the precondition file 7, if there is no matching condition in <support> or <not_support>, for example, <other> Internet Explore 12 </ other> is indicated. The tag <other> indicates that the condition of the terminal 3a does not exist in <support> or <not_support>, and also indicates the current condition of the terminal 3a.

  In addition, if it matches in <not_support> of the precondition file 7, it indicates that it matches in <not_support>. For example, <not_support> Fire Fox </ not_support>.

  <Other> is used for conditions that are supported and / or unsupported by the cloud server 100. On the other hand, <not_support> is used for a condition determined not to be supported by the system administrator M or the like.

  FIG. 14 is a diagram illustrating a description example of the precondition check result. In the precondition check result 8a-1 illustrated in FIG. 14, the descriptions 76c and 76e show one of the supported conditions for the OS and Adobe whose items are listed as software.

  In addition, the description 76d indicates that the condition for the browser does not match <support> or <not_support> by the tag <other>. It is shown that the browser of “Internet Explore 12” whose support status is unknown in the A system is used.

  In addition to the above, the precondition file 7, the terminal 3 identification information such as the device management ID, and information such as the date and time when the precondition check was executed may be included in the precondition check result 8 a-1.

  A display example of the collection result report 9 for the precondition check result 8a-1 as shown in FIG. 14 will be described with reference to FIG. FIG. 15 is a diagram illustrating a display example of a collection result report.

  FIG. 15 shows an example of a precondition check result list 9a corresponding to a part of the collection result report 9 that can be displayed on the terminal 3m of the system administrator M. The prerequisite check result list 9a is a table indicating whether or not the terminal 3 is operating with the supported software (and version) in each business for each terminal 3, and the terminal name, A system, B service, business It has items such as application C.

  In this example, regarding the terminal 3 having the terminal name “WIN-PC001”, it is determined that the supported software is used as the operating environment when the system A is operated, and “OK” is indicated. The same applies to the B service.

  Similarly, regarding the terminal 3 with the terminal name “WIN-PC002”, it is determined that the supported software is used as the operating environment when operating the A system, the B service, and the business application C, and “OK” is displayed. ing.

  Regarding the terminal 3 with the terminal name “WIN-PC003”, it is determined that the supported software is used as the operating environment in the operation of the business application C, and “OK” is indicated, but “NG” is indicated in the operation of the A system. Has been. In the following description, it is assumed that the terminal name “WIN-PC003” is the terminal 3a.

  When the system administrator M selects “NG”, a diagnosis result 81a is provided from the cloud server 100 and displayed on the terminal 3m. The diagnosis result 81a indicates the contents of the diagnosis result for each diagnosis item.

  The diagnosis item corresponds to software specified by the precondition file 7. The tag <OS>, tag <browser>, and tag <adobe> in the example of FIG. 12 correspond to diagnostic items.

  The contents of the diagnosis result indicate “no problem (Windows 7)” for the OS and “no problem (Adobe Reader 11.0)” for Adobe. In each parenthesis (), supported “Windows 7” and “Adobe Reader 11.0” indicated by the terminal 3a with the precondition check result 8 are shown.

On the other hand, since a version not specified in the tag <support> or the tag <not_support> is reported from the terminal 3a to the browser of the diagnostic item, for example,
"A supported browser is not installed.
The supported browsers are as follows.
・ Internet Explorer 8
・ Internet Explore 9
・ Internet Explorer 10
・ Internet Explore 11
A list of supported versions is shown.

  The system administrator M can grasp that a supported browser is not installed in the software situation when operating the A system of the terminal 3a.

  The diagnosis result 81a is information that can be displayed on the terminal 3a of the user A. Therefore, the user A can grasp which preconditions the terminal environment 5 of the terminal 3a satisfies the A system and which preconditions are not satisfied by displaying the diagnosis result 81a on the terminal 3a. it can.

  Next, a precondition review process sequence performed by the precondition review processing unit 143 of the cloud server 100 and the post-review check unit 63 of each terminal 3 will be described with reference to FIG. FIG. 16 is a diagram illustrating a processing sequence for reviewing the preconditions. In FIG. 16, the after-review checking unit 63 of the terminal 3 determines whether or not a predetermined time has elapsed since the previous confirmation of the precondition version 7v (step S371).

  When the predetermined time has not elapsed since the previous confirmation of the version of the prerequisite file 7 in the cloud server 100 and the prerequisite version 7v held by the terminal 3 (NO in step S371), the post-review checking unit 63 Step S371 is repeated at a predetermined interval.

  On the other hand, when the predetermined time has elapsed since the previous confirmation (YES in step S371), the post-review check unit 63 inquires and acquires the version of the precondition file 7 from the cloud server 100, and the terminal 3 holds it. It is confirmed whether or not the precondition version 7v matches (step S372). In the version inquiry, the device management ID of the terminal 3 is specified. If they match, the post-review check process by the post-review check unit 63 ends.

  On the other hand, if they do not match (if they do not match), the post-review check unit 63 requests and acquires the latest version of the prerequisite file 7 from the cloud server 100 (step S373). The device management ID of the terminal 3 is specified in the precondition file request.

  Then, the post-review check unit 63 performs a precondition check in the same manner as the precondition check unit 62 (step S374), and uploads the precondition check result 8 (step S375). Then, the post-review check process by the post-review check unit 63 ends.

  The precondition review process by the precondition review processing unit 143 in the cloud server 100 includes an automatic update process for automatically reviewing the precondition file 7 and a latest file providing process for providing the latest version of the precondition file 7.

  In the automatic update process, the precondition review processing unit 143 reads a record for a predetermined period from the mismatch information result table 159 (step S171). The predetermined period is, for example, two weeks.

  The precondition review processing unit 143 determines whether there is a check result whose occurrence status matches the review condition (step S172). The review conditions are, for example, the review conditions A, B, and C illustrated in FIG. 18, but are not limited to these.

  If it does not exist, the precondition review processing unit 143 ends this automatic update process. On the other hand, if it exists, the precondition review processing unit 143 adds the check result to the precondition file 7 as a new precondition, and updates the precondition version of the mismatch information result table 159 with respect to the precondition file 7. (Step S173), the automatic update process is terminated.

  In the latest file providing process, upon receiving a request from the terminal 3, the precondition reexamination processing unit 143 determines whether it is a version inquiry or a precondition file request (step S175). When the request from the terminal 3 is a version inquiry, the prerequisite review processing unit 143 acquires the prerequisite version from the prerequisite table 156 and notifies the terminal 3 (step S176).

  Based on the device management ID specified by the version inquiry, the terminal basic information table 151 is associated with the software information table 155, and is further associated with the precondition table 156 by the software ID of the software information table 155 (FIG. 9). . The prerequisite file 7 can be identified from the associated prerequisite table 156. The precondition version of the specified precondition file 7 managed in the precondition table 156 may be transmitted to the terminal 3.

  On the other hand, if the request from the terminal 3 is a precondition file request, the precondition review processing unit 143 transmits the precondition file 7 corresponding to the device management ID specified in the precondition file request to the terminal 3 (step) S177).

  Based on the device management ID specified by the prerequisite file request, the terminal basic information table 151 is associated with the software information table 155, and further associated with the prerequisite table 156 by the software ID in the software information table 155 (see FIG. 9). The prerequisite file 7 can be identified from the associated prerequisite table 156. The precondition file 7 may be specified from the associated precondition table 156 and transmitted to the terminal 3.

  Thereafter, the precondition review processing unit 143 receives the precondition check result 8 (step S178). The processing after reception of the precondition check result 8 is the same as steps S124 to S126 in the precondition check processing by the precondition check processing unit 142 in FIG.

  FIG. 17 is a diagram illustrating a table configuration example related to the precondition review process in the cloud server. In FIG. 17, the tables related to the prerequisite review process are a terminal basic information table 151, a software information table 155, and a mismatch information result table 159. Here, only the mismatch information result table 159 that is not described in FIGS. 6 and 9 will be described.

  In the mismatch information result table 159, as a result of the precondition check in the terminal 3, there is a matching condition among the conditions defined in the precondition file 7 (list of conditions of the tag <support> and the tag <not_support>). It is a table managed for each terminal 3 with respect to the condition of the terminal 3 that has been desired, and includes items such as a device management ID, a software ID, a precondition ID, a precondition version, a check result, and a check date and time.

  The device management ID indicates a device management ID registered in the terminal basic information table 151, and the terminal basic information table 151 and the mismatch information result table 159 are associated with each other by the device management ID.

  The software ID indicates identification information of software used for business, and the software information table 155 and the mismatch information result table 159 are associated with each other by the software ID.

  The precondition ID indicates identification information of the precondition file 7. The precondition version indicates a precondition version defined by the precondition file 7.

  The check result indicates a condition of the terminal 3 that does not match the tag <support> or the tag <not_support> and does not match. For example, in the case of the precondition check result 8 in FIG. 14, information corresponding to the description 76d (at least “Internet Explore 12”) is stored. The check date and time indicates the date and time when the precondition check was executed on the terminal 3.

  In the automatic update process, the precondition review processing unit 143 obtains and sums up information on mismatches that have occurred in the terminals 3 that have executed the precondition check in the same precondition file 7 from the check results. For example, when the mismatch information generated by the precondition check based on the precondition file 7a-1 in FIG. 12 is information equivalent to the description 76d, and it is determined that the condition can be supported by detailed automatic update processing described later By updating the precondition, the precondition file 7a-1 (FIG. 12) is updated to the precondition file 7a-2 (FIG. 19).

  FIG. 18 is a flowchart for explaining the automatic update processing by the precondition review processing unit. In FIG. 18, the precondition review processing unit 143 reads the mismatch information result table 159 and collects records for each check result during a predetermined period (step S171). The records may be collected by sorting by check results. The predetermined period is, for example, two weeks.

  Here, the check result of the mismatch information result table 159 indicates the condition of the terminal 3 that does not match. That is, a condition that does not match <support> or <not_support> in the precondition file 7 is indicated by the check result. For example, in FIG. 14, the condition indicated by the tag <other> corresponds.

  Then, the precondition review processing unit 143 performs the process of step S172. In the process of step S172, the precondition review processing unit 143 selects one check result and sets the selected check result record as a processing target (step S172-1).

  The precondition review processing unit 143 first verifies whether the number of mismatches of the precondition check that occurred during a certain period exceeds the number reference value (review condition A) (step S172-2). What is necessary is just to total the number of records in a certain fixed period with respect to the selected check result.

  When the number of reference values is exceeded (YES in step S172-2), that is, when the review condition A is met, the precondition review processing unit 143 stores the check result in the storage unit 130a as a review target (step S172-5), the process proceeds to step S172-6.

  On the other hand, when the number of cases does not exceed the reference number (NO in step S172-2), that is, when the review condition A is not met, the precondition review processing unit 143 counts the number of times that the same mismatch is continuously generated. Whether the reference value is exceeded (review condition B) is verified (step S172-3). When the number of times exceeds the reference value (YES in step S172-3), that is, when the review condition B is met, the precondition review processing unit 143 stores the check result in the storage unit 130a as the review target (step S172-5), the process proceeds to step S172-6.

  On the other hand, when the reference number of times is not exceeded (NO in step S172-3), that is, when the review condition B is not met, the precondition review processing unit 143 has a certain ratio of match and mismatch with respect to the precondition. (Review condition C) is verified (step S172-4).

  As an example of verification of the review condition C, records having the same software ID as the selected check result in the same period are extracted from the precondition check result table 157 and the precondition check result history table 158, and the number of records is totaled. The number of records indicates the total number of matches (tag <support> and tag <not_support>) and mismatches (tag <other>). When the number of records and the number of records of the check result selected in the mismatch information result table 149 indicate approximately 2: 1, it may be determined that a certain ratio has occurred.

  When the ratio reference value is exceeded (YES in step S172-4), that is, when the review condition C is met, the precondition review processing unit 143 stores the check result as a review target. The information is stored in the unit 130a (step S172-5), and the process proceeds to step S172-6.

  After step S172-5 or when the ratio reference value is not exceeded (NO in step S172-4, that is, when the review conditions A, B, and C are not met), the precondition review processing unit 143 It is determined whether or not the check result has been completed (step S172-5). When the check result that has not been processed still remains, the precondition review processing unit 143 returns to step S172-1, and repeats the same process as described above for the next check result. On the other hand, when all the check results have been completed, the precondition review processing unit 143 proceeds to step S173.

  In the above description, the order of verification of the review conditions A, B, and C is not defined. The order of review conditions B, A, and C may be the order, or another order.

  In the process of step S173, the precondition review processing unit 143 selects one from the check results to be reviewed (step S173-1).

  Then, the precondition review processing unit 143 excludes duplicate device management ID records from the selected check result records (step S173-2), and verifies all the review conditions A, B, and C (steps). S173-3). Exclusion of duplicate device management ID records is performed in order to extract conditions related to a plurality of terminals 3. Steps S172-2, S172-3, and S172-4 are performed on the records from which duplication is excluded.

  The precondition review processing unit 143 determines whether or not one or more of the review conditions A, B, and C are met (step S173-4). If all the review conditions A, B, and C are not met (NO in step S173-4), the precondition review processing unit 143 proceeds to step S173-6.

  On the other hand, when at least one of the review conditions A, B, and C is met (YES in step S173-4), the precondition review processing unit 143 reviews the precondition and updates the precondition version (step S173-5). In the review of the precondition, the precondition review processing unit 143 identifies the record in the precondition table 156 associated with the precondition ID of the record that exceeds one or more reference values, and the precondition is identified by the precondition ID of the identified record. The file 7 is specified, and the preconditions defined in the precondition file 7 are updated based on the check result. Further, the precondition review processing unit 143 updates the precondition version of the record specified in the precondition table 156.

  The review of the preconditions includes an update for refining the preconditions of the diagnostic item and an update for reviewing the conditions and changing the specifications, and at least one of the updates is performed. Updates that add diagnostic items and refine prerequisites include the addition of software that determines the prerequisites.

  For example, in FIG. 12, the diagnosis item corresponds to each target software by the tag <OS>, tag <browser>, and tag <adobe>. When a new OS is released, a condition that it is not supported is added by designating a new OS using a tag <not_support> under the tag <OS>.

  The update in which the specification is changed by reviewing the condition is equivalent to adding a version or the like determined to be supported using the tag <support> to the target diagnosis item. For example, “Internet Explore 12” is added using the tag <support> under the tag <browser>.

  The precondition file 7a-2 updated from the precondition file 7a-1 shows, for example, the contents as shown in FIG. FIG. 19 is a diagram illustrating a description example of the updated precondition file. The precondition file 7a-2 shown in FIG. 19 shows an example in which <support> Internet Explore 12 </ support> is added under the tag <browser> by the automatic update processing described in FIGS. .

  FIG. 20 is a diagram for explaining an example in which the latest prerequisite file is provided. In FIG. 20, the latest prerequisite file 7a-2 is transferred to the terminal 3a by the update file provision processing by the prerequisite review processing unit 143 of the cloud server 100 (step S7a).

  When the latest prerequisite file 7a-2 for the A system in the terminal 3a is received, the post-review checking unit 63 of the terminal 3a automatically performs the prerequisite check based on the received latest prerequisite file 7a-2. (Step S8a).

  When the cloud server 100 receives the precondition check result 8 based on the latest precondition file 7a-2, for example, a collection result report 9 and a diagnosis result 81 as shown in FIG. 21 can be displayed.

  FIG. 21 is a diagram illustrating a display example of an updated collection result report. FIG. 21 shows an example of a precondition check result list 9a-2 corresponding to a part of the collection result report 9 that can be displayed on the terminal 3m of the system administrator M. The precondition check result list 9a-2 has the same items as the precondition check result list 9a in FIG.

  The difference from the precondition check result list 9a of FIG. 15 is that the precondition check result of the system A with the terminal name “WIN-PC003” is changed from “NG” to “OK”. In the following description, it is assumed that the terminal name “WIN-PC003” is the terminal 3a.

  When the system administrator M selects “OK” for the A system, the cloud server 100 provides the diagnosis result 81a-2 and displays it on the terminal 3m. The diagnosis result 81a-2 indicates the contents of the diagnosis result for each diagnosis item, like the diagnosis result 81a of FIG.

  In the diagnostic result 81a-2, the diagnostic result is “no problem (Windows 7)” for the diagnostic item “OS” and “no problem (Adobe Reader 11.0)” for the diagnostic item “Adobe”. Indicated.

  On the other hand, the diagnostic item “browser” is different from the precondition file 7a before update because “Internet Explore 12” is reported to the cloud server 100 with the tag <support>, so the diagnostic items “OS” and “Adobe” Similarly, “No problem (Internet Explore 12)” is shown. In each parenthesis (), the condition indicated by the terminal 3a as the precondition check result 8a-2 is shown.

  As described above, in this embodiment, since the preconditions are automatically updated according to various changes in the terminal environment 5 occurring on the terminal 3 side, both the system administrator M and the user can improve the work efficiency. Can contribute.

  On the cloud server 100 side, the system administrator M can collect information on the terminal environment 5 without operating each terminal 3. In addition, when the user introduces the business application to the terminal 3, the user automatically performs the operation in response to the reception of the precondition file 7, so that it is not necessary for the user to check the operating environment. Even if the user has no knowledge for confirming the operating environment, the user refers to the diagnosis result 81 to determine whether the user terminal 3 has a precondition for using the business application. Can be confirmed.

  In addition, since software updated individually by each terminal 3 is reported to the cloud server 100 by the precondition check result 8, the change in the terminal environment 5 can be grasped in real time. In addition, since the preconditions are automatically reviewed according to changes in the terminal environment 5, it is possible to reduce the burden on the system administrator M related to the update performed on each terminal 3.

  Furthermore, since the system administrator M can know the environment of the user's terminal from the collection result report 9 in response to an inquiry from a user unfamiliar with IT, the system administrator M can appropriately cope with the inquiry.

  As described above, in the cloud server 100 according to the present embodiment, when the result of summing up the precondition check results 8 from the terminals 3 determined not to satisfy the contents of the transmitted precondition file 7 satisfies the review condition, the precondition Since the precondition file 7 is updated based on the check result 8, the review of the precondition file 7 can be automated.

  The present invention is not limited to the specifically disclosed embodiments, and can be principally modified and changed without departing from the scope of the claims.

Regarding the above embodiment, the following additional notes are disclosed.
(Appendix 1)
Sending environmental conditions of terminals for executing specific software to a plurality of computers, receiving a report about the environment from a computer determined not to satisfy at least the environmental conditions via a communication interface;
Based on the received report, the environmental condition is based on the received report on the environment, if the result of the report on the environment from the computer that does not satisfy the environmental condition satisfies the condition for reviewing the environmental condition. Transmitting the new environmental condition obtained by changing to the plurality of computers via the communication interface;
A management program for causing a computer to perform processing.
(Appendix 2)
The management program according to claim 1, wherein the condition for reviewing the environmental condition is that the number of computers not satisfying the environmental condition is equal to or greater than a predetermined number.
(Appendix 3)
Sending the environmental conditions of the terminal for executing a specific business application to a plurality of computers, receiving at least a report about the environment from a computer determined not to satisfy the environmental conditions via a communication interface,
Based on the received report, the environmental condition is based on the received report on the environment, if the result of the report on the environment from the computer that does not satisfy the environmental condition satisfies the condition for reviewing the environmental condition. Transmitting the new environmental condition obtained by changing to the plurality of computers via the communication interface;
A management program for causing a computer to perform processing.
(Appendix 4)
The management program according to appendix 3, wherein the environmental condition is information indicating each software and a version of the software supported by at least the specific business application.
(Appendix 5)
4. The management program according to claim 3, wherein the reported environment is indicated by a product name and version of software that does not match an environmental condition for the specific business application.
(Appendix 6)
The condition for reviewing the environmental condition is that the environmental condition is reviewed when the number of times the same environment is reported exceeds the reference number of times.
In the computer,
The management program according to any one of appendices 1 to 5, wherein when the condition for reviewing the environmental condition is satisfied, a process for updating the environmental condition is performed based on the reported environment.
(Appendix 7)
The condition for reviewing the environmental condition is that the environmental condition is reviewed when the number of reports on the environment from a computer that is determined not to satisfy the environmental condition for a certain period exceeds the reference number of cases. ,
In the computer,
The management program according to any one of appendices 1 to 5, wherein when the condition for reviewing the environmental condition is satisfied, a process for updating the environmental condition is performed based on the reported environment.
(Appendix 8)
The condition for reviewing the environmental condition is that the report on the environment from the computer that has determined that the environmental condition is not satisfied occurs at a certain rate, and that the environmental condition is reviewed.
In the computer,
The management program according to any one of appendices 1 to 5, wherein when the condition for reviewing the environmental condition is satisfied, a process for updating the environmental condition is performed based on the reported environment.
(Appendix 9)
Sending environmental conditions of terminals for executing specific software to a plurality of computers, receiving a report about the environment from a computer determined not to satisfy at least the environmental conditions via a communication interface;
Based on the received report, the environmental condition is based on the received report on the environment, if the result of the report on the environment from the computer that does not satisfy the environmental condition satisfies the condition for reviewing the environmental condition. Transmitting the new environmental condition obtained by changing to the plurality of computers via the communication interface;
A management method, wherein a computer performs processing.
(Appendix 10)
A communication interface that transmits environmental conditions of a terminal for executing specific software to a plurality of computers, and receives a report about the environment from a computer that is determined not to satisfy at least the environmental conditions via the communication interface;
Based on the received report, the environmental condition is based on the received report on the environment, if the result of the report on the environment from the computer that does not satisfy the environmental condition satisfies the condition for reviewing the environmental condition. A control unit that performs control to transmit a new environmental condition obtained by changing to the plurality of computers via the communication interface;
A management apparatus comprising:

3, 3a, 3b, 3m Terminal 4, 4a, 4b Policy file 4p Policy 4v Policy version 5 Terminal environment 6, 6a, 6b Security check result 7, 7a, 7b Precondition file 7v Precondition version 8, 8a, 8b Precondition Check result 9 Collection result report 11a CPU, 12a Main storage device 13a Auxiliary storage device 14a Input device 15a Display device 17a Communication I / F
18a Drive device 19a Storage medium 61 Security check unit 62 Prerequisite condition check unit 63 Post-review check unit 100 Cloud server 130a, 130b Storage unit 141 Basic operation processing unit 142 Prerequisite condition check processing unit 143 Prerequisite condition review processing unit B1 bus

Claims (8)

Sending environmental conditions of terminals for executing specific software to a plurality of computers, receiving a report about the environment from a computer determined not to satisfy at least the environmental conditions via a communication interface;
Based on the received report, the environmental condition is based on the received report on the environment, if the result of the report on the environment from the computer that does not satisfy the environmental condition satisfies the condition for reviewing the environmental condition. Transmitting the new environmental condition obtained by changing to the plurality of computers via the communication interface;
A management program for causing a computer to perform processing. 2. The management program according to claim 1, wherein the condition for reviewing the environmental condition is that the number of computers not satisfying the environmental condition is equal to or greater than a predetermined number. Sending the environmental conditions of the terminal for executing a specific business application to a plurality of computers, receiving at least a report about the environment from a computer determined not to satisfy the environmental conditions via a communication interface,
Based on the received report, the environmental condition is based on the received report on the environment, if the result of the report on the environment from the computer that does not satisfy the environmental condition satisfies the condition for reviewing the environmental condition. Transmitting the new environmental condition obtained by changing to the plurality of computers via the communication interface;
A management program for causing a computer to perform processing.   4. The management program according to claim 3, wherein the environmental condition is information indicating each software and a version of the software supported by at least the specific business application.   The management program according to claim 3, wherein the reported environment is indicated by a product name and version of software that does not match an environmental condition for the specific business application. The condition for reviewing the environmental condition is that the environmental condition is reviewed when the number of times the same environment is reported exceeds the reference number of times.
In the computer,
The management program according to any one of claims 1 to 5, wherein when the condition for reviewing the environmental condition is satisfied, a process for updating the environmental condition is performed based on the reported environment. Sending environmental conditions of terminals for executing specific software to a plurality of computers, receiving a report about the environment from a computer determined not to satisfy at least the environmental conditions via a communication interface;
Based on the received report, the environmental condition is based on the received report on the environment, if the result of the report on the environment from the computer that does not satisfy the environmental condition satisfies the condition for reviewing the environmental condition. Transmitting the new environmental condition obtained by changing to the plurality of computers via the communication interface;
A management method, wherein a computer performs processing. A communication interface that transmits environmental conditions of a terminal for executing specific software to a plurality of computers, and receives a report about the environment from a computer that is determined not to satisfy at least the environmental conditions via the communication interface;
Based on the received report, the environmental condition is based on the received report on the environment, if the result of the report on the environment from the computer that does not satisfy the environmental condition satisfies the condition for reviewing the environmental condition. A control unit that performs control to transmit a new environmental condition obtained by changing to the plurality of computers via the communication interface;
A management apparatus comprising:

Images