WO2015136643A1

WO2015136643A1 - Computer environment management system

Info

Publication number: WO2015136643A1
Application number: PCT/JP2014/056514
Authority: WO
Inventors: 知宏浦部
Original assignee: 株式会社野村総合研究所
Priority date: 2014-03-12
Filing date: 2014-03-12
Publication date: 2015-09-17

Abstract

The purpose of the present invention is to provide a technique whereby it is possible to reduce the labor, etc., required to manage kitting for an environment including software on user terminals in an organization. This system manages the user environment of each user terminal in an organization, including establishing and changing the user environment, wherein the user environment of each user terminal includes different software. A server in the system provides screens for the user terminals and the setter terminal in the organization, and sets and manages information relating to the user environment of each user terminal in the organization in response to operation by the setter terminal, wherein the user environment of each user terminal includes software installed on the user terminal. In connection with the above setting, the server creates execution modules for installing target software on target user terminals, and, upon being accessed by a user terminal, transmits an execution module for particular target software to the user terminal so that the execution module executes a process on the user terminal.

Description

Computer environment management system

The present invention relates to information processing technology. The present invention also relates to a technology for IT resource management, construction, and arrangement (also referred to as kitting or setup) related to the computer environment of a user group of an organization such as a company.

The information system of an organization such as a company manages IT resources including hardware such as terminals allocated for each user such as an employee. In addition, when an information system is introduced, changed, or moved, kitting of a computer environment is required for each user terminal. That is, each user terminal needs to construct and arrange an environment including software such as necessary OS, middleware, device driver, and application (also referred to as application). In this work, terminals and the like are installed and wired, necessary software is installed, and necessary settings are performed by an individual employee, a system administrator, or an operator such as a supporter of the maintenance operation service.

JP-A-8-137768 (Patent Document 1) is cited as an example of prior art related to IT resource management and kitting. Patent Document 1 describes that software and data distribution work such as installation and version upgrade, software license management, and the like that are used in each device constituting the network system to be managed are performed from a remote location. . Further, it is described that the file server device manages the software configuration, hardware configuration, distribution software, and script of each device in the DB and distributes the software to each device in accordance with an instruction from a remote device.

JP-A-8-137768

The above-described conventional technology related to management of IT resources and kitting has the problem that the number of users and terminals in the information system of the target organization and the change in the user environment increase, the time and effort required for work related to IT resource management and kitting. There is a problem that costs increase.

In an environment in which the same and common software is installed in the terminals of a plurality of users in an organization information system, kitting is possible by applying data such as a common OS image called a master. Therefore, the labor of the work can be relatively reduced. However, there may be an environment in which different software is installed depending on the department of the organization and the terminals of individual users. In this case, the common data cannot be applied, and kitting work including installation of different software is required for each individual user terminal. That is, the man-hours for the overall work increase, and the labor of the worker becomes great.

In conventional IT asset management, hardware asset management such as allocation of terminals to a plurality of users in an organization is performed. However, detailed management regarding software environments such as different OSs and applications for each individual user's terminal and support for software kitting for each user's terminal are not provided.

Note that Patent Document 1 does not describe distribution setting means, means for facilitating work, and the like corresponding to the case where the software configuration of each client device is different.

An object of the present invention is to provide a technique capable of reducing labor and the like regarding management of environment kitting including software of a user terminal of an organization.

A representative embodiment of the present invention is a computer environment management system that manages the computer environment of an organization, and has the following configuration.

A computer environment management system according to an embodiment includes: a user terminal of an organization; a terminal of a setter; and a server device that manages a computer environment targeted for the user terminal of the organization. The apparatus accepts access from the terminal of the user and the terminal of the setter and provides a screen, and for each terminal of the user of the organization based on an operation from the terminal of the setter on the screen Along with the setting of the user environment information, a setting unit that sets and manages a user environment including software to be arranged as user environment information, a software registration unit that registers software data and information to be arranged on the user terminal A preparation unit that creates an execution module for allocating the target software to the target user's terminal and constructing the user environment; and An execution unit that receives the access from the terminal of the user, transmits the execution module of the software to be arranged to the terminal of the user, and executes the process of the execution module on the terminal of the user, the user terminal of the organization Management including construction and change of user environment including different software is performed.

According to the representative embodiment of the present invention, it is possible to reduce the labor and the like regarding the management of the environment kitting including the software of the terminal of the user of the organization.

It is a figure which shows the structure of the computer environment management system of one embodiment of this invention. It is a figure which shows the functional block structure of the service site of the computer environment management system of this Embodiment. It is a figure which shows the process regarding a user environment list setting as a 1st process flow of the computer environment management system of this Embodiment. It is a figure which shows the process regarding kitting execution as a 2nd process flow of the computer environment management system of this Embodiment. It is a figure which shows the user environment and the example of kitting. It is a figure which shows the process example at the time of execution of kitting. It is a figure which shows the structural example of organization asset information. It is a figure which shows the structural example of user asset information. It is a figure which shows the structural example of pattern setting information. It is a figure which shows the structural example of software data and license information. It is a figure which shows the structural example of combination compatibility information. It is a figure which shows the structural example of arrangement | positioning execution module management information. It is a figure which shows the structural example of a software extension list | wrist. It is a figure which shows the example of a screen of kitting setting. It is a figure which shows the example of a screen of software registration. It is a figure which shows the example of a screen of kitting execution confirmation. It is a figure which shows the structure of the computer environment management system of other embodiment.

Hereinafter, a computer environment management system according to an embodiment of the present invention will be described in detail with reference to the drawings. Note that components having the same function are denoted by the same reference symbols throughout the drawings for describing the embodiment, and the repetitive description thereof will be omitted.

The computer environment management system according to the present embodiment provides a centralized management service for IT resource management and kitting related to a computer environment including hardware and software of a user group of an organization such as a company. This system continuously manages the computer environment, including the introduction, change, and relocation of an organization's information system, and the construction and change of a user environment that includes the addition, deletion, and update of software for individual user terminals. This system can set different software environments for each terminal of individual users, and based on the environment settings, automatic kitting, that is, construction and arrangement, etc. can be executed for each environment of individual user terminals. .

This system provides a uniform graphical user interface (GUI) screen such as Web to users including administrators, and each user can set and execute management and management of IT resources and kitting through the screen. Easy to operate. Thereby, it is possible to reduce the labor of IT resource management of the organization information system and work related to the environment kitting of individual user terminals. Kitting includes not only software installation at the time of initial introduction, but also changes in the user environment, such as subsequent version updates or uninstallations.

[System (1)]
FIG. 1 shows a configuration of a computer environment management system according to the present embodiment. The entire computer environment management system includes an information system 20 of an organization such as a company and a service site 10 of a business operator that are connected via a communication network 90. The communication network 90 is the Internet, a dedicated line, or the like. The service site 10 provides services such as maintenance and operation of the information system 20 of the organization that is a customer, IT resource management, and management of user environment kitting.

The organization includes users such as a plurality of employees, and includes, for example, general users U1 to U4 and a user U0 who is an administrator of the information system 20. The information system 20 includes a terminal 2 of each user, a firewall server 91, a business server 92, and the like connected to the LAN 95. The firewall server 91 is connected to an external communication network 90. The business server 92 is a server having a predetermined business function. The organization information system 20 has an intranet including a LAN 95, and can access the server 1 of the operator from the terminal 2 of each user connected to the LAN 95 through the communication network 90 and the VPN.

