JP2009223703A - Operating system switching method and system - Google Patents

Abstract

<P>PROBLEM TO BE SOLVED: To perform OS switching that does not need an original program by eliminating the need of setting a storage position of a terminal OS in a DHCP (Dynamic Host Configuration Protocol) config file and a PXE config file. <P>SOLUTION: In a system for performing network boot, a server having network information of a terminal and a server having storage position information of an OS of the terminal are installed, and when a user's terminal is activated, a boot file is acquired on the basis of OS storage position information which is returned when accessing the server directly or through another server, and the acquired boot file is downloaded and the system is activated. <P>COPYRIGHT: (C)2010,JPO&INPIT

Description

  The present invention relates to an operating system (OS) switching method and system, and more particularly to an OS switching method and system for switching the OS environment of a terminal by an operation of an administrator in a network boot terminal.

  In recent years, thin clients that allow client terminals to perform the minimum necessary processing and concentrate other processing on the server side have attracted attention.

  Some call centers and development companies that have introduced thin clients adopt a form in which a single terminal is used alternately by multiple people.

  Each person who is a terminal operator in that environment has a desire to use the OS environment he likes.

  The OS startup method when various conventional servers are used will be described below.

[First prior art]
As a first conventional technique, an OS activation method using a DHCP server and a TFTP server will be described.

  This method is composed of a terminal, a DHCP server, a TFTP server, and a storage device storing an operating system, and describes in advance network information including an IP address and a netmask assigned to the terminal in a DHCP server configuration file. In addition to this, using the next-server option, filename option and option root-path option, the path containing the IP address of the TFTP server and the boot file name for starting the operating system in the storage device in each value Name or file name, information indicating the storage location of the operating system in the storage device is described, the boot file is arranged in the TFTP server, the operating system is stored in the storage device, and the terminal is IP Setting to allocate addresses By keep, it is feasible.

  When the terminal is turned on, the terminal sends and receives DHCP Discover, DHCP offer, DHCP request, and DHCP Ack messages to and from the DHCP server, and at the same time the network information assigned to the terminal is determined, the next-server option Information indicating the storage location of the operating system in the storage device described in the IP address of the TFTP server described in, the boot file name described in the filename option or the path name including the boot file name, and the option root-path option , Download the boot file name or the path name including the boot file name from the IP address of the TFTP server, and load the downloaded boot file. In the loading process, the operating system is started using information indicating the storage location of the operating system (see, for example, Non-Patent Document 1).

[Second conventional technique]
As a second conventional technique, an OS activation method using a DHCP server, a TFTP server, and a PXE server will be described.

