JP5216531B2 - Information processing system, information processing apparatus, information processing method, and computer program - Google Patents

Description

  The present invention relates to a system, apparatus, method, and program for maintaining a client computer. More specifically, the present invention relates to an information processing system, an information processing apparatus, an information processing method, and an information processing system for realizing a net boot function in a network setting similar to that of a terminal previously used at the time of thin client terminal replacement. Regarding the program.

  In recent years, companies and universities have increasingly introduced thin client systems. A thin client system is a terminal (client device) used by employees, students, etc., which has the minimum functions such as input and display. This is a system that manages (stores and controls) data such as files and resources used by a server device.

  Typical thin client systems include "Network Computer" from Oracle (registered trademark), "Windows (registered trademark) Terminal" from Microsoft (registered trademark), and "Sun Ray (registered trademark)" from Sun Microsystems. and so on.

  Generally, a terminal used by a user in a thin client system (referred to herein as a “thin client terminal”) does not store application software and various data in a large-capacity storage medium such as a hard disk. Therefore, the thin client system has an advantage that the risk of leakage of information stored in the hard disk of the terminal disappears due to the loss of the thin client terminal. Therefore, a computer that is a thin client terminal does not have to include a large-capacity storage medium.

  Furthermore, there are significant advantages such as the reduction of the introduction cost by distributing high-performance computers to each employee and the reduction of operation and management burdens related to the installation work and version upgrade work of complicated application software.

  As described above, in the thin client terminal, application programs and various data necessary for using the computer are not stored in a large-capacity storage medium such as a hard disk, and are stored in the server device. For this reason, when using a thin client system, connection to a network is essential.

  The various network settings required for network connection are often performed by the support person on the side that delivered the thin client system. In the initial setting of the thin client terminal, it is often the case that the network is set up locally at the installation site of the thin client system. In addition, as described in Patent Document 1, maintenance service after the setting is completed, for example, version upgrade of application software, data backup, etc., may be performed remotely by a person in charge without going to the site. .

JP 2008-15913 A

  However, when the thin client terminal has to be replaced due to a failure or the like, the invention disclosed in Patent Document 1 has a problem that a quick response cannot be performed. In other words, when installing a new thin client terminal in place of a failed thin client terminal, in addition to replacing the thin client terminal, various network settings must be changed along with the replacement. There was a problem that it took time and effort.

  It is also possible to change the network settings if there is a system administrator with a wealth of network knowledge. However, if the administrator's knowledge is insufficient, the support staff will visit the site and work. I have to do it and I cannot respond quickly. In addition, there has been a problem that some users cannot use the thin client terminal until the network setting change work accompanying the replacement of the thin client terminal is completed.

  Furthermore, in companies and universities, network devices are installed and communication management is performed so that client terminals such as personal computers owned by individuals do not participate in the network of companies and universities. In such a case, there is a problem that it is very difficult for a person with poor network knowledge to change the settings of these network devices.

  In particular, in universities and the like, all terminals in a classroom are forcibly turned off when a predetermined time comes in order to limit the use of computers outside the time. At this time, instead of going to the classroom and turning off the power one by one, the power is turned off by transmitting a power-off operation instruction to each thin client terminal from the remote. In universities and the like, since classrooms are used for different times, it is important to appropriately manage information indicating which thin client terminals are installed in which classrooms.

  The present invention has been made in view of such a problem, and an information processing system that can easily perform various network settings accompanying replacement of a terminal due to a failure without particularly requiring network knowledge, An object is to provide an apparatus, a method, and a program.

  Still another object of the present invention is to provide an information processing system, apparatus, method, and program that make it possible to easily manage the installation location of a terminal when the terminal is changed due to a failure.

In order to solve the above-described problems, an information processing system according to the present invention has the following configuration. That is, the invention according to claim 1 is a plurality of network devices including a first network device that stores information for performing startup setting of a thin client terminal, and an information processing apparatus that manages the plurality of network devices The information processing apparatus stores management information in which a thin client terminal connected to a network and a network device that manages setting information related to the thin client terminal are associated with each other. A first storage means, a first thin client terminal connected to a network, a first reception means for receiving a designation of a second thin client terminal to be replaced with the first thin client terminal; Having setting information related to the first thin client terminal received by the first receiving means; Specifying means for specifying a number of network devices, and setting information related to the first thin client terminal managed by the network device for each of the plurality of network devices specified by the specifying means. Requesting means for making a change request to change to setting information related to the client terminal, wherein the first network device stores a second storage means for storing an installation image used for starting the thin client terminal; Third setting means for storing information of a thin client terminal that permits use of an installation image stored in the second storage means as setting information for performing start setting of the thin client terminal, and the request means In response to the request by the first storage means stored in the second storage means First changing means for changing information on the client terminal to information on the second thin client terminal, second receiving means for receiving a request to use the installation image from the thin client terminal, and the second Whether or not the thin client terminal that has made the request permits the provision of an installation image to the thin client device according to the setting information stored in the third storage unit after the reception unit has received the use request And a providing unit that provides the installation image to the thin client terminal when it is determined to be permitted by the determining unit, and the setting information is changed by the first changing unit. The second thin of the installation image provided to the first thin client terminal Since the provision to the client terminal is permitted by the determination unit, a startup process according to the installation image performed on the first thin client terminal before the change of the setting information is performed on the setting information. Is executed by the second thin client terminal after the change, and the setting of the first thin client terminal is taken over by the second thin client terminal .