The terminal 2 includes various information processing terminals such as desktop and notebook PCs, tablets, and smartphones. T11, T21 and the like indicate identification information of the terminal 2. One or more terminals 2 are assigned to one user. For example, the user U1 uses a terminal T11 that is a PC, and the user U2 uses a terminal T22 that is a PC. The user U3 uses two terminals, a terminal T31 that is a PC and a terminal T32 that is a tablet. The administrator U0 uses a terminal T0 such as a PC.

The service site 10 includes a server 1, a DB 50, and a terminal 3 of the administrator Us. The configuration of the server 1 is shown in FIG. The DB 50 includes a storage device, a DB server, and the like, and includes an asset management DB 51, a software DB 52, and a backup DB 53. The administrator Us uses the terminal 3 such as a PC to access the server 1 or the like as appropriate, and performs operations such as setting of the service site 10 and operation maintenance and management related to the customer information system 20.

Note that the service site 10 of the business operator may be configured by a virtual server, a virtual storage, or the like of a data center or a cloud computing system. Also, there may be a plurality of organization information systems 20, and the service site 10 may provide services to a plurality of organizations.

In the computer environment management system according to the present embodiment, the administrator U0 of the organization information system 20 or the administrator Us of the business operator is a main setter for managing IT resources and kitting. The administrator U0 sets the environment of each user according to a request from each user of the organization. Alternatively, the operator Us administrator Us sets the environment of the user in the organization in accordance with a request from the customer administrator U0.

[System (2)]
FIG. 2 shows a functional block configuration of the service site 10 of the computer environment management system of the present embodiment. The server 1 of the service site 10 includes a GUI unit 11, an organizational asset management unit 12, a user environment management unit 13, an application approval unit 14, a software registration unit 15, a license check unit 16, a combination compatibility check unit 17, an arrangement preparation unit 18, The arrangement reception execution unit 19, the backup unit 31, the environment division unit 32, and the environment integration unit 33 are included. Each processing unit of the server 1 is realized by software program processing.

The asset management DB 51 stores organization asset information 61, user environment information 62, pattern setting information 63, and the like. The software DB 52 stores software data 71, license information 72, combination compatibility information 73, execution module management information 74, software extension list 75, and the like. The backup DB 53 stores backup data 81 and the like.

The GUI unit 11 is configured by a Web server, for example, and provides a screen using a Web interface as a GUI for a user who uses the service. The server 1 accepts access from the terminal of each user of the organization and the terminal 2 of the administrator U0 who is a setting person, and provides a web page screen (FIG. 14 and the like described later) by the GUI unit 11. Each user can perform operations such as browsing, setting, and execution of information related to the IT resource and kitting management service provided by the service site 10 on the screen.

The organizational asset management unit 12 sets and manages IT asset information including a list of terminals of the user group of the organization in the organizational asset information 61 (FIG. 7 described later) based on the operation from the terminal of the setter.

The user environment management unit 13 sets information related to the management of kitting including a list of software of each user terminal of the organization in the user environment information 62 (FIG. 8 described later) based on an operation from the terminal of the setter. to manage. Further, the user environment management unit 13 sets and manages a pattern of software configuration used for setting the user environment in the pattern setting information 63 based on the operation from the setting person's terminal.

The application approval unit 14 is a process for registering, in the user environment information 62, information including a prior application regarding use of software such as an application on the user's terminal 2 and an approval for the application based on an operation from the terminal of the setter. I do.

The software registration unit 15 registers and manages software data and information such as necessary applications in software data 71 (FIG. 10 described later) in accordance with management of IT resources and kitting.

The license check unit 16 registers and manages information related to licenses and contracts of software such as registered applications in the license information 71 (FIG. 10 described later). The software data 71 and the license information 72 may be integrated into one. When setting the software environment for each user terminal in the user environment information 62, the license check unit 16 refers to the license information 72 and checks the license conditions related to the setting.

The combination compatibility check unit 17 registers and manages the compatibility in the combination of software such as applications in the combination compatibility information 73 (FIG. 11 described later). The compatibility of the combination is determined to be poor if there is a problem or a performance drop. The combination compatibility check unit 17 may register and manage information such as a security level in software such as a single application in the combination compatibility information 73. The combination compatibility check unit 17 refers to the combination compatibility information 73 when setting the software environment for each user terminal in the user environment information 62, and assumes that a combination of software such as an application is installed in the user terminal by the setting. Check the compatibility of the combination in the state.

When the software environment setting for each user terminal in the user environment information 62 is executed, the arrangement preparation unit 18 creates an execution module for kitting such as automatic arrangement and construction of the software. The execution module data and information are stored in the execution module management information 74 (FIG. 12 described later). The execution module is a package including an execution format program for automatic distribution of software such as a target application, installation on a user terminal, and necessary settings.

The placement reception execution unit 19 receives a confirmation access from an individual user terminal based on the setting of the user environment, refers to the user environment information 62 and the execution module management information 74, and uses the execution module to specify the target The target software kitting for the user terminal 2 is automatically executed.

The backup unit 31 automatically stores, in the backup data 81 of the backup DB 53, the backup data for the user data before the migration related to the software in accordance with the change and kitting of the software of the user environment. The backup unit 31 automatically migrates user data to the migration destination user environment by restoration using the backup data 81. The user data includes, for example, a document file created by an application. The backup unit 31 refers to a software extension list 75 (FIG. 13 described later) during backup and restore processing, and determines user data associated with software such as an application from the extension.

The computer environment management system according to the present embodiment is easy even when dividing a plurality of terminals 2 into an environment or when integrating a single terminal 2 into the environment as a kitting setting accompanying a change in the user environment. Has a function to assist in setting and executing kitting. The server 1 includes an environment division unit 32 and an environment integration unit 33 corresponding to this function. An example of division and integration is shown in FIG.

The environment dividing unit 32 sets kitting corresponding to the case where the environment of one terminal 2 of the user is divided and increased to the environment of two or more terminals 2. For example, each application can be set to be installed on each of the plurality of terminals 2 after the division, and the license conditions and the compatibility of the combinations at that time are also checked.

The environment integration unit 33 sets kitting corresponding to a case where the environments of two or more terminals 2 of a user are integrated and reduced to the environment of one terminal 2. For example, it is possible to set so that a plurality of applications are installed in one terminal 2 after integration, and the license conditions and the compatibility of the combinations at that time are also checked.

[Processing flow (1)]
FIG. 3 shows processing relating to setting of the user environment as a first processing flow of the computer environment management system of FIG. S1 etc. represent processing steps.

(S1) First, the organizational asset information 61 is set by a setter such as the administrator U0 or the administrator Us. If it has been set, S1 can be omitted. The server 1 is accessed from the setting person's terminal. The GUI unit 11 provides a screen for setting organizational asset information to the setter's terminal. The setter inputs or confirms information on the IT resource including the list of the terminal 2 of the user of the organization on the screen. The organizational asset management unit 12 sets input information on the screen in the organizational asset information 61.

