JP2002251347A - Network system, information processor, method, control program and computer readable storage medium - Google Patents

Abstract

PROBLEM TO BE SOLVED: To update the property information of a driver with a simple operation on a network. SOLUTION: A setup program in an installation server device 385 accesses an API(application program interface) of an OS or a system call without waiting for a transmission request for driver information from client devices 381 to 383, performs a driver setup instruction and controls processing that distributes a driver. The setup program concurrently controls the OS so as to transmit the driver property information to be transmitted to the client devices 381 to 383 from the server device 385 spontaneously or by waiting for requests from the client devices 381 to 383 on which a driver have been installed.

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 apparatus, a method, a control program, and a computer-readable storage medium for displaying and managing PCs and peripheral devices shared on a network. It is about things.

[0002]

2. Description of the Related Art In recent years, personal computers (hereinafter, referred to as personal computers).
With the spread of peripheral devices such as printers, scanners, digital cameras, and the like, networks such as LANs have become widespread, and the need to share printers, modems, scanners, and the like with a plurality of PCs on the network has increased. Was. Also, many drivers for using these peripheral devices have been provided, and their installation methods have been provided.

[0003]

However, when a driver of a peripheral device is upgraded due to a functional upgrade or the like, the user himself has to upgrade the driver. When the user upgrades the driver version, the new driver information is shared on the network by a PC (server PC, etc.)
It is a common practice to store the information in a specific folder and upgrade the driver on each PC using the driver information.

However, when the version is upgraded by these methods, there are the following problems. That is, user information set as property information in each driver, for example, layout information and font information, or device option information commonly set in the network system is set in the initial state of the driver. It is a problem. Therefore, after all, it is necessary to set the property information of the driver that returns to the initial state at the time of installation. For these reasons, the operation of setting the driver property information after installing the driver is not only troublesome,
The items that make those settings are also becoming more complex,
There is a problem that it causes a setting error or the like.

[0005] Therefore, it is conceivable that the driver will be automatically upgraded in the future. For example, a system administrator upgrades a driver on a plurality of PCs at once by issuing an instruction from a server PC or the like. The version can be upgraded on each PC without the user being particularly aware of the folder in which the new driver information is stored.

[0006] However, the procedure of driver installation, version upgrade, and setup differs for each device. Further, the type of the driver must be selected according to the environment of the device or the client device, and the operation is complicated. Further, there is a problem that complicated processing such as addition or change of a driver based on an instruction in the client device, setting of property information of the driver in each client, and the like must be performed, resulting in extremely low work efficiency.

[0007] Thus, the user of each PC or P
If the setting of the C software is left to the system administrator, there is a problem that the load on the system administrator is increased and the work efficiency is reduced. Furthermore, in recent years, in a large-scale system, installation on a large number of PCs is increasing. After the driver is installed on many PCs, it becomes necessary to set the properties of the complicated driver on many PCs. Under such circumstances, the user's labor and the number of P
There is a problem that a system administrator for setting C is required, and setting errors often occur.

The present invention has been made in view of the above points, and has as its object to provide a mechanism that enables property information to be updated on a network by a simple operation.

[0009] Further, in order to reduce the effort of setting the driver property information and to reduce setting mistakes, when upgrading the version of the driver installed in the client, the server device distributes the driver property information to the client. An object is to provide a mechanism for setting in a device.

Further, in order to reduce the load of the driver installation and the property information setting processing performed in each client, the driver is push-installed according to a setup instruction from the server device, and the property information setting processing for the driver is performed. The purpose is to provide a mechanism for performing.

[0011]

The information processing apparatus according to the present invention will be described below as means for solving the above-mentioned problems. The information processing apparatus according to the present invention includes a driver in an information processing apparatus communicating with a client device. Recognition means for recognizing a client device to which information property information is to be distributed, and distribution control means for controlling processing of distributing the property information to the client device and a setup instruction for setting up the property information. It is characterized by having the following.

Another information processing apparatus according to the present invention is an information processing apparatus capable of communicating with a server apparatus.
Input means for inputting property information of driver information and a setup instruction from the server device; and, based on the setup instruction, the property information so that driver information in the information processing apparatus can recognize the property information. And a property information input unit for inputting the information to the information processing apparatus.

[0013]

DESCRIPTION OF THE PREFERRED EMBODIMENTS Embodiments of a network system, an information processing apparatus, a method, a control program, and a computer-readable storage medium according to the present invention will be described below with reference to the drawings.

FIG. 1 is a block diagram illustrating a schematic configuration of an apparatus according to the present embodiment. In FIG. 1, reference numeral 1 denotes a system bus to which the following constituent blocks are connected.

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

A communication controller 4 controls input / output data at the communication port 5. The signal output from the communication port 5 is transmitted via a communication line 6 to a communication port of another device (designated by reference numeral 7 in FIG. 1) on the network. Communication with a printer, scanner, or the like shared on the network is performed via the communication control unit 4. In the present embodiment, a network such as a LAN will be described. However, it goes without saying that the present invention is applicable even when the communication port 5 and the communication line 6 connected to the communication control unit 4 are general public lines. .

Reference numeral 8 denotes an external storage device control unit. 9, 10
Is a disk for data files, for example, 9 is a flexible disk FD, and 10 is a hard disk HD.

