JP5175957B2 - Information processing apparatus and client management method - Google Patents

Description

  Embodiments described herein relate generally to an information processing apparatus that manages a program that runs on a client computer, and a client management method that is applied to the apparatus.

  A technique for managing an operating system (OS) and application programs operating on a client computer by a server is used. The client computer downloads a disk image including an OS and an application program from a server, for example, and executes the OS and the application program. In this technology, the OS and application programs used in the client computer and the application of security patches can be updated on the server without having to be performed for each client computer. Can be improved.

  In addition, a virtualization technology that can simultaneously operate a plurality of environments in which different operating systems operate on one physical computer is used. In the virtualization technology, computer hardware (physical resources) is virtualized, and a plurality of virtual machines including different OSs and applications can be simultaneously executed on the computer.

JP 2007-323354 A

  Furthermore, a technique for managing the operating system (OS) and application programs operating on the client computer by the server and a virtualization technique can be combined. Thereby, for example, the OS and application program can be executed in a virtual machine operating on the client computer using the disk image including the OS and the application program transmitted by the server.

  However, a single disk image including an OS and an application program can be used only by client computers having the same hardware configuration (for example, client computers of the same model). Therefore, when the server manages a plurality of types of client computers, it is necessary to create a disk image for each model. Further, network information such as a computer name, a product key, and an IP address set in the OS needs to be set in each client computer.

  It is an object of the present invention to provide an information processing apparatus and a client management method that can reduce the time required until an operating system can be used on a virtual machine that runs on a client computer.

  According to the embodiment, the information processing apparatus includes a virtual hard disk image generation unit, a storage device, a setup unit, and a distribution unit. The virtual hard disk image generation means generates a master virtual hard disk image in which an operating system to be executed on the virtual machine is installed, and corresponds to the first and second client computers and depends on the master virtual hard disk image. And a second differential virtual hard disk image. The storage device stores a client information database indicating computer names of the first and second client computers. The setup means starts the first operating system corresponding to the pair of the master virtual hard disk image and the first differential virtual hard disk image on the virtual machine, thereby causing the first operating system to perform a first setup process. And executing a second setup process in the second operating system by starting a second operating system corresponding to the pair of the master virtual hard disk image and the second differential virtual hard disk image on the virtual machine. And the computer name of the first client computer is read from the client information database, and the computer name of the read first client computer is changed to the first difference. Set the virtual hard disk image, the leading computer name of the second client computer from the client information database, sets the computer name of the lead has been the second client computer to said second differential virtual hard disk image. The distribution means sets the pair of the master virtual hard disk image and the first differential virtual hard disk image to the first client in order to execute the first operating system on the virtual machine in the first client computer. A pair of the master virtual hard disk image and the second differential virtual hard disk image for delivering the second operating system on a virtual machine in the second client computer for distribution to the computer; Deliver to client computers. The virtual hard disk image generation means further generates a third differential virtual hard disk image depending on the master virtual hard disk image or the first differential virtual hard disk image in order to update the first operating system. The distribution means further distributes the third differential virtual hard disk image to the first client computer.

The conceptual diagram which shows the example of the network to which the information processing apparatus which concerns on embodiment is connected. The conceptual diagram which shows the example of a structure of the client computer connected to the information processing apparatus of the embodiment. The conceptual diagram which shows another example of a structure of the client computer connected to the information processing apparatus of the embodiment. The conceptual diagram which shows the structure of the information processing apparatus of the embodiment. 2 is an exemplary block diagram showing the configuration of the information processing apparatus of the embodiment. FIG. 4 is a diagram showing an example of client information used by the information processing apparatus of the embodiment. FIG. 4 is a diagram showing an example of driver set information used by the information processing apparatus of the embodiment. FIG. 4 is a diagram showing an example of master image information used by the information processing apparatus of the embodiment. FIG. 2 is an exemplary diagram showing an example of a hierarchical structure of a virtual hard disk file used by the information processing apparatus of the embodiment. FIG. 2 is an exemplary diagram showing an example of a virtual hard disk distributed to a client computer by the information processing apparatus of the embodiment. FIG. 6 is an exemplary view showing another example of the hierarchical structure of the virtual hard disk file used by the information processing apparatus of the embodiment. FIG. 6 is an exemplary view showing another example of a virtual hard disk distributed to a client computer by the information processing apparatus of the embodiment. FIG. 6 is an exemplary view showing another example of the hierarchical structure of the virtual hard disk file used by the information processing apparatus of the embodiment. FIG. 6 is an exemplary view showing another example of a virtual hard disk distributed to a client computer by the information processing apparatus of the embodiment. FIG. 6 is an exemplary flowchart illustrating an example of a procedure of a master image creation process which is executed by the information processing apparatus of the embodiment. 6 is a diagram showing another example of master image information used by the information processing apparatus of the embodiment. FIG. 5 is an exemplary flowchart illustrating an example of a procedure of client management processing which is executed by the information processing apparatus of the embodiment. 2 is an exemplary diagram illustrating an example of a client computer connected to the information processing apparatus of the embodiment. FIG. 6 is a diagram showing another example of client information used by the information processing apparatus of the embodiment. FIG. 6 is a diagram showing another example of client information used by the information processing apparatus of the embodiment. FIG. 6 is an exemplary flowchart illustrating an example of a procedure of driver set management processing which is executed by the information processing apparatus of the embodiment. 6 is an exemplary flowchart illustrating an example of a procedure of a distribution image creation process which is executed by the information processing apparatus of the embodiment. 6 is an exemplary flowchart illustrating an example of the procedure of an image update process which is executed by a client computer connected to the information processing apparatus of the embodiment. 6 is an exemplary view showing an example of a list transmitted from the information processing apparatus of the embodiment to a client computer. 6 is an exemplary flowchart illustrating an example of the procedure of an image update response process which is executed by the information processing apparatus of the embodiment.