(S2) If you want to install and use software such as an individual application on an individual user's terminal 2, perform pre-application and approval procedures. A setter such as the administrator U0 or the administrator Us receives a prior application regarding use of an application or the like from an individual user.

In S2, the setter performs new registration of the software if the application software such as the application is not registered in the software DB 52. The GUI unit 11 of the server 1 provides a screen for software registration to the terminal of the setter. The setter registers information on the newly registered software on the screen. The software registration unit 15 stores the registered software information in the software data 71.

Also, the license check unit 16 stores license information and contract information of the registered software in the license information 72. When the target software is approved, the data body of the target software is registered. For example, a procedure for storing newly purchased software data in the software DB 52 is performed.

When the application software such as the application is already registered in the software DB 52, the process of S2 is not necessary. If registered, software such as the application is displayed as an option on the screen, and the setter can select software from the option.

(S3) In S3, the setter registers information on the target application or the like in the software list of the user's terminal 2 in the user environment information 62 based on the prior application for the software such as the application from the user.

(S4) In S4, pre-approval information by a predetermined approver regarding the user environment application applied and registered in S3 is registered in the user environment information 62. The approver is, for example, a leader of a department to which a user who is an applicant belongs, an administrator U0, another set user, or the like. For example, the administrator U0 confirms the application that has been applied and registered on the screen, and confirms the use of the application and the approval of kitting with a predetermined approver. In the case of approval, the administrator U0 inputs approval information on the screen.

The GUI unit 11 provides a screen including the contents of the user environment information 62. On the screen, the setter inputs approval information regarding the use of the target application regarding the user environment including the software list of the terminal 2 of the target user. For example, in the case of approval, a check indicating approval is turned on. The application approval unit 13 sets the approval information input on the screen in the row of the user terminal in the user environment information 62.

(S5) A setter such as the administrator U0 or the administrator Us registers and updates the contents of the license information 72 and the combination compatibility information 73 on the screen as appropriate. For example, when purchasing a license, the license check unit 16 stores the license information input on the screen by the setter in the license information 72. Further, the combination compatibility check unit 17 stores, in the combination compatibility information 73, the compatibility information of the software combination input on the screen by the setter. Based on the collection and analysis of software security information for individual OSs and applications, the business operator can provide information on the security level of a single software and the incompatibility of combinations of multiple software from time to time. The information 73 may be registered.

(S6) The setter confirms the contents of the approved user environment kitting settings on the screen, and then inputs an instruction to execute the settings. For example, the setter presses a setting button on the screen.

(S7) The license check unit 16 of the server 1 automatically executes a license check process for information on the setting contents of the user environment instructed to execute the setting in S6. The license check unit 16 refers to the license information 72 and confirms whether there is a problem in conditions such as the number of licenses of software such as the target application. In the example of license check, when setting up additional installation of an application, the total number of licenses plus the number of licenses required for using the application in units such as departments is the number of purchased licenses. Whether it exceeds or not is judged as a condition.

(S8) In S8, if the license check unit 16 satisfies the license condition (S8-N) based on the check result in S7, the process proceeds to S10, and if the license condition is not satisfied (S8-Y), the process proceeds to S9. .

(S9) In S9, the license check unit 16 displays information such as an alert or an error indicating that the license condition is not satisfied on the screen of the setter's terminal. For example, when the total number of licenses exceeds the number of purchases, an alert is sent to that effect. The setter confirms by checking the check result including the alert on the screen. For example, the setter can recognize that there is a problem in terms of licenses, and can examine procedures such as additional purchase of necessary licenses.

(S10) Further, the combination compatibility check unit 17 of the server 1 automatically executes the combination compatibility check process for the information on the setting contents of the user environment instructed to execute the setting in S6. The combination compatibility check unit 17 refers to the combination compatibility information 73 and determines whether the compatibility is good or bad regarding the combination of a plurality of software including the OS and applications in the software list of the target user environment.

(S11) In S11, the combination compatibility check unit 17 proceeds to S13 if the combination compatibility is good or the compatibility is not bad as a result of the check in S10, and proceeds to S12 if the combination compatibility is bad.

(S12) In S12, the combination compatibility check unit 17 displays information such as an alert and an error indicating that the combination of the software combinations of the user environment to be set is incompatible on the screen of the setting person's terminal. The setter confirms by checking the check result including the alert on the screen. For example, the setter can recognize that there is a problem in the compatibility of the combinations, and can consider changing the software combinations.

(S13) In S13, the server 1 displays the information on the user environment in S6 and the information on the check results in S7 and S10 on the screen of the setter's terminal. Displays information that confirms whether to execute the settings. This screen includes, for example, a setting execution button. The setter looks at the screen and determines whether to execute the contents of the setting in S6. For example, when the setting person determines that there is no problem because there is no particular alert, the setting person presses the setting execution button (S13-Y). For example, if the setter determines that there is a problem due to an alert regarding the license or combination compatibility, the setting is terminated without executing the setting (S13-N). Further, when the setter determines that there is no problem after looking at the contents of the alert or the like, the setter may perform the setting. In the case of ending without setting, the setting can be redone by returning to S2 and the like and repeating similarly.

(S14) In S14, the user environment management unit 13 of the server 1 reflects and stores the setting of the user environment kitting executed in S13 in the corresponding line of the user environment information 62. The arrangement preparation unit 18 of the server 1 creates an execution module for software such as an application to be kitted on the terminal 2 of the target user in the setting of kitting of the set user environment. The arrangement preparation unit 18 stores the created execution module data and information in the execution module management information 74.

[Processing flow (2)]
FIG. 4 shows processing relating to execution of kitting as a second processing flow of the computer environment s management system of FIG. Assume the situation that has been set by the processing of FIG.

(S21) The user terminal 2 accesses the server 1 to check its own environment and kitting as appropriate, such as at startup or when connected to the network.

(S22) The placement acceptance execution unit 19 of the server 1 accepts a confirmation access from the user terminal 2. When receiving the confirmation access, the arrangement reception execution unit 19 refers to the row of the user's terminal 2 in the user environment information 62 using the personal ID or the like corresponding to the user's terminal 2. The arrangement reception execution unit 19 confirms the presence / absence of registration of software in a state in which the software of the terminal 2 of the user is approved and in which kitting can be executed, that is, the presence / absence of a corresponding execution module. For example, the arrangement reception execution unit 19 refers to the execution module management information 74 in association with the user environment information 62 and confirms the presence or absence of the execution module.

Alternatively, the arrangement reception execution unit 19 compares, for example, the current software environment at the time of access of the user's terminal 2 with the registration status of the software of the user's terminal 2 in the user environment information 62 and the difference therebetween. Thus, the software to be executed for kitting may be determined. In that case, the server 1 acquires and uses environment information (inventory information) at the time of access from the user terminal 2.

(S23) In S23, when the execution module corresponding to software such as an application that can execute kitting on the terminal 2 of the user is registered, the arrangement reception execution unit 19 displays a screen for the terminal 2 of the user. Then, it is confirmed whether the kitting of the type such as the addition of the application or the like is to be executed immediately. When the user immediately adds the application on the screen, the user presses an execution button, for example (S23-Y). In this case, the process proceeds to S24. As a result of the confirmation in S22, when the software that can execute kitting, that is, the execution module is not registered (S23-N), the process is terminated. In S23, when the user does not execute immediately, for example, when executing later, the user presses the corresponding button (S23-N). In this case, the process is temporarily terminated, and after a predetermined time has passed, the process returns to S23 and the same confirmation is performed. Note that the confirmation step of S23 may be omitted.