This method is composed of a terminal, a DHCP server, a TFTP server, a PXE server, and a storage device storing an operating system, and a network including an IP address and a netmask assigned to the terminal in advance in the configuration file of the DHCP server. In addition to describing information, using the next-server option, option dhcp-class-identifier option, option root-path option, and option vendor-class-identifier option, the IP address of the PXE server, the corresponding Describes the character string indicating the host name, the information indicating the storage location of the operating system in the storage device, the character string "PXE Client", and, in addition, the suboption PXE_DISCOVERY_CONTROL (tag number) 6) Use PXE_BOOT_SERVERS (tag number 8) and PXE_BOOT_NENU (tag number 9) . Regarding these description methods, [tag number: length: value] is described in hexadecimal in accordance with the detailed rules described in Intel's Preboot Execution Environment V2.1.
-As PXE_DISCOVERY_CONTROL, "06.01.07"("06" is the tag number, "01" is the length of the value, "07" is the third bit, and only responses from the servers listed in PXE_BOOT_SERVERS Means not allowed);
PXE_BOOT_SERVER as "08: 07: 00: 0c [TFTP server IP address hexadecimal string]"("08" is the tag number, "07" is the value length, "00" is the delimiter, " 0c is an identifier called server type);
-As PXE_BOOT_MENU, "09: 09: 00: 0c [length when the character string corresponding to the server type 0c is displayed on the terminal screen is 16 evolved]: [the character string corresponding to the server type 0c is the terminal 16 evolution of the character string displayed on the screen] ”(“ 09 ”is the tag number“ 09 ”is the length of the value,“ 00 ”is the delimiter, and“ 0c ”is an identifier called the server type);
Is described.

  Furthermore, a number and a character string are described in a comma-separated list in the [Server Types] section of the configuration file of the PXE server. In this case, the decimal number is a hex version of the hexadecimal server type described in the configuration file of the DHCP server, and the path of the TFTP server is described in the character string. Also, create a term with the storage path name of the server type boot file, and describe the number of boot files and the boot file name required to start the operating system corresponding to the server type in the term. Keep it. This can be realized by placing a boot file in the TFTP server, storing an operating system in the storage device, and setting a terminal to assign an IP address to the DHCP server.

  When the terminal is turned on, the terminal sends and receives DHCP Discover, DHCP offer, DHCP request, and DHCP Ack messages to and from the DHCP server, and at the same time the network information allocated to the terminal is determined, the next-server IP address of the PXE server described in the option, information indicating the storage location of the operating system in the storage device described in the option root-path option, "PXE Client" described in the option dhcp-class-identifier option Information included in the character string and option vendor-class-identifier option is acquired, and the menu information specified in PXE_BOOT_MENU is displayed on the screen. When the operator of the terminal selects the menu, the terminal transmits the server type corresponding to the menu to the PXE server, and acquires the IP address of the TFTP server corresponding to the server type and the boot file path information from the PXE server. Then, the boot file is downloaded from the TFTP server, the downloaded boot file is loaded, and the operating system is activated using the information indicating the storage location information of the operating system in the loading process.

  In the case of this method, the tag numbers 128 to 254 in the PXE option field can be used as vendor specifications. Therefore, the option root-path option describing the DHCP configuration file is not described above, and is described in the PXE option. However, it can be returned to the terminal (for example, see Non-Patent Document 2).

[Third conventional technique]
As a third conventional technique, an OS startup method and an OS startup system will be described.

In the related art, when the terminal is turned on, the OS selection program is downloaded and expanded on the memory, and then the OS selection program is connected to the management server holding the management information, and the terminal starts up. The system information is acquired, and it is determined whether the operating system information is internal or external to the terminal. If the information is internal to the terminal, the information is expanded on the MBR memory inside the terminal, and the MBR image The active partition information contained therein is rewritten with the partition information of the operating system to be started obtained from the management server, thereby loading the operating system to be booted and starting the terminal. If it is outside the terminal, the network boot loader and the operation information to be activated are expanded in the memory, the operation information to be activated is read, and the terminal is started up (see, for example, Patent Document 1).
Japanese Patent No. 3732764 "Free BSD network installation using pxeboot" http://wiki.milkcup.jp/index.php?pxeboot%A4%F2%BB%C8%CD%D1%A4%B7%A4%BFFreeBSD%A4%CE % A5% CD% A5% C8% A5% EF% A1% BC% A5% AF% A5% F3% A5% F3% A5% B9% A5% C8% A1% BC% A5% EB "How to use PXE" http://corvus.kek.jp/~manabe/pcf/pxe.htm

  However, the above prior art has the following problems.

  In the first prior art, since it is necessary to give storage location information of each operating system to the boot loader, it is necessary to describe the root-path option of the configuration file of the DHCP server.

  In the second prior art, since it is necessary to give the storage location information of each operating system to the boot loader, it is necessary to write the storage location information of the operating system in advance in the PXE option field of the configuration file of the PXE server.

  In the third prior art, it is not necessary to change the configuration files of the DHCP server and the PXE server based on the original OS selection program and operating system information in the management server. However, the OS selection program is required.

  The present invention has been made in view of the above points, and it is not necessary to set the storage location of the operating system of the terminal in the DHCP configuration file and the PXE configuration file, and it is possible to switch the OS without requiring a unique program. An object is to provide an operating system switching method and system.

  FIG. 1 is a diagram for explaining the principle of the present invention.

The present invention (Claim 1) is an OS switching method for switching the operating system environment of a terminal by an operation of an administrator in a network booting terminal,
In a system comprising a normal terminal used by a user, a management terminal operated by an administrator, an address issuing server, a startup OS management server, a TFTP server, and an external storage device,
Request network information from the normal terminal and the management terminal to the address issuing server (step 1),
The address issue server transmits a storage location information request for requesting storage location information of the operating system to the boot OS management server (step 2).
In response to the storage location information request, the boot OS management server stores the storage location information of the operating system corresponding to the storage location information request from the boot OS management table holding the storage location of the operating system in the external storage device of each terminal. Obtain the TFTP server address and boot file name, and return it to the address issuing server (step 3).
The address issuing server acquires the network information of the terminal from the configuration file, and transmits it to the terminal together with the received storage location information of the operating system, the address of the TFTP server, and the boot file name (step 4).
Based on the address of the TFTP server, the storage location information of the operating system, and the boot file name, the terminal requests a boot file from the TFTP server (step 5) and downloads the boot file (step 6).

The present invention (Claim 2) is an OS switching method for switching the operating system environment of a terminal by an operation of an administrator in a network booting terminal,
In a system comprising a normal terminal used by a user, a management terminal operated by an administrator, a DHCP server, a boot OS management server, a boot OS menu display server, a TFTP server, and an external storage device,
Send a network information request from the normal terminal and the management terminal to the DHCP server,
The DHCP server returns the network information and menu display information of the terminal corresponding to the network information request to the terminal from the configuration file storing the network information and menu display settings of the terminal,
The terminal displays the menu display information received from the DHCP server. When the OS menu is selected by the user of the terminal, the terminal transmits a message including a server type parameter corresponding to the OS menu to the boot OS menu display server. ,
The boot OS menu display server transmits the server type included in the message to the boot OS management server,
The boot OS management server acquires the storage location of the operating system corresponding to the server type, the address of the TFTP server, and the boot file name from the boot OS management table that holds the storage location of the operating system in the external storage device of each terminal. , Return to the boot OS menu display server,
The boot OS menu display server sends the storage location information of the operating system acquired from the boot OS management server and the address of the TFTP server to the terminal,
The terminal requests a boot file from the TFTP server and downloads the boot file based on the address of the TFTP server, the storage location information of the operating system, and the boot file name acquired from the startup OS menu display server.

The present invention (Claim 3) is an OS switching method for switching the operating system environment of a terminal by an operation of an administrator in a network booting terminal,
In a system consisting of a normal terminal used by a user, a management terminal operated by an administrator, an address issuing server, a TFTP server, and an external storage device,
Request network information from the normal terminal and management terminal to the address issuing server,
In response to the network request, the address issue server acquires network information from the configuration file, acquires storage location information of the operating system in the external storage device, a TFTP server address, and a boot file name from the startup OS management table. Return it to your device,
The terminal requests a boot file from the TFTP server and downloads the boot file based on the storage location information of the operating system, the address of the TFTP server, and the boot file name acquired from the address issuing server.

The present invention (Claim 4) is an OS switching method for switching the operating system environment of a terminal by an operation of an administrator in a network booting terminal,
In a system comprising a normal terminal used by a user, a management terminal operated by an administrator, a DHCP server, a startup OS menu display server, a TFTP server, and an external storage device,
Request network information from the normal terminal and the management terminal to the DHCP server,
The DHCP server returns the network information and the boot OS menu display server address from the config file to the terminal,
Based on the address of the boot OS menu display server, the terminal requests storage location information of the operating system from the boot OS menu display server,
The boot OS menu display server acquires the storage location information of the operating system, the address of the TFTP server, and the boot file name from the boot OS management table, returns them to the terminal,
Based on the address of the TFTP server, the storage location information of the operating system, and the boot file name, the terminal requests the boot file from the TFTP server and downloads the boot file.

  FIG. 2 is a principle configuration diagram of the present invention.

The present invention (Claim 5) is an operating system switching system for switching the OS environment of a terminal by an operation of an administrator in a network booting terminal,
A normal terminal 10 used by a user, a management terminal 20 operated by an administrator, an address issuing server 100, a startup OS management server 300, a TFTP server 200, and an external storage device 400,
The normal terminal 10 and the management terminal 20 are
Network information requesting means 11 for requesting network information from the address issuing server 100;
Boot file acquisition means for requesting a boot file from the TFTP server 200 and downloading the boot file based on the address of the TFTP server 200 acquired from the address issuing server 100, the storage system storage location information and the boot file name 12 and
The address issuing server 100
A configuration file 141 that holds network information of the terminals 10 and 20;
Storage location information requesting means 170 for transmitting a storage location information request for requesting storage location information of the operating system to the boot OS management server 300;
The network information of the terminal is acquired from the configuration file 141, and the storage location information / address response means 120 to be transmitted to the terminals 10 and 20 together with the received storage location information of the operating system, the address of the TFTP server 200 and the boot file name is provided. And
The boot OS management server 300
A boot OS management table 370 that holds storage location information of the operating system in the external storage device 400 of each terminal 10, 20;
In response to the storage location information request, the storage location information of the operating system, the address of the TFTP server 200 and the boot file name corresponding to the storage location information request are acquired from the startup OS management table 370 and Storage position information response means 320 to be returned.

The present invention (Claim 6) is an OS switching system for switching the operating system environment of a terminal by an operation of an administrator in a network booting terminal,
In a system comprising a normal terminal used by a user, a management terminal operated by an administrator, a DHCP server, a boot OS management server, a boot OS menu display server, a TFTP server, and an external storage device,
Normal terminals and management terminals
Network information requesting means for transmitting a network information request to the DHCP server;
Displays the menu display information received from the DHCP server, and when the user of the terminal selects the OS menu, transmits a message including a server type parameter corresponding to the OS menu to the startup OS menu display server. Means,
The TFTP server address, the operating system storage location information, and the boot file name are acquired from the boot OS menu display server, and the boot file is requested from the TFTP server based on these information groups, and the boot file is downloaded. Boot file acquisition means,
The DHCP server
A configuration file that stores the network information of the terminal and settings for displaying the menu;
In response to a network information request from the terminal, network information response means for returning the network information and menu display information of the corresponding terminal from the configuration file to the terminal,
The boot OS menu display server
Server type transfer means for transmitting the server type included in the message received from the terminal to the boot OS management server;
Storage location information transfer means for transmitting the storage location information of the operating system acquired from the boot OS management server and the address of the TFTP server to the terminal;
The boot OS management server
A boot OS management table that holds the storage location of the operating system in the external storage device of each terminal;
Storage location information response means for acquiring the storage location of the operating system corresponding to the server type received from the startup OS menu display server, the address of the TFTP server, and the boot file name from the startup OS management table and returning them to the startup OS menu display server And having.

The present invention (Claim 7) is an OS switching system for switching the operating system environment of a terminal by an operation of an administrator in a network booting terminal,
In a system consisting of a normal terminal used by a user, a management terminal operated by an administrator, an address issuing server, a TFTP server, and an external storage device,
Normal terminals and management terminals
Network information requesting means for requesting network information to the address issuing server;
Boot file acquisition means for requesting a boot file from the TFTP server and downloading the boot file based on the storage location information of the operating system, the address of the TFTP server, and the boot file name acquired from the address issuing server; Have
The address issuing server
A configuration file that stores network information,
A startup OS management table that holds storage location information of the operating system in the external storage device, a TFTP server address, and a boot file name;
In response to a network request from the terminal, the network information is acquired from the configuration file, the storage location information of the operating system in the external storage device, the address of the TFTP server, and the boot file name are acquired from the boot OS management table, and Storage position information response means for returning.

The present invention (Claim 8) is an OS switching system for switching the operating system environment of a terminal by an operation of an administrator in a network booting terminal,
In a system comprising a normal terminal used by a user, a management terminal operated by an administrator, a DHCP server, a startup OS menu display server, a TFTP server, and an external storage device,
Normal terminals and management terminals
Network information requesting means for requesting network information from the DHCP server;
Storage location information requesting means for requesting the startup OS menu display server for storage location information of the operating system based on the address of the startup OS menu display server received from the DHCP server;
Boot file acquisition means for requesting a boot file from the TFTP server and downloading the boot file based on the TFTP server address, operating system storage location information and boot file name acquired from the DHCP server. ,
The DHCP server
A configuration file that holds the network information and the address of the boot OS menu display server;
In response to a request for network information from the terminal, the network information response means for acquiring the network information and the address of the boot OS menu display server from the config file and returning it to the terminal;
The boot OS menu display server
A boot OS management table for storing operating system storage location information, a TFTP server address, and a boot file name;
In response to a request for storage location information from the terminal, storage location information response means for obtaining the storage location information of the operating system, the address of the TFTP server, and the boot file name from the startup OS management table and returning the storage location information to the terminal .

  As described above, according to the present invention (claims 1 and 5), in the system including the normal terminal, the management terminal, the address issuing server, the boot OS management server, the TFTP server, and the external storage device, The configuration file has only the network information of the terminal in the configuration file, and the storage location of the operating system of the terminal in the external storage device is obtained from the boot OS management server. The storage location of the operating system in the storage device is held, and the storage location is returned according to the request of the address issuing server. This eliminates the need to describe the storage location information of the operating system in which the terminal is activated in the DHCP configuration file, thereby solving the problem in the first conventional technique.

  Further, since the terminal does not download a unique OS selection program, the problem in the third prior art can be solved.

  According to the present invention (claims 2 and 6), in the system comprising a normal terminal, a management terminal, a DHCP server, a boot OS management server, a boot OS menu display server, a TFTP server, and an external storage device, the DHCP server is a configuration file. The network information of the terminal and the setting for menu display only, the boot OS menu display server has only the server type related information in the configuration file, and the storage location of the operating system of the terminal in the external storage device is the boot OS Obtained from the management server, the boot OS management server holds the storage location of the operating system in the external storage device of each terminal in the boot OS management table, and returns the storage location according to the request of the boot OS menu display server. This eliminates the need to describe the storage location information of the operating system in which the terminal is activated in the PXE configuration file, thereby solving the problem in the second prior art.

  Further, according to the present invention (claims 3 and 7), in a system comprising a normal terminal, a management terminal, an address issuing server, a TFTP server, and an external storage device, the address issuing server includes the network information of the terminal and the startup OS in the configuration file. It has a management table, holds the storage location of the operating system in the external storage device of each terminal, and returns the storage location in the DHCP response according to the DHCP request of the terminal. This eliminates the need to describe the storage location information of the operating system in which the terminal is activated in the DHCP configuration file, thereby solving the problem of the first prior art. Further, since the terminal does not download a unique OS selection program, the problem of the third conventional technique can be solved.

  Furthermore, the present invention (Claims 4 and 8) is a system comprising a normal terminal, a management terminal, a DHCP server, a boot OS menu display server, a TFTP server, and an external storage device. The boot OS menu display server only has information and menu display settings, and has a server type related information and a boot OS management table in the configuration file, and the operating system in the external storage device of each terminal in the table. The storage location is held, and the storage location is returned in the DHCP response according to the DHCP request. This eliminates the need to describe the storage location information of the operating system in which the terminal is activated in the PXE configuration file, thereby solving the problem of the second conventional technique. Further, since the terminal does not download an original OS selection program, the problem of the third conventional technique can be solved.

  Hereinafter, embodiments of the present invention will be described with reference to the drawings.

[First Embodiment]
FIG. 3 is a system configuration diagram according to the first embodiment of the present invention.

  The system shown in the figure has a configuration in which a normal terminal 10, a management terminal 20, an address issuing server 100, a TFTP server 200, a boot OS management server 300, and an external storage device 400 are connected to a network 30.

  FIG. 4 shows the configuration of the address issuing server in the first embodiment of the present invention.

  The address issue server 100 includes an address issue request reception unit 110, an address issue request response unit 120, an address issue request message analysis unit 130, an address issue request message assembly unit 140, a startup OS management server request message assembly unit 150, and an startup OS. The management server response message analysis unit 160, the startup OS management server information transmission unit 170, the startup OS management server information reception unit 180, the setting information reading unit 190, and the setting information file 101 are configured.

  FIG. 5 shows the configuration of the boot OS management server in the first embodiment of the present invention.

  The boot OS management server 300 includes an address issue server request reception unit 310, an address issue server request response unit 320, an address issue server request message analysis unit 330, an address issue server response message assembly unit 340, a start OS acquisition unit 350, and an external storage device. The setting unit 360 includes a boot OS management table 370 and a boot OS setting unit 380.

  FIG. 6 shows the configuration of the boot OS management table in the first embodiment of the present invention. In the example shown in the figure, the boot OS management table 370 stores a MAC address, an IP address of the TFTP server, a boot file name or path name, storage location information of the boot operating system of the terminal, and a boot flag. The boot OS management table 370 is a storage medium such as a disk device.

  Based on the above configuration, the operation will be described taking the version upgrade work as an example.

  FIG. 7 is a flow of a normal terminal / management terminal according to the first embodiment of the present invention, and FIG. 8 is a setting flow accompanied by version upgrade work according to the first embodiment of the present invention.

  The administrator uses the boot OS setting unit 380 of the boot management server 300 in the management terminal 20 to set the normal terminal 10 to the MAC address, the IP address of the TFTP server, the boot file name or path name, and the operating system of the terminal 10. Is set in the boot OS management table 370 (step 101), and the management terminal 20 sets only the MAC address in the boot OS management table 370 in advance (step 102).

  In the management terminal 20, the administrator uses the startup OS setting unit 380 of the startup OS management server 300 to indicate startup in the item including the storage location information of the operating system to be started up on the normal terminal in the startup OS management table 370. Set a flag.

  When the power of the normal terminal 10 / management terminal 20 is turned on (step 103), the network information is requested (address payout request message) to the address payout server 100 in the network to which the terminals 10 and 20 belong by DHCP Discover (step 103). Step 104). Since the address issue server 100 behaves as a DHCP server for each of the terminals 10 and 20, the address issue request receiving unit 110 receives the request, and the address issue request message analyzing unit 330 receives the request from the inside of the address issue request message. And the MAC address is passed to the boot OS management server request message assembling unit 150. The boot OS management server request message assembling unit 150 creates an HTTP request having a MAC address as a parameter in the entity body, and passes the HTTP request to the boot OS management server information transmission unit 170. The boot OS management server information transmission unit 170 transmits an HTTP request to the boot OS management server 300 (step 105).

  The boot OS management server 300 receives a request from the address payout server 100 by the address payout server request reception unit 310, acquires a MAC address from the entity body of the HTTP request by the address payout server request message analysis unit 330, and acquires the boot OS. The MAC address is passed to the unit 350 (step 106). The boot OS acquisition unit 350 uses the MAC address and the boot flag in the boot OS management table 370, stores the operating system storage location information to be returned to the terminals 10 and 20, the IP address of the TFTP server 200, the boot file name, Alternatively, a path name is acquired (step 107). The acquired information group is transferred to the address payout server response message assembling unit 340. The address issue server response message assembling unit 340 creates an HTTP response having an information group as a parameter in the entity body, and passes it to the address issue server request response unit 320. The address issue server request response unit 320 returns a response to the address issue server 100 (step 108).

  The address issuing server 100 that has received the HTTP response message by the activated OS management server information receiving unit 180 passes the message to the activated OS management server response message analyzing unit 160, and stores the operating system storage location from the entity body in the HTTP response. The information, the IP address of the TFTP server, the boot file name or the path name are acquired, and the acquired information group is passed to the address delivery response message assembling unit 140. The address payout response message assembling unit 140 sets the IP address, netmask, and other network information assigned to the terminals 10 and 20 already acquired from the configuration file, and the address of the TFTP server 200 from the above information group as the next-server option. Then, a response message in which the boot file name or path name is set in the filename option and the storage location information of the operating system is set in the option root-path option is created and passed to the address issue request response unit 120. The address payout request response unit 120 returns it to the terminals 10 and 20 as DHCP Offer (step 109).

  The terminals 10 and 20 that have received a response from the address issuing server 100 transmit a DHCP request (step 110). The address payout server 100 that has received the message by the address payout request receiving unit 110 performs the above-described series of processing (step 111), and the address payout request responding unit 120 sends a DHCP Ack to the terminals 10 and 20. (Step 112).

  The terminals 10 and 20 whose IP addresses have been determined acquire the IP address and boot file name of the TFTP server 200 or the path name and operating system storage location information from the information included in the response from the address issuing server 100 ( Step 113), request the boot file to the TFTP server 200 (Step 114), and download the boot file (Step 115).

  The terminals 10 and 20 that have downloaded the boot file load the boot file (step 116), and the boot loader reads storage location information of the operating system in the process (step 117), so that the terminals 10 and 20 are activated. (Step 118).

  Before the upgrade operation by the management terminal 20 is performed, the management terminal 20 asks the boot OS setting unit 380 of the boot OS management server 300 to upgrade the normal terminal 10 to be upgraded before the power is turned on. The MAC address and its own MAC address are transmitted (step 201). Upon receiving the information, the boot OS setting unit 380 obtains the operating system storage location information corresponding to the MAC address of the normal terminal 10 in the boot OS management table 370, the IP address of the TFTP server, the boot file name, or the path name. (Step 202) The IP address, boot file name or path name of the TFTP server is stored in the field corresponding to the MAC address of the management terminal 20 in the boot OS management table 370 (Step 203). Further, the external storage device setting unit 360 is requested to newly create an operating system area of the management terminal 20 whose copy source is the operating system corresponding to the MAC address of the normal terminal 10 (step 204). The created storage location information is copied to the field corresponding to the MAC address of the management terminal (step 205).

  After performing the upgrade work by the management terminal 20, before the power of the management terminal 20 is terminated, the MAC address of the normal terminal 10 to be upgraded is given to the boot OS setting unit 380 of the boot OS management server 300. And its own MAC address are transmitted (step 206). The boot OS setting unit 380 that has received the information uses the storage location information of the operating system corresponding to the MAC address of the management terminal in the boot OS management table 370 as the storage location information of the operating system of the normal terminal 10 to be upgraded. (Step 207), and thereafter the storage location information of the operating system, the IP address of the TFTP server, the boot file name or the path name corresponding to the MAC address of the management terminal are deleted (step 208).

  As described above, the storage location of the operating system in which the latest version upgrade has been performed on the normal terminal 10 without changing the configuration file of the DHCP server and without requiring an original OS selection program after the upgrade is performed. It becomes possible to give.

  Also, assuming that OS_A is stored in the storage location of the operating system before the upgrade in this embodiment and OS_B is stored in the storage location of the operating system after the upgrade, switching from OS_A to OS_B Can also be realized easily.