Hereinafter, embodiments will be described with reference to the drawings.
First, an example of a network to which an information processing apparatus according to an embodiment is connected will be described with reference to FIG. The information processing apparatus 1 can be realized as a server computer, for example. This information processing apparatus 1 is also referred to as a management server 1.

  On this network, a management server 1 and a plurality of client computers 2 and 3 are connected. The management server 1 and the plurality of client computers 2 and 3 are connected to each other via a network such as a LAN. The management server 1 distributes the disk image to each of the plurality of client computers 2 and 3. This disk image is a disk image including an OS and application programs that operate on the virtual machines of the client computers 2 and 3. The management server 1 can also update the OS and application programs operating on the virtual machines of the client computers 2 and 3 by distributing the disk image to the client computers 2 and 3.

  FIG. 2 shows the configuration of the client computer 2. In the following, the client computer 2 connected to the management server 1 will be described as an example, but other client computers connected to the management server 1 have the same configuration. The client computer 2 includes physical hardware 21, a virtual machine monitor 23, a host OS 22, a virtual machine 25, and a user use OS 26.

  The physical hardware 21 includes hardware resources such as a processor, a memory, a storage device, and various devices provided in the client computer 2. The virtual machine monitor 23 is also called a hypervisor and operates on the physical hardware 21. On the virtual machine monitor 23, the host OS 22 and the virtual machine 25 operate. On the virtual machine 25, the user use OS 26 operates.

  The virtual machine monitor 23 controls the physical hardware 21 according to a command output by the host OS 22 and a command output by the user use OS 26 via the virtual machine 25. The virtual machine monitor 23 assigns processors to, for example, the virtual machine 25 on which the host OS 22 and the user use OS 26 operate. The virtual machine monitor 23 includes a communication module 24 for performing communication with the management server 1. The communication module 24 receives a disk image including the OS image of the user use OS 26 distributed from the management server 1.

  The host OS 22 is also called a management OS and has a user interface and a virtual machine management function. The host OS 22 operates on the virtual machine monitor 23. That is, the command output by the host OS 22 is output to the physical hardware 21 via the virtual machine monitor 23.

  The user use OS 26 is also called a guest OS and indicates an OS used by a user who uses the client computer 2. The user use OS 26 operates on the virtual machine 25 as described above. The virtual machine 25 executes the user use OS 26 using a disk image including the OS image of the user use OS 26 distributed from the management server 1. This disk image is, for example, data in a virtual hard disk (VHD) file format.

  The disk image also includes driver program data corresponding to the client computer 2. In addition, the user use OS 26 includes agent software 27. The agent software 27 installs the driver program included in the disk image in the user use OS 26. As described above, the user can use the user use OS 26 operating on the virtual machine 25.

  Further, the communication module 24 determines whether or not the disk image distributed from the management server 1 last time is different from the disk image currently stored in the management server 1, that is, the disk image corresponding to the current user use OS 26. The management server 1 is inquired as to whether or not it has been updated on the management server 1. When the disk image corresponding to the current user use OS 26 is updated on the management server 1, the communication module 24 receives the updated disk image from the management server 1. The communication module 24 receives, for example, a disk image including a difference between a disk image corresponding to the current user-used OS 26 and a disk image on the management server 1 corresponding thereto from the management server 1. The communication module 24 may be provided in the agent software 27 as shown in FIG.

  FIG. 4 shows the configuration of the management server 1. The management server 1 includes physical hardware 11, a virtual machine monitor 13, a host OS 12, and a virtual machine 14. The management server 1 has a function of distributing a disk image (VHD file) for operating the user use OS 26 on the virtual machine 25 provided in the client computer 2 to the client computer 2.

  The physical hardware 11 includes hardware resources such as a processor, a memory, a storage device, and various devices provided in the management server 1. The virtual machine monitor 13 is also called a hypervisor and operates on the physical hardware 11. On the virtual machine monitor 13, a host OS 12 and a virtual machine 14 operate. An arbitrary guest OS can be operated on the virtual machine 14.

  The virtual machine monitor 13 controls the physical hardware 11 according to a command output by the host OS 12 and a command output by the guest OS via the virtual machine 14. For example, the virtual machine monitor 13 assigns processors to the host OS 12 and the virtual machine 14 on which the guest OS operates.

  The host OS 12 is also called a management OS, and has a user interface and a virtual machine management function. The host OS 12 operates on the virtual machine monitor 13. That is, the command output by the host OS 12 is output to the physical hardware 11 via the virtual machine monitor 13.

  The configuration of the host OS 12 operating on the management server 1 will be described with reference to FIG. The host OS 12 includes a client management module 15, a driver set management module 16, a virtual image management module 17, a communication module 18, a client management database 12A, a driver set management database 12B, a driver file group 12C, a master image management database 12D, and a virtual disk A file group (VHD file group) 12E is provided.

  The client management module 15 manages the client management database 12A. FIG. 6 shows an example of the configuration of client information stored in the client management database 12A. The client information includes a plurality of entries respectively corresponding to a plurality of client computers. Each entry includes, for example, a client name, a model name, a master image name, and a status. The client name indicates the computer name of the client computer. The model name indicates the model name of the client computer. For example, the hardware configuration of computers differs between client computers set with different model names. The master image name indicates, for example, the name of the master virtual hard disk file in which the user use OS used in the client computer is installed. The status indicates whether a disk image to be distributed to the client computer has been created. The status includes, for example, “created” indicating that the disk image to be distributed to the client computer has been created, and “not created” indicating that the disk image to be distributed to the client computer has not been created. Is set. The client management module 15 adds, edits and deletes entries corresponding to the client computer.

  The driver set management module 16 manages the driver set management database 12B. FIG. 7 shows a configuration example of the driver set information stored in the driver set management database 12B. The driver set information includes a plurality of entries respectively corresponding to a plurality of client computer models. The driver set information includes, for example, a model name and a driver set name. The model name indicates the model name of the client computer. The model name corresponds to the model name included in the above client information. The driver set name indicates the name of the driver set used in the client computer. The driver set includes a driver program for using a device or the like connected to the target client computer. That is, by installing a driver set program corresponding to the model of the client computer, devices connected to the client computer can be controlled. This driver set is stored in a storage device in the management server 1 as a driver file group 12C, for example. The driver set management module 16 adds, edits, and deletes entries corresponding to the model of the client computer.