Reference numeral 11 denotes an input control unit, which is a keyboard 1
2. An input device such as a mouse 13 is connected. The user
By operating the keyboard 12, operation commands and the like for the system can be issued. The mouse 13 is a CRT1
6 for pointing and processing image information
The device functions as a device PD, whereby the cursor on the CRT 16 is arbitrarily moved in the X and Y directions to select a command icon on a command menu to give an instruction for processing, an instruction for editing, an instruction for a drawing position, and the like. Can also be done.

Reference numeral 14 denotes a video image memory (VRAM)
15 is a display output control unit, and 16 is a CRT
(Cathode-Ray Tube). Data displayed on the CRT 16 is developed 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
A denotes an image reading device control unit, which controls the connected image reading device 1B.

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

(First Embodiment) Hereinafter, a first embodiment will be described with reference to FIGS. FIG.
5 is a flowchart showing a processing operation of a PC functioning as a server device. First, in step S201, the server device obtains connection information of all PCs and peripheral devices on the network, and stores the information.

Next, in step S202, the server device acquires driver setup information, which is a preferred example of driver information of peripheral devices in each PC. The peripheral device driver is a driver for a printer, a scanner, a digital camera, a facsimile or the like. As a method of acquiring the setup information, for example, the information is collected by starting a module for acquiring the driver information installed in the own device on each PC, and the information is collected.
Transmission and reception through a network are conceivable. In step S203, the server device displays connection information of all PCs and peripheral devices on the network based on the acquired information. Hereinafter, an embodiment using the driver information structure will be described.

FIG. 3 shows an example of a driver information structure that has been set up. PC name, IP address, OS (operating system) type, user name, number of device drivers, information of each device driver,
And property information. Each device driver information includes device type such as printer and scanner,
It consists of a driver name, version information, output port, share name, driver information address, property information name, and property information address. For example, for the first registered printer, the driver name is LASER-830, the version is 1.00.00, the output port is local, and the shared name is LASER-8.
30, the driver information address is 0x10000, the property information name is standard setting, and the property information address is 0x50000. This information is recorded for each PC.

FIG. 4 is a diagram showing an example of a structure of property information. This example is property information of a printer driver. In the present embodiment, an example is shown in which page settings, finish settings, paper feed settings, and print quality settings are set. The property information includes information referred to by the driver module when performing the printing process. This structure differs depending on the driver type, version, and the like. Property information can also be stored in the registry of the OS. Further, information can be input to the driver, and the input information can be output as external information of property information, for example, as an external file by the driver.

FIG. 14 is a diagram showing a driver setting screen. Hereinafter, generation of property information by a driver and external file output processing which is a preferred example of external information will be described. Displayed on the CRT of the server device, the user operates a GUI (graphical user interface) on the screen by using a pointing device or a keyboard.

In the property information, finishing processing represented by the presence or absence of stapling, print quality, paper feed information for operating the device, and the like can be set. Here, as an example, the property information selection tab 1401 is in a state where a tab for page setting is selected. Reference numeral 1402 denotes a favorite selection unit for the user to select favorite property information.

Reference numeral 1403 denotes a property information addition instructing unit. When the property information addition instructing unit 1403 is instructed,
A property information addition screen appears as shown in FIG.
Reference numeral 1404 denotes a property information editing unit. When the property information editing unit 1404 is instructed, a favorite editing screen appears as shown in FIG.

Reference numerals 1406 to 1413 denote parameter indicating units for indicating parameters stored in property information. Page layout 140 such as output paper size 1406, number of copies 1407, print orientation 1408, 2in1, etc.
9, page layout arrangement order 1410, presence / absence of stamp 141 including watermark print embedded in print data 141
2. Stamp type 1411, presence / absence of staples, and sorting method (for example, face-up / face-down)
, Etc., can be designated.

Reference numeral 1414 denotes a property information confirmation unit.
When the property information confirmation unit 1414 is pressed, a screen (not shown) for confirming the content of the parameter of the property information is displayed.

Reference numerals 1415 to 1421 denote user-defined papers respectively, 1416 denotes a page option, return to standard, O
A selection unit for selecting K, cancel, apply, and help.

The administrator operates 1401 to 1421 to store the above parameters as property information in the driver of the server device.

FIG. 15 shows a property information addition screen. Reference numeral 1501 denotes a name input unit 1501 for inputting the name of property information. Reference numeral 1502 denotes an icon designating unit for designating an icon corresponding to the property information.
Reference numeral 1503 denotes a comment input unit into which a comment related to property information can be input. Reference numeral 1504 denotes a property information display switching unit.

Reference numeral 1506 denotes a property information display unit.
Reference numeral 1507 denotes a screen switching button. When OK is pressed,
Parameters currently set in the driver (partially displayed in the property information display unit 1506) are registered as property information. In the example of FIG.
The property information is stored under the property information name of “order slip”. When the saving process is completed, a property information setting screen is displayed as shown in FIG.

As shown in FIG. 16, a “procurement section order form” is configured as property information and can be selected (display section 1422). From the next time, when the property information selection unit 1402 is used to specify the property information name “Procurement Section Order Form”, the parameters stored in the driver and set previously are called, and the printing processing is performed by applying the parameters. Can be.