[Second Embodiment]
FIG. 9 is a system configuration diagram of the second embodiment of this invention.

  The system shown in FIG. 1 includes a normal terminal 10, a management terminal 20, a TFTP server 200, a startup OS management server 300, an external storage device 400, a DHCP server 500, and a startup OS menu display server 600 connected to the network 30. It is.

  FIG. 10 is a configuration diagram of the boot OS menu display server according to the second embodiment of the present invention.

  The boot OS menu display server 600 includes a boot OS menu request unit 610, a boot OS menu request response unit 620, a boot OS menu request message analysis unit 630, a boot OS menu response message assembly unit 640, and a boot OS management server request message assembly unit 650. , A boot OS management server response message analysis unit 660, a boot OS management server information transmission unit 670, a boot OS management server information reception unit 680, a setting information reading unit 690, and a setting information file 601.

  FIG. 11 is a configuration diagram of the boot OS management server according to the second embodiment of the present invention.

  The startup OS management server 300 includes a startup OS menu display server request reception unit 301, a startup OS menu display server request response unit 302, a startup OS menu display server request message analysis unit 303, a startup OS menu display server response message assembly unit 304, startup The OS acquisition unit 350, the external storage device setting unit 360, the boot OS management table 370, and the boot OS setting unit 380 are configured.

  FIG. 12 shows the configuration of the boot OS management table in the second embodiment of the present invention.

  The boot OS management table 370 shown in the figure includes a server type, an IP address of the TFTP server, a boot file name or path name, storage location information of the boot operating system of the terminal, and a boot flag. The boot OS management table 370 is a storage medium such as a disk device.

  The operation in the above configuration will be described below using a version upgrade operation as an example.

  FIG. 13 is a processing flow of the normal terminal / management terminal in the second embodiment of the present invention, and FIG. 14 is a setting flow associated with version upgrade work in the second embodiment of the present invention. .

  The startup OS setting unit 380 of the startup OS management server 300 sets the server type that the normal terminal 10 can start up, the IP address of the corresponding TFTP server, the boot file name or path name, and the storage location of the operating system of the terminal. Only the server type and the IP address of the TFTP server 200 are set in the startup OS management table 370 as server types that can be set in the management table 370 and can be started by the management terminal 20.

  The administrator uses the boot OS setting unit 380 of the boot OS management server 300 to set a flag indicating the boot in the item including the storage location information of the operating system to be booted on the normal terminal 10 in the boot OS management table 370.