The virtual image management module 17 manages the generation and update of a virtual image (virtual hard disk file) used in the client computer 2.
There are two types of virtual hard disk files: a virtual hard disk file serving as a master (basic virtual hard disk file) and a differential virtual hard disk file that records changes to the basic virtual hard disk file. The differential virtual hard disk file is used as a pair with the basic virtual hard disk file. The basic virtual hard disk file and the differential virtual hard disk file form a hierarchical structure in which the basic virtual hard disk file is “parent” and the differential virtual hard disk file is “child”. In other words, it can be said that the differential virtual hard disk file that is the “child” depends on the basic virtual hard disk file that is the “parent”. In addition, not only the basic virtual hard disk file but also the differential virtual hard disk file can be designated as the parent of the differential virtual hard disk file. Therefore, a hierarchical structure having the basic virtual hard disk file as a vertex is configured such that the first differential virtual hard disk file whose parent is the basic virtual hard disk file is designated as the parent of the second differential virtual hard disk file. You can also. Furthermore, a plurality of differential virtual hard disk files can be set as children for one parent (basic virtual hard disk file or differential virtual hard disk file).

  By using a pair of a basic virtual hard disk file (parent) and a differential virtual hard disk file (child) having a hierarchical structure, different system environments can be easily created. For example, a system environment in which an OS is installed in a master virtual hard disk file is created, and a system environment in which a security patch is applied to a differential virtual hard disk file. Further, for example, a system environment in which an OS is installed in a master virtual hard disk file is created, and a system environment in which an application program is installed in a differential virtual hard disk file is created. Further, for example, a system environment in which an OS and an application program are installed in a master virtual hard disk file is created, a different computer name is set in each of the plurality of differential virtual hard disk files, and a plurality of system environments having different computer names are created. create. Since the difference virtual hard disk file records only the portion that has changed with respect to the parent system environment as described above, the disk capacity required for recording can be minimized.

  The virtual hard disk file includes identification information (UUID: universally unique ID) unique to the virtual hard disk file. This UUID is set, for example, in the UUID field included in the footer of the virtual hard disk file.

  The differential virtual hard disk file includes a UUID (Parent unique ID) indicating the virtual hard disk file designated as the “parent” of the differential virtual hard disk file. The UUID of the parent virtual hard disk file is set, for example, in the “Parent unique ID” field included in the header of the child differential virtual hard disk file. That is, an ID indicating a parent virtual hard disk file (basic virtual hard disk file or differential virtual hard disk file) of the differential virtual hard disk file can be detected from the differential virtual hard disk.

  The virtual image management module 17 includes a master VHD generation unit 171, an OS installation unit 172, a first differential VHD generation unit 173, an application installation unit 174, a master image registration unit 175, a setup VHD generation unit 176, and a second differential VHD generation unit 177. A driver storage unit 178 and a setup unit 179.

  The master VHD generation unit 171 generates a basic virtual hard disk file (basic VHD file) used as a master image. The master image is an OS image in which an OS is installed, for example. The master image is also called a master virtual hard disk image. When a plurality of client computers 2 and 3 connected to the management server 1 use different OSs (user use OSs 26), the master VHD generation unit 171 generates basic VHD files corresponding to the number of OSs. The master VHD generation unit 171 assigns a name (master image name) to the generated basic VHD file. This name may be given by an administrator who uses the management server 1. The master VHD generation unit 171 outputs the generated basic VHD file to the OS installation unit 172.

  The OS installation unit 172 installs a predetermined operating system (OS) in the basic VHD file output by the master VHD generation unit 171. Specifically, the OS installation unit 172 mounts the basic VHD file on the virtual machine 14 and installs the OS on the mounted basic VHD file. Then, the OS installation unit 172 installs the agent software 27 in the basic VHD file. The OS installation unit 172 outputs the basic VHD file (master image) in which the OS and the agent software 27 are installed to the first differential VHD generation unit 173.

  The first differential VHD generation unit 173 generates a first differential VHD file using the basic VHD file output by the OS installation unit 172. In other words, the first differential VHD generation unit 173 generates a first differential VHD file whose parent is the basic VHD file (that is, depends on the basic VHD file). This first differential VHD file is also used as a master image. The first differential VHD generation unit 173 uses a different set of application programs in a client computer using the same OS (user use OS 26) among the plurality of client computers 2 and 3 connected to the management server 1. The first differential VHD file is created for each basic VHD file by the number of sets of the application programs. The first differential VHD generation unit 173 assigns a name (master image name) to the first differential VHD file. This name may be given by an administrator who uses the management server 1. The first differential VHD generation unit 173 outputs the generated first differential VHD file to the application installation unit 174.

  The application installation unit 174 installs a predetermined application program in the first differential VHD file output by the first differential VHD generation unit 173. In other words, the application installation unit 174 mounts the differential VHD file on the virtual machine 14 and installs the application program on the mounted differential VHD file. The application installation unit 174 may install an update program such as an OS security patch in the first differential VHD file. The application installation unit 174 outputs the first differential VHD file to the master image registration unit 175.

  The master image registration unit 175 registers master image information indicating the basic VHD file and the first differential VHD file created as described above in the master image management database 12D. The master image registration unit 175 registers an entry including “master image name” and “state” corresponding to the created VHD file in the master image management database 12D. “Distribution impossible” is set in the “state” included in this entry.

  FIG. 8 shows an example of the configuration of master image information stored in the master image management database 12D. The master image information includes a plurality of entries respectively corresponding to a plurality of master images. The master image information includes, for example, a master image name and a state. The master image name indicates the name of the master image. The status indicates whether the master image can be delivered to the client computer. For example, one of “Distributable” indicating that the master image can be distributed and “Distributable” indicating that the master image cannot be distributed is set in the state. The master image registration unit 175 adds, edits, deletes an entry corresponding to the master image.

  The setup VHD generation unit 176 generates a setup differential VHD file in which a setup module is incorporated. The setup module is a module for executing an OS setup process when the OS is activated. This setup process includes, for example, a process for setting a computer name, a process for setting a product key, a process for setting network information such as an IP address, and a process for setting user information such as a user name.

  Specifically, the setup VHD generation unit 176 first generates a differential VHD file whose parent is the first differential VHD file (that is, depends on the first differential VHD file). Then, the setup VHD generation unit 176 incorporates a setup module into the generated differential VHD file. The differential VHD file in which the setup module is incorporated is also referred to as a setup differential VHD file. Note that the processing by the setup VHD generation unit 176 can use, for example, a sysprep tool of Windows (registered trademark) OS. The setup VHD generation unit 176 notifies the master image registration unit 175 that the setup differential VHD file has been generated.

  In response to the notification from the setup VHD generation unit 176, the master image registration unit 175 updates the master image management database 12D. The master image registration unit 175 sets “distributable” in the “state” of the entry corresponding to the first differential VHD file (master image) that is the parent of the generated setup differential VHD file.

  With the above configuration, a basic VHD file and a first differential VHD file that are master images and a setup differential VHD file incorporating a setup module are generated, and master image information indicating the master image is registered in the master image management database 12D. Is done.

  The above-described client management module 15 selects a master image used in each of a plurality of client computers from the master images registered in the master image management database 12D. A master image used in each of the plurality of client computers is selected by an administrator of the management server 1, for example. Further, the client management module 15 may select a master image used in each of a plurality of client computers using data indicating the correspondence between the client computer and the master image. The client management module 15 sets the master image name of the selected master image in the entry of the corresponding client computer.

  The second differential VHD generation unit 177 generates a second differential VHD file (also referred to as a client VHD file) in which necessary data is stored for each client computer. Specifically, the second differential VHD generation unit 177 refers to the client management database 12A and determines whether there is a client computer whose status is “not created”. If there is no client computer whose status is “not created”, that is, if the status of all client computers is “created”, the process is terminated. When there is a client computer whose status is “not created”, the second differential VHD generation unit 177 duplicates the setup differential VHD file corresponding to the client computer, and creates the second differential VHD file for the client computer. Generate.

  Specifically, the second differential VHD generation unit 177 reads the master image name corresponding to the client computer whose status is “not created”. Then, the second difference VHD generation unit 177 reads the setup difference VHD file whose parent is the VHD file corresponding to the read master image name. Then, the second differential VHD generation unit 177 generates the second differential VHD file by duplicating the read setup differential VHD file. The second difference VHD generation unit 177 assigns a computer name corresponding to the client computer to the generated second difference VHD file. The second difference VHD generation unit 177 outputs the generated second difference VHD file to the driver storage unit 178.

  The driver storage unit 178 mounts the second differential VHD file output by the second differential VHD creation unit 177. The driver storage unit 178 reads the driver set corresponding to the model of the client computer with reference to the driver set management database 12B. Specifically, the driver storage unit 178 reads the driver set name corresponding to the model of the client computer with reference to the driver set management database 12B. Then, the driver storage unit 178 reads a driver set corresponding to the read driver set name from the driver file group 12C. The driver storage unit 178 arranges the read driver set at a predetermined position in the second differential VHD file. The driver storage unit 178 reads the computer name corresponding to the client computer with reference to the client management database 12A. The driver storage unit 178 arranges the read computer name at a predetermined position in the second differential VHD file. Then, the driver storage unit 178 unmounts the second differential VHD file. The driver storage unit 178 outputs the second differential VHD file to the setup unit 179.

  The setup unit 179 uses the second differential VHD file output by the second differential VHD file generation unit 177 to start up the OS on the virtual machine 14. That is, the setup unit 179 starts the OS using the second differential VHD file, the first differential VHD file that is the parent of the second differential VHD file, and the basic VHD file that is the parent of the first differential VHD file.

  When the OS is started on the virtual machine 14, the OS setup process (mini setup) is executed by the setup module incorporated in the second differential VHD file. In this OS setup process, the computer name arranged in the second differential VHD file is set in the OS. The setup process may include a process for setting a product key, a process for setting network information such as an IP address, and a process for setting information on a user who uses the OS.

  When the setup process is completed, the setup unit 179 rewrites the status of the client information corresponding to the client computer in the client management database 12B to “created”. Then, the setup unit 179 shuts down the running OS. Next, the setup unit 179 stops the virtual machine 14 and unmounts the VHD file used for executing the OS.

  With the above configuration, a disk image (also referred to as a distribution image) distributed to the client computer 2 is generated. The distribution image distributed to the client computer 2 includes, for example, a VHD file necessary for executing the user use OS 26 on the virtual machine 25 in the client computer 2. Therefore, for example, the distribution image distributed to the client computer 2 includes the second differential VHD file, the first differential VHD file that is the parent of the second differential VHD file, and the basic VHD file that is the parent of the first differential VHD file. . In the above description, the process of generating a disk image distributed to one client computer 2 has been described. However, the disk image distributed to each of a plurality of client computers connected to the management server 1 is the same process. Generated by. Alternatively, the second differential VHD file whose parent is the basic VHD file may be generated without generating the first differential VHD file in which the application program is installed. In that case, the second differential VHD file and the basic VHD file are distributed to the client computer 2.

  FIG. 9 shows an example of the hierarchical structure of a VHD file used as a distribution image. Each VHD file is set with an ID (UUID). For example, ID “1” is set in the basic VHD file 401. For example, ID “5” is set in the differential VHD file 405. In FIG. 9, two VHD files connected by solid lines indicate that the VHD file described on the left side is a parent VHD file and the VHD file described on the right side is a child VHD file. For example, the parent of the differential VHD file 405 and the differential VHD file 406 is the basic VHD file 401.

  In the example shown in FIG. 9, a basic VHD file 401 (master A) and a basic VHD file 402 (master B) are generated as master images. In addition, a differential VHD file 405 (PC1), a differential VHD file 406 (PC2), a differential VHD file 407 (PC3), and a differential VHD file 408 (PC4) are generated as client VHD files.

  The difference VHD file 403 and the difference VHD file 404 indicate the setup difference VHD file generated by the setup VHD generation unit 176. Therefore, the differential VHD files 405 and 406 are differential VHD files generated by duplicating the differential VHD file 403. The differential VHD files 407 and 408 are differential VHD files generated by copying the differential VHD file 404.

  FIG. 10 shows a VHD file distributed to each client computer when the VHD file is configured as shown in FIG. In the configuration of the VHD file shown in FIG. 9, the basic VHD file 401 (master A) and the differential VHD file 405 (PC1) are distributed to the PC1. The basic VHD file 401 (master A) and the differential VHD file 406 (PC2) are distributed to the PC2. The basic VHD file 402 (master B) and the differential VHD file 407 (PC3) are distributed to the PC3. Further, the basic VHD file 402 (master B) and the differential VHD file 408 (PC4) are distributed to the PC 4.