FIG. 17 shows a property information editing screen. On this screen, the property information instruction unit 170
In step 1, the name of the property information to be deleted is selected,
When the delete button 1711 is pressed, the property information can be deleted. Similarly, the selected property information can be output to an external file by pressing the file save instruction unit 1706. By pressing a file read button 1705 and selecting a desired external file (not shown), parameters relating to printing can be read from an external file in which print parameters have been defined, and newly defined as property information.

FIG. 18 is a flowchart showing an example of a process in which an administrator registers property information in the install server. The administrator instructs and selects parameters relating to print processing to be stored on the driver setting screen shown in FIG. 14 (S1801).

Then, the property information addition instructing section 140
3 is pressed (S1802), and the property information addition screen shown in FIG. 15 is displayed. On the property information addition screen,
A property information name 1501, an icon 1502, and a comment 1503 are input (S1803), and the screen switching button 1507, which is a property information registration instruction, is pressed.
By pressing the K button (S1804), the property information is registered in the driver (return to the driver setting screen in FIG. 14).

When the property information editing unit 1404 is pressed on the driver setting screen shown in FIG. 14 (S1805), the property information editing screen shown in FIG. 17 is displayed. Then, when the administrator presses the file save instruction unit 1706, the driver automatically outputs the property information as an external file to a predetermined directory (S1806). Hereinafter, a file in which the property information is externally output is referred to as an external file.

The administrator sets the client for each client
Alternatively, one or more pieces of property information are created for different printers set in the same client. One or more of these files are created in a predetermined directory. The external file is preferably an external file name associated with a client device name, a printer name, or the like.
By transmitting these external files to other information processing devices,
The setting information is utilized by being read by the driver or registered in the OS.

FIG. 5 is a diagram showing an example of a screen displaying PCs and peripheral devices on the network. Reference numeral 301 denotes a menu, 302 denotes a toolbar, and 303 denotes a main window on which icons representing PCs and peripheral devices are displayed.
302a to 302i are PCs on the toolbar 302.
And icons representing functions performed by operating peripheral devices. For example, reference numeral 302a denotes an icon for executing a copy function of reading image data from a selected scanner and outputting the image data to a selected printer.
302b is a FAX function, 302c is an image data reading function, 302d is a function of reading image data and performing OCR processing, 302e is a function of managing FAX reception data and distribution data, 302f is a display switching function, and 302f is a display switching function.
g is a display screen editing function, 302h is a function for performing information update processing, and 302i is an icon for executing a function for canceling the update processing.

Reference numerals 303a to 303q denote icons representing PCs and peripheral devices shared on the network.
These icons 303a to 303q are displayed with their icons changed according to the type of device such as a PC, a printer, a scanner, or a FAX modem, or a status such as "processing" or "error occurred". 303c is an icon representing the own device, and 303b is an icon representing a domain to which the own device is logged on. Since the own device is a special device, it is displayed at the top in distinction from other PCs. Other PCs are displayed in ascending or descending order in alphabetical order.

The icons of the PCs and peripheral devices which are shared on the network like the icon 303p but have no driver installed are displayed in gray. A “+” mark is displayed when there is a connected device 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. Is done. If there is no connected device like the icon 303q, no mark is added.

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

FIG. 6 is a diagram showing an example of a screen for displaying the driver setup status of each PC on the network, which is displayed based on the driver information structure obtained from each PC. In the figure, the drivers installed in “My PC” are 6 printers and 2 scanners.
There are pieces. Among them, for example, a printer named “INKJET-10V” has a driver name “INKJET-10V”, a version number “1.00.00”, and property information “standard setting”.
Indicates that the printer driver is shared on the network set to be shared under the name "INKJET-10V".

Returning to the flowchart of FIG. 2, in step S204, the setup program including the installer in the server device determines whether or not property information has been requested. Here, if the property information has not been requested, the process ends. If the setup program in the server device determines that the property information has been requested, the process proceeds to step S205. As a method of requesting the property information, a method is conceivable in which a menu is displayed on each device by a mouse operation to request the property information of the corresponding driver from the server.

Next, in step S205, the setup program in the server determines whether or not there is the requested driver property information. Then, when there is no property information, the setup program in the server device notifies that there is no corresponding property information, and ends the processing. When the setup program in the server device has the corresponding property information,
It moves to step S206. Even if the same device supports different functions depending on the version, the presence or absence of the driver property information may be determined based on the device type, the driver name, and the version information. The determination is made by comparing whether or not all the pieces of information match.

In step S206, the requested PC
Send the corresponding property information list to. Here, traffic on the network can be reduced by transmitting the minimum information necessary for the user to select, instead of transmitting all the information to the PC that has made the request.

Further, in step S207, the setup program in the server device determines whether or not there has been a request for property information from the PC. If there is no request, the process ends. If there is a request, the process proceeds to step S208, where the setup program in the server device requests the OS in the server device to transmit the requested property information of the driver, and ends the process.

FIG. 7 is a flowchart showing a processing operation of the PC functioning as a client device. First, in step S601, it is determined whether to acquire driver property information from the server device. Here, if not acquired, the process ends.