(S24) In S24, upon receiving an instruction to execute kitting in S23, the arrangement reception execution unit 19 reads out an execution module corresponding to software such as the target application from the execution module management information 74 of the software DB 51, and It transmits to the user's terminal 2. That is, the server 1 automatically distributes the execution module.

(S25) The user terminal 2 executes the processing of the program included in the execution module received from the server 1. Thereby, the user terminal 2 performs kitting, that is, construction and setting of the user environment according to the contents described in the execution module program. The contents of the kitting are additional installation and version upgrade of the target application. For example, the user terminal 2 installs software data such as a target application included in the execution module at a specified position in the terminal 2. The software data may be managed separately from the execution module. In this case, the target software data is separately downloaded from the server 1 to the user terminal 2 based on the program processing.

(S26) In S26, backup / restore processing is performed when saving or migrating user data is required in conjunction with the above-described software kitting. For example, in the case of application migration between user terminals, the backup unit 31 of the server 1 refers to the software extension list 75 and determines the extension of user data associated with the target application. Further, for example, in the case of updating due to version upgrade of the application, the backup unit 31 refers to the software extension list 75 and determines the extension associated with the old version application and the extension associated with the new version application.

The backup unit 31 stores, for example, the user data of the application of the terminal 2 before migration in the backup data 81 of the backup DB 53 based on the determination of the extension. In addition, when the user data of the application is periodically saved as the backup data 81 during normal operation, the data can be used.

The backup unit 31 reads the user data associated with the application from the backup data 81 and restores it to the migration destination terminal, for example, with installation of migration of the target application on the migration destination terminal.

(S27) In S27, the user terminal 2 reports to the server 1 information representing the status of completion or incomplete as a result of the kitting process. The server 1 receives the situation information from the user terminal 2 and reflects and records the situation information in the corresponding line of the user environment information 62 or the corresponding line of the execution module management information 74. Depending on the user's instruction, the state of the terminal 2, the state of the communication network 90, etc., a kiting incomplete state may occur.

(S28) In S28, if the above-mentioned kitting is completed or successful (S28-Y), the process is terminated, and if it is not completed or failed (S28-N), the process returns to S23 and tries kitting again.

[Examples of user environment and kitting]
FIG. 5 shows an example of user environment and kitting. FIG. 5A shows an example of updating software in a PC that is a terminal of a certain user Ua as an example of updating the user environment. The terminal of the user Ua is in a state where “OSa1” that is an OS and “application A1” and “application A2” that are applications are installed. From this state, the update contents are version upgrade by applying a correction patch of the application A1, deletion or uninstallation of the application A2, and addition or installation of the application A4. These update contents are described in the above-described setting information of the user environment kitting.

(B) of FIG. 5 shows an example of division as an example of a change in the user environment. The environment before the transition is a state in which a certain user Ub uses a PC that is one terminal. The environment after the shift by the division is a state in which the user Ub uses a PC and a tablet which are two terminals. Further, as an example, the PC that is the terminal before the transition is continuously used as the first terminal after the transition. A tablet which is the second terminal after the migration is newly added.

PC software before migration is OSa1, application A1, and application A3. The software of the PC that is the first terminal after the migration is OSa1 and the application A1, and the application A3 is deleted, that is, uninstalled. The software of the tablet that is the second terminal after the migration is OSa3 and application A3. If the app A3 can be migrated from the PC, the app A3 is installed. If the app A3 cannot be migrated from the PC, a version of the app A3 corresponding to the OSa3 of the tablet is newly installed. In addition, along with the shift due to the division of the environment, user data such as the application A3 is transferred.

In the case of the kitting setting in the above example (b), the environment division unit 32 includes a list of software of each terminal before and after the transition in the organizational asset information 61 and the user environment information 62 based on the operation of the setter. Register environment information. According to the setting, necessary kitting is performed at each terminal before and after the transition.

(C) of FIG. 5 shows an example of integration as an example of a change in the user environment. The environment before the transition is a state in which a certain user Uc uses a PC and a smartphone, which are two terminals. The environment after migration by integration is a state in which the user Uc uses a PC that is one terminal. Further, as an example, the PC that is the first terminal and the smart phone that is the second terminal before the transition are replaced with another PC. That is, a new PC is installed and used as the terminal after the transition, and the use of the terminal before the transition is stopped.

The software of the PC that is the first terminal before the transition is OSa1 and application A1, and the software of the smartphone that is the second terminal is OSa4 and application A4. The software of the PC that is the terminal after the migration is OSa2, application A1, application A4, and application A5. OSa2 is a new OS different from OSa1, and application A1 and the like are versions of applications corresponding to OSa2. The application A1 is based on the transition from the first terminal. The application A4 is based on migration from the second terminal. The application A5 is newly installed additionally. Further, user data such as the application A1 is migrated along with the migration due to the integration of the environment.

In the case of the kitting setting in the example (c) above, the environment integration unit 33 includes a list of software of each terminal before and after the transition in the organizational asset information 61 and the user environment information 62 based on the operation of the setter. Register environment information. According to the setting, necessary kitting is performed at each terminal before and after the transition.

[Kitting execution]
FIG. 6 shows a processing example when executing kitting. This example shows a case of additional installation of the application A4 as an example of updating the environment of the PC that is the terminal T21 of the user U2. As a premise, according to the setting of the user environment information 62 of the server 1, the target application A4 is registered in the software list of the terminal T21 of the user U2 based on the prior application.

The terminal T21 of the user U2 accesses the server 1 for confirmation when starting up. The arrangement reception execution unit 18 of the server 1 receives the access, refers to the software list of the terminal T21 of the user U2, and checks whether there is an app that can execute kitting. In this example, there is an application A4 that can execute kitting. Therefore, the arrangement reception execution unit 18 transmits, that is, automatically distributes the execution module corresponding to the application A4 to the terminal T21 of the user U2.

The terminal T21 of the user U2 receives the execution module of the application A4 from the server 1, and executes the processing of the execution module program. Processing includes termination of the related process, setting of installation of the application A4, storage of data of the application A4 at a specified address, activation of the related process, and the like. Thereby, the application A4 is installed in the terminal T21 of the user U2. Similarly, when the version of the application A1 is updated or the application A2 is deleted, automatic kitting using an execution module is possible.

[Organizational asset information]
FIG. 7 shows a configuration example of the organizational asset information 61. The table of the organization asset information 61 in FIG. 7 includes, as management items, organization ID, department, personal ID, user name, terminal ID, manufacturer, model number, IP address, building, floor, area, remarks, and the like. As shown in FIG. 7, the organization asset information 61 includes information on a list of terminals 2 of a plurality of users in the organization. An asset includes at least the user terminal 2 constituting the organization information system 20. Although not shown, the organizational asset information 61 can be similarly managed for other hardware such as servers and network devices.