The configuration file of the DHCP server 500 includes
IP address assigned to normal terminal / management terminal;
・ Network information including net masks;
-IP address of the boot OS menu display server 600 in the next-server option;
-A string indicating the host name in the option dhcd-clas-identifier option;
-Option vendor-class-identifier option "PXEClient"string;
In addition,
option Suboption of vendor-encapsulated-options-PXE_DISCOVERY_CONTROL [tag number 6];
-PXE_BOOT_SERVERS [tag number 8];
・ Use PXE_BOOT_MENU [tag number 9]
− "06:01:07";
-"08: 07: 00: 0c: [TFTP server IP address hexadecimal string]";
-As PXE_BOOT_MENU, "09: 09: 00: 0c [length when the character string corresponding to the server type 0c is evolved to 16 characters on the terminal screen]: [the character string corresponding to the server type 0c is set to the terminal 16 evolutions of character strings displayed on the screen] ";
Is described. However, a server type independent of the server type assigned to the normal terminal 10 is assigned to the management terminal 20.

  When the power of the normal terminal 10 / management terminal 20 is turned on (step 302), each terminal 10, 20 sends network information to the DHCP server 500 in the network 30 to which the terminal 10, 20 belongs by DHCP Discover. Request (step 303).

The DHCP server 500 that has received the request,
-IP address assigned to the terminal acquired from the config file;
・ Network information including net masks;
-IP address of the boot OS menu display server 600 in the next-server option;
-Option address assignment-A character string indicating the host name in the class-identifier option;
-Option vendor-class-identifier option, "PXE Client"string;
And in addition,
option vender-encapsulated-options sub-option PXE_DISCOVERY_CONTROL [tag number 6];
・ PXE_BOOT_SERVERS [Tag number 8]
-Value of PXE_BOOT_MENU [tag number 9];
-PXE_BOOT_MENU value corresponding to the value of PXE_BOOT_MENU [tag number 9];
Is returned to the terminals 10 and 20 as a DHCP Offer (step 304).

  The terminals 10 and 20 that have received the response from the DHCP server 500 transmit DHCP request (step 305), and the DHCP server 500 that has received the message returns a DHCP Ack to the terminals 10 and 20 (step 306).

  When the terminal 10 or 20 receives the message from the DHCP server 500 and determines the IP address (step 307), it analyzes the option field included in the message and displays the OS selection menu on the screen of the terminal 10 or 20. .

  The operator selects one of the displayed OS menus (step 308) (the OS menu displayed on the normal terminal 10 and the OS menu displayed on the management terminal 20 are independent by the above-described setting). And a message including the server type corresponding to the OS menu as a parameter is transmitted to the startup OS menu display server 600 (step 309).

  The startup OS menu display server 600 behaves as a PXE server for the normal terminal 10 / management terminal 20, receives a message from each terminal 10, 20 by the startup OS menu request reception unit 610, and analyzes the startup OS menu request message. The server type is acquired from the inside of the message by the startup OS menu request message analysis unit 630 and transferred to the startup OS management server request message assembly unit 650. The boot OS management server request message assembly unit 650 creates an HTTP request having the server type as a parameter in the entity body, and passes the HTTP request to the boot OS management server information transmission unit 670. The boot OS management server information transmission unit 670 transmits an HTTP request to the boot OS management server 300 (step 310).

  The startup OS management server 300 receives the request message by the startup OS menu display server request reception unit 301, and the startup OS menu display server request message analysis unit 303 acquires the server type from the entity body of the HTTP request and acquires the startup OS. The server type is passed to unit 350. The boot OS acquisition unit 350 uses the server type and the boot flag in the boot OS management table 370, stores the operating system storage location information to be returned to the terminals 10 and 20, the boot file name or path name, and the TFTP server 200. The IP address is acquired, and the acquired information group is passed to the boot OS menu display server response message assembling unit 304. The boot OS menu display server response message assembly unit 304 creates an HTTP response having the above information group as a parameter in the entity body, and passes it to the boot OS menu display server request response unit 302. The boot OS menu display server request response unit 302 returns a response to the boot OS menu display server 600 (step 311).

  The startup OS menu display server 600 that has received the above HTTP response message by the startup OS management server information receiving unit 680 passes the above message to the startup OS management server response message analysis unit 660, and from the entity body in the HTTP response. The storage location information of the operating system, the boot file name or path name, and the IP address of the TFTP server 200 are acquired, and the acquired information group is passed to the boot OS menu response message assembling unit 640. The boot OS menu response message assembling unit 640 creates a message having the above information group as a parameter, and passes it to the boot OS menu request response unit 620. The message is returned to the terminals 10 and 20 by the startup OS menu request response unit 620 (step 312).

  The terminals 10 and 20 that have received the response from the startup OS menu display server 600 obtain the IP address, boot file name or path name, and storage location information of the TFTP server 200 from the parameters included in the received message. A boot file is downloaded from the TFTP server 200 (step 313).

  The terminals 10 and 20 that have downloaded the boot file load the boot file (step 314). In the process, the boot loader reads the storage location information of the operating system, thereby starting the terminals 10 and 20.

  Before the upgrade operation by the management terminal 20 is performed, before the management terminal 20 is turned on, the activation OS setting unit 380 of the activation OS management server 300 is informed of the upgrade target normal terminal 10. The server type and its own server type are transmitted (step 401). Upon receiving the information, the boot OS setting unit 380 acquires the IP address, boot file name, or path name of the TFTP server 200 corresponding to the server type of the normal terminal 10 in the boot OS management table 370, and starts the OS management table. It is stored in the field corresponding to the MAC address of the management terminal 20 in 370 (step 402). Further, the external storage device setting unit 360 is requested to newly create an operating system area of the management terminal 20 whose copy source is the operating system corresponding to the MAC address of the normal terminal 10 (step 403). The created storage location information is copied to the field corresponding to the MAC address of the management terminal 20 (step 404).

  After performing the upgrade work by the management terminal 20, before the power of the management terminal 20 is terminated, the server of the normal terminal 10 to be upgraded is sent to the boot OS setting unit 380 of the boot OS management server 300. The type and its server type are transmitted (step 405). The boot OS setting unit 380 that has received the information uses the storage location information of the operating system corresponding to the server type of the management terminal in the boot OS management table 370 as the storage location information of the operating system of the normal terminal 10 to be upgraded. After that, the storage location information, boot file name, or path name of the operating system corresponding to the server type of the management terminal 20 is deleted (step 407).

  As described above, the storage location of the operating system in which the latest version upgrade has been performed on the normal terminal 10 without changing the configuration file of the PXE server and without requiring a unique OS selection program after performing the version upgrade operation. It becomes possible to give.

  Also, assuming that OS_A is stored in the storage location of the operating system before the upgrade in this embodiment and OS_B is stored in the storage location of the operating system after the upgrade, switching from OS_A to OS_B is also possible. It can be easily realized.