When acquiring, the setup program in the server device proceeds to step S602, and requests the property information list of the corresponding driver from the server device. When making a request, the device type, driver name, and version information are transmitted.

In step S603, the setup program in the server determines whether a list of driver property information has been obtained. If it cannot be obtained because there is no driver property information corresponding to the server device, the process ends.

If the property information list can be obtained, the process proceeds to step S604, and it is determined whether to obtain the property information. When the property information of the driver is not acquired, the process is terminated.

If the property information of the driver is to be obtained, the process proceeds to step S605, and a request for obtaining the property information is transmitted to the server. Then, step S60
In step 6, it is determined whether the property information has been acquired. If it cannot be obtained, the process returns to step S605, and waits until it can be obtained.

If the property information has been acquired, the process proceeds to step S607, and the corresponding driver is updated based on the acquired property information.

(Second Embodiment) In the flowcharts shown in FIGS. 2 and 7, all the property information of the driver is centrally managed by the server device. In this case, large-size information is transmitted over the network. Will be exchanged. Therefore, in order to prevent traffic from increasing, only the minimum information is registered and managed in the server device.
A method in which the property information body is managed by each PC, and when the property information is required, a request from the server device is received and transmitted to the designated PC.

FIG. 8 is a flowchart showing the processing operation of the server device when each client device manages the property information of the driver installed in itself, and FIG. 9 is a flowchart showing the processing operation of the client device. Steps S1101 to S1107 in FIG. 8 are the same as steps S201 to S207 in the flowchart in FIG.

In step S1108, the device type, driver name, version information, property information, and PC information to be transmitted are transmitted to the PC managing the driver property information, and the designated P
Instruct C to transmit the property information.

On the other hand, as shown in FIG. 9, the client device determines in step S1201 whether or not there is a request for transmitting property information from the server device. If there is no request, the process ends.

If there is a transmission request, step S120
Then, the process proceeds to step 2, and the property information of the specified driver is read from the management data. The structure of the management data is
A structure similar to the structure shown in FIG. 3 is conceivable. Then, in step 1203, the property information is transmitted to the designated PC.

(Third Embodiment) In the first and second embodiments described above, the case where there is a request from a client device has been described. However, an operation may be performed from a server device to a corresponding client device. Conceivable. FIG. 10, 1
1 is a flowchart showing the processing operation of the server device and the client device in that case.

FIG. 10 is a flowchart showing the processing operation of the server device. Steps S701 to S703 correspond to steps S201 to S201 in the flowchart of FIG.
This is the same as S203.

In step S704, the setup module in the client device determines whether to update the property information of the client device. If there is no update instruction, the process ends. If there is an update instruction, the process moves to step S705. As an operation method here, for example, it is conceivable to select a certain driver and issue an update / setup instruction of property information. Update and setup instructions are available from Remote Precedure Cal
l (Remote Procedure Call, hereinafter referred to as "RPC") or this is preferably implemented using SOAP (Simple Object Access Protocol), which is an example of implementation using XML using object orientation. For example, as an example of an update instruction from a server device, R that remotely calls an update processing module of a client device may be used.
PC. In addition, not only SOAP, but also H
Another mechanism may be provided that provides a mechanism for exchanging driver and device information using TTP.

In step S705, step S702
Based on the information acquired in step (1), it is determined whether or not there is a client device in which the specified driver is installed. If there is no corresponding client device because the power of the corresponding PC has been turned off or the driver has been deleted, the processing is terminated. If there are corresponding PCs, those PCs are displayed. FIG. 12 is a diagram showing an example of a screen when there is a corresponding PC. Here, a PC whose property information is to be updated is selected.

In step S 706, the setup module in the client device transmits the update instruction to the PC
OS to send property information update notification to
Control. Then, in step S707, the setup module in the client device determines whether there is a request for transmitting property information from each client device.

If there is no transmission request, step S7
Move to 09. If there is a transmission request, step S7
08, the setup module in the client device sends the designated property information to the P
A command for controlling the OS to be transmitted to C is generated. Here, the property information is a file described in a predetermined data format. In a client PC in which a driver is mounted, the user can input or output the property information by instructing the driver.

In step S709, the setup module in the client device updates all P
It is determined whether there is a response from C. Here, if there is a response from all the PCs, the process is terminated. If there is no response from all the PCs, the process returns to step S708, and the processing is continued.

FIG. 11 is a flowchart showing the processing operation of the client device. First, step S9
In step 01, it is determined whether an update notification of property information has been received from the server device. If there is no notification, the process ends.

If the notification has been received, the process shifts to step S902 to determine whether to update the property information. FIG. 13 is a diagram showing an example of a message displayed in that case. If the user selects "No" to cancel the update, the server apparatus is notified that the update is not to be performed, and the process ends. If “Yes” is selected and the update is performed, the process proceeds to step S903, where a request for transmitting property information is made to the server, and the process proceeds to step S904.
Move to

In step S904, the setup module in the client device determines whether the property information and the setup information have been obtained from the server device. If not acquired, step S903
Return to and wait until you can get it. If the property information and the setup information can be obtained, step S9
In step 05, the property information of the driver specified based on the acquired information is updated and set according to the setup instruction included in the setup information.

