JP2009116517A - Terminal management device and terminal management program - Google Patents

Abstract

<P>PROBLEM TO BE SOLVED: To provide a terminal management technology for grasping a use state of an executable file in a terminal 1 connected through a network 2 in easily understandable forms. <P>SOLUTION: A terminal management device 3 for acquiring an operation log in a terminal and terminal operation information associated with the operation log through a network is provided with: an executable file information recording part 42 for recording the executable file information relevant to the executable file introduced to the terminal; a start information acquisition part 34a for acquiring start information specifying the executable file started by the terminal from the operation log; an association part 36b for associating the executable file information with the terminal operation information of the terminal which starts the executable file based on the start information; and a browsing screen generation part 36a for generating a browsing screen displaying the executable file information and the terminal operation information associated by the association part. <P>COPYRIGHT: (C)2009,JPO&INPIT

Description

  The present invention relates to a terminal management technique for acquiring an operation log in a terminal and terminal operation information related to the operation log via a network.

  As a technology for managing software installed on a terminal by a server, the server includes management means for managing software management information by associating software information already provided to the terminal with information specific to the terminal. The software management information includes the date and time information of the software installation. When there is a software uninstallation request from the terminal, the software management information is checked and a command for uninstalling the software is displayed. A system for issuing to a terminal is known (for example, see Patent Document 1). In this prior art, information on software installed on the terminal is recorded on the server side as software management information, so the server installation date and information on the installation destination terminal can be grasped on the server side. However, it is impossible to grasp the daily usage status of software.

  In addition, as a technology for managing the usage status of ASP (Application Service Provider) -compatible software installed on the terminal, a software library that can be dynamically linked is added to the required location of the application program to establish a network. By providing a connection function and sending the user usage information from the user terminal device to the server in this software library, the software provider can provide continuous and reliable user usage information to the network. And a technique for displaying and printing graphs and tables for analyzing and analyzing the usage frequency and usage time of all users regarding the ASP-compatible software (see, for example, Patent Document 2) ). With this conventional technology, the usage status of a specific application program embedded with a software library that transfers usage status to the server can be ascertained on the server side. Since such a software library is not embedded, this technique cannot be applied to a general terminal installation application program management technique.

In a system in which the remote control server and client terminal are connected via a communication network, the monitor screen displayed on the monitor is transmitted to the remote control server and received by the remote control server when the operator remotely operates the terminal. The captured image recording means of the remote control server records the monitor screen of the client terminal as a captured image in the operation log at a predetermined interval, and after this recording, There is one in which a log reproduction processing unit reproduces a captured image (monitor screen) recorded in an operation log (see, for example, Patent Document 3). In this prior art, it is possible to monitor the operation of the terminal by reproducing the captured image stored in the data storage unit on the monitoring monitor, but the contents such as what program is running on the terminal It is difficult to grasp.

JP 2002-258968 (paragraph number 0015-0016, FIG. 1) JP 2003-271256 A (paragraph numbers 0034, 0051, 0062, FIG. 2) JP 2006-108947 A (paragraph numbers 0019, 0020, 0051, 0062, FIG. 2)

  In view of the above situation, an object of the present invention is to provide a terminal management technique that can grasp the usage status of an executable file such as an application program installed in a terminal connected via a network in an easy-to-understand form. is there.

  In a terminal management apparatus that acquires an operation log in a terminal and terminal operation information related to the operation log via a network, in order to solve the problem, in the present invention, execution related to an executable file installed in the terminal An executable file information recording unit that records executable file information, a startup information acquisition unit that acquires startup information that identifies an executable file running on the terminal from the operation log, and the startup information based on the startup information, An associating unit that associates executable file information with terminal operation information of a terminal that is running the executable file, and generates a browsing screen that displays at least the associated executable file information and terminal operation information in association with each other. A browsing screen generation unit.

  According to this configuration, the executable file information related to the executable file installed in the terminal is recorded in the executable file information recording unit. Furthermore, the activation information acquisition unit detects the executable file being executed from the operation log acquired from the terminal via the network, so that the activation information indicating the activation of the executable file in the specific terminal can be obtained. Furthermore, the associating unit associates the executable file information based on the startup information with the terminal operation information of the terminal that is running the executable file, and the browsing screen generating unit associates the executable file information with the terminal. Operation information can be displayed. As a result, the administrator can grasp the list of executable files installed on the terminal together with the terminal operation information of the terminal that has started the executable file, or start the executable file through the browsing screen. It is easy to grasp all the terminals that are present and to grasp only the executable file that is being activated.

  In one preferred embodiment of the present invention, the terminal operation information includes an operation image obtained by capturing an operation screen on the terminal. As a result, it is possible to grasp the situation at the terminal in which the specific executable file is activated in a more easily understandable form.

  The technical features of the terminal management apparatus according to the present invention described above can also be applied to similar terminal management programs and terminal management methods. For example, in a terminal management program for a terminal management apparatus that acquires an operation log in a terminal and terminal operation information related to the operation log via a network, executable file information related to an executable file installed in the terminal A function for recording the executable file information and the executable file based on the startup information. The computer realizes a function of associating the terminal operation information of the terminal being made and a function of generating a browsing screen for displaying at least the associated executable file information and the terminal operation information in association with each other. Naturally, such a terminal management program can also obtain the effects described in the above-described terminal management apparatus, and can further incorporate the above-described additional technology.