“Organization ID” is identification information of the target organization. “Department” is identification information of a department in the organization. “Personal ID” and “user name” are identification information and names of users of the organization. “Terminal ID” is identification information of the terminal 2 used by the user. Items such as the manufacturer, model number, and IP address are each information related to the terminal 2. Items such as a building, a floor, and an area are identification information of a place where the terminal 2 is installed. “Remarks” is information of any remarks described by an administrator or the like.

Depending on the organization's information system 20 and the department or business, a plurality of terminals 2 may be assigned for each user. For example, the user U3 is assigned two terminals T31 and T32 as in the example of FIG. The server 1 collects asset or environment information (inventory information) from the server in the information system 20 or the terminal 2 of each user, and describes the collected information in the organizational asset information 61 or the user environment information 62. Good.

[User environment information]
FIG. 8 shows a configuration example of the user environment information 62. The table of the user environment information 62 in FIG. 8 includes management items such as a personal ID, a terminal ID, an OS, one or more applications, remarks, and the like. As shown in FIG. 8, the user environment information 62 includes software list information for each user terminal 2 using the user's personal ID as a key.

“Personal ID” and “terminal ID” are the same as the items of the organizational asset information 61 and are associated as keys. The “OS” item stores identification information of an OS installed in the terminal 2. One or more “application” items store identification information of applications installed in the terminal 2. In the example of FIG. 8, columns such as A1 and A2 are separately provided as a plurality of applications, but a format in which information of a plurality of applications is described in one item without being divided may be used. Although not shown, software such as middleware and device drivers can be similarly managed. “Remarks” is information of any remarks described by an administrator or the like.

For example, OSa1 and application A1 are set in the terminal T11 of the user U1. The terminal T21 of the user U2 is set with OSa1, application A1, application A2, and application A4. OSa1 and application A1 are set in the first terminal T31 of the user U3. OSa3 and application A3 are set in the second terminal T32 of the user U3.

In conventional IT resource management of organizations, hardware information as shown in the example of FIG. 7 is managed. On the other hand, in the computer environment management system of this embodiment, the user environment information 62 of FIG. 8 is managed by addition and association in the DB 50 in addition to the organizational asset information 61 of FIG. That is, the user environment information 62 manages software environment information for each individual user terminal 2 and can correspond to different configurations of OSs, applications, and the like for each individual user terminal 2. When setting the user environment kitting, the setter sets software such as an OS and an application in the corresponding row using the personal ID of the target user as a key. For example, when the application A2 is newly installed in the terminal T11 of the user U1, the setter registers the information of the application A2 in the row of the terminal T11 of the user U1.

The computer environment management system according to the present embodiment is a mechanism that automatically performs kitting so that the software environment registered in the user environment information 62 is in the state of the software list.

Although the user environment information 62 is not shown in the figure, the above-described approval / non-approval information is managed for each software such as OS and application or for each row of the user terminal. The user environment information 62 may manage a user environment including a list of current software of the user terminal 2 separately from the setting of kitting. In the user environment information 62, a status such as whether or not kitting has been completed may be managed for each software such as an OS or an application. The organizational asset information 61 and the user environment information 62 are managed as other items, such as a status for identification corresponding to the case of environment division or integration, a status for identification of the environment before and after the migration, and the like. Good.

[Pattern management information]
FIG. 9 shows a configuration example of the pattern management information 63. The table of the pattern management information 63 in FIG. 9 includes a pattern ID, a pattern name, an OS, one or more applications, remarks, and the like as management items. “Pattern ID” and “Pattern name” are pattern identification information and name. “OS” and “application” are identification information of an OS and an application constituting a combination of software. “Remarks” is information about any remarks related to the pattern.

When the user environment information 62 is set, the setter can appropriately set and use a pattern including a combination of user environment software. This facilitates the setting and reduces the work. The setter designates and registers a combination of software such as an OS and an application constituting the pattern on the screen. The user environment management unit 13 stores the registered software combination in the pattern setting information 63 as a pattern.

In the example of the pattern setting information 63 in FIG. 9, in the pattern having the pattern ID P1 and the name “master 1”, the OS that is a constituent element is OSa1. This pattern is an example of an OS image common to terminals of a plurality of users in an organization, for example. The pattern whose pattern ID is P2 and whose name is “base 1” is composed of OSa1 and application A1. This pattern is an example of software that is commonly used as a base of the greatest common divisor in a specific department. Similarly, the pattern P3 is a combination of {OSa1, application A1, application A2}, and is an example assuming a specific business use.

When setting the user environment of the user environment information 62, the setter can select from existing patterns set in the pattern management information 63, and set the pattern by applying the pattern as it is. For example, the software list of the terminal T11 of the user U1 in FIG. 8 is {OSa1, application A1}, which corresponds to the pattern P2 in FIG. The setter can set the corresponding software configuration simply by specifying the pattern P2.

Also, when setting the user environment, the setter can select from existing patterns, edit the contents of the pattern, and use it for setting the user environment. The setter can edit the contents of the existing pattern and set a new pattern. Editing includes adding and deleting apps, updating versions, and the like. The setter can also set a new pattern by selecting and combining two existing patterns. For example, {OSa1, application A1, application A2, application A4}, which is a combination obtained by adding the application A4 to the existing pattern P3, can be set as a new pattern.

[Software data and license information]
FIG. 10 shows a configuration example of the software data 71 and the license information 72. The table of software data 71 and license information 72 in FIG. 10 includes “software”, “manufacturer, product name”, “Version”, “address”, “license, contract contents”, “number of uses, amount” as management items. , “Remarks”, etc. As other items, software data size, storage capacity necessary for installation, and the like may be provided.

“Software” stores identification information of software such as an application as a key. “Manufacturer, product name” stores information on software manufacturer and product name. “Version” stores software version information. In some cases, software is identified and defined, including the version. The “address” stores an address in the software DB 52 that stores the data body of the software, an external URL, or the like.

“License, contract contents” stores information on the license and contract contents of the software. This information includes, for example, paid / free, valid period or term, number of license purchases, license type, and the like. The license type includes, for example, user fixed, machine fixed, and the like.

“Number of usages, amount of money” stores information such as the current number of software licenses used in the organization and the total amount calculated according to the number of usages. In “Remarks”, information on any remarks regarding other licenses, contract contents, etc. can be described.

[License check]
It supplements about the license check. There are various licenses and contracts. For example, a machine-fixed type license is permitted to be installed on one terminal with one license. For example, a user fixed type license is granted to one user with one license, and installation is permitted to a predetermined number of terminals. In addition, there are licenses and contracts related to software versions, such as upgrades and downgrades.

The license check unit 16 uses the organization asset information 61 and the license information 72 to manage licenses related to IT resources of the organization. The license check unit 16 manages the number of purchased licenses and the current number of uses in units such as organizations and departments. In the above-described license check process, the license check unit 16 determines whether the number of licenses exceeds the number of purchases when the application for which kitting is set is included as a license condition.

The license check function allows the organization to prevent the user environment from being in a state where the license or contract content is not satisfied, and to reduce costs by eliminating or reducing redundant licenses.

