JP2003140852A - Network system, information processing device, information processing method and control program - Google Patents

Abstract

PROBLEM TO BE SOLVED: To set up a driver by a simple operation, when the driver of peripheral equipment on a network is not installed. SOLUTION: When a setup instruction of the driver is generated, an instruction is transmitted so that the driver designated by a user is set up on a designated PC, and setup processing of the driver is executed following the instruction. For example, in the case of a printer driver, it is determined whether the setup processing is finished normally or not, and when the driver is installed normally, test print is executed.

Description

Detailed Description of the Invention

[0001]

BACKGROUND OF THE INVENTION 1. Field of the Invention The present invention relates to a network system, an information processing device, a method, and a computer-readable storage medium, and displays and manages information processing devices and peripheral devices shared on a network. Regarding

[0002]

2. Description of the Related Art In recent years, personal computers (hereinafter,
Along with the widespread use of peripheral devices such as PCs), printers, scanners, digital cameras, etc., networks such as LANs have also become widespread, and there is an increasing need for sharing printers, modems, scanners, etc. by a plurality of PCs on the network. It was In addition, many drivers for using these peripheral devices have been provided, and installation methods have been provided.

As an installation method, a printer driver is stored in a specific directory of a server device connected to a client device via a network, and driver installation or version upgrade of the client device is performed based on an instruction from the client device. There is a way to do it. In addition, there is a technique of notifying a client device of an update of a driver stored in a predetermined server device, and requesting the transmission of the driver in the server device by the client, thereby downloading the driver by pulling from the client.

Further, although not driver distribution, in the world of data distribution, there is known a technique for performing data distribution by push without waiting for a request from a client device when data is updated in a data distribution server device. Has been.

[0005]

In order to make peripheral devices available, it is necessary to install a driver corresponding to each device. For example, when a new device is available on the client device, a new driver needs to be added. There is also a problem of how to upgrade the driver version when the driver is already installed.

When the driver installation or version upgrade is completed for the client device,
There is a problem that it is difficult to determine whether the driver is actually set up normally.

Furthermore, the procedure of driver installation, version upgrade, and setup differs for each device. Moreover, the driver type must be selected according to the environment of the device or the client device, and the operation is complicated. Further, according to the conventional technology, a complicated process must be executed in a client that adds or changes a driver or sets a driver based on an instruction from a client device, which causes a problem that work efficiency is extremely low. .

Further, in recent years, the network system has become large in scale, and there are many opportunities to install or upgrade drivers for a plurality of client devices and set up the drivers. Cumbersome driver installation process or version upgrade process,
Alternatively, there is a problem that the work load when the driver setting process is performed on the client device is further increased.

In order to solve such a problem, the present invention provides
An object of the present invention is to provide a mechanism for reducing the work load when setting up information and enabling the driver information setup process for a client device to be performed by a simple work.

Further, in a printing system including a plurality of client devices, the setup condition of each client device in which the driver should be installed is so that each user can perform the installation process without being aware of the driver setup condition. The purpose is to provide a mechanism for implementing the driver installation processing according to.

Further, in order to avoid a complicated installation operation in the client device,
An object of the present invention is to provide a mechanism for performing push installation and driver setup without waiting for a request from a client device from a server device to a client device.

It is another object of the present invention to provide a mechanism for executing a test print after the driver information installation is completed in order to check whether the driver information setup is normally completed.

Further, if the above-mentioned problems are solved in the present application, the following problems will appear. When the drivers are collectively installed in the client device by the push installation, there is a problem that the burden of work for checking the operation of each client device one by one is large if the driver information is properly set up in the plurality of client devices. Therefore, one of the embodiments of the present invention is to push-install driver information from a server device to a plurality of client devices in order to enable confirmation of whether or not a peripheral device has been normally set up after a setup instruction. , The purpose is to make a test print.

[0014]

The present invention provides the following means in order to achieve the above object.

According to a first aspect of the present invention, in an information processing apparatus that communicates with a client apparatus, apparatus management means for managing a setup status of a driver of a peripheral device connected to the client apparatus in the client apparatus, and the setup status. And a transmission control means for controlling the process of transmitting the driver information corresponding to the plurality of client devices to the client device.

According to a second aspect of the present invention, the setup status includes information indicating a version of the driver information incorporated in the client device, and the transmission control means indicates that the information indicating the version is the server device. If the driver information is older than the existing driver information, the transmission process is controlled so that the driver information included in the server device is transmitted to the client device.

According to a third aspect of the present invention, the set-up f
The up status includes identification information of driver information incorporated in the client device, and the transmission control unit is faf,
When the driver information indicated by the identification information of the driver information does not exist in the client device, the transmission process is controlled so as to transmit the driver information to the client device.

According to a fourth aspect of the present invention, the setup status is collected by the server device by communicating with the client device.

According to a fifth aspect of the present invention, the driver information includes a printer driver.

According to a sixteenth aspect of the present invention, in an information processing device that communicates with a plurality of client devices, a determination means that determines a plurality of client devices for which driver information should be installed, and a peripheral device connected to the client devices. And transmission control means for controlling the process of delivering the driver information for controlling the above to the plurality of clients judged by the judgment means.

According to a seventeenth aspect of the present invention, the driver information is printer driver driver information, and the driver information includes a test print instruction for a printer in which the driver information is set up. .

The invention described in claim 18 is characterized in that the client device sets up the driver information based on the setup instruction.

According to a nineteenth aspect of the present invention, the information processing apparatus has a selecting means for manually selecting a client device, and the judging means judges the client device selected by the selecting means. Characterize.

According to a twenty-eighth aspect of the present invention, in an information processing device that communicates with a peripheral device and a server device, a recognition means for recognizing a setup instruction and driver information from the server device and a setup instruction to the server device are requested. Without having to do so, in response to recognizing the setup instruction, it has a program management means for installing driver information for controlling the peripheral device in the client device.

According to a twenty-ninth aspect of the invention, the program management means controls the client device so that the client device registers in association with the identification information of the peripheral device and the driver information.

According to a thirtieth aspect of the present invention, the program management means is an OS installed in the client device.
The OS is controlled so as to be recognized by the OS in a state of being associated with the identification information of the peripheral device and the driver information via the application programming interface of.

According to a thirty-first aspect of the present invention, the program management means compares the identification information of the existing driver stored in the client device with the identification information of the driver instructed by the setup instruction, When the identification information of the existing driver and the identification information of the driver instructed to set up do not match, the driver instructed to set up is stored in the client device.

In the thirty-second aspect of the present invention, in the program management means, the information indicating the version of the existing driver stored in the client device is newer than the information indicating the version of the driver instructed to be set up. In the case of, the driver information of the client device is updated to the driver information instructed to perform the setup.

According to a forty-third aspect of the present invention, in an information processing device that communicates with a server device and a peripheral device, program management means for performing driver setup based on a driver setup instruction of the peripheral device from the server device. , In response to the end of the setup,
It is characterized by generating an instruction for causing the peripheral device to perform a test print for confirming that the setup is normally completed.

According to a forty-fourth aspect of the present invention, the program management means is an OS installed in the client device.
The OS installation means is called via the application programming interface, and the OS installation means called via the application programming interface introduces driver information into the client device.

The invention according to claim 45 is the information processing device according to claim 43 or 44, characterized in that the program management means is activated in response to a command from the server device.

According to the forty-sixth aspect of the present invention, the command from the server device is a simple object access
It is characterized by being described using a protocol.

According to a 55th aspect of the present invention, in an information processing apparatus that communicates with a client apparatus, a determination means for determining a client apparatus which is a driver setup destination, an instruction for setting up the driver to the client apparatus, and the above It is characterized by further comprising transmission control means for controlling the process of transmitting to the client device an instruction for causing the client device to perform a test print for confirming that the driver setup for the client device has been completed normally.

According to a 56th aspect of the present invention, the information processing apparatus communicates with a plurality of client apparatuses, and the transmission control means instructs to install driver information, and
It is characterized by having a transmission control means for controlling a transmission process so as to transmit the instruction of the test print to the plurality of client apparatuses.

According to a 57th aspect of the present invention, the information processing apparatus further has a selecting means for manually selecting a client apparatus, and the judging means judges the client apparatus selected by the selecting means. It is characterized by

The invention described in Item 58 is characterized in that a test print request source is printed in the test print.

The invention described in Item 59 is characterized in that, in the test print, the print server name used when the test print is performed is printed.

In a seventy-first aspect of the invention, in a network system including a client device and a server device, a device management means for managing a setup status of a driver of a peripheral device connected to the client device in the client device, and the setup. Transmission control means for controlling a process of transmitting driver information corresponding to the client device to a plurality of client devices based on a situation; recognition means for recognizing a setup instruction and driver information from the server device; and the server device. Program management means for installing driver information for controlling the peripheral device in the plurality of client devices in response to receiving the driver information from the server device without requesting driver information from the server device. Characterized by having It is a network system that.