According to this configuration, it is possible to perform the easy changing of various network settings associated with the replacement of the thin client terminal.

The invention according to claim 2 is an information processing apparatus that manages a plurality of network devices, a thin client terminal connected to a network, a network device that manages setting information related to the thin client terminal, The first storage means for storing the management information associated with the first thin client terminal, the first thin client terminal connected to the network, and the designation of the second thin client terminal to be replaced with the first thin client terminal A first receiving unit that receives the setting information, a specifying unit that specifies a plurality of network devices having setting information related to the first thin client terminal received by the first receiving unit, and the plurality of specified by the specifying unit For each network device, the first thin client managed by the network device Requesting means for making a change request to change the setting information related to the second thin client terminal to the setting information related to the second thin client terminal, and the network device has setting information for performing activation setting of the thin client terminal The first network device stores the installation image used for starting the thin client terminal, and the start setting of the thin client terminal. As setting information for the above, a third storage unit that stores information of a thin client terminal that permits the use of the installation image stored in the second storage unit, and in response to a request by the request unit, 2 stores the information of the first thin client terminal stored in the second storage means. A first changing means for changing to information on the client terminal; a second receiving means for receiving a use request for the installation image from the thin client terminal; and after the second receiving means receives the use request, A determination unit that determines whether the thin client terminal that has made the request permits the provision of an installation image to the thin client device according to the setting information stored in the third storage unit; Providing means for providing the installation image to the thin client terminal when it is determined to be permitted, and provided to the first thin client terminal by changing the setting information by the first changing means. Provision of the installed image to the second thin client terminal When the setting information is changed, the startup process according to the installation image performed in the first thin client terminal before the change of the setting information is changed to the second thin client terminal after the change of the setting information. The setting of the first thin client terminal is carried over to the second thin client terminal.

  According to the present invention, it is possible to easily perform various network settings accompanying replacement of a thin client terminal due to a failure or the like without particularly requiring network knowledge. In addition, it is possible to appropriately manage the location information of the thin client terminal after the change.

  Hereinafter, an embodiment of the present invention will be described with reference to the accompanying drawings. For convenience of explanation, Mac OS (registered trademark) X of Apple (registered trademark) will be described as an example, but this is not intended to limit the scope of application of the technical idea of the present invention.

  FIG. 1 is a diagram showing a configuration of an information processing system according to an embodiment of the present invention. The information processing system has each component described below.

  The management server 101 has a management database (DB) 600, stores information such as the thin client terminal 107, the NetBoot server 102, and the switch 103, and performs centralized management. Details of the stored information will be described later with reference to FIG. In addition, the management server 101 provides a terminal management function to the management terminal 104.

  The NetBoot servers 102-1 to 102-3 are NetBoot servers (in this specification, these are collectively referred to as the NetBoot server 102), and provide the NetBoot service and the DHCP service to the thin client terminal 107. Further, the NetBoot server 102 includes DHCP service static mapping setting information 800 and NetBoot server filter setting information 810 shown in FIG. NetBoot refers to a mechanism that can start up and control a client computer through a network, among the functions of MacOS X Server.

  The switches 103-1 to 103-3 are L2 switches (SW) (in this specification, these are collectively referred to as SW103), and determine and transfer data packets in the data link layer of the OSI reference model. Execute the communication control to be performed. The SW 103 is a communication control device that couples the NetBoot server 102 and the thin client terminal 107. The SW 103 has SW filter setting information 700 shown in FIG. 7 (details will be described later with reference to FIG. 7), and can control the connectable thin client terminal 107 by performing filter setting.

  The management terminal 104 is a terminal device used by a system administrator (administrator user) who uses the terminal management function provided by the management server 101, and is equipped with a Web browser as standard. The DNS server 105 is a server that stores a correspondence table of IP addresses and computer host names. The file server 106 is a server device that provides a file sharing service to each thin client terminal.

  The thin client terminals 107-1 to 107-6 are thin client terminals (in this specification, these are collectively referred to as the thin client terminal 107) used by terminal users (general users), and are large disks such as hard disks. Various data created and used by business applications or the like are not stored in the capacity storage medium. Therefore, the thin client terminal 107 mounts the shared area of the file server 106 as a storage destination of various data at the time of activation. Therefore, the terminal user (general user) can always use the same home area regardless of which thin client terminal is used.

  The devices 101 to 107 are connected to each other via a network 108 such as a LAN (Local Area Network) so that they can communicate with each other. The network 108 may be any type of network other than a LAN, such as a WAN (Wide Area Network), a dedicated line, and the Internet, and is not particularly limited.

  FIG. 2 is a block diagram illustrating an embodiment of the hardware configuration of the management server 101.

  The CPU 201 comprehensively controls the devices 202 to 210 connected to the system bus 211, and is controlled by an operating system (OS) that is a control program. The RAM 202 is a main memory (main storage device) of the management server 101, and also functions as a work area, a temporary save area, and the like. The ROM 203 is a read-only storage device, and stores a boot program that is a program that does not need to be rewritten.

  The input control unit 204 controls input from the input unit 205 such as a pointing device such as a keyboard or a mouse. A display control unit 206 controls display by a display unit 207 such as a CRT monitor or a liquid crystal monitor.

  The external memory control unit 208 controls access to the external memory 209 that stores data such as the OS, programs for realizing each function of the management server 101, various databases (DB), files, applications, master files, user files, and the like. To do. In the external memory 209, various tables for realizing each function of the management server 101 are stored. Examples of the external memory 209 include a hard disk (HD), a flexible disk (FD), a compact flash (registered trademark) that can be connected to a PCMCIA card slot via an adapter, smart media, and the like.

  In the information processing in the present embodiment, a program recorded in the external memory 209 by the CPU 201 is loaded into the RAM 202 as necessary, and the CPU 201 executes the program.

  The communication control unit 210 executes communication control processing with an external device via the network 108 such as a LAN or the Internet.

  The above is an example of the hardware configuration of the management server 101. Since the NetBoot server 102, the DNS server 105, and the file server 106 have substantially the same hardware configuration, detailed description of these hardware configurations is omitted. To do. Since the thin client terminal 107 can of course be configured by a computer that does not have an external memory such as a hard disk, the external memory control unit 208 and the external memory 209 may not be included in the configuration of FIG.

  FIG. 3 is a block diagram showing a functional configuration of the management server 101 according to the embodiment of the present invention. The storage unit 301 stores various types of data related to the terminal device, which will be described later with reference to FIG. 6, that is, individual information of each thin client terminal 107 and information such as the SW 103 and the NetBoot server 102 used by each terminal 107.

  The screen information generation unit 302 generates screen information for accepting designation when the terminal 107 fails, and screen information for designating a maintenance terminal to be exchanged with the malfunctioning terminal. Specific examples of screens based on the screen information generated by the screen information generation unit 302 are shown in FIGS.

  The accepting unit 303 accepts designation of a faulty terminal designated via a screen based on screen information and a maintenance terminal exchanged with the faulty terminal. The specifying unit 304 specifies a network device (for example, SW103) associated with the failed terminal received by the receiving unit 303 and a server device (for example, the NetBoot server 102) that provides a service to the failed terminal. This specification is performed using various data related to the terminal device shown in FIG.

  The request unit 305 makes a request for changing the setting information managed by the network device or the server device. The update unit 306 performs various data update processing stored and managed by the storage unit 301 in accordance with the replacement of the terminal 107.

  Before explaining the processing at the time of replacing the thin client terminal 107 according to the embodiment of the present invention, the activation processing of the thin client terminal 107 will be described with reference to FIG. Unlike a normal computer, the thin client terminal 107 does not store all or part of a program necessary for activation on a large-capacity storage medium such as a hard disk. For this reason, the thin client terminal 107 acquires an installation image on the network and performs various settings according to the control.

  When the thin client device 107 receives a power-on instruction, the thin client device 107 loads machine firmware (EFI) after performing a hardware self-test (step S401). Based on the setting, an IP address request by DHCP is transmitted to the SW 103 via the network (step S402).

  The IP address request transmitted from the thin client terminal 107 via the network is determined by the L2 switch (SW) 103 as to whether or not it can be transferred to the NetBoot server 102 (step S403). The determination of whether transfer is permitted (permitted / not permitted) is made based on whether or not the MAC address of the thin client terminal 107 is registered in the SW filter setting information 700 in the L2 switch (SW) 103. If transfer is not possible, a result indicating that transfer is not possible is sent from the SW 103 to the thin client terminal 107, and the activation process is terminated (stopped) (step S404).

  On the other hand, if the transfer is permitted (YES in step S403), the SW 103 transfers the IP address request from the thin client terminal 107 to the NetBoot server 102 that provides the DHCP service (step S405).

  Thereafter, the DHCP processing is performed in the NetBoot server 102 (step S406). In this DHCP filter process, the NetBoot server 102 first determines whether or not the MAC address of the thin client terminal 107 that has made an IP address request is registered in the DHCP service static mapping setting information 800. Then, based on the result of the presence / absence of registration in step S406, it is determined whether the NetBoot server 102 is managing the thin client terminal 107 (step S407). If it is not a management target, the NetBoot server 102 transmits an unacceptable result to the thin client terminal 107 (step S408). It is not always necessary to transmit the impossible result. When it is a management target (YES in step S407), information for assigning an IP address associated with the MAC address of the thin client terminal 107 in the DHCP service static mapping setting information 800 is transmitted by communication using DHCP ( Step S409).

  The thin client terminal 107 that has received the IP address assignment information by DHCP from the NetBoot server 102 performs the IP address and other accompanying settings on itself according to the received information (step S410).

  Thereafter, the thin client terminal 107 transmits a NetBoot service detection request by BSDP (Boot Server Discovery Protocol) to the NetBoot server 102 (step S411). In this process, the NetBoot server 102 that has received the service detection request determines whether or not the MAC address of the requesting thin client terminal 107 is registered in the NetBoot service filter setting information 810 (step S412). Based on the result of the presence / absence of registration in step S412, the NetBoot server 102 determines whether or not the thin client terminal 107 is a management target (step S413). If it is determined that it is not a management target, the NetBoot server 102 transmits an unacceptable result to the thin client terminal 107 (step S414). It is not always necessary to transmit the impossible result. On the other hand, if it is determined that it is a management target (YES in step S413), service information is provided by BSDP (step S415). When the NetBoot server 102 performs the process in step S407, it may be determined whether or not the MAC address of the thin client terminal 107 that has requested the IP address is registered in the NetBoot service filter information 810. Of course, it is possible to make a determination by referring to the DHCP service static mapping setting information 800 when performing the process of step S412, and the DHCP service static mapping setting information 800 and the NetBoot service filter information 810 are included. Of course, it is also possible to hold the integrated data and make a determination by referring to the data.

  Thereafter, the thin client terminal 107 starts OS activation (step S416). In OS startup, first, the thin client terminal 107 receives a boot file and a kernel from the NetBoot server 102 by TFTP and loads them onto the RAM 202 (step S417). Thereafter, the thin client terminal 107 performs OS startup processing according to the received kernel control.

  The thin client terminal 107 performs NFS mount on the NetBoot image (boot program) on the NetBoot server 102 according to the control by the kernel (step S418). Then, the thin client terminal 107 activates the OS by a boot process according to the mounted NetBoot image, as in the case where the OS is installed on a general hard disk.

  In the OS startup process, the thin client terminal 107 makes an IP address assignment request by DHCP (step S419). The NetBoot server 102 that has received the request transmits IP address assignment information to the thin client terminal 107 (step S420). Since this process is the same as that in steps S402 to S409, the details are omitted.

  The thin client terminal 107 performs IP address setting for itself based on the received IP address assignment information, and then makes a host name resolution request based on a query request to the DNS server 105 (step S421). This resolution request is also a process performed in the startup process according to the NetBoot image.

  The DNS server 105 that has received this request acquires a host name associated with the IP address by searching a management table (not shown) using the IP address of the requesting thin client terminal 107 as a key. (Step S422). Then, the DNS server 105 transmits the acquired host name to the thin client terminal 107 that has made the host name resolution request (step S423).

  The thin client terminal 107 uses the scutil command to change its own host name to the host name received from the DNS server 105 (step S424).

  Thereafter, the thin client terminal 107 makes a home directory request to the file server 106 using the mount_nfs command (step S425). The file server 106 performs mount processing in response to this request (step S426). As a result, the home directory of the thin client terminal 107 is set.

  FIG. 5 is a diagram illustrating an example of processing executed when a thin client terminal is replaced in an embodiment of the present invention. In this specification, a terminal that is removed from the network due to a failure is referred to as a “failed terminal”, and a terminal that is replaced with a failed terminal and newly joins the network is described as a “maintenance terminal”.

  First, the management terminal 104 requests the management server 101 to display a terminal replacement instruction screen (step S501). This request is sent from the management terminal 104 to the management server 101 when the “maintenance terminal replacement” tab 1401 in FIG. 14 displayed on the display unit (eg, Web browser) of the management terminal 104 is clicked by a user operation. Be notified.

  The management server 101 that has received the request issued in step S501 transmits a terminal replacement instruction screen shown in FIG. 14 to the management terminal 104 (step S502). Then, a terminal replacement instruction screen shown in FIG. 14 is displayed on the display unit of the management terminal 104.

  FIG. 14 is a diagram showing a terminal replacement instruction screen according to an embodiment of the present invention generated by the screen information generating unit 302. When the administrator user issues an input instruction via this screen displayed on the display unit of the management terminal 104, the management terminal 104 can issue a terminal change instruction to the management server 101.

  The faulty terminal display / selection column 1402 is a column for displaying / selecting a faulty terminal. Among the terminals managed by the management DB 600 of the management server 101, a list of terminals whose status information is set as faulty is listed. Is displayed. Further, the failed terminal to be replaced is determined based on the designation of the radio button in the list. Details of the management DB 600 will be described later with reference to FIG.

  A maintenance terminal display / selection column 1403 is a column for displaying / selecting a maintenance terminal, and status information is set for maintenance (maintenance) among maintenance terminals managed by the management DB 600 of the management server 101. A list of available terminals is displayed.

  Reference numeral 1404 denotes a “replacement” button. By instructing to click the replacement button 1404, the corresponding maintenance terminal is designated as a maintenance terminal to be replaced. Reference numeral 1405 denotes a “failed terminal registration” tab. When the tab 1405 is clicked, the management terminal 104 requests the management server 101 to display a failure terminal registration screen (not shown). In this failure terminal registration screen, the terminal to be set as the failure terminal is designated, and when the information is sent to the management server 101, the status information of the designated terminal in the management DB 600 is changed to failure, and the terminal Set as a terminal.

  Returning to the description of FIG. 5, the management terminal 104 receives an input of selection of a replacement terminal (failed terminal and maintenance terminal) via the terminal replacement instruction screen shown in FIG. 14 (step S503). The management terminal 104 transmits a replacement instruction including the replacement terminal information specified in step S503 to the management server 101 (step S504).

  The management server 101 that has received the replacement instruction from the management terminal 104 acquires the terminal information of the failed terminal and the maintenance terminal from the terminal information 601 (step S505). The management server 101 identifies the SW 103 that is the connection destination of the failed terminal from the acquired terminal information (network device identification), and issues an SW filter setting change instruction to the SW 103 (step S506).

  The SW 103 that has received the SW filter setting change instruction from the management server 101 changes the SW filter setting information 700 (step S507). After the change process is completed, the result is transmitted to the management server 101 (step S508). Details of the SW filter setting information 700 will be described later with reference to FIG.

  When the change process of the SW filter setting information 700 is normally completed, the management server 101 acquires data regarding the replacement target terminal (failed terminal) from the terminal-NetBoot server combination information 602 (step S509). Then, from the acquired data, the management server 101 identifies the NetBoot server 102 that manages the replacement target terminal (failed terminal) (step S510, server device identification). The management server 101 transmits an instruction to change the setting information (DHCP service static mapping setting information 800 and NetBoot service filter setting information 810) managed by the server 102 to the identified NetBoot server 102 (step S511). .

  The NetBoot server 102 that has received the setting information change instruction from the management server 101 changes the DHCP service static mapping setting information 800 and the NetBoot service filter setting information 810 related to the replacement terminal (step S512). The NetBoot server 102 transmits the processing result to the management server 101 (step S513). Details of the DHCP service static mapping setting information 800 and the NetBoot service filter setting information 810 will be described later with reference to FIG.

  When the setting information change processing by the NetBoot server 102 is normally completed, the management server 101 performs update processing of the terminal information 601 (step S514), and transmits a series of processing results to the management terminal 104 (step S515). . As a result, a screen as shown in FIG. 15 is displayed on the display unit of the management terminal 104.

  The management DB 600 in the management server 101, the SW filter setting information 700 in the SW 103, the DHCP service static mapping setting information 800 and the NetBoot service filter setting information 810 in the NetBoot server 102 will be described with reference to FIGS. .

  FIG. 6 is a diagram illustrating an example of the management DB 600 stored in the management server 101. The management DB 600 stores a plurality of tables, that is, terminal information 601, terminal-NetBoot server combination information 602, and NetBoot server information 603. The terminal information 601, terminal-NetBoot server combination information 602, and NetBoot server information 603 are also referred to as a first storage unit, a second storage unit, and a third storage unit of the management DB 600, respectively.

  The terminal information 601 is a table for storing and managing various terminal information of the thin client terminal 107 used in the system according to the present invention. The terminal information 601 stores a terminal ID 601-1 for uniquely identifying a terminal, a terminal host name 601-2, a terminal IP address 601-3, a terminal MAC address 601-4, and a terminal serial number 601-5. Further, the terminal information 601 stores a connection destination subnet name 601-6, a connection destination switch IP address 601-7, a connection destination switch port number 601-8, and terminal status information 601-9. From the terminal information 601, it is possible to grasp which thin client terminal 107 is associated with the SW 103. The terminals whose status information 601-9 is other than “active” are the terminal host name 601-2, the terminal IP address 601-3, the connection destination subnet name 601-6, the connection destination switch IP address 601-7, and the connection destination switch. Data setting for port number 601-8 has not been made.

  The NetBoot server information 603 is a table for storing and managing various server information of the NetBoot server 102 used in the system according to the embodiment of the present invention. The NetBoot server information 603 stores a NetBoot server ID 603-1 for uniquely identifying the NetBoot server 102, a NetBoot server host name 603-2, and a NetBoot server IP address 603-3.

  The terminal-NetBoot server combination information 602 is a related entity indicating which thin client terminal is associated with which NetBoot server, and stores the NetBoot server host name 602-1 and the terminal host name 602-2. Note that the data registered in the terminal-NetBoot server combination information 602 need only be information that can uniquely identify the terminal 107 and the NetBoot server 102. For example, an IP address or the like may be registered. It is not limited to the example.

  FIG. 7 is a diagram illustrating an example of SW filter setting information 700 that is a table stored in the SW 103. The SW filter setting information 700 stores the SW-IP address 701 indicating the IP address of the SW 103, the SW-port number 702, the subnet name 703 to which the SW 103 participates, and the MAC address of the terminal 107 to which the SW 103 permits communication. From the SW filter setting information 700, it is possible to grasp which thin client terminal 107 and SW 103 are associated with each other.

  The SW 103 refers to the SW filter setting information 700 and determines whether to permit or reject the relay of the communication based on the MAC address of the terminal 107 that has performed the communication. Since only the MAC address of the terminal 107 that permits communication is registered in the SW filter setting information 700, for example, even if a terminal such as a personal computer owned by an individual is to be used in the system according to the present invention, Cannot communicate. This makes it impossible to use personally owned terminals with this system.

  FIG. 8 is a diagram illustrating an example of DHCP service static mapping setting information 800 and NetBoot server filter setting information 810 stored in the NetBoot server 102. Note that the DHCP service static mapping setting information 800 and the NetBoot server filter setting information 810 are also referred to as a first storage unit and a second storage unit of the NetBoot server 102, respectively.

  The DHCP service static mapping setting information 800 is a table that statically manages an IP address assigned to a terminal in response to a DHCP IP address request from the thin client terminal 107. The table 800 stores a NetBoot server host name 801 that is a server host name, a terminal IP address 802 that is IP address information to be assigned to the terminal, and a terminal MAC address 803 that is MAC address information of the terminal 107 to which the IP address is assigned. . The terminal IP address 802 and the terminal MAC address 803 are uniquely associated, and the IP address to be assigned is determined according to the MAC address of the client terminal that has requested the IP address.

  Since only the MAC address of the terminal 107 that is permitted to give an IP address is registered in the table 800, for example, even if an attempt is made to use a personally owned computer terminal in the system according to the present invention, the terminal obtains the IP address. I can't do it. This makes it impossible to communicate with other devices, making it impossible to use personally owned terminals in this system.

  The NetBoot service filter setting information 810 is a table for the NetBoot server 102 to manage the thin client terminal 107 that provides the boot image. The NetBoot service filter setting information 810 includes a NetBoot server host name 811 that is a NetBoot server host name, and a terminal MAC address 812 that is MAC address information of the terminal 107 to which the NetBoot server 102 provides a boot image.

  Next, details of processing performed by each device of the system according to the present invention in the processing of FIG. 5 will be described with reference to FIGS. The step numbers shown in the figure indicate the step numbers in FIG. As an example taken up here, the faulty terminal (host name is “mac001”) selected in the faulty terminal display / selection column 1402 of FIG. 14 and the maintenance terminal (serial number is STK selected in the maintenance terminal display / selection column 1403). -201) will be described.

  FIG. 9 is a diagram showing an outline of the terminal information acquisition process (step S505) performed by the CPU 201 of the management server 101. This process is performed in response to a terminal replacement instruction (step S504) from the management terminal 104. In the case of the replacement instruction, the management server 101 receives the terminal ID of the failed terminal and the terminal ID information of the maintenance terminal from the management terminal 104. Then, the terminal information 601 in the management DB 600 is searched using each of the two received terminal IDs as a search key, and the terminal information of each of the designated failure terminal and maintenance terminal is acquired from the terminal information 601 and stored in the RAM 202. An example of the stored result is shown as “Result of S505” in FIG.

  FIG. 10 is a diagram showing an outline of the SW filter setting change process (step S507) performed by the SW 103. This process is performed according to the SW filter setting change instruction (step S506) from the management server 101. In the case of the change instruction, the management server 101 acquires the IP address of the switch to which the failed terminal is connected from the terminal information of the failed terminal acquired from the terminal information 601 in Step 505 (connection destination switch IP address 601- 7). The management server 101 obtains the terminal MAC address 601-4 of the failure terminal and the maintenance terminal, the connection destination switch port number 601-8 of the failure terminal, and the connection destination subnet name of the failure terminal acquired in step S505 to the SW 103 having the IP address. 601-6 is transmitted.

  The SW 103 that has received the change instruction specifies the record to be changed in the SW filter setting information 700 by using the MAC address of the failed terminal as a key, and replaces the terminal MAC address information of the specified record with the MAC address of the maintenance terminal (step) S507).

  By performing the processing described with reference to FIG. 10, the SW 103 transfers the communication of the maintenance terminal to be used instead of the failed terminal, and the administrator user directly changes the setting of the SW 103. There is no need.

  FIG. 11 is a diagram showing an outline of the identification processing (steps S509 and S510) of the NetBoot server 102 performed by the management server 101.

  First, the management server 101 searches the terminal-NetBoot server combination table 602 using the data that can identify the failed terminal as the search condition from the terminal information of the failed terminal acquired in step S505, and acquires a record corresponding to the failed terminal. (Step S509). Examples of data that can identify a failed terminal include a terminal ID, a terminal host name, a terminal IP address, and the like, and in the case of FIG. 11, the terminal host name.

  The management server 101 searches the NetBoot server information 603 using the NetBoot server host name as a search key from the terminal-NetBoot server combination information acquired in step S509. By doing so, information of the NetBoot server 102 that has provided the DHCP service and the NetBoot service to the failed terminal is acquired, and the NetBoot server 102 is specified (step S510, server device specification).

  Next, a setting information change instruction described with reference to FIG. 12 is issued to the NetBoot server 102 identified by the process described with reference to FIG. 11 (step S511).

  FIG. 12 is a diagram showing an outline of the setting information change process (step S512) performed by the NetBoot server 102. This process is performed in response to a setting information change instruction (step S511) from the management server 101. At the time of the instruction, the management server 101 obtains the host name and MAC address of the failed terminal and the MAC address of the maintenance terminal from the terminal information of the failed terminal and the maintenance terminal acquired in step S505 and stored on the RAM 202. Transmit to the NetBoot server 102.

  Receiving the setting information change instruction from the management server 101, the NetBoot server 102 searches the NetBoot service filter setting information 810 using the received terminal MAC address of the failed terminal as a search key, and obtains a record corresponding to the terminal MAC address. To do. Then, the NetBoot server 102 changes the terminal MAC address of the record to the MAC address of the maintenance terminal (step S512). In addition, the NetBoot server 102 searches the DHCP service static mapping setting information 800 using the MAC address of the failed terminal as a search key, and acquires a record corresponding to the terminal MAC address. Then, the NetBoot server 102 changes the terminal MAC address of the record to the MAC address of the maintenance terminal (step S512).

  The DHCP static mapping setting information 800 managed in the NetBoot server 102 is changed by the processing described with reference to FIG. Therefore, when a maintenance terminal is newly connected to the network, an IP address is provided by the DHCP service based on the changed information. In addition, since the NetBoot service filter setting information 810 is also updated, even when the thin client terminal 107 is activated after a new maintenance terminal joins the network, the boot process similar to that for the failed terminal is performed. Is called.

  FIG. 13 is a diagram showing an overview of the setting information change process (step S514) of the management DB 600 performed by the management server 101. This processing is processing in which the management server 101 updates the management DB 600 when the above-described processing described with reference to FIGS. 9 to 12 ends normally.

  The management server 101 has a part of the terminal information of the failed terminal developed on the RAM 202, that is, a terminal host name, a terminal IP address, a connection destination subnet name, a connection destination switch address, and a connection destination switch port number. To get. The management server 101 updates the corresponding data of the maintenance terminal using the acquired partial data, and deletes the data of the failed terminal (or updates by NULL). Then, the management server 101 changes the status information of the failed terminal to “repair” and the status information of the maintenance terminal to “operation”, confirms the changed data, and updates the management DB 600.

  Through the processing described with reference to FIG. 13, the data of the network device managing the terminal 107 is correctly changed. In this way, it is possible to update the management information (such as the SW filter setting information 700 managed by the SW 103) held by the network device when the terminal 107 is changed based on this data.

  FIG. 15 is a diagram illustrating an example of a screen that is generated by the screen information generation unit 302 as a result of the above processing and is displayed on the display unit of the management terminal 104. In FIG. 15, the faulty terminal (the terminal whose host name is “mac001”) and the maintenance terminal (the terminal whose serial number is STK-201) selected in FIG. 14 are the faulty terminal display / selection column 1402 and the maintenance terminal display / selection column, respectively. 1403 is not displayed. This is because the status information of the failure terminal and the terminal selected as the maintenance terminal has been correctly changed (the failure terminal is “failure” → “repair”, and the maintenance terminal is “maintenance” → “operation”).

  As described above, the system administrator only selects the failure terminal and the maintenance terminal, and when the maintenance terminal is connected to the network as described with reference to FIGS. Various settings of the network device for use in the environment are changed. Therefore, even an administrator who has no knowledge of the network can easily change the setting of the network device that is necessary when the terminal is replaced.

  Finally, the processing when the thin client terminal 107 (for example, the terminal having the serial number STK-201) newly participating in the network after the above setting change is started will be briefly described with reference to FIG.

  First, an IP address request by DHCP is transmitted from the thin client terminal 107 to the SW 103 in step S402 in FIG. The SW 103 determines whether the IP address request can be transferred based on the SW filter setting information 700 shown in FIG. Since the MAC address of the thin client terminal 107 is set as the terminal MAC address by the terminal change process shown in step S507 (FIG. 10), the SW 103 transfers the IP address request to the NetBoot server 102.

  Also, DHCP service static mapping setting information 800 and NetBoot service filter setting information 810, which are setting information for determining whether the thin client terminal 107 is a management target of the NetBoot server 102, have been updated (FIG. 12). . In response to a DHCP IP address acquisition request or NetBoot service detection request made to the NetBoot server 102, the NetBoot server 102 can determine whether or not the thin client terminal 107 is a management target terminal. As a result, those services can be provided.

  By adopting the configuration described in this specification, for example, even if the thin client terminal 107 connected to the SW 103 is exchanged, the settings of the IP address and host name of the terminal before the exchange are changed. Will be taken over.

  Here is an example of the benefits of this. For example, a university or the like often creates a batch file for starting or stopping terminals installed in each classroom, and performs processing for specifying these terminals by host name or IP address. According to the present invention, since the information does not change even if the terminals are exchanged, once the batch file is created, the effect that there is no need to exchange the batch file itself can be obtained. Since it is very difficult for a person with little knowledge to update the batch file, it is also a great advantage of the present invention that there is no need to update the batch file accompanying the replacement of the thin client terminal.

  In the description of the above embodiment, the MAC OS X has been described as an example. However, the present invention can also be applied to a system based on another OS. It is also possible to supply the information processing method according to the present invention as a computer-executable program. In such a case, the information processing method according to the present invention is realized by executing the program stored in the system. it can. Moreover, it is also possible to embody the information processing method according to the present invention using a computer-readable storage medium storing such a program. Further, the program can be read by a computer and operated in cooperation with an OS or other application software running on the computer.