Here, the setup instruction is for controlling, for example, a process in which a setup module in the client device calls an API of the OS in the client device and registers the received property information in the registry area of the OS. The setup instruction may control a process of issuing an instruction to the driver setup module to instruct the driver to read the property information.

Although the confirmation message is displayed in step S902 in this example, the updating process may be performed automatically without displaying the message.

As described above, in this embodiment, the PCs and peripheral devices shared on the network are displayed in the window, and the property information of the driver of the peripheral device is shared on the network. The property information of the driver can be updated by the operation. Further, the server device can set common property information for each client device. Furthermore, by distributing the management of property information to client devices and exchanging information as needed, it is possible to minimize traffic on the network.

(Fourth Embodiment) In the third embodiment, the setting or updating of the driver property information has been described. However, in the present embodiment, the server device side replaces the driver of the client device with a new one. This is a process for actively distributing a driver without waiting for a request from a client device when adding or updating. In this embodiment, portions different from the above-described embodiment will be described.

The setup program in the install server device calls the API or the system call of the OS without waiting for the driver information transmission request from the client device, and performs the driver setup instruction and the control of the process of distributing the driver. Do. Then, the setup program transmits the property information of the driver to be transmitted to the client device in parallel from the installation server device voluntarily or after a request from the client device after the driver is installed. Control the OS.

FIG. 20 is a diagram showing an example of a printing system according to the present embodiment. Client device A 381, client device B3, which are preferred examples of the client
82, a client device C383, an install server device 385 which is a preferred example of a server device, and an LA which is a preferred example of a network which is a file server device 386.
N (local area network) 360. Install server device 3 of the present embodiment
In the file server 386, client devices 381 to 383 are composed of PCs, which are preferable examples of an information processing device, and the internal structure is the same as that of FIG.

FIG. 23 is a diagram showing a software module as a preferred example in each client device. An example of a driver installation process in a client will be described with reference to FIG. An OS is installed in the client device. The area of the software module in each client device is composed of a user area 377 and an O.
It is divided into S regions 378.

Driver Installation Module 371
Is prepared as an application that operates on the OS. The system program 379 manages the driver name, the printer name, and the directory of the driver stored in the client device by registering them in the registry 376.

The driver installation module 371
Calls the system installer 374 via an API (application programming interface). The system installer 374 is provided as a function of the OS. In response to a command from the driver installation module 371, the system installer 374 is installed from the outside and copies or moves the driver 372 stored in the user area 377 to the system file area 375. I do. In a part of the system file area 375, a registry area 376 for registering various information of a device using the driver is secured. Further, the driver installer module 371 can call the system installer 374 to store the driver setup information and the property information in the registry area. The registry may be prepared for each user.

Here, the driver installation module 371 calls the API of the OS for registering the property information in the registry 376 according to the setup instruction received from the external device, or calls the driver installed in the system file. Perform processing to read property information. The property information of the driver includes, for example, the O
The favorite print settings can be stored as property information in the registry area of the OS for each printer registered in S.

The driver property information may be received from the install server in the form of the external file described with reference to FIG. 14 and read into the file system of the user area 377. In this case, the driver installer can automatically read the driver property information in the file format, pass it to the driver, and reflect the driver property information in the driver settings.

FIG. 19 is a diagram showing an example of a process in which the install server distributes the driver to the client and sets the property information. In the present embodiment, as described above with reference to FIG. 14, the property information of the driver is obtained by outputting the information input by the administrator in the install server device as an external file. This processing is started when a setup program having a remote installation function mounted on the install server device 385 is started. In the processing of FIG. 19, the setup program in the install server device 385 distributes the driver by push installation without waiting for a request from the client device.

A setup program (management means) in the install server device 385 manages property information for each printing device registered in the OS, and stores property information suitable for functions and options for each model of the printer. It is also conceivable that the OS is controlled so as to distribute the property information and the property information is distributed.

The OS of each client device which has received the driver and the setup information from the install server device via the network inputs the property information of the driver and a setup instruction of the property information to the driver installer (input means).

Based on the setup instruction, the installer installs the property information in the OS in the install server device 385 so that the driver in the install server device 385 can recognize the property information. For example, upon receiving a setup instruction command, the driver installer causes the driver to recognize the property information input from the OS by inputting and reading the property information. Further, in response to the setup instruction, the driver installer calls the API of the OS and registers the property information in the registry of the OS, and the driver recognizes the property information via the OS.

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”.

The description returns to the processing of FIG. First, in step S1901, the setup program in the install server device 385 determines whether an instruction to remotely install a driver on each client device has been issued. The instruction of the remote installation is issued by, for example, the user using C
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 install server device 3
If the setup program in 85 determines that there is no remote installation instruction, the process ends.

On the other hand, if it is determined in step S1901 that the setup program in the install server device 385 has instructed remote installation, the process proceeds to step S1.
The process advances to step 902 to create setup information of a driver to be remotely installed. Driver setup information includes the name of the driver to be installed, the driver itself,
The information includes information such as a printer name, an output port name, and a module for making the port available. The printer name is
Here, it is registered and managed in the registry of the OS of each client device.