According to a 72nd aspect of the present invention, in an information processing apparatus which communicates with a client apparatus, a determination means for determining a client apparatus which is a driver setup destination, an instruction for setting up the driver to the client apparatus, and the above Transmission control means for controlling the process of transmitting a test print instruction confirming that the driver setup to the client device has been normally completed, a setup instruction from the server device, driver information, and Receiving means for receiving the instruction of the test print, and a driver for controlling the peripheral device in response to receiving the driver information from the server device without requesting the driver information from the server device. Information on the client device Installed in a network system, comprising a program management means for issuing an instruction for test printing on the basis of an instruction of the test print.

The inventions described in claims 6 to 15 are inventions of methods or control programs corresponding to the inventions described in claims 1 to 5, and the inventions described in claims 20 to 27 are claims 16 to 19. The invention of a method or a control program corresponding to the invention described in claim 33, the invention of claims 33 to 42 is an invention of a method or a program corresponding to the invention of claims 28 to 32, and The inventions described in claims 54 to 54 are inventions of methods or programs corresponding to the inventions claimed in claims 43 to 46, and the inventions claimed in claims 60 to 69 are methods corresponding to the inventions claimed in claims 55 to 59. Alternatively, the invention according to claim 70 is the invention of a medium, and the invention according to claim 70 is an invention of a medium corresponding to claims 1 to 5, claims 16 to 19, claims 28 to 32, and claims 55 to 59. Substantially.

[0041]

BEST MODE FOR CARRYING OUT THE INVENTION Embodiments of a network system, an information processing apparatus, a method, and a control program computer-readable storage medium of the present invention will be described below with reference to the drawings.

FIG. 1 is a block diagram for explaining the configuration of a PC showing a preferred example of the information processing apparatus used in the embodiment of the present invention. In FIG. 1, reference numeral 1 denotes a system bus, to which the following constituent blocks are connected via the system bus 1. In each of the embodiments of the present application, a PC having the following configuration is used as a preferred example of a client device to which a driver is to be installed and an install server device that issues a driver setup instruction to the client device.

2 is a CPU (Central Process)
singing Unit). Reference numeral 3 denotes a program memory (hereinafter referred to as PMEM), which appropriately selects / reads a program for processing described later from the hard disk 10 and executes the program by the CPU 2. Also, the keyboard 12
The data input from the PM is also a text memory
It is stored in the EM as code information.

A communication control unit 4 controls input / output data in the communication port 5. The signal output from the communication port 5 is transmitted to the communication port of another device (denoted by reference numeral 7 in FIG. 1) on the network via the communication line 6. Communication with printers, scanners and the like shared on the network is performed via this communication control unit 4. Although a network such as a LAN is described in the present embodiment, it goes without saying that the present invention is applicable even if the communication port 5 and the communication line 6 connected to the communication control unit 4 are general public lines. .

Reference numeral 8 is an external storage device control unit. 9, 10
Is a disk for data files, for example, 9 is a floppy (registered trademark) disk FD and 10 is a hard disk HD. A driver installation module is stored in the HD 10 of the client apparatus, and an installer for setting up a driver for the client apparatus is installed in the HD 10 of the server apparatus. Then, each program is loaded from the HD 10 of each device to the PMEM 3 as needed, and is executed by the CPU 2.

Reference numeral 11 denotes an input control section (input control means) to which an input device (input means) such as a keyboard 12 and a mouse 13 is connected. The user can operate the keyboard 12 to issue a system operation command or the like. The mouse 13 also functions as a pointing device PD on the CRT 16 for instructing processing of image information, whereby the cursor on the CRT 16 is arbitrarily moved in the X and Y directions to select a command icon on the command menu. In addition to instructing processing, it is possible to instruct an object to be edited, instruct a drawing position, input a GUI command, and the like. For example, when the user uses the PD to move the cursor to a predetermined position on the screen and the user presses a predetermined portion of the PD in this state, the driver installation module installed in the device responds to the input, It operates such as issuing various commands. The driver installation module is a preferred example of the transmission control unit, and the OS controls the communication control unit such that the OS operates the communication control unit according to a predetermined command to transmit desired information. it can.

14 is a video image memory (VRAM)
15 is a display output control unit and 16 is a CRT
(Cathode-Ray Tube). The data displayed on the CRT 16 is expanded on the VRAM 14 as bitmap data.

Reference numeral 17 denotes a printer control unit, which controls output of data to the connected printer 18. 1
An image reading device control unit A controls the connected image reading device 1B.

The program stored in the PMEM 3 in this embodiment may be stored in a storage medium such as the hard disk 10 or the floppy disk 9. Further, it may be stored on another device connected to the network.

(First Embodiment) A case where a driver for a peripheral device is set up will be described below with reference to FIGS. FIG. 2 is a flowchart showing a processing operation for setting up a driver in the server device. First, in step S201, the server device, which is a preferred example of the information processing device, acquires the connection status information of the PC and the peripheral device on the network by the device management module (device management means) in the server device, and the information is acquired. Memorize Peripheral devices include, for example, inkjet printers, digital cameras, copiers having a printer function, and the like.