It is a figure which shows the structure of the information processing system which concerns on one Embodiment of this invention. It is a block diagram which shows the hardware constitutions of the management server which concerns on one Embodiment of this invention. It is a block diagram which shows the function structure of the management server which concerns on one Embodiment of this invention. It is a flowchart explaining the starting process flow of a thin client terminal based on one Embodiment of this invention. It is a flowchart at the time of replacing | exchanging thin client terminals based on one Embodiment of this invention. It is a figure which shows management DB preserve | saved and managed with the management server which concerns on one Embodiment of this invention. It is a figure which shows SW filter setting information preserve | saved and managed with the switch which concerns on one Embodiment of this invention. It is a figure which shows the DHCP service static mapping setting information and NetBoot server filter setting information which are preserve | saved and managed with the NetBoot server which concerns on one Embodiment of this invention. It is a figure which shows an example of the terminal information acquisition process performed by the management server which concerns on one Embodiment of this invention. It is a figure which shows an example of SW filter setting change process performed by the switch which concerns on one Embodiment of this invention. It is a figure which shows an example of a NetBoot server specific process performed by the management server which concerns on one Embodiment of this invention. It is a figure which shows an example of the setting information change process performed by the NetBoot server which concerns on one Embodiment of this invention. It is a figure which shows an example of the setting information change process performed by the management server which concerns on one Embodiment of this invention. It is a figure which shows an example of the terminal replacement instruction | indication screen which concerns on one Embodiment of this invention. It is a figure which shows an example of the terminal replacement instruction | indication screen which concerns on one Embodiment of this invention.