[Third Embodiment]
FIG. 15 is a system configuration diagram according to the third embodiment of the present invention.

  The system shown in FIG. 1 has a configuration in which a normal terminal 10, a management terminal 20, an address issuing server 100, a TFTP server 200, and an external storage device 400 are connected to a network 30.

  FIG. 16 is a configuration diagram of an address issuing server in the third embodiment of the present invention. In this figure, the same components as those in FIG.

  The address issue server 100 includes an address issue request reception unit 110, an address issue request response unit 120, an address issue request message analysis unit 130, an address issue response message assembly unit 140, a boot OS acquisition unit 151, a boot OS management table 152, and a boot OS. A setting unit 153 and an external storage device setting unit 154 are included.

  FIG. 17 is a configuration diagram of the boot OS management table according to the third embodiment of the present invention.

  The startup OS management table 152 shown in the figure has, for each terminal, a MAC address, an IP address of a TFTP server, a boot file name or path name, storage location information of the startup operating system of the terminal, and a startup flag. The boot OS management table 152 is a storage medium such as a disk device.

  The operation in the above configuration will be described below using a version upgrade operation as an example.

  FIG. 18 is a processing flow of the normal terminal / management terminal in the third embodiment of the present invention, and FIG. 19 is a setting flow associated with version upgrade work in the third embodiment of the present invention. .

  The administrator uses the startup OS setting unit 153 of the address issuing server 100 to start OS management of the normal terminal 10 including the MAC address, the IP address of the TFTP server 200, the boot file name or path name, and the storage location of the operating system of the terminal 10. The management terminal 20 sets only the MAC address in the boot OS management table 152 in advance (step 501).

  The administrator uses the boot OS setting unit 153 of the address issuing server 100 to set a flag indicating the boot in the item including the storage location information of the operating system to be booted on the normal terminal 10 in the boot OS management table 152.

  When the normal terminal 10 / management terminal 20 is powered on (step 502), DHCP Discover requests network information from the DHCP server in the network to which each terminal belongs (step 503). Since the address issue server 100 behaves as a DHCP server for each of the terminals 10 and 20, the address issue request receiving unit 110 receives the above request, and the address issue request message analyzing unit 130 receives the request from the inside of the address issue request message. The MAC address of the terminal is acquired, and the MAC address is passed to the boot OS acquisition unit 151. The boot OS acquisition unit 151 uses the MAC address and boot flag in the boot OS management table 152 to store the operating system storage location information to be returned to the terminals 10 and 20, the IP address of the TFTP server 200, the boot file name, A path name is acquired (step 504). The address issue response message assembling unit 140 uses the next-server option with the network information including the IP address and netmask assigned to the terminal already acquired from the configuration file, and the TFTP server 200 address as the boot file name or path name. Is set in the filename option and the storage location information of the operating system is set in the option root-path option, and is sent to the address payout request response unit 120. The address payout request response unit 129 returns it to the terminal as DHCP Offer (step 505).

  The terminals 10 and 20 that have received the response from the address payout server 100 transmit a DHCP request (step 506), and the address payout server 100 that has received the message by the address payout request receiving unit 110 performs the series of operations described above. The processing is executed, and the address payout request response unit 120 returns it to the terminals 10 and 20 as DHCP Ack (step 507).

  The IP address is determined (step 508), and the terminals 10 and 20 obtain the IP address and boot file name or path name of the TFTP server 200 or the operating system storage location information from the information included in the response from the address issuing server 100. Then, the boot file is requested to the TFTP server 200 (step 509), and the boot file is downloaded (step 510).

  The terminals 10 and 20 that have downloaded the boot file load the boot file (step 511), and the boot loader reads the storage location information of the operating system in the process (step 512), thereby starting the terminals 10 and 20. (Step 513).

  Before the upgrade operation by the management terminal 20 is performed, before the management terminal 20 is turned on, the MAC of the normal terminal 10 to be upgraded is sent to the startup OS setting unit 153 of the address assignment server 100. The address and its own MAC address are transmitted (step 601). The boot OS setting unit 153 that has received the information acquires the storage location information of the operating system corresponding to the MAC address of the normal terminal 10 in the boot OS management table 152, the IP address of the TFTP server, the boot file name, or the path name. (Step 602), storing the IP address, boot file name or path name of the TFTP server in the field corresponding to the MAC address of the management terminal 20 in the startup OS management table 152 (Step 603) and setting the external storage device The unit 154 is requested to create a new operating system area of the management terminal 20 whose copy source is the operating system corresponding to the MAC address of the normal terminal 10 (step 604), and the newly created storage location information is obtained. The MAC address of the management terminal 20 Copied to the corresponding field (step 605).

  After performing the upgrade work by the management terminal 20, before the power of the management terminal 20 is terminated, the MAC address of the normal terminal 10 to be upgraded is given to the boot OS setting unit 153 of the address issuing server 100. And its own MAC address are transmitted (step 606). The boot OS setting unit 153 that has received the information copies the information to the storage location information of the operating system corresponding to the MAC address of the management terminal 20 in the boot OS management table 152 (step 607), and then the management terminal 20 The operating system storage location information corresponding to the MAC address, the IP address of the TFTP server 200, the boot file name or the path name are deleted (step 608).

  As described above, the storage location of the operating system in which the latest version upgrade has been performed on the normal terminal 10 without changing the configuration file of the DHCP server and without requiring an original OS selection program after performing the version upgrade operation. Can be given.

  Also, assuming that OS_A is stored in the storage location of the operating system before the upgrade in this embodiment, and OS_B is stored in the storage location of the operating system after the upgrade, the OS_A to OS_B Switching can be easily realized.