FIG. 11 shows another example of the hierarchical structure of a VHD file used as a distribution image.
In the example shown in FIG. 11, a basic VHD file 401 (master A), a differential VHD file 409 (master A1), and a differential VHD file 410 (master A2) are generated as master images. Also, a differential VHD file 413 (PC1), a differential VHD file 414 (PC2), a differential VHD file 415 (PC3), and a differential VHD file 416 (PC4) are generated as client VHD files.

  The differential VHD file 411 and the differential VHD file 412 indicate the setup differential VHD file generated by the setup VHD generation unit 176. Therefore, the differential VHD files 413 and 414 are differential VHD files generated by duplicating the differential VHD file 411. The differential VHD files 415 and 416 are differential VHD files generated by duplicating the differential VHD file 412.

  FIG. 12 shows a VHD file distributed to each client computer when the VHD file is configured as shown in FIG. In the configuration of the VHD file shown in FIG. 11, a basic VHD file 401 (master A), a differential VHD file 409 (master A1), and a differential VHD file 413 (PC1) are distributed to the PC1. The basic VHD file 401 (master A), the differential VHD file 409 (master A1), and the differential VHD file 414 (PC2) are distributed to the PC2. A basic VHD file 401 (master A), a differential VHD file 410 (master A2), and a differential VHD file 415 (PC3) are distributed to the PC3. The basic VHD file 401 (master A), the differential VHD file 410 (master A2), and the differential VHD file 416 (PC4) are distributed to the PC 4. Such a distribution image is distributed to the client computer 2 by the communication module 18.

  The communication module 18 manages the distribution of the disk image to the client computer 2. The communication module 18 distributes a disk image to the client computer 2 by communicating with the communication module 24 provided in the client computer 2.

  The communication module 18 of the management server 1 (host OS 12) includes a list request reception unit 181, a list transmission unit 182, a distribution request reception unit 183, and a VHD file distribution unit 184. The communication module 24 of the client computer 2 includes a list request transmission unit 241, a list reception unit 242, a distribution request transmission unit 243, a VHD file reception unit 244, and a VHD file update unit 245.

  The list transmission request unit 241 of the client computer 2 requests the management server 1 to transmit the VHD file list. The VHD file list is a list (also referred to as an ID list) including IDs corresponding to a plurality of VHD files (disk images) used in the client computer 2.

  The list request receiving unit 181 of the management server 1 receives the VHD file list transmission request transmitted by the client computer 2. The list request reception unit 181 notifies the list transmission unit 182 that transmission of the VHD file list is requested.

  In response to this notification, the list transmission unit 182 generates a list of VHD files to be distributed to the client computer 2 that has requested the VHD file list. Specifically, the list transmission unit 182 reads the status of the client information corresponding to the client computer with reference to the client management database 12A. The list transmission unit 182 determines whether or not the read status is “created”. When the read status is “created”, the list transmission unit 182 reads the VHD file for the client computer from the VHD file group 12E. For example, the list transmission unit 182 reads a VHD file to which a computer name corresponding to the client computer 2 is assigned. Then, the list transmission unit 182 detects the ID of this VHD file from the read VHD file. The list transmission unit 182 adds the ID of the detected VHD file to the VHD file list.

  Next, the list transmission unit 182 determines whether or not a parent VHD file exists in the read VHD file. For example, when the read VHD file is a differential VHD file, the list transmission unit 182 determines that the parent VHD file exists in the VHD file. For example, when the parent ID is set in the read VHD file, the list transmission unit 182 determines that the parent VHD file exists in the VHD file.

  When the read VHD file includes a parent VHD file, the list transmission unit 182 reads the parent VHD file from the VHD file group 12E. Then, the list transmission unit 182 detects the ID of this VHD file from the read parent VHD file. The list transmission unit 182 adds the ID of the detected VHD file to the VHD file list. The list transmission unit 182 follows the parent VHD file as described above, and adds an ID to the VHD file list. That is, the process of adding an ID to the VHD file list is repeated until the parent that is the basic VHD file is reached.

  If the read VHD file does not have a parent VHD file, that is, if the read VHD file is a basic VHD file, the list transmission unit 182 rearranges the IDs added to the VHD file list. Specifically, the list transmission unit 182 rearranges the IDs in order from the parent to the child, starting with the ID corresponding to the basic VHD file.

  After rearranging the IDs in the VHD file list or when the read status is not “created”, the list transmission unit 182 transmits the VHD file list to the client computer 2. If the read status is not “created”, for example, a VHD file list that does not include an ID corresponding to the VHD file is transmitted.

  The list receiving unit 242 of the client computer 2 receives the VHD file list transmitted by the list transmitting unit 182 of the management server 1. The list receiving unit 242 outputs the received VHD file list to the distribution request transmitting unit 243.

  The distribution request transmission unit 243 determines whether or not the currently received VHD file list has been changed from the previously received VHD file list. If the currently received VHD file list has not been changed from the previously received VHD file list, the distribution request transmitting unit 243 ends the process. When the currently received VHD file list is changed from the previously received VHD file list, the distribution request transmitting unit 243 is included in the previously received VHD file list among the VHD files included in the currently received VHD file list. The management server 1 is requested to distribute a VHD file that has not been received.

  FIG. 13 shows an example in which the VHD file corresponding to the image distributed to the PC 1 is changed with respect to the configuration shown in FIG. Specifically, in FIG. 13, a differential VHD file 417 (master A3) is added as a master image, and a new differential VHD file 419 for PC1 is generated as a child of the master A3. Here, it is assumed that the client computer 2 is the PC 1.

  In this case, the list transmission unit 182 of the management server 1 performs the basic VHD file 401 (master A), the difference VHD file 409 (master A1), and the difference before the VHD file is changed as shown in FIG. A VHD file list including each ID of the VHD file 413 (PC1) is transmitted to the client computer 2. Specifically, the list transmission unit 182 includes the ID “1” of the basic VHD file 401 (master A), the ID “9” of the differential VHD file 409 (master A1), and the ID “9” of the differential VHD file 413 (PC1). A VHD file list including 13 ″ is transmitted to the client computer 2. Further, after the VHD file is changed, the list transmission unit 182 includes the VHD including the IDs of the basic VHD file 401 (master A), the differential VHD file 417 (master A3), and the differential VHD file 419 (PC1). The file list is transmitted to the client computer 2. Specifically, the list transmission unit 182 has the ID “1” of the basic VHD file 401 (master A), the ID “17” of the differential VHD file 417 (master A3), and the ID “17” of the differential VHD file 419 (PC1). A VHD file list including 19 ″ is transmitted to the client computer 2.

  At this time, since the VHD file list received this time has been changed from the previously received VHD file list, the distribution request transmission unit 243 of the client computer 2 receives the previous received VHD file included in the currently received VHD file list. The management server 1 is requested to distribute a VHD file not included in the VHD file list. That is, the distribution request transmission unit 243 requests the management server 1 to distribute the differential VHD file 417 (master A3) and the differential VHD file 419 (PC1). More specifically, the distribution request transmission unit 243 transmits a distribution request including the ID “17” of the differential VHD file 417 and the ID “19” of the differential VHD file 419 (PC1) to the management server 1.

  The distribution request receiving unit 183 of the management server 1 receives a VHD file distribution request from the client computer 2. The distribution request receiving unit 183 notifies the VHD file distribution unit 184 that the VHD file distribution request has been received from the client computer 2.

  The VHD file distribution unit 184 reads the corresponding VHD file from the VHD file group 12E based on the VHD file ID specified in the distribution request. Then, the VHD file distribution unit 184 transmits the read VHD file to the client computer 2.

  Next, the VHD file receiving unit 244 receives the VHD file from the management server 1. Then, the VHD file reception unit 244 outputs the received VHD file to the VHD file update unit 245.

  The VHD file update unit 245 updates the disk image stored in the client computer 2 using the received VHD file. For example, the VHD file update unit 245 replaces the disk image when the user use OS 26 is activated next time. In the example shown in FIG. 14, the difference VHD file 409 (master A1) and the difference VHD file 413 (PC1) are discarded, and the difference VHD file 417 (master A3) and the difference VHD file 419 (PC1) are new disk images. Stored as

  When booting with a new disk image, the driver installation unit 271 installs the driver using the updated driver set when the disk image is updated. The agent software 27 is not limited to the driver set, and performs necessary processing in response to the disk image being updated.

  With the above configuration, only the changed VHD file among the disk images (VHD files) used in the client computer 2 is transmitted from the management server 1 to the client computer 2, and the time required for transmission can be shortened. .

  Next, an example of a procedure of master image creation processing by the virtual image management module 17 will be described with reference to the flowchart of FIG. In the example illustrated in FIG. 15, a basic VHD file in which the OS is installed and a first differential VHD file in which the basic VHD file is a parent and an application program is installed are created. In the following, it is assumed that the basic VHD file and the first differential VHD file are used as master images of distribution images distributed to the client computers 2 and 3.

  First, the master VHD generation unit 171 creates a basic virtual hard disk file (basic VHD file) used as a master image (block B11). Next, the OS installation unit 172 installs a predetermined operating system (OS) in the basic VHD file (block B12). That is, the OS installation unit 172 mounts the basic VHD file on the virtual machine 14 and installs the OS on the mounted basic VHD file. Then, the OS installation unit 172 installs the agent software 27 in the basic VHD file (block B13).

  Next, the first differential VHD generation unit 173 generates a first differential VHD file using the master image (basic VHD file) (block B14). Then, the application installation unit 174 installs a predetermined application program in the first differential VHD file (block B15). That is, the application installation unit 174 mounts the first differential VHD file on the virtual machine 14 and installs the application program on the mounted first differential VHD file. Then, the master image registration unit 175 registers master image information indicating the basic VHD file and the first differential VHD file created as described above in the master image management database 12D (block B16). The master image registration unit 175 registers an entry including “master image name” and “state” corresponding to the created VHD file in the master image management database 12D. “Distribution impossible” is set in the “state” included in this entry.

  Next, the setup VHD generation unit 176 generates a setup differential VHD file in which a setup module is incorporated. (Block B17). The setup module is a module for executing an OS setup process when the OS is activated. In response to the generation of the setup differential VHD file, the master image registration unit 175 updates the master image management database 12D (block B18). That is, the master image registration unit 175 sets “distributable” in the “state” of the entry corresponding to the first differential VHD file (master image) that is the parent of the generated setup differential VHD file.

  FIG. 16 shows an example in which master image information is registered in the master image management database 12D by the master image creation process. The example shown in FIG. 16 shows the master image management database 12D when the VHD file group shown in FIG. 11 is created, for example. When the VHD file group shown in FIG. 11 is created, the basic VHD file 401 that is the master image “A”, the differential VHD file 409 that is the master image “A1”, and the differential VHD file 410 that is the master image “A2”. Is created. Therefore, entries corresponding to the master images “A”, “A1”, and “A2” are registered in the master image management database 12D. In addition, “Distribution impossible” is set in the “status” of each entry.

  When the setup module is incorporated into each of the differential VHD file 409 that is the master image “A1” and the differential VHD file 410 that is the master image “A2”, the master images “A1” and “A2” “Distributable” is set in the “state” of the entry corresponding to each (see FIG. 8).

  Next, the flowchart shown in FIG. 17 shows an example of the procedure of the client management process executed by the client management module 15. In the following, it is assumed that five client computers shown in FIG. 18 are managed. These five client computers are assigned computer names “PC1”, “PC2”, “PC3”, “PC4”, and “PC5”, respectively. The model names of the client computers “PC1”, “PC2”, and “PC3” are “model 1”, and the model names of the client computers “PC4” and “PC5” are “model 2”. That is, the client computers “PC1”, “PC2”, and “PC3” and the client computers “PC4” and “PC5” are computers having different hardware configurations.

  First, the client management module 15 registers the client computer in the client management database 12A (block B21). That is, the client management module 15 adds an entry of client information indicating the client computer to the client management database 12A.

  Next, the client management module 15 selects a master image to be assigned to the client computer from the master images registered in the master image management database 12D (block B22). For example, the client management module 15 selects a master image designated for each client computer. The client management module 15 may assign a master image designated by the administrator to the client computer.

  Then, the client management module 15 registers the master image name corresponding to the selected master image in the client management database 12A (block B23).

  FIG. 19 shows an example when an entry corresponding to each of the five client computers described above is added to the client management database 12A by the block B21. For example, in the client computer “PC1”, an entry with the computer name “PC1”, the model name “model 1”, and the status “uncreated” is added to the client management database 12A. Note that no value is set for the master image name of the entry to be added. Similarly, entries corresponding to the client computers “PC2” to “PC5” are added.

  FIG. 20 shows an example in which the master image name is set in the client management database 12A by the block B23. In the client computer “PC1”, for example, “A1” is set as the master image name. In the client computer “PC3”, for example, “A2” is set as the master image name. The client computer “PC5” indicates that the master image has not yet been selected.