In the conventional service, when a different software environment is used for each individual user terminal, the management of the license becomes complicated, and the work is troublesome. Conventionally, when a specific application is additionally installed as common software in a common OS image as a master and managed as a master, the application is uniformly installed on a plurality of user terminals. The number of man-hours is reduced. However, since the application is installed on a user terminal that does not require the use of the application, an extra number of licenses for the application is required, and the cost of the customer is increased.

On the other hand, in the present embodiment, the license check function provides support for facilitating license management, thus reducing labor. Even if a different software environment is set for each terminal 2 of an individual user, the license check function can automatically determine whether there is a problem in terms of license. In the present embodiment, it is not necessary to add the specific app as a common app and manage it as a master. In addition, for setting a specific user environment, it is possible to set a combination pattern in which a specific application is added and cope with it.

[Combination compatibility information]
FIG. 11 shows a configuration example of the combination compatibility information 73. The table of combination compatibility information 73 in FIG. 11 includes a combination number, an OS, one or more applications, compatibility, remarks, and the like as management items. “Combination number” is an identification number of a combination of software. “OS” and “application” store software identification information. The “compatibility” stores information indicating the compatibility in the combination of the software, and is “good” or “bad”, for example. For example, a specific combination is set as “bad”, and other combinations are automatically determined as “good” or “normal”. The value of compatibility is not limited to the binary values of “good” and “bad”, and the degree of incompatibility may be set. “Remarks” can describe any remarks regarding the combination.

In the example of FIG. 11, the combination of software with the combination number 1 is {OSa1, app A2 Ver2.0}, and this combination is registered as “good” and recommended in the remarks. The combination with the combination number 2 is {OSa1, application A2 Ver3.0}, the compatibility is registered as “bad”, and non-update (Ver2.0) is recommended in the remarks. The combination with the combination number 3 is {OSa1, application A1, application A2}, and the compatibility is registered as “good” and recommended in the remarks. A combination with a combination number of 4 is {OSa1, application A2, application A3}, and the compatibility is registered as “bad”, and it is described as deprecation due to performance degradation in the remarks. A combination with a combination number of 5 is {OSa1, application A4, application A5}, and the compatibility is registered as “bad”, and the remarks state that use is prohibited due to frequent errors.

Although the combination compatibility information 73 is not shown, information such as security level, installation recommendation and prohibition can be registered even in a single software unit. The combination compatibility information 73 may be a format for managing only information on combinations that are not compatible. When it is desired to recommend a specific software combination, “good” or “recommended” may be set in the “compatibility” item.

The business administrator Us and supporter access the server 1 from the terminal 3 and update the contents of the combination compatibility information 73 as needed. Alternatively, the server 1 may collect information from an external site and update the content of the combination compatibility information 73 using the collected information. That is, in the present embodiment, know-how and experience knowledge regarding the compatibility of software combinations are accumulated as combination compatibility information 73 and used for kitting. Based on the reference of the combination compatibility information 73 and the result of the combination compatibility check, the setter can prevent setting of the user environment due to a combination with poor compatibility, and easily set a combination with good compatibility as an individual user environment or pattern. Can do. Organizations can easily build and operate user environments with high security and high performance.

[Combination compatibility check]
It supplements about combination compatibility check. In the combination compatibility check process, the combination compatibility check unit 17 refers to the contents of the combination compatibility information 73 to determine whether the compatibility is good or not, and displays the check result on the screen together with remark information. For example, when setting the update to upgrade the version of the application A2 of a user's terminal from Ver2.0 to Ver3.0, the combination compatibility check unit 17 determines that the compatibility is bad from the reference of the combination compatibility information 73 in FIG. Judgment is made and an alert that recommends non-update is output to the setter.

In addition, for example, when a combination including {OSa1, application A2, application A3} is set as software of a terminal of a certain user, the combination compatibility check unit 17 is incompatible with reference to the combination compatibility information 73 in FIG. And a deprecated alert due to performance degradation is output to the setter.

Further, for example, when a combination including {OSa1, application A4, application A5} is set as software of a certain user's terminal, the combination compatibility check unit 17 is incompatible with reference to the combination compatibility information 73 in FIG. It is determined that the use prohibition alert due to frequent errors is output to the setter. Alternatively, the server 1 may be controlled not to alert but to forcibly prohibit setting by the combination or execution of kitting by the setting.

Other examples of processing related to combination compatibility check are as follows. In a combination of a plurality of softwares, there is a mutual relationship or dependency relationship, and if the combination is to be installed and used, the combination may be registered in the combination compatibility information 73. For example, the combination with the combination number 6 is {OSa1, application A6, application A7}, and this combination is registered as “good” or “essential” in the “compatibility” item. Based on the information on the combination, for example, the combination compatibility check unit 17 indicates that installation of both the application A6 and the application A7 is recommended or required when the application A6 or the application A7 is installed alone. Output an alert. Even if a combination including one of the application A6 and the application A7 is registered as an incompatible combination, the same effect can be obtained.

In the conventional service, it is possible to update by applying a correction patch or set use prohibition, etc., by checking security for vulnerabilities etc. for each individual software. On the other hand, the computer environment management system according to the present embodiment has a function of checking compatibility of a plurality of software combinations related to setting of user environment kitting in addition to checking the security of a single software. In a conventional service, an operator such as an administrator needs to check whether there is a problem caused by a combination of software for each kitting environment of individual user terminals. On the other hand, in the present embodiment, support for facilitating management of software combinations is provided by the function of combination compatibility check, so that the labor of confirmation and the like is reduced.

[Execution module and management information]
FIG. 12 shows a configuration example of the execution module management information 74. In the table of the execution module management information 74 in FIG. 12, the management items include an execution module, target software, version, target user terminal, kitting type, arrangement date and time, arrangement status, and the like.

The “execution module” item stores identification information of the execution module and information such as an address indicating the storage location of the execution module data. The data of the execution module is stored at the position indicated by the identification information or address in the software DB 52. The execution module includes data of the target software, an execution format program, and the like. The execution module may be a correction patch or the like.

“Target software” and “Version” store identification information and version of software such as an application to be kitted. “Target user terminal” stores identification information of a user and a terminal to be kitted. The “kitting type” stores information indicating the type of kitting, and this information includes, for example, update, addition, deletion, division, integration, and the like.

The “arrangement date / time” stores the date / time of the designated arrangement and its conditions before the execution of the arrangement, and stores the date / time of the arrangement as a history after the execution of the arrangement. For example, it can be set so that execution of kitting is permitted when there is a confirmation access from the user's terminal within a specified period. The “arrangement status” stores a value representing the status of the arrangement, and this value includes, for example, “uncompleted” when not completed before arrangement, “done” when normally completed after arrangement, and the like.

[Software extension list]
FIG. 13 shows a configuration example of the software extension list 75. The table of the software extension list 75 of FIG. 13 includes, as management items, software and version items such as applications, and one or more extension items related to the software and version. For example, the extension a is associated with Ver1.0 of the application A1, and the extension a and the extension b are associated with Ver2.0 of the application A1.

[Pre-application and approval]
It supplements about prior application and approval. Various types of pre-application and approval methods can be applied depending on the organization. Examples include the following.