Here, referring to FIG. 21, step S190 is performed.
The process 2 will be described in detail. FIG. 21 is an example of a screen for setting driver information displayed on the CRT of the install server device. The administrator creates setup information including a setup instruction using this setting screen. Reference numeral 331 denotes a printer name indicating unit. 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 on the network may be designated by the printer name designation unit 331.

Reference numeral 332 denotes a port designation unit. In the port designation section, a port can be added by pressing the 334 port addition instruction section with a mouse.

In the setting example of FIG. 21, an IP address as information indicating the location of the printer on the network, and the use of lpr as a printing protocol are designated, and a logical port corresponding to these is created. Is shown. lpr is a traditional print management program, but of course other print management programs may be used. Further, a network protocol different from TCP / IP may be used.

Reference numeral 333 denotes a driver designation unit for designating a driver to be installed in each client device. By operating the driver addition instruction unit 335, the driver can be designated.

The above is an example of port creation when a network printer using TCP / IP and lpr performs 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 an LPD port may be specified, and setup information may be created based on the specified COM port or LPD port. Also, a setting indicating printing via the print server device can be set as the port. For example, the print server name of the print server device 387 is “SVPC1” and the printer name of the printer 384 is LA.
In the case of SER950, if "\\ SVPC1 \ LASER950" and a port are specified, SVPC1 is set as a print server.
A port for causing the ASER 950 to perform printing is set.

When the OK button 336 on the screen shown in FIG. 21 is pressed, FIG. 22 is displayed, and the flow shifts to steps S1903 and S1904.

In step S1903, FIG.
On the setting screen, the setup program in the install server device 385 selects a client device on which the selected driver is to be installed. It is also possible to select a plurality of client devices to be distributed at the same time.

FIG. 22 shows an example of a screen for instructing a client device for setting up a driver used in the processing of FIG. 19 and setting of property information. It is also possible to select a plurality of client devices at the same time. Also,
The property information distribution setting unit 221 can also set ON / OFF of execution of property information setting processing. Using the property information file selection unit 222, a property information file created using the setting screen in FIG. 17 and desired to be distributed to each client device is selected. In FIG. 22, the property information A is in a selected state. Also,
In this example, one or a plurality of client devices in a domain are selected, but designation across the same domain is also possible.

In step S 1904, the setup program in install server device 385 specifies whether to distribute the property information based on the input from property information distribution setting section 221, and further, property information file selection section 222. Specify the property information name to be distributed based on the input from.

In step S1905, the setup program in the install server device 385 determines whether or not the setup program is set to execute the driver property information setting process when the driver installation is completed on each client device. to decide. If the setup program in the installation server device 385 determines that the property information of the driver is not set to perform the setting process in the client, the setup program performs the process of step S1907. If the client is set to execute the property information setting process in the property information setting process, the process advances to step S1906.

In step S1906, the setup program in the install server device 385 automatically reads the external file including the property information and corresponding to the property information name specified in S1904. here,
The external output file is created by the administrator, and
An instruction to automatically read from the directory in the install server device 385 in which the file specified in 1904 is stored, additionally store the main body of the property information and the property information to be distributed as setup information, and distribute the setup information to the client. Issued to OS.

Then, in step S1907, the setup program (recognition means) in server device 385
Recognizes the driver setup information including the setup instruction set and recognized in the above-described steps, and the driver to be installed. Further, the setup program determines and recognizes the client device on which the one or more drivers specified in step S1903 are to be installed, and instructs the OS via the API to distribute the determined client device to the determined client device, and executes the processing. To end. The install server device 385 stores the property information in the install server device 385.
It is preferable to start the distribution process in response to the input of the instruction to start the driver installation.

In the processing shown in FIG. 19, the install server device 385 collects the OS type and OS version in advance and collects them.
5 based on the information of each client device stored in
Automatic judgment is being performed. However, if it is not possible to automatically determine the OS installed in each client device, before the setup program generates the setup information in step S1902, the user sets the OS type and version and the graphical user interface shown in FIG. And the architecture of the CPU may be changed.

Also, in the processing shown in FIG. 19, the property information is actively distributed without waiting for a request from the server.
May transmit the property information in response to a property information transmission request from each client device.

The property information is output as an external file by the driver, and is
And is used in each client device. Each client device automatically reads property information from the external file acquired from the install server device 385 outside each client device, and inputs the read property information to a driver in each client device to read it.

(Other Embodiments) In order to operate various devices in order to realize the functions of the above-described embodiments, an apparatus connected to the various devices or a computer in a system is used in the above-described embodiment. Supply the software program code to realize the functions of
The present invention also includes those implemented by operating the various devices according to programs stored in a computer (CPU or MPU) of the system or apparatus.

In this case, the software program code itself implements the functions of the above-described embodiment, and the program code itself and means for supplying the program code to the computer
For example, a recording medium storing such a program code constitutes the present invention. As a recording medium for storing such a program code, for example, a flexible disk, a hard disk, an optical disk, a magneto-optical disk, a CD-RO
M, a magnetic tape, a nonvolatile memory card, a ROM, or the like can be used.