Further, the flowchart of FIG. 21 shows an example of the procedure of the driver set management process executed by the driver set management module 16.
First, the driver set management module 16 reads client information with reference to the client management database 12A (block B31). The driver set management module 16 detects the model name included in the client information. For example, in the example of the client management database 12A shown in FIG. 20, “model 1” and “model 2” are detected.

  Next, the driver set management module 16 collects a corresponding driver set for each model (block B32). The driver set includes a plurality of drivers (driver programs) necessary for each model. The driver set management module 16 arranges the collected driver sets for each model as a driver file group 12C in the management server 1 (block B33).

  Next, the driver set management module 16 registers the driver set information indicating the arranged driver set in the driver set management database 12B (block B34). Specifically, the driver set management module 16 adds, for example, an entry including a model name and a driver set name to the driver set management database 12B. Then, the driver set management module 16 notifies the virtual image management module 17 that the driver set information is registered in the driver set management database 12B (block B35).

  Through the above processing, the driver set information indicating the driver set collected for each model is registered in the driver set management database 12B. For example, in the example shown in FIG. 7, it can be seen that the “driver 1” driver set is used for the “model 1” computer.

Next, an example of the procedure of the distribution image creation process executed by the virtual image management module 17 will be described with reference to the flowchart shown in FIG.
First, the second differential VHD generation unit 177 refers to the client management database 12A and determines whether there is a client computer whose status is “uncreated” (block B401). If there is no client computer whose status is “not created” (NO in block B401), that is, if the status of all client computers is “created”, the processing is terminated.

  When there is a client computer whose status is “not created” (YES in block B401), the second differential VHD generation unit 177 generates a setup differential VHD file whose parent is the VHD file of the master image corresponding to the client computer. By copying, a second differential VHD file (also referred to as a client VHD file) for the client computer is created (block B402). Then, the driver storage unit 178 mounts the created client VHD file (block B403).

  Next, the driver storage unit 178 reads the driver set corresponding to the model of the client computer with reference to the driver set management database 12B (block B404). Specifically, the driver storage unit 178 reads the driver set name corresponding to the model of the client computer with reference to the driver set management database 12B. Then, the driver storage unit 178 reads a driver set corresponding to the read driver set name from the driver file group 12C. The driver storage unit 178 arranges the read driver set at a predetermined position in the client VHD file (block B405).

  Also, the driver storage unit 178 reads the computer name corresponding to the client computer with reference to the client management database 12A (block B406). The driver storage unit 178 places the read computer name at a predetermined position in the client VHD file (block B407). Then, the driver storage unit 178 unmounts the client VHD file (block B408).

  Next, the setup unit 179 activates the OS on the virtual machine 14 using the client VHD file (block B409). That is, the setup unit 179 activates the OS using the client VHD file, the first differential VHD file that is the parent of the client VHD file, and the basic VHD file that is the parent of the first differential VHD file.

  When the OS is started on the virtual machine 14, OS setup processing (mini-setup) is executed by the setup module incorporated in the client VHD file. In this OS setup process, the computer name arranged in the client VHD file is set in the OS. The setup process may include a process for setting a product key, a process for setting network information such as an IP address, and a process for setting information on a user who uses the OS.