(1) A setter such as the administrator U0 receives a prior application regarding the use of an application etc. from an applicant such as a user. This means is optional. Upon receiving the application, the setter registers the application or the like as a kitting target on the screen of the software list of the corresponding user terminal in the user environment information 62 on the screen. The setter informs a predetermined approver about the application and the registered application, and obtains approval. The setter inputs the approval information in the row of the user terminal in the user environment information 62. The setting authority such as the administrator U0 is set with a registration authority for the personal ID or the like.

(2) A general user accesses the server 1 from the terminal 2 and registers information such as the applicant and the application to be applied on the screen of the provided service. A predetermined approver accesses the screen from the terminal 2, sees application information, and registers approval information when approving it. A setter such as the administrator U0 accesses the screen from the terminal, confirms application and approval information, and based on the information, sets the application etc. in the row of the user terminal of the user environment information 62. Register as a target. Each user is authorized for a personal ID or the like, and logs in to the service screen using the personal ID or the like.

[GUI]
In this system, the following examples are given as screens of Web pages provided by the GUI unit 11. That is, there are a service login and top screen, a user environment kitting setting screen shown in FIG. 14, a software registration screen shown in FIG. 15, a kitting execution confirmation screen shown in FIG.

The user terminal 2 accesses the server 1, and the GUI unit 11 provides a Web page for the service. The user logs in by inputting his / her personal ID or the like on the Web page displayed on the screen of the terminal 2. The server 1 searches and refers to information in the DB 50 using a personal ID or the like as a key, and provides a Web page including information corresponding to the terminal 2 of the user.

[Screen (1)]
FIG. 14 shows an example of a screen for setting user environment kitting. 14 includes an organization user environment column 100, an individual user environment column 110, a setting button 120, a pattern setting column 130, and the like. A setting person such as the administrator U0 or the administrator Us can confirm the setting of the software environment of the terminal of each user of the organization and the setting of the kitting on this screen. The setter can check and set the user environment kitting for each terminal 2 of an individual user.

In the organization user environment column 100, user environment information including a list of software of the terminals 2 of a plurality of users in the organization is displayed based on the user environment information 62 of FIG. 101 is an item for displaying and setting information of software such as a plurality of OSs and applications, and is an example in which the information is divided and displayed in columns for each application, for example. For example, OSa1 and application A1 are registered in terminal T11 of user U1. Each user terminal row has a check box in the column of each application 101.

The setter can designate the app as an installation target by turning on the check box of the target app in the row of the target user's terminal. By unchecking the check box, the application can be designated as not to be installed. The present invention is not limited to the above format, and a format may be used in which information on software targeted for kitting is input as choices, text, or the like by selecting a row of the target user's terminal.

102 indicates an item that allows a pattern to be selected for each row of the user's terminal. The setter can select a desired pattern from the list box options 102 in the row 102 of the target user's terminal, and specify the pattern as the environment of the user's terminal. The setter may specify a combination of software in the item 101, or may specify a pattern in the item 102.

103 indicates an item for setting approval information regarding the user environment. The setter can select and register approval or not by checking on / off or the like in the item 103 in the target user's terminal row. It should be noted that an approval item may be provided for each individual software.

104 shows an example of a command button related to a setting operation related to the user environment. Examples of commands include setting copy, setting deletion, environment division, environment integration, and the like. When setting the setting of a certain user environment on this screen, the setter uses the copy settings command to copy the contents of the selected existing user environment line, and the settings of the target user environment. can do. Further, the setter can edit the configuration of the software or the like in the copied content as necessary to obtain the setting contents of the target user environment. Further, the setter can delete the setting contents of the target user environment line by using the setting deletion command on this screen. Even when setting the user environment for a large number of users, the effort of the setting person is small.

The environment division and environment integration commands are processed by the environment division unit 32 and the environment integration unit 33 to set the user environment division and integration. For example, when an environment division command is executed, an environment division setting screen is displayed. The screen displays an environment including a list of user terminal software before the transition and an environment including a list of user terminal software after the transition. The setter can specify the contents of software kitting for each of the plurality of user terminals. In this case, the user environment before and after the transition may be graphically displayed on the screen as in the example of FIG. The setter is less labor-intensive even when the environment is divided or integrated.

In the column 100, the contents of the organizational asset information 61 may be displayed together, or a software registration column or a command may be provided.

In the individual user environment column 110, the setting user selects and designates the environment of an individual user terminal by personal ID, terminal ID, etc., and details of the environment of the designated user terminal are displayed in the format of Table 111, etc. Is displayed. The user environment may be specified by a line in the column 100. As the detailed information of the user environment, for example, a list of software of the user terminal is displayed in Table 111. This table 111 displays information such as version, license information, approval information, kitting type, arrangement date, arrangement status, etc., for each software row, based on the software data 71, execution module management information 74, and the like. The In the column 110, the setter can confirm the software configuration and the like of the individual user environment, and can specify details such as kitting in the individual software row.

112 displays information such as the above check result and alert regarding the individual user environment in the column 110. For example, information such as whether or not a condition such as a license is satisfied and the contents of the license are displayed as a license check result. For example, information on the quality of compatibility or remarks is displayed as a result of checking the compatibility of combinations.

The setting button 120 is a button for inputting whether to set or cancel the user environment kitting according to the contents specified and displayed in the column 100 or the column 110. When the “Set” button is pressed, the user environment management unit 13 reflects the contents of the setting in the user environment information 62 and saves it.

The pattern setting column 130 can be set as a pattern by designating a desired combination of software by the setter. The setter inputs a combination of OS and application, inputs pattern name and remark information, and presses a pattern setting button. Thereby, the user environment management unit 13 reflects and saves the setting contents of the pattern in the pattern setting information 63.

[Screen (2)]
FIG. 15 shows an example of a software registration screen. The setter can register software data and information in the software DB 52 on this screen. The screen in FIG. 15 includes a registered software list column 151 and a newly registered software column 152.

The column 151 displays a list of software registered in the software DB 52 based on the software data 71 and the like. The setter can check the registered software information.

In the column 152, information on newly registered software can be input by the setter, and the software can be registered by a registration button. The software registration unit 15 performs processing for registering software data and information in the software DB 52. The registered software can be selected as an option on the screen of FIG.

[Screen (3)]
FIG. 16 shows an example of a kitting execution confirmation screen. The screen shown in FIG. 16 is provided when the user terminal 2 accesses the server 1 to confirm the user environment and kitting. FIG. 16 shows a screen example related to the environment of the terminal T21 of the user U2. In the screen of FIG. 16, 161 displays environment information including a list of software installed in the current user terminal. 162 displays environment information including a list of software of user terminals in a registered state corresponding to the setting of the user environment information 62. That is, 161 and 162 display the user environment before and after the execution of kitting, and information such as the kitting target software and the contents of kitting in comparison. In this example, application A4 is added.

163 indicates a column including a button for checking whether the setting according to the contents of 161 and 162 is to be executed immediately or to be executed later to the setter. With the “OK (execute)” button, the server 1 executes kitting of the target software. In the case of the “execute later” button, the server 1 repeats the kitting execution confirmation after a predetermined time has elapsed. By viewing this screen, the setter can confirm the contents of the environment kitting of his / her terminal in an easy-to-understand manner, and can execute automatic kitting with a simple operation.