[First Embodiment]
Hereinafter, a first embodiment of the present invention will be described with reference to the drawings. In the system using the terminal monitoring apparatus of the present invention, as shown in FIG. 1, a terminal 1 to be managed is connected to a terminal management apparatus 3 via a network 2. This network may be a WAN such as the Internet, or a LAN constructed in a company or a specific group. Each terminal 1 includes a monitor 51 for displaying various types of information and an input operation device 52 such as a keyboard and a mouse. The terminal management apparatus 3 also includes a monitor 55 and an input operation device 56.

   FIG. 2 shows a functional block diagram of the terminal management apparatus 3 and the terminal 1 constituting this computer network system. The terminal 1 is configured by a general-purpose computer, and acquires an operation of the input operation device 52 by an operator and displays various information on the monitor 51. The operation screen displayed on the monitor 51 is captured and an operation image is captured. And an operation log generation unit 15 that generates an operation log representing the content of the operation on the terminal 1.

  The terminal 1 includes user identification information for identifying an operator such as an operator name and an operator code input through a login operation performed before the operator uses the terminal 1, and terminal identification information for identifying the terminal 1. Is transmitted to the terminal management device 3 as terminal information. The terminal management device 3 records and manages the received terminal information in a terminal information recording unit (not shown). By managing the user identification information sent from the logged-in terminal 1 in this way, the terminal management device 3 can identify the operator who is using the terminal 1 at that time. As the terminal identification information, information that can uniquely identify the terminal 1, such as a code uniquely assigned to each terminal 1, a terminal name, a MAC address, and an IP address can be used.

  In addition, various executable files are introduced into each terminal 1, but executable file information that is information related to these executable files is managed by the terminal management device 3. This executable file information may be transferred from the terminal to the terminal management device through the program management function of the OS of the terminal, or may be collected from the terminal management device to the terminal. Further, the executable file information may be transferred and recorded in the executable file information recording unit based on the executable file introduction information collected from the terminal in a questionnaire format, or additional information may be manually input later. Furthermore, an executable file and its executable file information may be extracted by searching all data storage units such as a hard disk of each terminal. Note that the executable file can be introduced into the terminal in various forms such as downloading via a network, copying and pasting from a CD or DVD, as well as installation using an installation program. In this embodiment, an executable file refers to a file for executing processing represented by an application program, and executable file information includes, for example, an executable file name, a common name, a program type, an icon, and a created file extension. Providing information that identifies the executable file, such as the type, nature, and system of the executable file, such as a child, terminal identification information of the terminal where the executable file is installed, executable file setting information, and executable file This is not limited to this.

  In each terminal 1, every time a terminal operator performs some operation, an operation log representing the contents of the operation is generated and sent to the terminal management device 3 via the network 2. In the present embodiment, the operation log describes the contents of each operation action in the terminal 1 and includes an operation type and operation target information. In this embodiment, the operation target information includes the executable file name and the file attribute information of the file being processed by the executable file. The file attribute information uses the file name. It is not limited to. In each terminal 1, an operation image displayed on the monitor 51 of the terminal is captured at a predetermined timing, and an operation image is generated and sent from the terminal 1 to the terminal management device 3 via the network 2. Here, the predetermined timing is a point in time when a specific operation is performed, a predetermined time interval, or the like, but is not limited thereto. Note that the operation log and the operation image are also appended with the terminal identification information of the terminal 1 on which this operation was performed and a time stamp indicating the date and time when the operation was performed. In the present embodiment, the terminal information and the operation image are individually transmitted. However, when the operation image is transmitted, the terminal information and the operation image may be transmitted in a format to which the terminal information is added.

  The terminal management device 3 is also generally constituted by a general-purpose computer, and most of the functions related to the present invention in the terminal management device 3 are created when a terminal management program installed in the terminal management device 3 is started. As representative of them, an operation image sent from the terminal 1 is acquired, an operation image recording unit 33 for recording and managing, an operation log sent from each terminal 1 is acquired, and evaluation is performed for each terminal. An operation log evaluation unit 34 that obtains information such as an executable file during startup in the terminal 1, the executable file information managed by the terminal management device 3, the terminal 1 in which the executable file is introduced, and the terminal 1 A management screen generation unit 36 that generates a screen for displaying a list of terminal operation information on the monitor 55 is exemplified. In the present invention, the terminal operation information refers to the terminal information and the operation image described above. However, the present invention is not limited to this, and other information is replaced by these as long as the object of the present invention is achieved. Alternatively or additionally, it may be used as terminal operation information.

  Furthermore, an executable file information recording unit 42 that records and manages executable file information of executable files installed in each terminal 1 is constructed in the terminal management device 3. The executable file information recording unit 42 records information about executable files installed in all the terminals 1 belonging to the computer network system. By requesting the executable file information recording unit 42, It is possible to obtain a list of terminal names in which arbitrary executable files are introduced, and conversely, executable file names introduced in arbitrary terminals 1.

  In addition, the operation log evaluation unit 34 extracts the activation information for identifying the executable file activated on each terminal 1 from the operation log sent from the terminal 1 and writes the activation information in the activation information table 44. An information acquisition unit 34a is included. The activation information in the present embodiment includes terminal identification information, operation target information, and a time stamp. If the operation type of the received operation log is “activation”, new activation information related to the operation log is generated and recorded in the activation information table. If it is “finished”, execution related to the operation log is performed. The activation information whose possible file name and file attribute information match is deleted from the activation information table 44. However, the generation and deletion of the activation information are not limited to the operation log operation types described above, and may be performed when obtaining operation logs of other operation types. By managing the activation information in this way, it is possible to manage the executable file activated in each terminal 1 and the file attribute information processed by the executable file. With such a configuration, it is possible to display the file attribute information of the file that is being processed by the executable file that is being activated along with the terminal information on the browsing screen.

  Further, the management screen generating unit 36 associates each executable file information recorded in the executable file information recording unit 42 with the terminal operation information related to the terminal 1 that starts the executable file. A browsing screen generation unit 36a that generates a browsing screen that displays executable file information and terminal operation information based on this association is included. First, the associating unit 36b selects one executable file name from the executable file information recording unit 42, and extracts startup information related to the same executable file name as the selected executable file name from the startup information table 44. . Next, terminal operation information having the same terminal identification information as that of the extracted activation information is extracted. This process associates the selected executable file with the terminal operation information. By performing this process on all the executable files recorded in the executable file information recording unit 42, it is possible to realize the association between the executable file information and the terminal operation information. When an operation image is used as the terminal operation information, the terminal operation information corresponding to the activation information can be extracted based on the terminal identification information and the time stamp of the activation information. It is also possible to extract and display an operation image at the time when a specific operation is performed, such as when an executable file is started based on the time stamp. Furthermore, the operation image to be displayed is not limited to the one acquired as described above, and the operation image acquired at the time of association can also be used. By configuring in this way, the operation in real time can be confirmed. can do.

  Next, in the system composed of the terminal 1 and the terminal management apparatus 3 configured as described above, the usage status of the executable file installed in the terminal 1 through the monitor 55 of the terminal management apparatus 3 is described with reference to the flowchart of FIG. The procedure for checking will be described. First, in the executable file information recording unit 42, executable file information of executable files installed in all terminals 1 belonging to the system is recorded as schematically shown in FIG. To do.

  First, the operation log evaluation unit 34 acquires an operation log (see the upper part of FIG. 4) sent from each terminal 1 (# 01). When the terminal identification information and the executable file name acquired from the acquired operation log are recorded in the executable file information recording unit 42 (Yes branch of # 02), the activation information acquisition unit 34a is given. The terminal identification information, the executable file name, and the operation file name are acquired from the operation log, and the activation information is created (see the middle part of FIG. 4) and written in the activation information table 44 (# 03). At this time, user identification information can be acquired from a terminal information recording unit (not shown) using terminal identification information related to the operation log as a key, and included in the activation information. As described above, the operation log evaluation unit 34 creates the activation information based on the operation logs sequentially acquired, and updates the activation information table 44 that dynamically changes based on the created activation information.

  In the management screen generation unit 36, the association unit 36b associates the terminal operation information and the executable file information by the above-described processing based on the contents of the activation management table (# 04). The lower part of FIG. 4 schematically represents the association between the executable file information and the terminal operation information via the startup information created by the above-described processing. Thereafter, the browsing screen generation unit 36a creates various browsing screens that can easily check the usage status of the executable file installed in the terminal 1 based on the association of the associating unit 36b (# 05). ), And can be displayed on the monitor 55.

  FIG. 6 illustrates the most basic browsing screen, in which an executable file name and the number of terminals that have installed the executable file are displayed in association with each executable file.

  In FIG. 7, in addition to the association display of FIG. 6, the terminal operation information of the terminal 1 that is currently activating the executable file identified by each executable file name is associated with the executable file name in the right end area. It is displayed in a display form that connects with a line. As the terminal operation information here, a terminal name as terminal identification information, which is one of the terminal operation information, and an operation image at the terminal are displayed. In this browsing screen, the display of the number of executable files introduced may be omitted.

  Also, if there are a large number of terminals running the executable files listed, it will not be possible to see the monitor image and it will be difficult to see, so only the terminal operation information of the terminal that is running the specific executable file is displayed. It is good to do so. FIG. 8 shows such a browsing screen, in which a terminal name and an operation image are displayed as terminal activation information of a terminal that is activating the startable file “XY Shop 2004”. It should be noted that the terminal 1 displayed on the browsing screen is displayed in units of a group to which some terminals 1 belong, such as a department group, or the terminal 1 is specified in units of groups and the browsing screen is displayed. It may be. Thus, on the browsing screen, at least one of the executable file information described above and at least one of the terminal operation information are displayed in association with each other, thereby improving visibility. In these examples, the association is expressed by a line, but is not limited to this, and other graphic symbols may be used.

  Further, since the file attribute information of the file processed by the executable file has been acquired by the startup information acquisition unit 34a, as shown in FIG. 9, the terminal that is starting the specific executable file on the browsing screen In addition to the terminal name and the operation image, the file attribute information of the file operated by the executable file can be displayed. As a result, the administrator can easily grasp what kind of file is being operated by the specific terminal 1 that is starting the specific executable file. It is also possible to check for appropriate actions quickly and reliably.

  In the description of the above embodiment, the list of the names of the terminals that have started the executable file for each executable file name on the browsing screen is displayed. However, the type and attribute information of the executable file or the operation of the executable file You may employ | adopt the structure which displays as a list the information regarding the terminal corresponding to it for every conditions. For example, when the executable file to be displayed is a web browser or the like, the URL currently being accessed is a specified unit, and the name of the terminal accessing the URL for each URL may be displayed as a list. From the viewpoint of

[Second Embodiment]
In the browsing screen of the first embodiment described above, a window created by an executable file may be active or inactive. In order to clearly distinguish these states, in this embodiment, in addition to the function unit of the first embodiment, the terminal management device 3 can be executed during activation based on the activation information acquired by the activation information acquisition unit 34a. A window display form determination unit 34b that determines from the operation log whether the window created by the file is active is provided. The terminal 1 generates an operation log related to the operated executable file and transmits it to the terminal management apparatus 3. At this time, the window display form determination unit 34b is active in the executable file window related to the received operation log among the startup information of the terminal 1 recorded in the startup information table when the operation log is received, It is determined that the windows of the other executable files are inactive, and the activation information table 44 is updated.

  Since the flow of the process of this embodiment is the same as that of the first embodiment except for the process of the browsing screen generation unit 36a, the description is omitted. The browsing screen generation unit 36a in the present embodiment depends on whether the window of the executable file included in the operation image of the terminal operation information displayed in association with the executable file information is active or inactive. , Change the display form of the association. For example, as shown in FIG. 10, association display is performed with a solid line when active, and display with a dotted line when inactive.

  As described above, in the present embodiment, the display form is changed depending on whether the window of the executable file is active. Thus, how each executable file is operated in each terminal 1. It is possible to grasp easily.

  In the above-described embodiment, operation logs and operation information including operation images in a large number of terminals 1 are sent to the terminal management apparatus 3 via the network 2, and the above-described monitor 55 of the terminal management apparatus 3 is connected to the monitor 55. The browsing screen is displayed. In such a terminal management system, a function necessary for the management apparatus is a function of the management screen generation unit 36. Therefore, a system in which other data servers have functional units other than the management screen generation unit 36 included in the terminal management device 3 described above can be provided. It is also possible to construct the management screen generator 36 in each terminal 1.

  The term operation image used in this specification refers to a still image file obtained by capturing an operation screen, a collection of still image files, and a moving image obtained by converting continuous still images into animations. A collection of files and video files. Therefore, the operation image transferred from the terminal 1 to the terminal management apparatus 3 may be a still image or a moving image. Also, when the operation image is introduced into the browsing screen, a still image called a slide show may be continuously displayed or a moving image may be displayed. For this reason, various types of operation image formats can be selected when recorded in the operation image recording unit 33. For example, JPEG or GIF is used for still images, and MPEG or AVI is used for moving images. As for the transmission form of such operation images from the terminal 1 to the terminal management apparatus 3, it may be performed in real time or by batch processing.

System configuration diagram of a terminal management system using a terminal management apparatus according to the present invention Functional block diagram showing an example of a terminal and a terminal management apparatus in a computer network system incorporating the terminal management technology according to the present invention Explanatory drawing explaining the data structure of an executable file information table typically Explanatory drawing which explains typically the procedure which creates the start management table which changes dynamically from the operation log, and associates The flowchart showing the flow of processing of the terminal management apparatus by this invention Screen diagram showing an example of the browsing screen Screen diagram showing an example of the browsing screen Screen diagram showing an example of the browsing screen A screen view showing another example of the browsing screen Explanatory drawing when introducing the association display based on the display form of the window to the browsing screen

Explanation of symbols

1: terminal 2: network 3: terminal management device 10, 30: GUI unit 14: operation screen capture unit 15: operation log generation unit 33: operation image recording unit 34: operation log evaluation unit 34a: activation information acquisition unit 34b: window Display form determination unit 36: management screen generation unit 36a: browsing screen generation unit 36b: association unit 42: executable file information recording unit 44: activation information table 55: monitor

Claims (3)

In a terminal management apparatus that acquires operation logs in a terminal and terminal operation information related to the operation logs via a network,
An executable file information recording unit for recording executable file information related to an executable file installed in the terminal;
An activation information acquisition unit for acquiring activation information for identifying an executable file activated on the terminal from the operation log;
An association unit that associates the executable file information with terminal operation information of a terminal that is starting the executable file, based on the startup information;
A browsing screen generator for generating a browsing screen for displaying at least the associated executable file information and terminal operation information in association with each other;
A terminal management device. The terminal management apparatus according to claim 1, wherein the terminal operation information includes an operation image obtained by capturing an operation screen on the terminal. In a terminal management program for a terminal management device that acquires operation logs in a terminal and terminal operation information related to the operation logs via a network,
A function for recording executable file information related to an executable file installed in the terminal;
A function of acquiring start information for specifying an executable file started on the terminal from the operation log;
A function for associating the executable file information with terminal operation information of a terminal that is starting the executable file based on the startup information;
The terminal management program which implement | achieves the function which produces | generates the browsing screen which links | relates and displays the said executable file information and terminal operation information linked | related at least with the computer.

Images