When the setup process is completed, the setup unit 179 rewrites the status of the client information corresponding to the client computer in the client management database 12A to “created” (block B410). Then, the setup unit 179 ends the running OS (virtual machine 14), and returns to block B401.
Through the above processing, the management server 1 can create a distribution image distributed to the client computer. At this time, by executing the setup process including the setting of the computer name on the management server 1 side, the client computer 2 does not need to perform the setup process. As a result, it is possible to reduce the time required for the client computer 2 to use the operating system using the distributed disk image.

  In addition, the amount of data can be reduced by managing the disk images used by a plurality of client computers using the basic VHD file and the differential VHD file. For example, a disk image (differential VHD file) including data such as a driver set that differs depending on the model of the client computer and a computer name that differs for each client computer is created for each client, and a disk image (OS image) on which the OS is installed is It is created as a basic VHD file shared between client computers. Thereby, it is not necessary to create an OS image for each client computer, and the amount of data can be reduced.

The flowchart of FIG. 23 shows an example of the procedure of image update processing executed by the communication module 24 provided in the client computer 2.
First, the list transmission request unit 241 requests the management server 1 to transmit a VHD file list (block B51). Then, the list receiving unit 242 determines whether or not the VHD file list transmitted by the management server 1 has been received (block B52). When the VHD file list has not been received from the management server 1 (NO in block B52), for example, the list receiving unit 242 waits for a predetermined period and executes block B52 again.

  When the VHD file list is received from the management server 1 (YES in block B52), the list reception unit 242 outputs the received VHD file list to the distribution request transmission unit 243. Then, the distribution request transmission unit 243 determines whether or not the currently received VHD file list is changed from the previously received VHD file list (block B53). The VHD file list includes IDs respectively corresponding to a plurality of VHD files used in the client computer 2 as shown in FIG. 24, for example. This VHD file list includes, for example, the ID “1” of the basic VHD file 401 (master image A), the ID “9” of the differential VHD file 409 (master image A1), and the ID of the differential VHD file 413 (PC1 image). “13” is included (see FIG. 11).

  If the currently received VHD file list has not been changed from the previously received VHD file list (NO in block B53), the distribution request transmitting unit 243 ends the process.

  When the currently received VHD file list is changed from the previously received VHD file list (YES in block B53), the distribution request transmitting unit 243 receives the last received VHD file included in the currently received VHD file list. The management server 1 is requested to distribute a VHD file not included in the VHD file list (block B54).

  Next, the VHD file receiving unit 244 determines whether or not the requested VHD file has been received from the management server 1 (block B55). When the VHD file requested from the management server 1 has not been received (NO in block B55), for example, the VHD file receiving unit 244 waits for a predetermined period and executes block B55 again.

  When the VHD file requested from the management server 1 is received (YES in block B55), the VHD file receiving unit 244 outputs the received VHD file to the VHD file updating unit 245. The VHD file update unit 245 updates the disk image stored in the client computer 2 using the received VHD file (block B56). The VHD file update unit 245 notifies the driver installation unit 271 that the disk image has been updated. The driver installation unit 271 installs a driver using the updated driver set when the disk image is updated at the next startup. The agent software 27 is not limited to the driver set, and performs necessary processing in response to the disk image being updated.