[Effects]
As described above, according to the computer environment management system of the present embodiment, labor, time, cost, etc. relating to management of IT resources and kitting related to the environment including hardware and software of the terminal 2 of the user of the organization. Can be reduced.

According to the present embodiment, even when there are a large number of users and terminals in the organization or when there are many changes in the user environment, the setting is easy, and the labor of kitting can be reduced. According to the present embodiment, even when a different software environment is set for each individual user terminal, the setting is easy, and labor and the like can be reduced. According to the present embodiment, setting is easy even when there is a division or integration of the user environment, and it is possible to reduce labor and the like.

According to this embodiment, it is possible to manage an organization's IT resources and kitting with a simple operation through a unified GUI screen. Work such as support for system administrators and business operators is reduced. A flexible and flexible computer environment can be constructed and operated for each information system 20 of the organization.

The present invention has been specifically described above based on the embodiments. However, the present invention is not limited to the above-described embodiments, and various modifications can be made without departing from the scope of the invention. Other embodiments include the following.

FIG. 17 shows a configuration of a computer environment management system according to another embodiment. The computer environment management system of FIG. 17 is a form in which the server 1 and the DB 50 which are elements of the service site 10 of FIG. 1 are integrated and connected in the organization information system 20. For example, one of the firewall server 91 and the business server 92 connected to the LAN 95 is configured as the server 1 having functions of IT resource and kitting management. The server 1 manages the above-described data and information in the DB 50. The administrator U0 can access and set the server 1 from the terminal 2. The administrator Us of the service site 10 can access and set the server 1 in the information system 20 from the terminal 3.

As another embodiment, the terminal 2 of each user of the organization is a processing unit 21 that is a predetermined client program as shown in FIG. 17 as a component of the computer environment management system in addition to known elements such as a Web browser. May be additionally installed. The processing unit 21 of the terminal 2 communicates with the server 1 and performs part of the above-described kitting setting and execution processing.

As another embodiment, an intermediary server for managing IT resources and kitting may be provided between the terminal 2 of each user of the information system 20 of FIG. 1 and the server 1 of the service site 10. For example, one of the firewall server 91 and the business server 92 that are elements in the information system 20 is configured as an intermediary server. When executing the kitting, the execution module is once acquired from the server 1 of the service site 10 by the mediation server, and the execution module is distributed to the terminal 2 of each user from the mediation server.

The present invention can be used for management of information systems of organizations such as companies.

DESCRIPTION OF SYMBOLS 1 ... Server, 2 ... Terminal, 3 ... Terminal, 10 ... Service site, 11 ... GUI part, 12 ... Organization asset management part, 13 ... User environment management part, 14 ... Application approval part, 15 ... Software registration part, 16 ... License check unit, 17 ... combination compatibility check unit, 18 ... arrangement preparation unit, 19 ... arrangement reception execution unit, 20 ... information system, 31 ... backup unit, 32 ... environment division unit, 33 ... environment integration unit, 50 ... DB, 51 ... Asset management DB, 52 ... Software DB, 53 ... Backup DB, 61 ... Organizational asset information, 62 ... User environment information, 63 ... Pattern setting information, 71 ... Software data, 72 ... License information, 73 ... Combination compatibility information, 74: Arrangement execution module management information, 75 ... Software extension list, 81 ... Backup data, 90 ... Communication network, 95 ... L N.

Claims

An organization user terminal, a setter terminal, and a server device that manages a computer environment for the organization user terminal;
The server device
A screen unit that accepts access from the terminal of the user and the terminal of the setter and provides a screen;
A setting unit configured to set and manage a user environment including software arranged for each user terminal of the organization as user environment information based on an operation from the setting person's terminal on the screen;
A software registration unit for registering software data and information arranged in the terminal of the user;
Along with the setting of the user environment information, a preparation unit that creates an execution module for placing the target software on the target user's terminal and constructing the user environment;
An execution unit that receives access from the user's terminal, transmits a software execution module to be placed on the user's terminal, and executes processing of the execution module on the user's terminal;
A computer environment management system for performing management including construction and change of a user environment including different software for each user terminal of the organization.
The computer environment management system according to claim 1.
The server device includes a license management unit,
The license management unit manages license information of the software, and checks whether or not a license condition associated with the use of the target software on the user terminal is satisfied according to the setting of the user environment information. The computer environment management system which outputs the check result information including the alert when not satisfy | filling to the said setting person's terminal.
The computer environment management system according to claim 1.
The server device has a combination compatibility management unit,
The combination compatibility management unit manages compatibility information related to a combination of a plurality of software based on an operation from the setter's terminal, and the target software on the user terminal is set according to the setting of the user environment information. A computer environment management system that checks compatibility of a combination of a plurality of softwares including and outputs check result information including an alert when the compatibility is poor to the terminal of the setter.
The computer environment management system according to claim 1.
The server device has an application approval unit,
The application approval unit accepts an application regarding the use of software on the user terminal,
The setting unit sets a user environment including the requested software in the user environment information,
The application approval unit registers approval information by a predetermined approver regarding the application software or the user environment including the software, and sets the user environment including the approved software, or builds by the setting. A computer environment management system that allows execution.
The computer environment management system according to claim 1.
The setting unit sets a pattern related to a user environment including software of the user's terminal based on an operation from the setting person's terminal on the screen, and sets the user environment by selecting the pattern A computer environment management system having a setting function.
The computer environment management system according to claim 1.
The setting unit selects and copies the content of the user environment setting including the software of the first user's terminal based on the operation from the setter's terminal on the screen, and the setting content or the A computer environment management system having a setting copy function for setting a user environment of a terminal of a second user using contents edited by a setter.
The computer environment management system according to claim 1.
The server device has a backup unit,
When the user environment including the user terminal software is changed, the backup unit stores the user data backup data of the user terminal software before the change in the DB, and uses the DB backup data, A computer environment management system for transferring user data of the software to a user terminal after change.
The computer environment management system according to claim 1.
The server device includes an environment dividing unit,
The environment dividing unit, when setting the user environment information by the setting unit, when dividing the user environment from an environment including software of one terminal to an environment including software of each of a plurality of terminals, A computer environment management system configured to set an environment including software to be arranged in each of the plurality of terminals based on an operation from the setting person's terminal on the screen.
The computer environment management system according to claim 1.
The server device has an environment integration unit,
The environment integration unit, when setting the user environment information by the setting unit, the screen when the user environment is integrated from an environment including software of a plurality of terminals into an environment including software of one terminal. The computer environment management system which sets the environment containing the software of the object of arrangement | positioning of the said 1 terminal based on operation from the said setting person's terminal in.
The computer environment management system according to claim 1.
The setting unit sets and manages organization asset information including a list of user terminals constituting the organization information system based on an operation from the setter's terminal on the screen, and manages the organization asset. A computer environment management system for managing information relating to a user terminal of information and information relating to the user terminal of the user environment information in association with each other.
The computer environment management system according to claim 1.
When the execution unit receives access from the user terminal, the execution unit confirms the presence or absence of an execution module of the software to be arranged on the user terminal, and the screen includes the current user terminal software. The environment information and the user environment information including the target software of the user terminal arrangement after the change by the setting of the user environment information are displayed in comparison, and the target software arrangement is performed according to the execution instruction by the user A computer environment management system.