Next, in step S202, the server device acquires and recognizes information indicating the setup status of the peripheral device of each PC. Peripheral device drivers include drivers for printers, scanners, digital cameras, fax machines, and the like. As a method of acquiring the setup status information, for example, by activating a module (device management means) that acquires driver information installed in the device on each PC, the module communicates with peripheral devices and other PCs and collects information. Then, it is possible to communicate such information through a network. The driver information is, for example, a device driver for controlling the peripheral device, and the setup status of the driver of the peripheral device is the registered name of the registered peripheral device, the driver name for operating the peripheral device (driver (Registered name in the system), driver version information, driver module name, etc. The device name is a preferred example of printer identification information. The driver name is a preferred example of driver identification information. For example, the printer name and the driver name include identifiers such as numbers and symbols that can be recognized by the information processing device, other than character strings.

FIG. 3 is a diagram showing an example of the driver information structure that has been set up. It is composed of a PC name, an IP address, an OS type, a user name, the number of device drivers, and information about each device driver. Each device driver information includes a device type such as a printer or a scanner, a driver name, version information, an output port, and shared information. For example, the printer registered first has a driver name of printer2000, a version of 1.00.00, an output port of local, and shared information of shared setting (ON).

FIG. 4 is a diagram showing an example of a screen for displaying PCs and peripheral devices on the network. Reference numeral 401 is a menu, 402 is a toolbar, and 403 is a main window on which icons representing PCs and peripheral devices on the network are displayed.

Reference numerals 402a to 402g denote a toolbar 402.
Are icons representing respective functions performed by operating the PC and peripheral devices. For example, 402a is an icon for executing a copy function of reading image data from the selected scanner and outputting the image data to the selected printer. 402b is a FAX function, 402c is an image data reading function, 402d is a function for reading image data,
Reference numeral 402e is an icon for executing a function of performing OCR processing, 402e is a function of managing FAX reception data and delivery data, 402f is a function of updating information, and 402g is an icon for executing a function of stopping the update processing.

403a to 403ae are icons representing PCs and peripheral devices shared on the network. These icons 403a to 403ae are P
The icon is changed and displayed depending on the type of device such as C, printer, scanner, or fax modem, or the status such as "in process" or "error occurred". 403
a is an icon representing the own device, and 403b is an icon representing the domain in which the own device is logged on. Since its own device is a special device, it is displayed separately from other PCs.

Further, like the icon 403ad, the icons of PCs and peripheral devices which are shared on the network but have no driver installed are grayed out. A “+” mark is displayed when connected devices are present but not expanded and displayed like icons 403d and 403e, and a “−” mark is displayed when expanded like icon 403ab. . Icon 4
When there is no connected device like 03c and 403g, no mark is added.

In this way, the connection status of all PCs and peripheral devices on the network, and further the status can be confirmed on the screen. In this example, all the icons are not displayed for the convenience of the screen, but all the PCs and peripheral devices can be confirmed by using the scroll bar arranged on the side of the screen.

FIG. 5 is a diagram showing an example of a screen displaying the driver setup status of each PC on the network. Reference numeral 501 is a menu, 502 is a toolbar, and 503 is a main window on which icons representing PCs and peripheral devices on the network are displayed.

Reference numerals 502a to 502g denote the toolbar 502.
Is an icon representing each function performed by operating the PC and peripheral devices, and the content thereof is the icon 40 shown in FIG.
The same as 2a`402g. Reference numerals 503a to 503n are icons representing PCs and peripheral devices shared on the network. Here, the driver information of the peripheral device is displayed and can be confirmed.

Returning to the flowchart of FIG. 2, in step S203, the installer in the installation server device determines whether or not to set up the driver of the peripheral device. For example, in FIG. 4, the printer 403a
By selecting d, driver setup instructions can be given from the menu. If there is no driver setup instruction, this process ends.

When there is a driver setup instruction, the process proceeds to step S204, and a screen for prompting the user to set up a driver is displayed. FIG. 6 is an example of a screen for selecting the driver to be set up. Here, the manufacturer is selected and the user specifies the target printer. In addition, the user can specify a folder containing setup information.

Further, in step S205, based on the input from the PD, the installer in the install server device selects the client device for which the driver is set up. FIG. 7 is an example of a screen for selecting a client device for which a driver is set up. Here, a domain and a client device are selected. On this occasion,
Multiple client devices can be selected.

When the installer in the install server device receives an OK instruction from the PD or the like, the installer proceeds to step S206 and determines whether or not the instructed driver needs to be set up in each instructed client device. , Driver information from each client device. If you do not need to set up because the specified driver is already installed, etc.,
Do not install.

If the installer in the install server device needs to be set up, step S20 is performed.
7 and sends an instruction to the client device instructed in step S205 to execute the driver setup process instructed in step S204.
Control S. Then, the driver setup process is executed according to the instruction. The setup instruction includes a driver setup instruction structure and a setup instruction command. FIG. 8 is an example of a driver setup instruction structure included in the setup instruction, and includes a device type, driver name, version information, output port, setup information, and the like. The setup information may be sent together with this structure, but may be stored in a shared folder on the network and the path name thereof may be designated.

Next, in step S208, the installer in the install server device determines whether or not the driver setup processing has been completed normally. As a determination method, it is determined whether or not the driver installation processing is normally performed, and at the same time, it is determined whether or not the driver actually operates normally. For example, when the driver can be installed normally, a message indicating normal completion is transmitted to the client device that has given the setup instruction so that it can be confirmed on the screen.

In the case of a printer, a test print may be further executed to check the print result to determine whether the installation was successful. FIG. 9 shows an example of driver setup confirmation printing. In this way, by printing the output source client device name, the driver name, the version information, etc., which is the print request source, it is possible to confirm on which client device the setup processing has been completed normally. If the processing ends normally, the processing ends.

If the process is not completed normally, step S20.
In step 9, the installer in the install server device determines whether or not to issue an execution instruction again to the client device that did not end normally. If there is a re-execution instruction, the process returns to step S204, and if there is no re-execution instruction, the process ends.

As described above, when the driver for the peripheral device is not installed on the screen displaying the client device and the peripheral device shared on the network, the driver can be installed by a simple operation, and You can confirm that it was actually installed, and you can greatly improve the work efficiency on the network.

(Second Embodiment) FIG. 39 is a diagram showing an example of a printing system according to the present embodiment. A client device A indicated by 381 which is a preferable example of a client, a client device B indicated by 382, a client device C which is indicated by 383, an installation server device 385 which is a preferable example of a server device, and a web server device 386 are preferable for a network. They are connected via a LAN (Local Area Network) 360, which is an example. In the install server device 385 and the web server 386 of the present embodiment, client devices 381 to 383 are configured by a PC which is a preferred example of the information processing device, and the internal structure thereof is the same as that in FIG.

FIG. 32 shows an installation server device 385.
9 is a flowchart of an example in the installation server device 385 when a remote installation instruction of a driver is given from FIG. This processing is started when an installer (transmission control means) having a remote installation function mounted on the installation server device 385 is activated. The operation of the installer in the install server device 385 will be described below. Hereinafter, the client device A, the client device B, and the client device C are collectively referred to as “each client device”.

First, the installer in the install server device 385 determines in step S3201 whether or not a remote installation instruction has been given to each client device. The remote installation instruction may be issued by, for example, the user using C of each client device in FIG.
When the mouse 13 or the keyboard 12 is operated with reference to the graphical user interface displayed on the RT 16, a setup instruction is input to the input control unit 11 in response to the operation. Here, the installation server device 3
If the installer in 85 determines that there is no remote installation instruction, the process ends. When performing remote installation, the installer in the install server device 385 moves to step S3202. On the other hand, if it is determined in step S3201 that the installer in the install server device 385 has instructed remote installation, the process advances to step S3202 to create setup information for the driver to be remotely installed. The driver setup information is a driver name that is a preferred example of identification information of the driver to be installed,
It is composed of information such as a driver version number which is a preferable example of information indicating a driver version, a printer name which is a preferable example of device identification information, an output port name, a module for making a port available, and the like. . Also,
The printer name is a registered name registered in the registry of the OS of each client device. FIG. 33 is an example of a screen for setting driver information.

Reference numeral 331 is a printer name designating section. The printer name instructing unit 331 can select or input a printer name to be registered in each client device. A plurality of printers searched for on the network are assigned to the printer name designating unit 3
The instruction may be made at 31. Next, 332 is a port designation unit. In the port designation section, a port can be added by pressing the addition instruction section for 334 ports with a mouse. FIG. 33 shows a state in which an IP address as information indicating the location of the printer on the network and the use of lpr as the printing protocol are specified, and logical ports associated with these are created. . Although lpr is a traditional print management program developed by a BSD OS, other print management programs may be used. Reference numeral 333 is a driver designation unit for instructing a driver to be installed in each client device. A driver can be designated by operating the driver addition instruction unit 335.

The above uses TCP / IP and lpr
This is an example of port creation when a network printer is made to perform print processing. Ports can also be created for local printers. For example, when setting a local printer of a client device, a COM port or L
The PD port may be designated and the setup status information may be created based on this.

Further, it is possible to set the port to indicate printing via the print server. For example, when the print server name of the print server 387 is "SVPC1" and the printer name of the printer 384 is LASER950, if "\\ SVPC1 \ LASER950" is specified as the port, the SVPC1 is used as a print server to print to the LASER950. The port to set the port is set.

Further, in the above process, the install server device 385 collects the OS type and the OS version in advance and install server device 385.
Automatic determination is performed based on the information of each client device stored therein. However, if the OS installed in each client device cannot be automatically determined, before the installer generates the setup information in S3202,
The graphical user interface shown in FIG. 33 may be modified so that the user can specify the type and version of the OS and the architecture of the CPU.

Then, the process proceeds to step S3203 and the process shown in FIG.
As shown in FIG. 4, the installer in the install server device 385 selects the client device to install the selected driver. It is also possible to select multiple client devices at the same time. After selecting the client device to be installed, the installer (judgment means) in the install server device 385 judges the selected PC and performs the process of step S3204. Here, the installer in the install server device 385 sets whether to execute the test print when the driver installation is completed on each client device. The installer in the install server device 385 performs the process of step S3206 when the test print execution is not set. Here, when setting the test print execution, the process proceeds to step S3205, and
The installer in the install server device 385 additionally stores the test print instruction information in the setup information.

FIG. 34 is an example of a screen for instructing a client device for setting up a driver and a test print. In this way, it is possible to select a plurality of client devices at the same time. Also, ON / OFF of test print execution can be set. In this example, the client device in the domain is selected, but other designation methods are also possible.

In step S3206, the installer (determination means) in the server device determines one or a plurality of client devices for which the setup information set in the above process and the driver to be installed are instructed, and the determined clients Send to the device and end the process.

FIG. 37 is a diagram showing modules of software as a preferable example in each client apparatus. Here, an example of a general driver installation process will be described. An OS is installed in the client device. The configuration in each client device is the user area 37.
1 and the OS 377 area. The driver installation module 371 is prepared as an application that operates on the OS, and is a preferred example of the program management unit and the recognition unit. The system program of 379 is the driver name stored in the client device,
The version number, the printer name, and the driver directory in the system are registered in the registry 376. And the driver installer module (recognition means)
The information in the registry 376 can be recognized through the API (application programming interface) of the OS. Here, the driver installation module 371 is designed to operate in response to a command received from an external device. The driver installation module 371 (program management means) is an API
The system installer 374 (OS installation means) is called via. The system installer is O
The driver 372, which is prepared as one function of S and is externally introduced and stored in the user area 376, is copied or moved to the system file area 375. A part of this system file area is a registry area 376 for registering various information of a device using a driver.
Is secured. The driver installer module 371 can also call the system installer 374 to store the device information in the registry area.

FIG. 35 shows the installation server device 305.
7 is a flowchart of an example in each client device when a remote installation instruction of a driver is given from FIG. No operator is required at each client device. A module for driver installation that has already been activated (hereinafter referred to as a driver installation module) monitors for an instruction from the installation server device 305.

Here, the driver installation module is assumed to be resident in the client device. And the driver installation module
Waiting for an instruction from the install server device 305.
The driver installation module may be activated in response to a remote activation command from the installation server device 385 to automatically start the installation process. SOAP (Simple) which is an example of RPC
It is preferable to call the driver installation module remotely by using Object Access Protocol). Alternatively, the installation server device 3
Each client device receives a restart command from 85,
Each client device may be set so that the driver installation module is activated when the client device is rebooted, and the driver installation module may execute the setup instruction after the reboot. As a result, resources such as RAM can be effectively used and security can be improved rather than making the driver installation module always resident.

The processing in the driver installation module will be described below.

First, the driver installation module (recognition means) recognizes and determines whether or not there is an installation instruction from the installation server device 305 in step S3501. If there is no instruction, the installation process ends. If there is an installation instruction, the process moves to step S3502. In step S3502, the driver installation module determines whether the output port stored in the setup information has already been set. If the designated output port already exists, the process moves to step S3504. If no output port exists, the process proceeds to step S3503, and the driver installation module sets up the designated output port. Specifically, for example, TCP / IP
When performing print processing using lpr above, the driver installation module instructs the OS to incorporate the lpr module and creates a corresponding logical port. Here, it is preferable to use the lpr module included in the setup information created in S3202.
Then, the process proceeds to step S3504.

In step S3504, the driver installation module determines whether or not a driver corresponding to the driver name and version for which installation has been instructed has already been set. If the instructed driver has already been set, the process advances to step S3506.
If the instructed driver is not set, the process advances to step S3505. In step S3505, the driver installation module executes driver installation. Here, the driver installation module instructs the OS to automatically store the main body of the driver program included in the setup information created in S3202 in a predetermined storage area in the client device, and controls the installation process. . When the driver installation process ends, the process moves to step S3506.

Then, in step S3506, it is determined whether the printer instructed to be installed already exists. In the present embodiment, the O of each client device is
The name already registered in the registry of S is searched, and it is determined whether or not there is the same printer name as the printer to be newly registered. If the same printer name does not exist, the process advances to step S3507 to set the printer with the specified printer name. In this embodiment,
The driver installer module instructs the OS to register the printer name as a new printer in the OS registry. Then, the driver installer module controls the OS to associate the printer name with the driver. If the printer already exists, the process advances to step S3508. Since the OS cannot set up printers with the same name, different printer names are automatically created by adding branch numbers, for example. Then, the driver installer module controls the OS so that the printer name and the printer name are associated with each other by the printer name.
Next, proceeding to step S3509, the driver installer module determines whether or not there is a test print execution instruction. The driver installer module
If there is no test print execution instruction, the installation process ends. When there is a test print execution instruction, the driver installation module causes the printer, which has been installed, to execute the test print processing. Specifically, the driver generates one job for outputting a document including the client name of the client device, the printer name to be printed, the driver name, and the like, and sends the job to the printer to perform the printing process. Alternatively, a command recognizable by the printer is transmitted to the printer such that the printer generates an output including a printer name (print request source) to be printed, a driver name, and the like.

It should be noted that the program of the driver main body is transmitted as the driver information in S3206. As another embodiment, instead of transmitting the driver, the installation server device 385 may transmit the URL indicating the location of the driver to be installed on the network together with the setup information. The driver installation module may download the driver from the web server 386 indicated by the URL and instruct the OS to perform the installation process.

According to the above-described embodiment, the installation server 305 generates the setup information only by issuing the batch setup instruction, and the client device automatically or semi-automatically installs the setup information based on the setup information. This will install the driver,
There is an effect that it is not necessary to perform different operations for each device, such as version upgrade and setup procedures, by rotating each client device one by one. Furthermore, select the driver type appropriately according to the environment of the device or client device, the version of the driver to be newly installed or updated, specify the printer name and instruct the client device to register, and associate the printer to be registered with the driver. There is an effect that it is not necessary to perform such complicated operation by turning each client device one by one.

Furthermore, according to the above-described embodiment, by performing the test print, the install server device 30
5, when the service person issues a driver setup instruction to a plurality of client devices and adds or updates the driver of the client device, it is necessary to confirm the operation of the peripheral device for each client device. Disappear. For example, just by checking the test print, the printing system is set so that the printer that has been set up can perform normal print processing, such as whether the driver settings for each client device have completed normally or the print server is operating normally. There is an effect that it is possible to determine whether or not it has been performed by merely looking at the test print output to the printer without checking the settings of the client devices one by one.

(Third Embodiment) A portion different from the above-described embodiment will be described below. FIG. 36 shows S3504 of FIG.
And a modified example of the process corresponding to S3505. This is a process called when the driver installation module in the client device shifts to the process of installing the driver after the port setup is completed based on the setup instruction from the install server device 305. When this process ends, the printer registration process is called.

In the present embodiment, when the install server device 385 selects driver update as an instruction to set up the driver, the driver update information, which is a preferred example of the information indicating the setup status, specifies the driver update. Information is stored and transmitted from the install server device to the client device.

In S3601, the driver installation module determines whether or not there is a driver with the driver name specified in the driver setup information. If the driver installation module determines that there is no driver with the specified driver name, a new driver installation process is performed in step S3602. Specifically, the driver module that constitutes the driver having the specified driver name is stored in a predetermined storage area of the client device. On the other hand, the driver installation module
If it is determined that there is a driver having the driver name designated by 01, the processing of S3603 is performed. In S3603,
The driver installation module determines whether the version of the existing driver in the client device is older than the driver to be updated specified in the driver setup information. If the driver installation module determines in S3603 that the version of the existing driver in the client device is older than the driver to be updated specified in the driver setup information, the driver installation module performs the driver update process in S3604. Tells the OS. Then, upon receiving the instruction from the driver installation module, O
The S stores the driver module in a predetermined storage area of the client device, and proceeds to S3606. On the other hand, S3
In 604, when the driver installation module determines that the version of the existing driver in the client device is newer than the version of the driver to be installed specified in the driver setup information, the process is ended. The driver installation module is S3
At 606, it is determined whether the module of the existing driver remains. If the driver installation module determines in step S3606 that all the modules of the existing driver are overwritten by the new driver and do not remain, the process ends. In step S3606, when the driver installation module determines that some or all of the modules of the existing driver remain, the processing of deleting the existing driver module is performed, and when the deletion is completed, the processing ends.

(Fourth Embodiment) A portion different from the above-described embodiment will be described below. FIG. 38 shows S3206 of FIG.
It is a modification of the process corresponding to. This is a process called when the driver installation module in the client device shifts to the process of installing the driver after the port setup is completed based on the setup instruction from the install server device 305. When this process ends, the printer registration process is called.

In S3801, the installer in the install server device 385 refers to the driver setup information, which is a suitable example of the setup status information collected in advance and stored in the install server, to identify the driver name in the client device and Retrieve version information. Then, in S3802, the installer in the install server device 385 determines whether or not the driver having the driver name specified in the driver setup information is in the client device. S3802
If the installer in the install server device 385 determines that there is no driver with the specified driver name, the OS transmission process is controlled so that the server device actively notifies the client of driver distribution in step S3804. To do. On the other hand, if the driver installation module determines in S3802 that there is a driver with the specified driver name, the process of S3803 is performed. S38
In 03, the driver installation module determines whether the version of the existing driver in the client device is older than the driver to be updated specified in the driver setup information. If the installer (transmission control means) in the install server device 385 determines in S3803 that the version of the existing driver in the client device is older than the driver to be updated specified in the driver setup information, S3.
The distribution process is controlled by the installer in the install server device 385 instructing the OS to perform driver distribution notification in 804. When the OS receiving the instruction of the driver installation module receives the ACK response from the client device in step S3805, the OS transmits driver information to the client device and ends the process in step S3807. AC from the client device in S3805
If no K response is received, the install server device 3
The installer in 85 displays an error and ends the process. If the above process is repeated for each PC, the driver can be actively distributed from the server side to a plurality of PCs without receiving a request from the client device side.

With the above processing, the driver can be automatically deleted and updated by issuing the setup instruction only once, and the work load of the driver update processing can be greatly reduced. Further, by grasping the driver name and version information in the client device from the setup status information, it is possible to selectively deliver the driver that needs to be newly installed to the client device side.

(Fifth Embodiment) Hereinafter, FIGS.
The case of checking the driver of the peripheral device and further deleting the driver will be described with reference to FIG. FIG. 10 is a flowchart showing a processing operation for checking and further deleting a driver. First, in step S1001, connection status information of all client devices and peripheral devices on the network is acquired and the information is stored.

Next, in step S1002, the setup status information of the driver of the peripheral device installed in the own device is acquired. Peripheral device drivers are drivers for printers, scanners, digital cameras, fax machines, and the like.

FIG. 11 is a diagram showing an example of the driver information structure that has been set up. It is composed of a PC name, an IP address, an OS type, a user name, the number of device drivers, and information about each device driver. Each device driver information includes a device type such as a printer or a scanner, a driver name, version information, an output port, and shared information. For example, the first registered printer has a driver name of LASER-830, a version of 1.00.00, an output port of local connection, and shared information of shared setting (ON).

FIG. 12 is a diagram showing an example of a screen displaying a PC including a client device on the network and peripheral devices. 301 is a menu, 302 is a toolbar,
Reference numeral 303 is a main window in which icons representing PCs and peripheral devices are displayed.

Reference numerals 302a to 302i denote toolbars 302.
Are icons representing respective functions performed by operating the PC and peripheral devices. For example, 302a is an icon for executing a copy function of reading image data from the selected scanner and outputting the image data to the selected printer. 302b is a FAX function, 302c is an image data reading function, 302d is an image data reading function,
Function for performing OCR processing, 302e for managing FAX received data and distribution data, 302f for display switching function, 302g for display screen editing function, 302h for updating information, 302i for canceling updating processing Is an icon for executing.

Reference numerals 303a to 303q are icons representing PCs and peripheral devices shared on the network.
These icons 303a to 303q are displayed after being changed depending on the device type such as a PC, a printer, a scanner, a FAX modem, or the status such as "in process" or "error occurred". Reference numeral 303c is an icon representing the own device, and 303b is an icon representing the domain in which the own device is logged on. Since its own device is a special device, it is displayed at the beginning in distinction from other PCs. The other PCs are displayed in alphabetical order in ascending or descending order.

Also, like the icon 303p, PCs and peripheral devices that are shared on the network but do not have the driver installed are grayed out. A “+” mark is displayed when the connected device is present like the icon 303j but is not expanded and displayed, and a “−” mark is displayed when the connected device is expanded like the icons 303h, 303k, and 303n. To be done. When there is no connected device like the icon 303q, no mark is added.

In this way, the connection status of all PCs and peripheral devices on the network, and further the status can be confirmed on the screen. In this example, all the icons are not displayed for the convenience of the screen, but all the PCs and peripheral devices can be confirmed by using the scroll bar arranged on the side of the screen.

FIG. 13 shows that, from the state shown in FIG. 12, the sharing setting of the printer represented by the icon 303i connected to the PC represented by the icon 303h and set to be shared on the network has been released, or the driver has been released. It is a figure which shows an example of the screen displayed when is deleted. As shown in the figure, the icon “303i” is displayed with a display “x” mark indicating “unusable”. In this state, the driver is installed, but it cannot be output because the actual output destination does not exist.

Returning to the flowchart of FIG. 10,
In step S1003, it is determined whether to check the driver of the peripheral device. For example, a screen as shown in FIG. 14 is displayed, and a driver's check instruction can be issued by selecting a device to check. On this screen, when it is determined that the device is not required because there is no corresponding device when the check is performed, it is possible to also specify the setting of whether or not to display a message. If there is no driver's check instruction, this process ends.

If there is a driver's check instruction, the process proceeds to step S1004, and it is determined whether all the drivers to be checked have been checked. If all drivers have been checked, this process ends.

If all the drivers have not been checked, the process proceeds to step S1005, and it is determined whether the driver to be checked is prohibited from being deleted. For example, if you execute a check process on a printer that you normally use frequently, and it happens that the device is not powered on, and it is determined that the target device does not exist, and it is deleted, you need to reinstall the driver. No, it is inconvenient for the user.

Therefore, the deletion prohibition setting can be made for the driver which is not desired to be deleted. FIG. 15 is an example of a screen for setting the deletion prohibition of the driver. Here, the deletion prohibition setting can be performed by selecting the driver whose deletion is to be prohibited and additionally registering it in the prohibition list. Conversely, it is also possible to select a driver for which deletion prohibition is to be released and delete it from the prohibition list.

If it is prohibited in step S1005, the process returns to step S1004 to check the next driver. If not prohibited, step S10
In step 06, it is determined whether or not there is a device corresponding to the driver. For example, in the case of a printer, the output port destination is inquired to determine whether or not there is a response. For a scanner or the like, the same processing is performed on the input port to check. If the target device exists,
Returning to step S1004, the next driver is checked.

If the target device does not exist, the process proceeds to step S1007, and it is determined whether or not to display the deletion message. This determination is performed according to the information set in step S1003. Here, if the message is set to be displayed, step S1008.
Move to. If the message is set not to be displayed, the process proceeds to step S1009.

In step S1008, a message prompting the user to specify whether or not to delete is displayed. FIG. 16 is an example of a message displayed when there is a driver to be deleted. In this way, the target driver is displayed, and the driver is instructed whether to delete it. Here, if “YES” is instructed, step S100.
Move to 9. If "No" is designated, the deletion process is canceled, the process returns to step S1004, and the next driver is checked.

In step S1009, the process of deleting the designated driver is executed. After the processing is completed, the process returns to step S1004 to check the next driver.

In the flow chart shown in FIG. 10, the driver is checked by the computer in which the device is set to be shared. However, it may be possible to instruct the driver to be deleted in the computer in which the device is set to be shared. 17 and 18 show a flowchart for a case where a computer in which a device is set to be shared gives a driver deletion instruction.

First, steps S801 and S802 are the same processes as steps S1001 and S1002. In step S803, it is determined whether all installed drivers have been checked. If all drivers have been checked, this process ends.

If all the drivers are not checked, the process proceeds to step S804, and it is determined whether the device corresponding to the driver is a local device or a device shared by the network. If it is not the local device, the process returns to step S803 to check the next driver.

If the device is a local device, the process proceeds to step S805, and it is determined whether or not there is a device corresponding to the driver. The determination method is step S1.
The same as 005. When the device corresponding to the driver exists, the process proceeds to step S811.

If there is no device corresponding to the driver, the process proceeds to step S806, and it is determined whether or not the driver has made sharing setting. If sharing is not set, the process proceeds to step S808.

If sharing is set, step S807.
Then, the other devices are notified via the network that the target device cannot be used, and the process proceeds to step S808. FIG. 19 is an example of an information structure for notifying the deletion of a driver, and has information such as a device type, a driver name, version information, and an output port.

In step S808, it is determined whether the target driver is prohibited from being deleted. The judgment method is
This is similar to the case of step S1005. If the deletion is prohibited, the process returns to step S803 to check the next driver.

If the deletion prohibition is not set, the process proceeds to step S809, and it is determined whether or not the deletion is executed.
The determination method is the same as in step S1008. If the deletion of the driver has been canceled, the process returns to step S803 to check the next driver.

When the driver deletion is instructed, the process proceeds to step S810, the driver deletion process is executed, and after the deletion process is completed, the process returns to step S803.
Check the following drivers.

In step S811, it is determined whether the target driver has canceled the sharing setting. Here, if the sharing setting of the target driver is not canceled, step S
Returning to 803, the next driver is checked.

If the target driver has canceled the sharing setting, the process advances to step S812 to notify another computer via the network that the target device cannot be used.

On the other hand, in the computer which is notified of the driver deletion notification as described above, as shown in FIG. 18, first, in step S901, it is determined whether or not the deletion notification is received. If the notification has not been received, the processing ends.

When the notification is received, the process proceeds to step S902, and it is determined whether or not there is a driver corresponding to the driver deletion notification. If there is no corresponding driver, the process ends.

If there is a corresponding driver, step S
In step 903, it is determined whether the target driver is prohibited from being deleted. The determination method is step S1005.
Is the same as. If the driver deletion prohibition is set, the process ends.

If the deletion prohibition is not set, the process proceeds to step S904, and it is determined whether or not to display a message. If the message display setting is not made, the process proceeds to step S906. If the message display is set, the process moves to step S905 and the message is displayed.

If the deletion instruction is not issued in step S905, the process ends. When the driver deletion instruction is given, the process proceeds to step S906, the target driver is deleted, and the process ends.

As described above, on the screen displaying the PC and peripheral devices shared on the network, the peripheral devices shared on the network are used after being deleted or the sharing setting is released. If you can't, you can easily uninstall the driver you no longer need. Further, it is possible to delete the driver of the peripheral device which has been set to be shared, or to notify the other computer when the sharing setting is canceled to delete the unnecessary driver. These functions can significantly improve the work efficiency on the network.

(Sixth Embodiment) Hereinafter, FIGS.
The case of updating the driver of the peripheral device will be described with reference to. FIG. 20 is a flowchart showing the processing operation for updating the driver version. First, in step S2001, connection status information of all PCs and peripheral devices on the network is acquired and stored.

Next, in step S2002, the setup status information is acquired by the driver of the peripheral device of each client device. Peripheral device drivers are drivers for printers, scanners, digital cameras, fax machines, and the like. As a method of acquiring the setup status information, for example, a module that acquires driver information installed in the client device is started on each client device to collect information, and the information can be communicated through a network. Conceivable.

FIG. 21 is a diagram showing an example of the driver information structure that has been set up. It is composed of a PC name, an IP address, an OS type, a user name, the number of device drivers, and information about each device driver. Each device driver information includes a device type such as a printer or a scanner, a driver name, version information, an output port, a shared name, and a driver information address. For example, the first registered printer has a driver name of LASER
-830, version is 1.00.00, output port is local, shared name is LASER-830, and driver information address is Ox10000. This information is recorded for each client device.

In step S2003, the connection status information of all client devices and peripheral devices on the network is displayed based on the acquired information. Since this screen display has already been described with reference to FIG. 12, detailed description thereof will be omitted.

FIG. 22 is a diagram showing an example of a screen displaying the driver setup status of each client device on the network, which is displayed based on the driver information structure acquired from each client device. For example, in the figure, the drivers installed in my client device are six printers and two scanners. Among them, for example, a printer "INKJET-10V" has a driver name "INKJET-10V", a version number "1.00.00", and an output port name "\\ NOTEPC01 \ INKJET-10V". so,
It indicates that the printer driver is shared on the network that is set to be shared by the name “INKJET-10V”.

Returning to the flowchart of FIG. 20,
In step S2004, it is determined whether the driver of the peripheral device has been updated. Here, if the driver has not been updated, the process ends. If the driver has been updated, the process proceeds to step S2005. As a method of updating the driver, it is possible to update the driver on each client device and register the driver information in the PC that will be the server device. In the present embodiment, the server device and the client device use a PC which is a preferred example of the information processing device. Alternatively, the user may download the latest driver from each manufacturer's site and register it. In addition, you can check the driver version by specifying a specific location on the network. FIG. 23 is an example of a screen for making driver version check settings. In this way, by setting a specific URL, it is possible to perform a driver version check on a regular basis and automatically obtain a driver update when it is updated.

In step S2005, it is determined whether the updated driver is the latest version. If it is not the latest version, there is no need to give a notification to update, and the process ends. If it is the latest version, the process proceeds to step S2006. As a method of determining the driver version, it can be considered to perform it based on the driver information of each printer managed by the server device. FIG. 24 is an example of a structure in which version control is performed for each driver. The type of device such as a printer or a scanner, the device driver name, the number of version information managed, the driver version information,
And driver information corresponding thereto. The determination is made by comparing the version information managed and the version information of the updated driver.

In step S2006, it is determined whether or not there is a client device using the updated driver. The determination is performed using the device driver information structure acquired from each client device. If there is no target client device, the process ends. If there is a target client device, the target client device list is displayed. FIG. 25 is an example of a screen for selecting a driver update target client device. When the target client device is selected and “OK” is selected here, the process proceeds to step S2007, and the selected client device is notified. Done. Further, when “select all target PCs” is selected, all target client devices are selected.

In step S2007, the selected target client device is notified that the driver has been updated. FIG. 26 is an example of a device update notification information structure, which includes a device type, a driver name, version information, and an output port.

Then, the process proceeds to step S2008, and it is determined whether or not there is a driver information acquisition request from the notified client device. If there is no request, or if there is a response from the client that it is not necessary to transmit the driver information, the process proceeds to step S210. If there is a request, the process advances to step S2009 to send the requested driver information to the client.

In step S2010, it is determined whether there is a response from all the notified client devices.
If there is a response from all the client devices, the process ends. If there is no response from all the client devices, the process returns to step S2008.

On the other hand, FIG. 27 is a flow chart showing the processing operation in the client. First, step S
At 901, it is determined whether or not there is a driver update notification from the server device. Here, if there is no notification, the process ends.

If there is a notification, the process proceeds to step S902, and it is determined whether or not the driver is updated. For example,
A method of displaying a message that the driver has been notified and instructing the user can be considered. FIG. 28 is an example of a message notifying that the driver has been updated.
If "No" is selected, notify the server device that the target driver information is not required,
The process ends. If "Yes" is selected, the process moves to step S903 to request the target driver information from the server device.

Next, in step S904, it is determined whether the driver information has been acquired. If you can't get it,
Returning to step S903, the server device is requested to acquire again. If the driver information can be acquired, step S
In step 905, the driver update process is performed. further,
In step S906, the latest driver installation status is notified to the server device, and the process ends.

In the flow charts shown in FIGS. 20 and 27, when the driver update process is performed, the client device to be notified is selected by the PC serving as the server device. There may be a case where the driver update process is performed by judging from the status of the installed driver. 29 to 31 are flowcharts in the case of performing a driver update process by judging from the status of the driver installed in the PC as a client.

Steps S1201 to S in FIG.
Step 1205 is steps S2001 to S2005.
Is the same as. Next, in step S1206, all the client devices are notified that the driver has been updated, and the process ends. The information structure to be notified is also as shown in FIG.

Then, according to the flowchart shown in FIG. 30, the request from the client is processed. First, in step S1301, it is determined whether there is a request for driver information. If there is no request, the process ends.

If there is a request, the process proceeds to step S1302, and the requested driver information is read from the managed driver information. Then, in step S1303
Then, the driver information is transmitted to the requesting client.

On the other hand, in the client, processing is performed according to the flowchart shown in FIG. This flowchart is almost the same as the flowchart shown in FIG. 27. Step S1401, step S1403 to step S1407 are the same as those described in step S901 to step S906 in FIG. 27, but step S14.
The difference is that there is a judgment of 02.

In step S1402, when the driver update notification is received from the server device, the necessary data is read from the driver update notification structure and compared with the driver information installed in the own device, and the notification is sent. It is determined whether there is a target driver. If there is no target driver, this notification is ignored and the process ends. When there is a target driver, the same processing as the flowchart shown in FIG. 27 is performed.

As described above, when the driver of the peripheral device is updated on the screen displaying the PC and the peripheral device shared on the network, the driver update process is performed by a simple operation. You can Also,
By notifying each client device of only the driver update information, it is possible to determine whether or not to perform the driver update process, so that the traffic on the network can be minimized. These functions can significantly improve the work efficiency on the network.

(Other Embodiments) In order to operate various devices in order to realize the functions of the above-described embodiments, a computer in an apparatus or system connected to the various devices is operated in the above-described embodiment. Supply the program code of software to realize the function of
What was carried out by operating the above-mentioned various devices according to the program stored in the computer (CPU or MPU) of the system or apparatus is also included in the category of the present invention.

In this case, the program code itself of the software realizes the functions of the above-described embodiments, and the program code itself and a means for supplying the program code to the computer,
For example, a recording medium storing such program code constitutes the present invention. Recording media for storing such program codes include, for example, floppy disks, hard disks, optical disks, magneto-optical disks, CD-ROMs,
A magnetic tape, a non-volatile memory card, a ROM or the like can be used.

Further, not only the functions of the above-described embodiments are realized by executing the supplied program code by the computer, but also the OS (operating system) or other operating system in which the program code runs in the computer. It goes without saying that the program code is also included in the embodiment of the present invention when the functions of the above-described embodiment are realized in cooperation with the application software of the above.

Further, after the supplied program code is stored in the memory provided in the function expansion board of the computer or the function expansion unit connected to the computer, the function expansion board or function expansion unit is instructed based on the instruction of the program code. It goes without saying that the present invention also includes a case where the CPU or the like included in the above-mentioned performs some or all of the actual processing and the functions of the above-described embodiments are realized by the processing.

The shapes and structures of the respective parts shown in the above-mentioned embodiments are merely examples of the embodiment for carrying out the present invention, and the technical scope of the present invention is thereby provided. It should not be construed as limiting. That is, the present invention can be implemented in various forms without departing from the spirit or the main features thereof. As described above, according to the present invention,
If the peripheral device driver is not installed on the screen where the PC and peripheral devices shared on the network are displayed, you can install the driver with a simple operation and confirm that it was actually installed. It is possible to significantly improve the work efficiency on the network.

According to the embodiment of the present application, when the driver of the peripheral device is not installed in the window displaying the PC and the peripheral device shared on the network, the system administrator can easily access the server device. The driver can be remotely installed by an operation, and the fact that the driver has been correctly installed can be confirmed by performing a test print on the printer, so that work efficiency can be improved.

[0156]

As described above, according to the present invention, it is possible to reduce the work load at the time of setup by performing the driver information setup process for the client device by a simple work. .

Furthermore, in a printing system including a plurality of client devices, driver installation processing is performed according to the setup status of each client device in which the driver should be installed, so that each user is aware of the driver setup status. There is an effect that the installation process can be performed without doing.

Further, since the server device performs the push installation and the driver setup on the client device without waiting for the request from the client device, the client device does not need a complicated installation operation. There is.

Furthermore, a mechanism for executing a test print after the driver information is installed is provided,
It is possible to confirm whether or not the driver information setup has been completed normally.

[Brief description of drawings]

FIG. 1 is a block diagram showing a schematic configuration of an information processing apparatus according to the present embodiment.

FIG. 2 is a flowchart showing a processing operation for setting up a driver.

FIG. 3 is a diagram showing an example of a driver information structure.

FIG. 4 is a diagram showing an example of a screen displaying a PC and peripheral devices on a network.

FIG. 5 is a diagram showing an example of a screen displaying the driver setup status of each client device on the network.

FIG. 6 is a diagram showing an example of a screen for selecting a driver to be set up.

FIG. 7 is a diagram showing an example of a screen for selecting a client device for setting up a driver.

FIG. 8 is a diagram showing an example of a driver setup instruction structure.

FIG. 9 is a diagram illustrating an example of driver setup confirmation printing.

FIG. 10 is a flowchart showing a processing operation for checking and further deleting a driver.

FIG. 11 is a diagram showing an example of a driver information structure.

FIG. 12 is a diagram showing an example of a screen displaying a PC and peripheral devices on a network.

FIG. 13 is a diagram showing an example of a screen displayed when the sharing setting of the printer represented by the icon 303i is canceled or the driver is deleted.

FIG. 14 is a diagram showing an example of a screen for selecting a device to be checked.

FIG. 15 is a diagram showing an example of a screen for making driver deletion prohibition settings.

FIG. 16 is a diagram showing an example of a message displayed when there is a driver to be deleted.

FIG. 17 is a flowchart showing a processing operation for checking a driver and further deleting the driver.

FIG. 18 is a flowchart showing a processing operation when a driver deletion notification is notified.

FIG. 19 is a diagram showing an example of an information structure for notifying deletion of a driver.

FIG. 20 is a flowchart showing a processing operation for updating the driver version.

FIG. 21 is a diagram showing an example of a driver information structure.

FIG. 22 is a diagram showing an example of a screen displaying the driver setup status of each client device on the network.

FIG. 23 is a diagram showing an example of a screen for making driver version check settings.

FIG. 24 is a diagram showing an example of a structure body whose version is managed for each driver.

FIG. 25 is a diagram showing an example of a screen for selecting a client PC for which a driver is updated.

FIG. 26 is a diagram showing an example of an information structure of a device update notification.

FIG. 27 is a flowchart showing a processing operation for updating the driver version.

FIG. 28 is a diagram showing an example of a message notifying that a driver has been updated.

FIG. 29 is a flowchart showing a processing operation for updating the driver version.

FIG. 30 is a flowchart showing a processing operation for updating the driver version.

FIG. 31 is a flowchart showing a processing operation for updating the driver version.

FIG. 32 is a diagram showing a flowchart of one example in the install server device 385.

FIG. 33 is a diagram showing an example of a screen for setting driver information in the install server device 385.

FIG. 34 is a diagram showing a client device selection screen in the install server device 385.

FIG. 35 is a diagram showing an example of each client device when a remote driver installation instruction is issued from the installation server device 305.

FIG. 36 is a diagram showing a modification of the processing corresponding to S3504 and S3505 of FIG.

FIG. 37 is a diagram showing modules of software as a preferable example in each client apparatus.

FIG. 38 is a diagram showing a modified example of the process corresponding to S3206 in FIG.

FIG. 39 is a diagram illustrating an example of a printing system according to the present embodiment.

[Explanation of symbols]

1 system bus 2 CPU 3 program memory 4 communication control unit 5 communication port 6 communication line 7 other device on network 8 external storage device control unit 9 floppy disk 10 hard disk 11 input control unit 12 keyboard 13 mouse 14 video image memory 15 display Output control unit 16 CRT 17 Printer control unit 18 Printer 1A Image reading device control unit 1B Image reading device 331 Printer name designation unit 332 Port designation unit 333 Driver designation unit 334 Port addition designation unit 335 Driver addition designation unit 371 Driver installation module 372 Driver 373 Application programming interface 374 System installer 375 System file 376 Registry 377 User area 378 OS area 379 System program Ram 380 LAN 381 client A 382 the client B 383 client C 384 printer A 385 install server 386 file server 387 print server

Claims (72)

[Claims] 1. An information processing apparatus that communicates with a client device, wherein a device management unit that manages a setup status of a driver of a peripheral device connected to the client device in the client device; and a plurality of the plurality of devices based on the setup status. An information processing apparatus comprising: a transmission control unit that controls a process of transmitting driver information corresponding to a client apparatus to the client apparatus. 2. The setup status includes information indicating a version of driver information incorporated in the client device, and the transmission control means determines that the information indicating the version is older than the driver information included in the server device. The information processing apparatus according to claim 1, wherein the transmission processing is controlled so as to transmit the driver information included in the server apparatus to the client apparatus. 3. The setup status includes identification information of driver information incorporated in the client device, and the transmission control means determines that the driver information indicated by the identification information of the driver information does not exist in the client device. 2. The transmission process is controlled so as to transmit the driver information to the client device.
The information processing device according to 1. 4. The information processing apparatus according to claim 1, wherein the setup status is collected by the server apparatus by communicating with a client apparatus. 5. The information processing apparatus according to claim 1, wherein the driver information includes a printer driver. 6. A method in an information processing device for communicating with a client device, comprising: a device management step of managing a setup status in a client device of a driver of a peripheral device connected to the client device, based on the setup status. And a transmission control step of controlling a process of transmitting driver information corresponding to the plurality of client devices to the client device. 7. The setup status includes information indicating a version of driver information incorporated in the client device, and in the transmission control step, when the information indicating the version is older than the driver information included in the server device. 7. The information processing method according to claim 6, further comprising: controlling transmission processing so as to transmit driver information included in the server apparatus to a client apparatus. 8. The setup status includes identification information of driver information incorporated in the client device, and in the transmission control step, when driver information indicated by the identification information of the driver information does not exist in the client device. The information processing method according to claim 6, further comprising: controlling a transmission process to transmit the driver information to a client device. 9. The information processing method according to claim 6, wherein the setup status is collected by the server apparatus by communicating with a client apparatus. 10. The information processing method according to claim 6, wherein the driver information includes a printer driver. 11. A control program executed in an information processing device that communicates with a client device, comprising: a device management step of managing a setup status of a driver of a peripheral device connected to the client device in the client device; A control program for causing an information processing device to execute a transmission control step of controlling a process of transmitting driver information corresponding to the plurality of client devices to the client device based on a situation. 12. The setup status includes information indicating a version of driver information incorporated in the client device, and in the transmission control step, the information indicating the version is:
12. The control program according to claim 11, further comprising: executing an information processing device so as to control a transmission process so that the driver information of the server device is transmitted to the client device when the driver information of the server device is older than the driver information of the server device. . 13. The setup status includes identification information of driver information incorporated in the client device, and in the transmission control step, when driver information indicated by the identification information of the driver information does not exist in the client device. The control program according to claim 11, further comprising: executing an information processing device to control a transmission process to transmit the driver information to a client device. 14. The control program according to claim 11, wherein the information processing device is executed so that the server device collects the setup status by communicating with a client device. 15. The control program according to claim 11, wherein the driver information includes a printer driver. 16. An information processing apparatus that communicates with a plurality of client devices, comprising: a determining unit that determines a plurality of client devices in which driver information should be installed; and driver information that controls a peripheral device connected to the client device. An information processing apparatus comprising: a transmission control unit that controls a process of delivering to a plurality of clients determined by the determination unit. 17. The information according to claim 16, wherein the driver information is printer driver driver information, and the driver information includes a test print instruction for a printer in which the driver information is set up. Processing equipment. 18. The information processing apparatus according to claim 16, wherein the client device sets up the driver information based on the setup instruction. 19. The information processing apparatus according to claim 16, further comprising a selection unit that manually selects a client device, and the determination unit determines the client device selected by the selection unit. The information processing device described. 20. A method in an information processing apparatus for communicating with a plurality of client devices, the determining step of determining a plurality of client devices for which driver information should be installed, and driver information for controlling a peripheral device connected to the client devices. And a transmission control step of controlling a process of delivering to the plurality of clients determined by the determination step. 21. The information processing method according to claim 20, wherein the driver information is printer driver driver information, and the driver information includes a test print instruction for a printer that has been set up. 22. The information processing method according to claim 20, wherein the client device sets up the driver information based on the setup instruction. 23. The information processing apparatus has a selection step of manually selecting a client device, and the determination step determines the client device selected in the selection step. Information processing method described. 24. A control program executed in an information processing device communicating with a plurality of client devices, the determining step of determining a plurality of client devices to which driver information is to be installed, and a peripheral connected to the client device. A control program that causes an information processing apparatus to execute a transmission control step of controlling a process of distributing driver information for controlling the apparatus to a plurality of clients determined in the determination step. 25. The control program according to claim 24, wherein the driver information is printer driver driver information, and the driver information includes a test print instruction for a printer that has been set up. 26. The control program according to claim 24, wherein the client device executes an information processing device to set up the driver information based on the setup instruction. 27. The information processing apparatus is caused to execute a selection step of manually selecting a client apparatus, and the information processing apparatus is executed so as to judge the client apparatus selected in the selection step in the judgment step. The control program according to claim 24. 28. In an information processing device that communicates with a peripheral device and a server device, a recognition means for recognizing a setup instruction and driver information from the server device, and the setup instruction without requesting the server device for the setup instruction. An information processing apparatus having a program management unit that installs driver information for controlling the peripheral device in the client device in response to recognizing. 29. The information processing apparatus according to claim 28, wherein the program management unit controls the client device so that the client device registers in association with the identification information of the peripheral device and the driver information. 30. The program management means, through an application programming interface of the OS mounted on the client device, associates the identification information of the peripheral device and the driver information with each other so that the OS recognizes the OS. 29. Controlling.
The information processing device according to 1. 31. The program management means compares the identification information of the existing driver stored in the client device with the identification information of the driver instructed by the setup instruction, and identifies the existing driver. ,
29. The information processing apparatus according to claim 28, wherein when the identification information of the driver instructed to set up does not match, the driver instructed to set up is stored in the client device. 32. The program management means, if the information indicating the version of the existing driver stored in the client device is newer than the information indicating the version of the driver instructed to be set up,
29. The information processing device according to claim 28, wherein the driver information of the client device is updated to the driver information instructed to perform the setup. 33. A method in an information processing device for communicating with a peripheral device and a server device, comprising: a recognition step of recognizing a setup instruction and driver information from the server device; An information processing method comprising: a program management step of installing driver information for controlling the peripheral device in the client device in response to recognizing a setup instruction. 34. The information processing method according to claim 33, wherein in the program managing step, the client device is controlled so that the client device registers in association with the identification information of the peripheral device and the driver information. 35. In the program management step, the OS is recognized by the OS in a state of being associated with the identification information of the peripheral device and the driver information via an application programming interface of the OS mounted on the client device. It controls, It is characterized by the above-mentioned.
The information processing method described in 3. 36. The program managing step compares the identification information of the existing driver stored in the client device with the identification information of the driver instructed by the setup instruction to obtain the identification information of the existing driver. ,
34. The information processing method according to claim 33, wherein when the identification information of the driver instructed to set up does not match, the driver instructed to set up is stored in the client device. 37. In the program management step, if the information indicating the version of the existing driver stored in the client device is newer than the information indicating the version of the driver instructed to be set up, the client 34. The information processing method according to claim 33, wherein the driver information of the device is updated to the driver information instructed to perform the setup. 38. A recognition program for recognizing a setup instruction and driver information from the server device in a control program executed in an information processing device communicating with the peripheral device and the server device, and requesting the server device for the setup instruction. And a program management step of installing driver information for controlling the peripheral device in the client device, in response to recognizing the setup instruction, without causing the information processing device to execute the control. program. 39. The program management step executes an information processing device to control the client device so that the client device registers in association with the identification information of the peripheral device and the driver information. 38. The control program according to 38. 40. In the program management step, the OS is recognized by the OS in a state of being associated with the identification information of the peripheral device and the driver information via the application programming interface of the OS mounted on the client device. 39. The control program according to claim 38, which executes the information processing device to control. 41. In the program management step, the identification information of the existing driver stored in the client device is compared with the identification information of the driver instructed by the setup instruction, and the identification information of the existing driver is compared. 39. The control program according to claim 38, wherein when the identification information of the driver instructed to set up does not match, the information processing device is executed to store the driver instructed to set up in the client device. 42. In the program management step, if the information indicating the version of the existing driver stored in the client device is newer than the information indicating the version of the driver instructed to be set up, the client 39. The control program according to claim 38, which executes the information processing device so as to update the driver information of the device to the driver information instructed to set up. 43. In an information processing device that communicates with a server device and a peripheral device, program management means for performing driver setup based on a driver setup instruction of the peripheral device from the server device, and responding to the end of the setup. The information processing apparatus generates an instruction to cause the peripheral device to perform a test print for confirming that the setup is normally completed. 44. The program management means calls an OS installation means via an application programming interface of the OS mounted on the client device, and the OS installation means called via the application programming interface comprises:
15. The information processing apparatus according to claim 14, wherein driver information is introduced into the client device. 45. The information processing apparatus according to claim 43 or 44, wherein the program management means is activated in response to an instruction from the server device. 46. The information processing apparatus according to claim 45, wherein the command from the server device is described using a simple object access protocol. 47. A method in an information processing device for communicating with a server device and a peripheral device, comprising: a program management step of performing driver setup based on a driver setup instruction of the peripheral device from the server device; And a step of generating an instruction for causing the peripheral device to perform a test print for confirming that the setup has been normally completed, in response to the completion of the above step. 48. In the program management step, an OS installation means is called via an application programming interface of the OS mounted on the client device, and in the OS installation step called via the application programming interface, The information processing method according to claim 47, wherein driver information is introduced into the client device. 49. The information processing method according to claim 47, wherein the program management step is started in response to a command from the server device. 50. The information processing method according to claim 49, wherein the command from the server device is described using a simple object access protocol. 51. A control program executed in an information processing device that communicates with a server device and a peripheral device, the program managing step of performing driver setup based on a driver setup instruction of the peripheral device from the server device. And a control for causing the information processing apparatus to execute a step of generating an instruction for causing the peripheral device to perform a test print for confirming that the setup is normally completed, in response to the end of the setup. program. 52. In the program management step, an OS installation means is called via an application programming interface of the OS mounted on the client device, and in the OS installation step called via the application programming interface, The control program according to claim 51, which executes an information processing device so as to introduce driver information into the client device. 53. The control program according to claim 51, wherein the program management step is executed in response to a command from the server device. 54. The control program according to claim 53, wherein the command from the server device is described using a simple object access protocol. 55. In an information processing device communicating with a client device, a determination means for determining a client device that is a driver setup destination, a driver setup instruction for the client device, and a driver setup for the client device are provided. Instruct the client device to perform a test print to confirm that it has completed normally.
An information processing apparatus comprising: a transmission control unit that controls a process of transmitting to the client device. 56. The information processing apparatus communicates with a plurality of client apparatuses, and the transmission control unit transmits a driver information installation instruction and a test print instruction to the plurality of client apparatuses. The information processing apparatus according to claim 55, further comprising: a transmission control unit that controls a transmission process. 57. The information processing apparatus further includes a selection unit for manually selecting a client device, and the determination unit determines the client device selected by the selection unit. 55
The information processing device according to 1. 58. The information processing apparatus according to claim 55, wherein a test print request source is printed in said test print. 59. The information processing apparatus according to claim 55, wherein in the test print, a print server name used when performing the test print is printed. 60. A method in an information processing device for communicating with a client device, comprising: a determining step of determining a client device to which a driver is set up; a driver setup instruction for the client device; Instruct the client device to perform a test print to confirm that the driver setup is completed normally.
An information processing method comprising a transmission control step of controlling a process of transmitting to the client device. 61. The information processing apparatus communicates with a plurality of client apparatuses, and in the transmission control step, a driver information installation instruction and a test print instruction are transmitted to be transmitted to the plurality of client apparatuses. The information processing method according to claim 60, further comprising a transmission control step of controlling processing. 62. The information processing method further includes a selecting step of manually selecting a client device, and the determining step determines the client device manually selected in the selecting step. The information processing method according to claim 60. 63. The information processing method according to claim 60, wherein a test print request source is printed in said test print. 64. The information processing method according to claim 60, wherein in the test print, a print server name used when performing the test print is printed. 65. A control program executed in an information processing device that communicates with a client device, the determining step of determining a client device that is a driver setup destination, a driver setup instruction to the client device, and Causing the information processing apparatus to execute a transmission control step of controlling a process of transmitting a test print confirming that the driver setup for the client device is normally completed to the client device to the client device. Characteristic control program. 66. The information processing apparatus communicates with a plurality of client apparatuses, and the transmission control means transmits a driver information installation instruction and a test print instruction to the plurality of client apparatuses. 66. The information processing method according to claim 65, wherein a transmission control step for controlling the processing is executed in the information processing apparatus. 67. The control program further causes the information processing apparatus to execute a selection step of manually selecting a client device, and the determination step determines the client device manually selected in the selection step. 66. The control program according to claim 65, which executes an information processing device. 68. The control program control program according to claim 65, wherein in the test print, the information processing device is executed so that a test print request source is printed. 69. In the test print, the information processing apparatus is executed such that the print server name used when performing the test print is printed. Control program. 70. The method according to any one of claims 11 to 15 or claim 2.
A computer-readable storage medium storing the control program according to any one of claims 4 to 47, claims 38 to 42, claims 51 to 54, or claims 65 to 69. 71. In a network system including a client device and a server device, device management means for managing a setup status in a client device of a driver of a peripheral device connected to the client device; and the client based on the setup status. A transmission control unit that controls a process of transmitting driver information corresponding to a device to a plurality of client devices, a recognition unit that recognizes a setup instruction from the server device and the driver information, and requests the server device for the driver information. Relative to the reception of the driver information from the server device, the network has a program management means for installing driver information for controlling the peripheral device in the plurality of client devices. Shi Temu. 72. In an information processing device that communicates with a client device, a determination means for determining a client device that is a driver setup destination, a driver setup instruction for the client device, and a driver setup for the client device are provided. A transmission control unit that controls a process of transmitting a test print instruction confirming that the print job is normally completed to the client device, a setup instruction from the server device, driver information, and the test print instruction are received. And a driver unit for controlling the peripheral device in the client device in response to receiving the driver information from the server device without requesting the driver information from the server device. Install and Network system, comprising a program management means for issuing an instruction for test printing on the basis of an instruction of the serial test print.