The flowchart shown in FIG. 25 shows an example of the procedure of the image update response process executed by the communication module 18 provided in the management server 1.
First, the list request receiving unit 181 determines whether or not a VHD file list transmission request has been received from a client computer (block B601). When the VHD file list transmission request has not been received from the client computer (NO in block B601), the list request receiving unit 181 executes block B601 again after waiting for a predetermined period, for example.

  When the VHD file list transmission request is received from the client computer (YES in block B601), the list request reception unit 181 notifies the list transmission unit 182 that the VHD file list transmission request has been received from the client computer. . The list transmission unit 182 refers to the client management database 12A and reads the status of the client information corresponding to the client computer (block B602). Then, the list transmission unit 182 determines whether or not the read status is “created” (block B603).

  When the read status is “created” (YES in block B603), the list transmission unit 182 reads the VHD file for the client computer from the VHD file group 12E (block B604). Then, the list transmission unit 182 detects the UUID of this VHD file from the read VHD file (block B605). The list transmission unit 182 adds the UUID of the detected VHD file to the VHD file list (block B606).

  Next, the list transmission unit 182 determines whether or not the parent VHD file exists in the read VHD file (block B607). For example, when the read VHD file is a differential VHD file, the list transmission unit 182 determines that the parent VHD file exists in the VHD file. For example, when the parent UUID is set in the read VHD file, the list transmission unit 182 determines that the parent VHD file exists in the VHD file.

  When the read VHD file has a parent VHD file (YES in block B607), the list transmission unit 182 reads the parent VHD file from the VHD file group 12E (block B608). Then, the list transmission unit 182 returns to the process of block B605.

  If the parent VHD file does not exist in the read VHD file (NO in block B607), that is, if the read VHD file is a basic VHD file, the list transmission unit 182 arranges the IDs added to the VHD file list. Change (block B609). Specifically, the list transmission unit 182 rearranges the IDs in order from the parent to the child, starting with the ID corresponding to the basic VHD file.

  After rearranging the IDs in the VHD file list or when the read status is not “created” (NO in block B603), the list transmission unit 182 transmits the VHD file list to the client computer 2 (block B610). . If the read status is not “created”, for example, a VHD file list that does not include an ID corresponding to the VHD file is transmitted.

  Next, the distribution request receiving unit 183 determines whether or not a VHD file distribution request has been received from the client computer 2 (block B611). When the VHD file distribution request is received from the client computer 2 (YES in block B611), the distribution request receiving unit 183 notifies the VHD file distribution unit 184 that the VHD file distribution request has been received from the client computer 2. To do. The VHD file distribution unit 184 reads the corresponding VHD file from the VHD file group 12E based on the VHD file ID specified in the distribution request. Then, the VHD file distribution unit 184 transmits the read VHD file to the client computer 2 (block B612).

  With the above processing, only the changed VHD file among the disk images (VHD files) used in the client computer 2 needs to be transmitted from the management server 1 to the client computer 2, thereby shortening the time required for transmission. be able to.

  As described above, according to the present embodiment, it is possible to shorten the time required until the operating system can be used on the virtual machine operating on the client computer. The management server 1 creates a distribution image distributed to the client computer. At that time, by executing the setup process including the setting of the computer name on the management server 1 side, the time required for the client computer 2 to use the operating system using the distributed disk image can be shortened. Can do.

  In addition, the amount of data can be reduced by managing the disk images used by a plurality of client computers using the basic VHD file and the differential VHD file. For example, a disk image (differential VHD file) including data such as a driver set that differs depending on the model of the client computer and a computer name that differs for each client computer is created for each client, and a disk image (OS image) on which the OS is installed is It is created as a basic VHD file shared between client computers. Thereby, it is not necessary to create an OS image for each client computer, and the amount of data can be reduced.

  Note that the virtual image creation process, client management process, driver set management process, distribution image creation process, image update process, and image update response process of this embodiment can all be executed by software. For this reason, this program is transmitted through a computer-readable storage medium storing a program for executing the procedures of virtual image creation processing, client management processing, driver set management processing, distribution image creation processing, image update processing, and image update response processing. The effects similar to those of the present embodiment can be easily realized simply by installing and executing on a normal computer.

  Although several embodiments of the present invention have been described, these embodiments are presented by way of example and are not intended to limit the scope of the invention. These novel embodiments can be implemented in various other forms, and various omissions, replacements, and changes can be made without departing from the scope of the invention. These embodiments and modifications thereof are included in the scope and gist of the invention, and are included in the invention described in the claims and the equivalents thereof.

  DESCRIPTION OF SYMBOLS 12 ... Host OS, 12A ... Client management database, 12B ... Driver set management database, 12C ... Driver file group, 12D ... Master image management database, 12E ... VHD file group, 15 ... Client management module, 16 ... Driver set management module, DESCRIPTION OF SYMBOLS 17 ... Virtual image management module, 171 ... Master VHD production | generation part, 172 ... OS installation part, 173 ... 1st difference VHD production | generation part, 174 ... Application installation part, 175 ... Master image registration part, 176 ... Setup VHD production | generation part, 177 2nd differential VHD generation unit, 178 ... driver storage unit, 179 ... setup unit, 18 ... communication module, 181 ... list request reception unit, 182 ... list transmission unit, 183 ... distribution request reception unit, 18 ... VHD file distribution unit, 2 ... client computer, 24 ... communication module 24, 241 ... list request transmission unit, 242 ... list reception unit, 243 ... distribution request transmission unit, 244 ... VHD file reception unit, 245 ... VHD file update unit , 26... OS used by the user, 27... Agent software, 271.

Claims (18)