When the computer executes the supplied program code, not only the functions of the above-described embodiment are realized, but also the OS (operating system) running on the computer or another program code. It goes without saying that such program codes are also included in the embodiments of the present invention when the functions of the above-described embodiments are realized in cooperation with the application software or the like.

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 the function expansion unit is specified based on the instruction of the program code. It is needless to say that the present invention also includes a case where the CPU or the like provided for performs part or all of the actual processing, and the processing realizes the functions of the above-described embodiments.

The shapes and structures of the respective parts shown in the above embodiments are merely examples of the embodiment for carrying out the present invention, and the technical scope of the present invention is thereby reduced. It should not be interpreted restrictively. That is, the present invention can be implemented in various forms without departing from the spirit or main features thereof.

[0109]

As described above, according to the present invention, the property information of the driver can be shared on the network, so that the property information of the driver can be updated by a simple operation. Further, the server device can set common property information for each client device.

Further, in the driver installed in the client, the property information of the driver is distributed from the server device and set in the client device. Therefore, the labor for setting the property information of the driver is reduced, and the setting mistake is reduced. be able to.

Further, the push installation of the driver is performed in accordance with the setup instruction from the server device, and the property information setting processing for the driver is performed. Therefore, the burden of the driver installation and property information setting processing performed in each client is reduced. Can be reduced.

[Brief description of the drawings]

FIG. 1 is a block diagram illustrating a schematic configuration of an apparatus according to an embodiment.

FIG. 2 is a flowchart illustrating a processing operation of a PC functioning as a server device.

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

FIG. 4 is a diagram illustrating an example of a property information structure.

FIG. 5 is a diagram illustrating an example of a screen displaying PCs and peripheral devices on a network.

FIG. 6 is a diagram illustrating an example of a screen that displays a driver setup status of each PC on a network.

FIG. 7 is a flowchart illustrating a processing operation of a PC functioning as a client device.

FIG. 8 is a flowchart illustrating a processing operation of the server device.

FIG. 9 is a flowchart illustrating a processing operation of the client device.

FIG. 10 is a flowchart illustrating a processing operation of the server device.

FIG. 11 is a flowchart illustrating a processing operation of the client device.

FIG. 12 is a diagram illustrating an example of a screen for selecting a PC for updating property information.

FIG. 13 is a diagram illustrating an example of a screen displayed when an update notification of property information is received.

FIG. 14 is a diagram illustrating an example of a driver setting screen.

FIG. 15 is a diagram illustrating an example of a property information addition screen.

FIG. 16 is a diagram illustrating an example of a property information setting screen.

FIG. 17 is a diagram illustrating an example of a property information editing screen.

FIG. 18 is a diagram illustrating an example of a process in which an administrator registers property information in an install server device.

FIG. 19 is a diagram illustrating an example of a process in which an install server device distributes a driver to a client device and sets property information.

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

FIG. 21 is a diagram illustrating an example of a screen for setting driver information displayed on a CRT of an install server device.

22 is a diagram illustrating an example of a client device for setting up a driver used in the process of FIG. 19 and a screen for instructing property information setting;

FIG. 23 is a diagram illustrating a software module as a preferred example in each client device.

[Explanation of symbols]

 Reference Signs List 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 flexible 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 381 Client device 382 Client device 383 Client device 384 Printer 385 Install server device 386 File server device 387 Print server device

Claims (39)