[Fourth Embodiment]
FIG. 20 is a system configuration diagram according to the fourth embodiment of the present invention.

  In the system shown in the figure, a normal terminal 10, a management terminal 20, a TFTP server 200, an external storage device 400, a DHCP server 500, and a startup OS menu display server 600 are connected to the network 30.

  FIG. 21 is a configuration diagram of the boot OS menu display server according to the fourth embodiment of the present invention.

  The boot OS menu display server 600 shown in the figure includes a boot OS menu request reception unit 610, a boot OS menu request response unit 620, a boot OS menu request message analysis unit 630, a boot OS menu response message assembly unit 640, and a boot OS acquisition unit. 651, a startup OS management table 652, a startup OS setting unit 653, and an external storage device setting unit 654.

  FIG. 22 is a configuration diagram of a boot OS management table according to the fourth embodiment of this invention.

  The boot OS management table 652 shown in the figure includes a server type, an IP address of the TFTP server, a boot file name or path name, storage location information of the boot operating system of the terminal, and a boot flag.

  The operation in the above configuration will be described below using a version upgrade operation as an example.

  FIG. 23 is a flow of processing of the normal terminal / management terminal in the third embodiment of the present invention, and FIG. 24 is a setting flow associated with version upgrade work in the third embodiment of the present invention. .

  The startup OS setting unit 653 of the startup OS menu display server 600 starts the server type that the normal terminal 10 can start up, the IP address of the corresponding TFTP server, the boot file name or path name, and the storage location of the operating system of the terminal Only the server type and the IP address of the TFTP server are set in the startup OS management table 652 as server types that can be set in the OS management table 652 and can be started by the management terminal 20 (step 701).

  The administrator uses the boot OS setting display unit 653 of the boot OS menu display server 600 to set a flag indicating the boot in the item including the storage location information of the operating system to be booted on the normal terminal 10 in the boot OS management table 652.

The configuration file of the DHCP server 500 includes
IP address assigned to the normal terminal 10 / management terminal 20;
・ Network information including net masks;
-IP address of the boot OS menu display server 600 in the next-server option;
-A string indicating the host name in the option dhcp-class-identifier option;
-Option vendor-class-identifier option "PXEClient";
In addition, in addition,
option is a suboption of vendor-encapsulated-options PXE_DISCOVERY_CONTROL [tag number 6];
-PXE_BOOT_SERVERS [tag number 8];
-PXE_MENU [tag number 9];
To each value-"06:01:07";
-"08: 07: 00: 0C [Hex string of IP address of TFTP server]";
-As PXE_BOOT_MENU, "09: 09: 00: 0C [length when the character string corresponding to the server type 0c is displayed on the terminal screen is 16 evolved]: [the character string corresponding to the server type 0c is the terminal 16 evolutions of character strings displayed on the screen]
Is described. However, a server type independent of the server type assigned to the normal terminal 10 is assigned to the management terminal 20.