First and second differential virtual hard disks that generate a master virtual hard disk image on which an operating system to be executed on a virtual machine is installed, correspond to the first and second client computers, and depend on the master virtual hard disk image A virtual hard disk image generation means for generating an image;
A storage device for storing a client information database indicating a computer name of each of the first and second client computers;
Causing the first operating system to execute a first setup process by booting a first operating system corresponding to the pair of the master virtual hard disk image and the first differential virtual hard disk image on the virtual machine; Causing the second operating system to execute a second setup process by booting a second operating system corresponding to the pair of the master virtual hard disk image and the second differential virtual hard disk image on the virtual machine; The computer name of the first client computer is read from the client information database, and the computer name of the read first client computer is read as the first differential virtual hard disk. Set-up means for setting an image, reading the computer name of the second client computer from the client information database, and setting the computer name of the read second client computer in the second differential virtual hard disk image; ,
Delivering a pair of the master virtual hard disk image and the first differential virtual hard disk image to the first client computer for executing the first operating system on a virtual machine in the first client computer; Delivering a pair of the master virtual hard disk image and the second differential virtual hard disk image to the second client computer for executing the second operating system on a virtual machine in the second client computer Distribution means for
The virtual hard disk image generation means further generates a third differential virtual hard disk image depending on the master virtual hard disk image or the first differential virtual hard disk image to update the first operating system,
The information processing apparatus further distributes the third differential virtual hard disk image to the first client computer. In response to an ID list request by the first client computer, an ID list including one or more IDs indicating one or more virtual hard disk images distributed to execute the first operating system is provided in the first list. List sending means for sending to client computers of
ID receiving means for receiving from the first client computer an image request including an ID selected by the first client computer from the one or more IDs included in the ID list;
The information processing apparatus according to claim 1, wherein the distribution unit distributes a virtual hard disk image or a differential virtual hard disk image corresponding to an ID included in the received image request to the first client computer.   The information processing apparatus according to claim 1, wherein the virtual hard disk image generation unit generates the master virtual hard disk image in which an operating system executed on the virtual machine and a predetermined application program are installed. Prior to distribution of the pair of the master virtual hard disk image and the first differential virtual hard disk image, a first ID including an ID indicating the master virtual hard disk image and an ID indicating the first differential virtual hard disk image When an ID list request is received from the first client computer after the list is transmitted to the first client computer and the third differential virtual hard disk image is generated, the ID indicating the master virtual hard disk image and the List transmitting means for transmitting a second ID list including an ID indicating a first differential virtual hard disk image and an ID indicating the third differential virtual hard disk image to the first client computer;
ID receiving means for receiving, from the first client computer, an image request including an ID indicating the third differential virtual hard disk image selected from the second ID list by the first client computer. ,
The information processing apparatus according to claim 1, wherein the distribution unit distributes the third differential virtual hard disk image to the first client computer in response to receiving a request including the ID. First and second differential virtual hard disks that generate a master virtual hard disk image on which an operating system to be executed on a virtual machine is installed, correspond to the first and second client computers, and depend on the master virtual hard disk image Generate an image,
Causing the first operating system to execute a first setup process by booting a first operating system corresponding to the pair of the master virtual hard disk image and the first differential virtual hard disk image on the virtual machine; Causing the second operating system to execute a second setup process by booting a second operating system corresponding to the pair of the master virtual hard disk image and the second differential virtual hard disk image on the virtual machine; A computer name of the first client computer is read from a client information database indicating a computer name of each of the first and second client computers, and the read first computer is read. The computer name of the client computer is set in the first differential virtual hard disk image, the computer name of the second client computer is read from the client information database, and the computer name of the read second client computer is set as the computer name. Set it to the second differential virtual hard disk image,
Delivering a pair of the master virtual hard disk image and the first differential virtual hard disk image to the first client computer for executing the first operating system on a virtual machine in the first client computer; Delivering a pair of the master virtual hard disk image and the second differential virtual hard disk image to the second client computer for executing the second operating system on a virtual machine in the second client computer And
The generating further generates a third differential virtual hard disk image depending on the master virtual hard disk image or the first differential virtual hard disk image to update the first operating system;
The distributing is a client management method of further distributing the third differential virtual hard disk image to the first client computer. In response to an ID list request by the first client computer, an ID list including one or more IDs indicating one or more virtual hard disk images distributed to execute the first operating system is provided in the first list. To the client computer
Receiving, from the first client computer, an image request including an ID selected by the first client computer from the one or more IDs included in the ID list;
6. The client management method according to claim 5, wherein the distributing includes distributing a virtual hard disk image or a differential virtual hard disk image corresponding to an ID included in the received image request to the first client computer.   The client management method according to claim 5, wherein the generating generates the master virtual hard disk image in which an operating system executed on the virtual machine and a predetermined application program are installed. Prior to distribution of the pair of the master virtual hard disk image and the first differential virtual hard disk image, a first ID including an ID indicating the master virtual hard disk image and an ID indicating the first differential virtual hard disk image When an ID list request is received from the first client computer after the list is transmitted to the first client computer and the third differential virtual hard disk image is generated, the ID indicating the master virtual hard disk image and the Transmitting a second ID list including an ID indicating a first differential virtual hard disk image and an ID indicating the third differential virtual hard disk image to the first client computer;
Receiving an image request from the first client computer including an ID indicating the third differential virtual hard disk image selected from the second ID list by the first client computer;
6. The client management method according to claim 5, wherein the distributing includes distributing the third differential virtual hard disk image to the first client computer in response to receiving a request including the ID. Virtual hard disk image generation means for generating a master virtual hard disk image on which an operating system to be executed on a virtual machine is installed, and generating a first differential virtual hard disk image corresponding to the client computer and depending on the master virtual hard disk image When,
A storage device for storing a client information database indicating a computer name of the client computer;
Starting the operating system corresponding to the pair of the master virtual hard disk image and the first differential virtual hard disk image on the virtual machine to cause the operating system to execute a setup process, and from the client information database, the client Setup means for reading the computer name of the computer and setting the computer name of the read client computer in the first differential virtual hard disk image;
An information processing apparatus comprising: distribution means for distributing a pair of the master virtual hard disk image and the first differential virtual hard disk image to the client computer in order to execute the operating system on a virtual machine in the client computer . List transmitting means for transmitting to the client computer an ID list including one or more IDs indicating one or more virtual hard disk images distributed to execute the operating system in response to an ID list request by the client computer When,
ID receiving means for receiving, from the client computer, an image request including an ID selected by the client computer from the one or more IDs included in the ID list;
The information processing apparatus according to claim 9, wherein the distribution unit distributes a virtual hard disk image or a differential virtual hard disk image corresponding to an ID included in the received image request to the client computer.   The information processing apparatus according to claim 9, wherein the virtual hard disk image generation unit generates the master virtual hard disk image in which an operating system executed on the virtual machine and a predetermined application program are installed. The virtual hard disk image generation means further generates a second differential virtual hard disk image depending on the master virtual hard disk image or the first differential virtual hard disk image to update the operating system;
The information processing apparatus according to claim 9, wherein the distribution unit further distributes the second differential virtual hard disk image to the client computer. Prior to distribution of the pair of the master virtual hard disk image and the first differential virtual hard disk image, a first ID including an ID indicating the master virtual hard disk image and an ID indicating the first differential virtual hard disk image When an ID list request is received from the client computer after the list is transmitted to the client computer and the second differential virtual hard disk image is generated, the ID indicating the master virtual hard disk image and the first differential virtual hard disk List transmitting means for transmitting a second ID list including an ID indicating an image and an ID indicating the second differential virtual hard disk image to the client computer;
ID receiving means for receiving an image request including an ID indicating the second differential virtual hard disk image selected from the second ID list by the client computer from the client computer;
13. The information processing apparatus according to claim 12, wherein the distribution unit distributes the second differential virtual hard disk image to the client computer in response to receiving the request including the ID. Generating a master virtual hard disk image on which an operating system running on the virtual machine is installed, generating a first differential virtual hard disk image corresponding to the client computer and dependent on the master virtual hard disk image;
The operating system corresponding to the pair of the master virtual hard disk image and the first differential virtual hard disk image is started on the virtual machine to cause the operating system to execute a setup process, and the computer name of the client computer is changed. Reading the computer name of the client computer from the client information database shown, and setting the computer name of the read client computer in the first differential virtual hard disk image;
A client management method for distributing a pair of the master virtual hard disk image and the first differential virtual hard disk image to the client computer in order to execute the operating system on a virtual machine in the client computer. In response to an ID list request by the client computer, an ID list including one or more IDs indicating one or more virtual hard disk images distributed to execute the operating system is transmitted to the client computer;
Receiving from the client computer an image request including an ID selected by the client computer from the one or more IDs included in the ID list;
The client management method according to claim 14, wherein the distributing includes distributing a virtual hard disk image or a differential virtual hard disk image corresponding to an ID included in the received image request to the client computer.   The client management method according to claim 14, wherein the generating generates the master virtual hard disk image in which an operating system executed on the virtual machine and a predetermined application program are installed. The generating further generates a second virtual virtual hard disk image dependent on the master virtual hard disk image or the first differential virtual hard disk image to update the operating system;
15. The client management method according to claim 14, wherein the distributing further distributes the second differential virtual hard disk image to the client computer. Prior to distribution of the pair of the master virtual hard disk image and the first differential virtual hard disk image, a first ID including an ID indicating the master virtual hard disk image and an ID indicating the first differential virtual hard disk image When an ID list request is received from the client computer after the list is transmitted to the client computer and the second differential virtual hard disk image is generated, the ID indicating the master virtual hard disk image and the first differential virtual hard disk A second ID list including an ID indicating an image and an ID indicating the second differential virtual hard disk image is transmitted to the client computer;
Receiving from the client computer an image request including an ID indicating the second differential virtual hard disk image selected by the client computer from the second ID list;
18. The client management method according to claim 17, wherein the distributing includes distributing the second differential virtual hard disk image to the client computer in response to receiving a request including the ID.

Images