Explanation of symbols

101 Management Server 102 NetBoot Server 103 L2 Switch (SW)
104 Management terminal 105 DSN server 106 File server 107 Thin client terminal

Claims (7)

An information processing system comprising: a plurality of network devices including a first network device that stores information for performing startup settings of a thin client terminal; and an information processing device that manages the plurality of network devices,
The information processing apparatus includes:
A first storage unit that stores management information in which a thin client terminal connected to a network and a network device that manages setting information related to the thin client terminal are associated;
A first accepting unit that accepts designation of a first thin client terminal connected to the network, and a second thin client terminal that replaces the first thin client terminal;
Specifying means for specifying a plurality of network devices having setting information related to the first thin client terminal received by the first receiving means;
Change request to change the setting information related to the first thin client terminal managed by the network device to the setting information related to the second thin client terminal for each of the plurality of network devices specified by the specifying means. A requesting means to perform
With
The first network device is:
Second storage means for storing an installation image used for starting the thin client terminal;
Third storage means for storing information of a thin client terminal that permits use of an installation image stored in the second storage means as setting information for performing startup setting of the thin client terminal;
First changing means for changing the information of the first thin client terminal stored in the second storage means to information of the second thin client terminal in response to a request by the requesting means;
Second accepting means for accepting a request to use the installation image from a thin client terminal;
After the second accepting unit accepts the use request, the thin client terminal that made the request provides the installation image to the thin client device according to the setting information stored in the third storage unit. A determination means for determining whether to permit,
Providing means for providing the installation image to the thin client terminal when it is determined to be permitted by the determining means;
With
By the change of the setting information by the first changing unit, the determination unit is permitted to provide the installation image provided to the first thin client terminal to the second thin client terminal. A startup process according to the installation image that was performed on the first thin client terminal before the change of the setting information is executed on the second thin client terminal after the change of the setting information; The setting of one thin client terminal is taken over by the second thin client terminal
An information processing system characterized by An information processing apparatus that manages a plurality of network devices,
A first storage unit that stores management information in which a thin client terminal connected to a network and a network device that manages setting information related to the thin client terminal are associated;
A first accepting unit that accepts designation of a first thin client terminal connected to the network, and a second thin client terminal that replaces the first thin client terminal;
Specifying means for specifying a plurality of network devices having setting information related to the first thin client terminal received by the first receiving means;
Change request to change the setting information related to the first thin client terminal managed by the network device to the setting information related to the second thin client terminal for each of the plurality of network devices specified by the specifying means. A requesting means to perform
With
The network device includes a first network device that stores setting information for performing activation setting of the thin client terminal,
The first network device is:
Second storage means for storing an installation image used for starting the thin client terminal;
Third storage means for storing information of a thin client terminal that permits use of an installation image stored in the second storage means as setting information for performing startup setting of the thin client terminal;
First changing means for changing the information of the first thin client terminal stored in the second storage means to information of the second thin client terminal in response to a request by the requesting means;
Second accepting means for accepting a request to use the installation image from a thin client terminal;
After the second accepting unit accepts the use request, the thin client terminal that made the request provides the installation image to the thin client device according to the setting information stored in the third storage unit. A determination means for determining whether to permit,
Providing means for providing the installation image to the thin client terminal when it is determined to be permitted by the determining means;
With
By the change of the setting information by the first changing unit, the determination unit is permitted to provide the installation image provided to the first thin client terminal to the second thin client terminal. A startup process according to the installation image that was performed on the first thin client terminal before the change of the setting information is executed on the second thin client terminal after the change of the setting information; An information processing apparatus , wherein the setting of one thin client terminal is taken over by the second thin client terminal . The said network device, the first network device which performs communication control for transmitting the data sent from the thin client terminal to other devices are included,
The first network device is:
Fourth storage means for storing setting information relating to the thin client terminal;
In response to a setting information change request by the requesting means, the setting information relating to the first thin client terminal stored in the fourth storage means is changed to setting information relating to the second thin client terminal . 2 change means;
First transmission means for transmitting the data received from the thin client terminal whose setting information is stored in the second storage means to another device;
The information processing apparatus according to claim 2 , further comprising: The first thin client terminal stored in the first storage means after the network device changes the setting information of the first thin client terminal to the second setting information in response to the change request by the request means. The information processing apparatus according to claim 2 , further comprising a third changing unit that changes the management information so that the network device associated with the second thin client terminal is associated with the network device. . It further comprises generation means for generating screen information for inputting a replacement instruction of the thin client terminal,
The receiving unit through the screen displayed based on the screen information, the first thin client terminal, and any of claims 2 to 4, characterized in that accepts a designation of the second thin client terminal The information processing apparatus according to claim 1. An information processing method for managing a plurality of network devices,
A first storage step of storing management information in which a thin client terminal connected to a network and a network device that manages setting information related to the thin client terminal are associated;
A first accepting step for accepting designation of a first thin client terminal connected to the network and a second thin client terminal to be replaced with the first thin client terminal;
A specifying step of specifying a plurality of network devices having setting information related to the first thin client terminal received in the first receiving step;
A change request for changing the setting information related to the first thin client terminal managed by the network device to the setting information related to the second thin client terminal for each of the plurality of network devices specified in the specifying step. A required process to perform,
Equipped with a,
The network device includes a first network device that stores setting information for performing activation setting of the thin client terminal, and the information processing method further includes:
According to the first network device,
A second storage step of storing an installation image used for starting the thin client terminal;
A third storage step for storing information of the thin client terminal that permits the use of the installation image stored in the second storage step as setting information for performing startup setting of the thin client terminal;
A first changing step of changing the information of the first thin client terminal stored in the second storing step to the information of the second thin client terminal in response to a request by the requesting step;
A second accepting step of accepting a use request for the install image from a thin client terminal;
After accepting the use request in the second accepting step, the thin client terminal that made the request provides the installation image to the thin client device according to the setting information stored in the third storing step. A determination step of determining whether to permit,
A provision step of providing the installation image to the thin client terminal when it is determined to permit in the determination step;
With
Due to the change in the setting information in the first change step, the determination step permits the provision of the installation image provided to the first thin client terminal to the second thin client terminal. A startup process according to the installation image that was performed on the first thin client terminal before the change of the setting information is executed on the second thin client terminal after the change of the setting information; An information processing method , wherein the setting of one thin client terminal is inherited by the second thin client terminal . A computer program for causing a computer to function as the information processing apparatus according to any one of claims 2 to 5.

Images