When the power of the normal terminal 10 / management terminal 20 is turned on (step 702), each terminal 10, 20 sends network information to the DHCP server 500 in the network 30 to which the terminal 10, 20 belongs by DHCP Discover. Request. The DHCP server 500 that has received the request,
-IP address assigned to the terminal acquired from the config file;
・ Network information including net masks;
-In the next-server option, the IP address of the boot OS menu display server 600;
-Option address assignment-A character string indicating the host name in the class-identifier option;
-Option vendor-class-identifier option "PXEClient";
In addition to the string
option Suboption of vendor-encapsulated-options-PXE_DISCOVERY_CONTROL [tag number 6];
-PXE_BOOT_SERVERS [tag number 8];
-Value of PXE_BOOT_MENU [tag number 9];
-PXE_BOOT_MENU value corresponding to the value of PXE_BOOT_MENU [tag number 9];
Is returned to the terminals 10 and 20 as DHCP Offer (step 704).

  The terminals 10 and 20 that have received the response from the DHCP server 500 transmit a DHCP request (step 705), and the DHCP server 500 that has received the message returns a DHCP Ack to the terminals 10 and 20 (step 706).

  The terminals 10 and 20 that have received the message from the DHCP server 500 and have determined the IP address analyze the option field included in the message and display the OS selection menu on the screen of the terminal 10 and 20 (step 707).

  When the operator selects one of the displayed OS menus (the OS menu displayed on the normal terminal 10 and the OS menu displayed on the management terminal 20 are independent according to the settings described above), the corresponding A message including the server type corresponding to the OS menu as a parameter is transmitted to the startup OS menu display server 600 (step 708).

  The startup OS menu display server 600 behaves as a PXE server for the normal terminal 10 / management terminal 20, receives a message from each terminal 10, 20 by the startup OS menu request reception unit 610, and analyzes the startup OS menu request message. Part 630. The startup OS menu request message analysis unit 630 acquires the server type from the inside of the message, passes the server type to the startup OS acquisition unit 651, and the startup OS acquisition unit 651 and the server type and startup in the startup OS management table 652 Using the flag, the storage location information of the operating system to be returned to the terminals 10 and 20, the boot file name or path name, and the IP address of the TFTP server 200 are acquired (step 710), and the acquired information group is set as the boot OS. It is passed to the menu display server response message assembly unit 640. The boot OS menu display server response message assembling unit 640 creates a message having the above information group as a parameter, passes it to the boot OS menu request response unit 620, and the boot OS menu request response unit 620 sends the message to the terminals 10 and 20. (Step 711).

  The terminals 10 and 20 that have received the response from the startup OS menu display server 600 obtain the IP address, boot file name or path name, and storage location information of the TFTP server 200 from the parameters included in the received message. Then, the boot file is downloaded from the TFTP server (step 712).

  The terminals 10 and 20 that have downloaded the boot file load the boot file (step 713), and the boot loader reads the storage location information of the operating system in the process (step 714), whereby the terminals 10 and 20 are activated. (Step 715).

  Before performing the upgrade work by the management terminal 20, before turning on the power of the management terminal 20, the normal OS 10 that is the target of the upgrade work is sent to the boot OS setting unit 653 of the boot OS menu display server 600. The server type and its own server type are transmitted (step 801). Upon receiving the information, the boot OS setting unit 653 acquires the IP address, boot file name, or path name of the TFTP server corresponding to the server type of the normal terminal 10 in the boot OS management table 652 (step 802), and boot OS management The information is stored in the field corresponding to the MAC address of the management terminal in the table 652 (step 803). Furthermore, the external storage device setting unit 654 is requested to newly create an operating system area of the management terminal 20 whose copy source is the operating system corresponding to the MAC address of the normal terminal 10 (step 804). The stored storage location information is copied to the field corresponding to the MAC address of the management terminal 20 (step 805).

  After performing the upgrade work by the management terminal 20, before the power of the management terminal 20 is terminated, the server of the normal terminal that is the upgrade work target is sent to the boot OS setting unit 653 of the boot OS menu display server 600. The boot OS setting unit 653 receives the information and transmits the storage type information of the operating system corresponding to the server type of the management terminal 20 in the boot OS management table 652. Copy to the storage location information of the operating system of the normal terminal 10 to be upgraded (step 807). Thereafter, the storage location information, boot file name or path name of the operating system corresponding to the server type of the management terminal 20 is deleted (step 808).

  As described above, the storage location of the operating system in which the latest version upgrade is performed on the normal terminal 10 without changing the configuration file of the PXE server after the version upgrade operation and without requiring an original OS selection program. Can be given.

  Also, assuming that OS_A is stored in the storage location of the operating system before the upgrade in this embodiment and OS_B is stored in the storage location of the operating system after the upgrade, switching from OS_A to OS_B Can also be realized easily.

  In addition, the operation of each component of the normal terminal, the management terminal, the address issuing server, the TFTP server, the startup OS management server, the startup OS menu display server, and the DHCP server in the above embodiment is constructed as a program. It can be installed and executed on a server (computer), or distributed through a network.

  Further, the constructed program can be stored in a portable storage medium such as a hard disk, a flexible disk, or a CD-ROM, and can be installed or distributed on each server (computer).

  The present invention is not limited to the above-described embodiments, and various modifications and applications can be made within the scope of the claims.

  The present invention switches operating systems such as a DHCP server, a TFTP server, an address issuing server, a boot OS management server, a boot OS menu display server, and a PXE server in a network boot (startup) system such as a thin client. Applicable to the system.

It is a figure for demonstrating the principle of this invention. It is a principle block diagram of this invention. It is a system configuration figure in a 1st embodiment of the present invention. It is a block diagram of the address delivery server in the 1st Embodiment of this invention. It is a block diagram of the starting OS management server in the 1st Embodiment of this invention. It is a block diagram of the starting OS management table in the 1st Embodiment of this invention. It is a flow of the normal terminal / management terminal in the 1st Embodiment of this invention. It is a setting flow accompanying the upgrade work in the 1st Embodiment of this invention. It is a system block diagram in the 2nd Embodiment of this invention. It is a block diagram of the starting OS menu server in the 2nd Embodiment of this invention. It is a block diagram of the starting OS management server in the 2nd Embodiment of this invention. It is a block diagram of the starting OS management table in the 2nd Embodiment of this invention. It is a flow of the normal terminal / management terminal in the 2nd Embodiment of this invention. It is a setting flow accompanying the upgrade work in the 2nd Embodiment of this invention. It is a system block diagram in the 3rd Embodiment of this invention. It is a block diagram of the address delivery server in the 3rd Embodiment of this invention. It is a block diagram of the starting OS management table in the 3rd Embodiment of this invention. It is a flow of the normal terminal / management terminal in the 3rd Embodiment of this invention. It is a flow accompanying the upgrade work in the 3rd Embodiment of this invention. It is a system block diagram in the 4th Embodiment of this invention. It is a block diagram of the starting OS menu display server in the 4th Embodiment of this invention. It is a block diagram of the starting OS management table in the 4th Embodiment of this invention. It is a flow of the normal terminal / management terminal in the 4th Embodiment of this invention. It is a flow accompanying the upgrade work in the 4th Embodiment of this invention.

Explanation of symbols

DESCRIPTION OF SYMBOLS 10 Normal terminal 11 Network information request | requirement means 12 Boot file acquisition means 20 Management terminal 100 Address issue server 101 Setting information file 110 Address issue request receiving part 120 Storage position information / address response means, address issue request response part 130 Address issue request message Analysis unit 140 Address payout response message assembly unit 141 Config file 150 Boot OS management server request message assembly unit 151 Boot OS acquisition unit 152 Boot OS management table 153 Boot OS setting unit 154 External storage device setting unit 160 Boot OS management server response message analysis Unit 170 storage location information request means, booted OS management server information transmitting unit 180 booted OS management server information receiving unit 190 setting information reading unit 200 TFTP server 300 Boot OS Management Server 301 Boot OS Menu Display Server Request Receiving Unit 302 Boot OS Menu Display Server Request Response Unit 303 Boot OS Menu Display Server Request Message Analyzing Unit 304 Boot OS Menu Display Server Response Message Assembly Unit 310 Address Dispensing Server Request Receiving Unit 320 Address issue server request response unit 330 Address issue server request message analysis unit 340 Address issue server response message assembly unit 350 Boot OS acquisition unit 360 External storage device setting unit 370 Boot OS management table 380 Boot OS setting unit 320 Storage location information response means 370 Boot OS Management Table 400 External Storage Device 500 DHCP Server 600 Boot OS Menu Display Server 601 Setting Information File 610 Boot OS Menu Request Reception unit 620 Startup OS menu request response unit 630 Startup OS menu request message analysis unit 640 Startup OS menu response message assembly unit 650 Startup OS management server request message assembly unit 651 Startup OS acquisition unit 652 Startup OS management table 653 Startup OS setting unit 654 External storage device setting unit 660 Boot OS management server response message analysis unit 670 Boot OS management server information transmission unit 680 Boot OS management server information reception unit 690 Setting information reading unit

Claims (8)