[Claims] 1. An information processing apparatus that communicates with a client device, a recognizing means for recognizing a client device to which property information of driver information is to be delivered; And a distribution control unit for controlling a process of distributing a setup instruction to perform the setting. 2. The information processing apparatus according to claim 1, wherein the setup instruction includes a setup instruction for controlling the client device so that the client device registers the property information in an OS. 3. The apparatus according to claim 1, wherein the setup instruction includes an instruction to control the driver information so that the driver information reads the property information.
An information processing apparatus according to claim 1. 4. A printer further comprising: a management unit that manages the property information for each printing device registered in an OS, wherein the distribution control unit controls a process of distributing the property information corresponding to the printing device. The information processing apparatus according to claim 2, wherein 5. The information processing apparatus according to claim 1, wherein the distribution control means controls a process of distributing the property information in response to an input of a driver setting start instruction in the information processing apparatus. apparatus. 6. The information processing apparatus according to claim 1, wherein the distribution control unit controls a process of automatically reading the property information generated by the driver information in the information processing device and distributing the property information to the client device in the information processing device. The information processing apparatus according to claim 1, wherein: 7. The information processing apparatus according to claim 1, wherein the setup instruction is realized by a simple object access protocol. 8. An information processing method in an information processing device that communicates with a client device, comprising: a recognition procedure for recognizing a client device to which property information of driver information is to be distributed; A distribution control procedure for controlling a process of distributing a setup instruction for setting up property information. 9. The information processing method according to claim 8, wherein the setup instruction includes a setup instruction for controlling the client device so that the client device registers the property information in an OS. 10. The information processing method according to claim 8, wherein the setup instruction includes an instruction to control the driver information so that the driver information reads the property information. 11. A management procedure for managing the property information for each printing device registered in an OS, wherein the distribution control procedure controls a process of distributing property information corresponding to the printing device. The information processing method according to claim 9, wherein: 12. The information processing according to claim 8, wherein in the distribution control procedure, a process of distributing the property information in response to input of a driver setting start instruction in the information processing apparatus is controlled. Method. 13. The distribution control procedure includes a step of controlling a process of automatically reading the property information generated by driver information in the information processing device and distributing the property information to the client device in the information processing device. 9. The information processing method according to claim 8, wherein: 14. The method according to claim 1, wherein the setup instruction is a simple
9. The information processing method according to claim 8, wherein the method is realized by an object access protocol. 15. A control program executed in an information processing device communicating with a client device, a recognition process for recognizing a client device to which property information of driver information is to be distributed, and the property information for the client device; And a distribution control process for controlling a process of distributing a setup instruction for setting up the property information. 16. The control program according to claim 15, wherein the setup instruction includes a setup instruction for controlling the client device so that the client device registers the property information in an OS. 17. The control program according to claim 15, wherein the setup instruction includes an instruction to control the driver information so that the driver information reads the property information. 18. The information processing apparatus further executes a management process of managing the property information for each printing device registered in an OS, and in the delivery control process, delivers the property information corresponding to the printing device. 17. The control program according to claim 16, causing the information processing apparatus to execute processing so as to control processing. 19. The information processing apparatus according to claim 19, wherein, in said distribution control processing, said information processing apparatus is executed so as to control a processing of distributing said property information in response to an input of a driver setting start instruction in said information processing apparatus. A control program according to claim 15. 20. The distribution control process, wherein the property information generated by the driver information in the information processing device is automatically read in the information processing device and the process of distributing the property information to the client device is controlled. The control program according to claim 15, wherein the control program causes an information processing apparatus to execute. 21. The setup instruction is simple
The control program according to claim 15, wherein the control program is realized by an object access protocol. 22. An information processing apparatus capable of communicating with a server device, an input unit for inputting property information of driver information and a setup instruction from the server device, and an information processing device in the information processing device based on the setup instruction. An information processing apparatus comprising: property information input means for inputting the property information to the information processing apparatus so that the driver information can recognize the property information. 23. The information processing apparatus according to claim 22, wherein said property information input means inputs said property information to said driver information. 24. The operating system according to claim 24, wherein the property information input means is an OS
23. The information processing apparatus according to claim 22, wherein the application program interface is called to input the property information to the OS. 25. The printing apparatus according to claim 25, further comprising a management unit that manages the property information for each printing device registered in the OS, wherein the property information input unit inputs property information corresponding to the printing device. Item 2
3. The information processing device according to 2. 26. The property information is output as external information based on driver information outside the information processing apparatus, and the property information input unit outputs property information from the external information acquired from outside the information processing apparatus. 23. The information processing apparatus according to claim 22, wherein the property information is automatically read and the read property information is input to driver information in the information processing apparatus. 27. An information processing method in an information processing device capable of communicating with a server device, comprising: an input procedure of inputting property information of driver information and a setup instruction from the server device; and the information based on the setup instruction. A property information inputting step of inputting the property information to the information processing device so that driver information in the processing device can recognize the property information. 28. The information processing method according to claim 27, wherein in the property information input step, the property information is input to the driver information. 29. In the property information input procedure, O
28. The information processing method according to claim 27, wherein the property information is input to the OS by calling an application programming interface of S. 30. A management procedure for managing the property information for each printing device registered in an OS, wherein the property information inputting step inputs property information corresponding to the printing device. An information processing method according to claim 27. 31. The property information is output as external information based on driver information outside the information processing apparatus. In the property information input procedure, property information is obtained from the external information acquired from outside the information processing apparatus. 28. The information processing method according to claim 27, further comprising automatically reading the property information and inputting the read property information to driver information in the information processing apparatus. 32. A control program executed in an information processing device capable of communicating with a server device, comprising: an input process of inputting property information of driver information and a setup instruction from the server device; Controlling the information processing apparatus to execute a property information input process of inputting the property information to the information processing apparatus so that driver information in the information processing apparatus can recognize the property information. program. 33. The information processing apparatus according to claim 3, wherein in the property information input processing, the information processing apparatus is executed to input the property information to the driver information.
3. The control program according to 2. 34. In the property information input processing, O
The control program according to claim 32, wherein the control program causes the information processing apparatus to execute an application programming interface of S to input the property information to the OS. 35. The information processing apparatus further executes a management process of managing the property information for each printing device registered in an OS, and in the property information input process, inputs property information corresponding to the printing device. 33. The control program according to claim 32, causing the information processing apparatus to execute. 36. The property information is output as external information by driver information outside the information processing apparatus. In the property information input processing, property information is obtained from the external information acquired from outside the information processing apparatus. 33. The computer-readable storage medium according to claim 32, wherein the control program causes the information processing apparatus to automatically read the property information and input the read property information to driver information in the information processing apparatus. 37. A recognizing means for recognizing a client device to which property information of driver information is to be distributed in a network system in which the client device and the information processing device can communicate with each other; And a distribution control unit for controlling a process of distributing a setup instruction for setting up the property information. 38. A network system in which a server device and an information processing device can communicate with each other, wherein: input means for inputting property information of driver information and a setup instruction from the server device; A network system comprising: property information input means for inputting the property information to the information processing apparatus so that driver information in the information processing apparatus can recognize the property information. 39. A computer-readable storage medium storing the control program according to any one of claims 15 to 21 and 32 to 36.