An OS switching method for switching the operating system environment of a terminal by an operation of an administrator in a network booting terminal,
In a system comprising a normal terminal used by a user, a management terminal operated by an administrator, an address issuing server, a startup operating system (OS) management server, a TFTP (Trivial File Transfer Protocol) server, and an external storage device ,
Request network information from the normal terminal and the management terminal to the address issuing server,
The address issuing server transmits a storage location information request for requesting storage location information of an operating system to the boot OS management server,
In response to the storage location information request, the boot OS management server stores the operating system storage location corresponding to the storage location information request from the boot OS management table that holds the storage location of the operating system in the external storage device of each terminal. Get the information and the TFTP server address and boot file name, return it to the address issuing server,
The address payout server acquires the network information of the terminal from the configuration file, and transmits the received storage location information of the operating system, the address of the TFTP server and the boot file name to the terminal,
The terminal is configured to request a boot file from the TFTP server and download the boot file based on the address of the TFTP server, the storage location information of the operating system, and the boot file name. Method. An OS switching method for switching the operating system environment of a terminal by an operation of an administrator in a network booting terminal,
A normal terminal used by a user, a management terminal operated by an administrator, a DHCP (Dynamic Host Configuration Protocol) server, a boot OS management server, a boot OS menu display server, a TFTP server, and an external storage device In the system,
A network information request is transmitted from the normal terminal and the management terminal to the DHCP server,
The DHCP server returns the network information and menu display information of the terminal corresponding to the network information request from the configuration file storing the network information and menu display settings of the terminal to the terminal,
The terminal displays the menu display information received from the DHCP server. When an OS menu is selected by the user of the terminal, a message including a server type parameter corresponding to the OS menu is displayed on the startup OS menu. To the server,
The boot OS menu display server transmits a server type included in the message to the boot OS management server,
The boot OS management server acquires the storage location of the operating system corresponding to the server type, the address of the TFTP server, and the boot file name from the boot OS management table holding the storage location of the operating system in the external storage device of each terminal. And return it to the boot OS menu display server,
The boot OS menu display server transmits the storage location information of the operating system acquired from the boot OS management server and the address of the TFTP server to the terminal,
The terminal requests a boot file from the TFTP server based on the TFTP server address, the operating system storage location information, and the boot file name obtained from the boot OS menu display server, and obtains the boot file. OS switching method characterized by downloading. An OS switching method for switching the operating system environment of a terminal by an operation of an administrator in a network booting terminal,
In a system consisting of a normal terminal used by a user, a management terminal operated by an administrator, an address issuing server, a TFTP server, and an external storage device,
Request network information from the normal terminal and the management terminal to the address issuing server,
In response to the network request, the address issuing server acquires network information from a configuration file, and acquires storage location information of the operating system in the external storage device, a TFTP server address, and a boot file name from a boot OS management table. And return it to the terminal,
The terminal requests a boot file from the TFTP server based on the storage location information of the operating system, the address of the TFTP server, and the boot file name obtained from the address issuing server, and downloads the boot file. An OS switching method characterized by: An OS switching method for switching the operating system environment of a terminal by an operation of an administrator in a network booting terminal,
In a system comprising a normal terminal used by a user, a management terminal operated by an administrator, a DHCP server, a startup OS menu display server, a TFTP server, and an external storage device,
Request network information from the normal terminal and the management terminal to the DHCP server;
The DHCP server returns the network information from the config file and the address of the boot OS menu display server to the terminal,
The terminal requests storage location information of an operating system from the boot OS menu display server based on the address of the boot OS menu display server,
The boot OS menu display server obtains operating system storage location information, a TFTP server address, and a boot file name from the boot OS management table, and returns them to the terminal.
The terminal is configured to request a boot file from the TFTP server and download the boot file based on the address of the TFTP server, the storage location information of the operating system, and the boot file name. Method. An operating system switching system for switching the OS environment of a terminal by an operation of an administrator in a network booting terminal,
A normal terminal used by a user, a management terminal operated by an administrator, an address issuing server, a startup operating system (OS) management server, a TFTP (Trivial File Transfer Protocol) server, and an external storage device,
The normal terminal and the management terminal are:
Network information requesting means for requesting network information to the address issuing server;
Boot file acquisition means for requesting a boot file from the TFTP server and downloading the boot file based on the address of the TFTP server acquired from the address issuing server, the storage system storage location information and the boot file name Have
The address issuing server is
A configuration file that holds the network information of the terminal,
Storage location information requesting means for transmitting a storage location information request for requesting storage location information of an operating system to the boot OS management server;
The network information of the terminal is acquired from the configuration file, and the storage location information / address response means to be transmitted to the terminal together with the received storage location information of the operating system, the address of the TFTP server, and the boot file name is provided. And
The boot OS management server
A boot OS management table that holds the storage location information of the operating system in the external storage device of each terminal;
In response to the storage location information request, the storage location information of the operating system, the address of the TFTP server and the boot file name corresponding to the storage location information request are obtained from the boot OS management table, and And an OS switching system characterized by comprising storage location information response means for returning the information. An OS switching system for switching the operating system environment of a terminal by an operation of an administrator in a terminal to be network booted,
In a system comprising a normal terminal used by a user, a management terminal operated by an administrator, a DHCP server, a boot OS management server, a boot OS menu display server, a TFTP server, and an external storage device,
The normal terminal and the management terminal are:
Network information requesting means for transmitting a network information request to the DHCP server;
A server that displays menu display information received from the DHCP server, and transmits a message containing a server type parameter corresponding to the OS menu to the boot OS menu display server when an OS menu is selected by the user of the terminal. Type transmission means;
The TFTP server address, operating system storage location information, and boot file name are obtained from the boot OS menu display server, and the boot file is requested from the TFTP server based on these information groups, and the boot file is downloaded. And a boot file acquisition means to
The DHCP server is
A configuration file that stores the network information of the terminal and settings for displaying the menu;
In response to the network information request from the terminal, network information response means for returning the network information and menu display information of the corresponding terminal from the config file to the terminal,
The boot OS menu display server is
Server type transfer means for transmitting a server type included in the message received from the terminal to the boot OS management server;
Storage location information transfer means for transmitting the storage location information of the operating system acquired from the boot OS management server and the address of the TFTP server to the terminal;
The boot OS management server
A boot OS management table that holds the storage location of the operating system in the external storage device of each terminal;
Storage that acquires the storage location of the operating system corresponding to the server type received from the boot OS menu display server, the address of the TFTP server, and the boot file name from the boot OS management table and returns them to the boot OS menu display server An OS switching system comprising: a position information response unit. An OS switching system for switching the operating system environment of a terminal by an operation of an administrator in a terminal to be network booted,
In a system consisting of a normal terminal used by a user, a management terminal operated by an administrator, an address issuing server, a TFTP server, and an external storage device,
The normal terminal and the management terminal are:
Network information requesting means for requesting network information to the address issuing server;
Boot file acquisition means for requesting a boot file from the TFTP server and downloading the boot file based on the storage location information of the operating system, the address of the TFTP server, and the boot file name acquired from the address delivery server; Have
The address issuing server is
A configuration file that stores network information,
A boot OS management table that holds storage location information of the operating system in the external storage device, an address of the TFTP server, and a boot file name;
In response to the network request from the terminal, the network information is acquired from the configuration file, and the storage location information of the operating system, the TFTP server address, and the boot file name in the external storage device are acquired from the boot OS management table. And an OS switching system characterized by comprising storage location information response means for returning to the terminal. An OS switching system for switching the operating system environment of a terminal by an operation of an administrator in a terminal to be network booted,
In a system comprising a normal terminal used by a user, a management terminal operated by an administrator, a DHCP server, a startup OS menu display server, a TFTP server, and an external storage device,
The normal terminal and the management terminal are:
Network information requesting means for requesting network information from the DHCP server;
Storage location information requesting means for requesting storage location information of the operating system from the boot OS menu display server based on the address of the boot OS menu display server received from the DHCP server;
Boot file acquisition means for requesting a boot file from the TFTP server and downloading the boot file based on the TFTP server address, operating system storage location information and boot file name acquired from the DHCP server; And
The DHCP server is
A configuration file that holds network information, the address of the boot OS menu display server,
In response to a request for network information from the terminal, network information response means for obtaining the network information from the configuration file, the address of the boot OS menu display server and returning it to the terminal;
The boot OS menu display server is
A boot OS management table for storing operating system storage location information, a TFTP server address, and a boot file name;
In response to the storage location information request from the terminal, the storage location information, the TFTP server address, and the boot file name are acquired from the operating system management table and returned to the terminal. And an OS response system.

Images