JP7551859B1 - System, management device and method - Google Patents

Abstract

[Problem] To make it possible to prompt specific distribution data such as an address book to be reliably linked to a network device or device group to which the data is to be distributed. [Solution] A program realizes a first management means for managing device information of one or more network devices to be managed, a second management means for managing an address book including destinations for data transmission that can be used by the network device, a distribution means for distributing the address book to a network device specified based on the device information, and a provision means for providing a notification to a user, the first management means being capable of managing any one or more network devices as a device group, and the provision means providing the notification when a setting for linking the address book to a network device or device group has not been executed. [Selected Figure] Figure 1

Description

The present invention relates to a system, a management device, and a method.

Device management systems and management devices are known that acquire and manage data related to the operation of image forming devices such as printers and multifunction devices (hereinafter referred to as devices). In recent years, the number of devices that can be managed by a single management device has been increasing due to an increase in the number of devices to be managed and the need to reduce costs and maintain management servers.

The device management system and management device can manage address books and the like that contain multiple pieces of destination information, such as the status, settings, firmware, and email addresses of the network devices that are the subject of management. The device management system and management device can obtain and distribute data via the network to the network devices that are the subject of management.

Patent Literature 1 also discloses a technology that monitors whether a network device is configured as intended by an administrator by comparing the setting values contained in the monitoring data with the setting information obtained from the monitored network device.

JP 2016-153992 A

The technology disclosed in Patent Document 1 realizes data distribution by creating a task that specifies the data to be distributed to the network devices to be managed and to a device group that groups together at least some of these network devices.

For example, when distributing an address book, if destination information to be distributed is to be added or edited, it may be desirable to retain the already distributed address book on the system side, edit the contents of that address book, and re-distribute it, rather than distributing a different address book. This is because the memory, functionality, and other constraints of the network device at the distribution destination may make it impossible to retain multiple address books, or to remotely edit an address book that has already been distributed. If a different address book is distributed, in some cases the distribution itself may fail, preventing the intended use of the address book by the recipient user. Therefore, in a device management system, for specific distribution data such as an address book, the link between the distribution data and the network device and device group to which it is to be distributed should be managed in advance. Furthermore, such linking should be performed especially when a data distribution task is created.

The present invention aims to provide a system, management device, and method that can encourage the reliable linking of specific distribution data, such as an address book, with the network device or device group to which the data is to be distributed.

In order to solve the above-mentioned problems, the program of the present invention is a program that causes a computer to realize a first management means for managing device information of one or more network devices to be managed via a network, a second management means for managing an address book containing destinations for data transmission that can be used by the network devices, a distribution means for distributing the address book managed by the second management means to a network device specified based on the device information managed by the first management means, and a provision means for providing a notification to a user, wherein the first management means is capable of managing any one or more network devices as a device group, and the provision means provides the notification when a setting has not been executed to link the network device or device group managed by the first management means to the address book managed by the second management means.

According to the present invention, it is possible to encourage specific distribution data, such as an address book, to be linked reliably to the network device or device group to which the data is to be distributed.

1 is a block diagram showing an example of a configuration of a device management system according to an embodiment. FIG. 2 is a block diagram illustrating an example of a hardware configuration of a device management server according to the embodiment. FIG. 2 is a block diagram showing an example of a software module configuration of a device management server according to an embodiment. FIG. 2 is a block diagram showing an example of a configuration of a device according to an embodiment. FIG. 4 is a diagram illustrating an example of a user interface according to the embodiment. FIG. 4 is a diagram illustrating an example of a user interface according to the embodiment. FIG. 4 is a diagram illustrating an example of a user interface according to the embodiment. FIG. 4 is a diagram illustrating an example of a user interface according to the embodiment. FIG. 4 is a diagram illustrating an example of a user interface according to the embodiment. FIG. 4 is a diagram illustrating an example of a user interface according to the embodiment. FIG. 4 is a diagram illustrating an example of a user interface according to the embodiment. 10 is a flowchart illustrating an example of a process executed by a device management system according to an embodiment. 10 is a flowchart illustrating an example of a process executed by a device management system according to an embodiment. 10 is a flowchart illustrating an example of a process executed by a device management system according to an embodiment. 11A and 11B are diagrams illustrating an example of a screen displaying a list of distribution setting information and an example of a screen displaying a list of monitoring settings according to the embodiment.

The program according to the embodiment causes a computer to realize a first management means, a second management means, a distribution means, and a provision means. The first management means manages device information of one or more network devices to be managed via a network. The second management means manages an address book including destinations for data transmission that can be used by the network devices. The distribution means distributes the address book managed by the second management means to a network device specified based on the device information managed by the first management means. The provision means provides a notification to a user. The first management means can also manage any one or more network devices as a device group. The provision means provides the notification when a setting has not been executed to link the address book managed by the second management means to the network device or device group managed by the first management means.

The program according to the embodiment further causes the computer to realize a processing means, a first determination processing means, a first display processing means, a second determination processing means, and a second display processing means. The processing means selects the network device for which an icon and a warning are to be displayed. The first determination processing means determines whether data is set in the network device for which the icon and the warning are to be displayed. The first display processing means displays the icon. The second determination processing means determines whether a cursor is present at the position of the icon. The second display processing means displays a message indicating the warning.

The program according to the embodiment also causes the computer to implement a third display processing means for displaying a link to the edit screen.

The management device according to the embodiment includes a first management means, a second management means, a distribution means, and a provision means. The first management means manages device information of one or more network devices to be managed via a network. The second management means manages an address book including destinations for data transmission that can be used by the network devices. The distribution means distributes the address book managed by the second management means to a network device specified based on the device information managed by the first management means. The provision means provides a notification to a user. The first management means can also manage any one or more network devices as a device group. The provision means provides the notification when a setting for linking a network device or device group managed by the first management means to an address book managed by the second management means has not been executed.

The method according to the embodiment is executed by a first management means, a second management means, a distribution means, and a provision means. The first management means manages device information of one or more network devices to be managed via a network, and also manages any one or more network devices as a device group. The second management means manages an address book including destinations for data transmission that can be used by a network device. The distribution means distributes the address book managed by the second management means to a network device specified based on the device information managed by the first management means. The provision means provides a notification to a user when a setting for linking a network device or device group managed by the first management means to an address book managed by the second management means has not been executed.

Below, specific examples of the above-mentioned programs, management devices, and methods will be described with reference to the drawings.

<System configuration>
1 is a block diagram showing an example of the configuration of a device management system according to an embodiment. The device management system manages one device management application 101, agents 106 and 107, devices 102, 103, 110, and 111. The agents 106 and 107 are sometimes referred to as agent applications. Hereinafter, the device management application 101 is referred to as a device management server 1000. Hereinafter, the devices 102, 103, 110, and 111 are collectively referred to as devices 2000.

Here, agent 106 and agent 107 are linked to device 2000 according to the addresses of each device included in device 2000. Below, an example will be described in which agent 106 is linked to device 102 and device 103, and agent 107 is linked to devices 110 and 111.

The device management server 1000, the agent 106, the device 102, and the device 103 are interconnected by the network 104. The agent 107, the device 110, and the device 111 are interconnected by the network 108. The network 104 and the network 108 are interconnected by the router 109. Hereinafter, the network 104 and the network 108 are collectively referred to as the communication line 3000. The router 109 may be configured to, for example, allow communication between the agent 107 and the device management server 1000, while blocking communication with the devices 110 and 111 on the network 108.

The directory server 105 is used by users. The device management server 1000 can also be configured to allow users of the directory server 105 to access the device management server 1000.

The following description will be given using the agent 106 and the device 102 as examples. The device management server 1000 instructs the agent 106 to operate the device 102. The agent 106 executes operations such as sending a request to the device 102 according to the instructions, and sends the results to the device management server 1000. Examples of operations include obtaining information from the device 102, changing settings of the device 102, instructing the device 102 to install an application, instructing the device 102 to update firmware, etc. The device 102 and the device management server 1000 do not communicate directly, and communication is carried out between the device management server 1000 and the agent 106 and between the agent 106 and the device 102.

Note that, although FIG. 1 shows agents 106 and 107, devices 102, 103, 110, and 111, the present invention is not limited to this. For example, even if a dozen agents manage tens of thousands of devices, the configuration and operation are the same as those described in this embodiment.

Here, the device management server 1000 is a server on which the UI control unit 30, device control unit 31, schedule control unit 32, and function control unit 33 shown in FIG. 3 operate in order to manage the device 2000.

<Device management server hardware configuration>
2 is a block diagram showing an example of a hardware configuration of a device management server according to an embodiment. A CPU (Central Processing Unit) 10 uses a RAM (Random Access Memory) 12 as a work area to execute various programs such as an OS (Operating System) and device management software stored in a ROM (Read Only Memory) 11 or a HDD (Hard Disk Drive) 19. Each component of the device management server 1000 is connected via a system bus 13.

The device management server 1000 also includes a disk controller (DKC) 18, a disk drive 20, a video card (VC) 14, and a display device 15. The disk drive 20 can mount storage media such as CD-ROMs, DVDs, magnetic tapes, and IC memory cards. The display device 15 is, for example, a cathode ray tube (CRT) television. The device also includes a keyboard controller (KBC) 16, a keyboard (KB) 17, and a pointing device such as a mouse, all of which are not shown. The device also performs data communication with devices on the communication line 3000 via a network interface card (NIC) 21.

<Software configuration of device management server>
Fig. 3 is a block diagram showing an example of a modular software configuration of a device management server according to an embodiment. Specifically, Fig. 3 shows an example of a modular software configuration of a UI control unit 30, a device control unit 31, a schedule control unit 32, and a function control unit 33 that operate on the device management server 1000. This modular software configuration is the subject of processing that is realized by executing the device management software, and is executed by the CPU 10 on the RAM 12, ROM 11, and HDD 19 shown in Fig. 2. This processing will be described later.

The UI control unit 30 is composed of a device display unit 301, a schedule display unit 302, and a function display unit 303. The device control unit 31 is composed of a device connection unit 311, a device data management unit 312, and a device data storage unit 313. The schedule control unit 32 is composed of a schedule management unit 321 and a schedule storage unit 322. The function control unit 33 is composed of a device setting distribution unit 331, an address book distribution unit 332, and a function information storage unit 333.

The UI control unit 30 manages the UI control of the device control unit 31, schedule control unit 32, and function control unit 33 through the device display unit 301, schedule display unit 302, and function display unit 303, respectively. It can also be implemented as a web-based application, in which case it can be used via a web browser.

The device connection unit 311 has a function of searching for devices, collecting information from devices, and executing settings. One example of the function of the device connection unit 311 is a device search function for the device 2000 using SNMP (Simple Network Management Protocol), IP Broadcast, SLP/Multicast, etc. In this case, the device connection unit 311 searches for the device 2000 at any timing.

The device connection unit 311 has a function of acquiring or changing device information such as MIB (Management Information Base) and security policy information via a communication line 3000 such as a LAN. The device connection unit 311 also acquires device information such as device name, product name, and IP address as a result of device search, and stores the information in the device data storage unit 313. The device data management unit 312 is responsible for managing the data in the device data storage unit 313.

The schedule management unit 321 works in conjunction with each function of the function control unit 33 to generate and manage the schedule input from the schedule display unit 302 and store it in the schedule storage unit 322.

The device setting distribution unit 331 of the function control unit 33 is responsible for distributing settings to the device based on input from the function display unit 303. The address book distribution unit 332 is responsible for distributing an address book to the device based on input from the function display unit 303. At that time, each piece of information is stored in the function information storage unit 333.

Here, the device data storage unit 313, the schedule storage unit 322, and the function information storage unit 333 are data recording media such as databases that run on the HDD 19, and schedule lists, device lists, function information, etc. are stored.

<Device software configuration>
4 is a block diagram showing an example of the configuration of a device according to the embodiment. Specifically, FIG. 4 shows an example of the software configuration of an information control unit 40 that operates on a device 2000.

The device 2000 has an information control unit 40 as a software module for managing multiple sets of dynamically changing information. A counter information management unit 401 manages the number of printed pages and the like, and stores this in a counter storage unit 402. A MIB (Management Information Base) information management unit 403 manages the MIB information, which is the aforementioned device information, and stores this in an MIB information storage unit 404. A power information management unit 405 manages power off information and reboot information, and stores this in a power information storage unit 406.

The status information management unit 407 manages status information such as online, offline, and error, and stores it in the status information storage unit 408. The address book information management unit 409 manages information such as the configuration and data of the address book, and stores it in the address book information storage unit 410. Distributed address book information is also managed and stored here. The setting value information management unit 411 stores various setting values, such as settings for device printing and network-related settings, in the setting value information storage unit 412. Each piece of data is sent to the device management server 1000 via SNMP or other protocols in response to a request from the device management server 1000.

<Device discovery and address book distribution flow>
5 to 11 are diagrams showing an example of a user interface according to an embodiment. Specifically, Fig. 5 to Fig. 11 show an example of a user interface (UI) of the device management server 1000. The flow of device search and address book distribution will be described with reference to Fig. 5 to Fig. 11.

The device management server 1000 searches for devices on the network in order to make them a target for management. This search algorithm can be SNMP, but any method is acceptable. Figure 5 shows an example of the UI after a search. After device search settings are made using the "Task" button shown in Figure 5, the search is executed. Here, the names of the devices found are displayed along with information about those devices. Device information here includes, for example, product name, IP address, and serial number. At this time, it is also possible to specify a specific device to exclude from management.

By selecting the "Task" button shown in Figure 5, you can also make settings related to the distribution of the address book. Figure 6 (A) shows an example of the UI that is displayed when the task type "Distribute address book" is selected from the "Task" button. If "Distribute to selected devices" is not checked, select the address book to distribute from the "Settings" button. The number of devices or device groups linked to the target device column is displayed. Set the distribution date and time from "Schedule" and press the "Create" button to create a task.

Linking an address book to a device is performed in advance by selecting "Address Book" from the "Data" button shown in Figure 5, and then selecting "Combine Address Book and Device." Figure 9 (A) shows an example of the UI. Address books that have already been created are listed, and the linking status with the target device is displayed in the target device column.

If you want to create a new link, press the "Create New" button here. This will display the new creation screen. Figure 10 (A) shows an example of the UI. In "Address Book", give the address book a name, set the necessary destination list, and in "Target Device", select the device to link. Figure 11 shows an example of the UI. After that, pressing Create will save it and it will be displayed as an address book list in Figure 9 (A).

FIGS. 12 to 14 are flowcharts showing an example of processing executed by the device management system according to the embodiment. Processing executed by the device management system 1000 as an information processing device will be described with reference to FIG. 12 to FIG. 14. Each step shown in FIG. 12 to FIG. 14 is realized by the CPU 10 loading a control program from the HDD 19, ROM 11, etc. into the RAM 12 and executing the program.

First Embodiment
The process executed by the device management server 1000 according to the first embodiment will be described with reference to Fig. 12(A), Fig. 13, and Fig. 14(A). In the first embodiment, the description of this process will be supplemented with the operation cases of Fig. 5 to Fig. 11. Note that the process shown in Fig. 12 to Fig. 14 is realized by the CPU 10 executing device management software.

When managing a device, the device management server 1000 first searches for the device, as described above. This device search may be performed each time, or may be performed periodically by setting a schedule.

When distributing an address book, as explained above, display the "Address book and device combination" in the "Address book" under "Data" shown in Figure 5, and link the address book to the device.

The process shown in Figure 13 is performed using the "Address Book and Device Combination" screen.

In step S1101, the function display unit 303 displays a UI that prompts the user to select "new creation" from the previous screen, and determines whether "new creation" has been selected. If so, the process proceeds to step S1105. If not, the process proceeds to step S1102.

In step S1102, the address book distribution unit 332 obtains existing address book data from the function information storage unit 333.

In step S1103, the function display unit 303 displays the address book data acquired in step S1102.

In step S1104, the function display unit 303 displays an icon and a warning. Details will be described later with reference to FIG. 12(A).

In step S1105, the function display unit 303 displays a new creation screen.

In step S1106, the function display unit 303 displays a UI that prompts input of the address book and device.

In step S1107, the function display unit 303 determines whether the Create button has been pressed to save the newly created address book. If the function display unit 303 determines that the Create button has been pressed, the process proceeds to step S1108. On the other hand, if the function display unit 303 determines that the Create button has not been pressed, the process proceeds to step S1105.

In step S1108, the address book distribution unit 332 stores the created address book in the function information storage unit 333.

The process shown in FIG. 12(A) shows an example of detailed processing of step S1104 shown in FIG. 13.

In step S1001, the address book distribution unit 332 selects the data for which an icon and warning are to be displayed.

In step S1002, the address book distribution unit 332 determines whether a target device or device group is set in the data selected in step S1001. If the address book distribution unit 332 determines that a target device or device group is set in the data, it ends the process. On the other hand, if the address book distribution unit 332 determines that a target device or device group is not set in the data, it advances the process to step S1003.

In step S1003, the function display unit 303 displays the icon.

In step S1004, the function display unit 303 determines whether the cursor is on the icon displayed in step S1003. If the function display unit 303 determines that the cursor is on the icon, the process proceeds to step S1005. On the other hand, if the function display unit 303 determines that the cursor is not on the icon, the process shown in FIG. 12(A) ends, and the process proceeds to step S1106 in FIG. 13.

In step S1005, the function display unit 303 displays a warning message.

Click the "Task" button shown in Figure 5, click "Task Settings" and select "Address book distribution" to create an address book distribution task.

The process shown in FIG. 14(A) is performed using the “Address Book Distribution” screen.

In step S1201, the function display unit 303 displays a UI that prompts the user to select a schedule and device.

In step S1202, the function display unit 303 determines whether to select the device input in step S1201. If so, the process proceeds to step S1209. If not, the process proceeds to step S1203.

In step S1203, the address book distribution unit 332 obtains existing address book data from the function information storage unit 333.

In step S1204, the function display unit 303 displays the address book data acquired in step S1203.

In step S1205, the function display unit 303 displays an icon and a warning. Details of step S1205 are shown in the steps of FIG. 12(A).

In step S1206, the function display unit 303 selects the address book to distribute according to the user's instructions.

In step S1207, the function display unit 303 determines whether the Create button has been pressed to save the input schedule or the selected address book or device information. If the function display unit 303 determines that the Create button has been pressed, the process proceeds to step S1208. On the other hand, if the function display unit 303 determines that the Create button has not been pressed, the process returns to step S1210.

In step S1208, the address book distribution unit 332 stores the created address book distribution task in the schedule storage unit 322 via the schedule management unit 321 and terminates the process.

In step S1209, the address book distribution unit 332 obtains device information from the device data storage unit 313 via the device data management unit 312.

In step S1210, the function display unit 303 displays the device information acquired in step S1209 as a device list.

In step S1211, the function display unit 303 selects the device to which the content is to be distributed in accordance with the user's instructions.

This series of actions makes it possible to display an icon and a warning when distributing an address book by specifying the address book, if the address book created in advance is not linked to the device.

Here, we will provide further details by referring to the user interface examples shown in Figures 5 to 11.

First, for preliminary linking, "Address Book" is selected from the "Data" button in the user interface shown in Figure 5, and "Address Book and Device Combinations" are displayed. Figure 11 shows an example of "Address Book and Device Combinations."

In step S1101, it is determined whether new creation has been selected, and in this case it is determined that new creation has not been selected.

Steps S1102 and S1103 display "Address Book 1", "Address Book 2", and "Address Book 3" as existing address book data.

In step S1001, "Address Book 2" is selected, and in step S1002, it is determined whether there is a linked device. Here, as shown in FIG. 9(A), it is determined that the target device has 0 devices and device groups, meaning that it is not linked.

The icon is displayed in step S1003. An example of the icon is shown in FIG. 9(B). The icon is displayed in the target device column of "Address Book 2."

Step S1004 determines whether the cursor is on the icon. Here, it is assumed that the user has moved the cursor over the icon, and that this has been determined.

A warning message is displayed in step S1005. An example of this is shown in FIG. 9B. Below the target device in "Address Book 2," the message "No device or device group has been set" is displayed.

If the user presses "Create new," step S1101 determines that a new entry is to be created, and step S1105 displays a new entry screen. An example of this new entry screen is shown in FIG. 10A. Here, the target address book is edited.

As before, this new address book is selected in step S1001, and a determination is made in step S1002 as to whether there is a linked device. Here, it is assumed that the new address book is not linked to a device, and this determination is made.

An icon is displayed in step S1003. An example of the icon is shown in FIG. 10(B). The icon is displayed on the sheet button for selecting the target device.

Step S1004 determines whether the cursor is on the icon. Here, it is assumed that the user has moved the cursor over the icon, and that this has been determined.

A warning message is displayed in step S1005. An example of this is shown in FIG. 10(B). Below the target device selection button, the message "No device or device group has been set" is displayed.

Steps S1106 to S1108 save the new address book, Address Book 4, that you created here, and thereafter it is displayed in the address book list as shown in Figure 9 (A).

To distribute these address books, click the "Tasks" button in the example user interface shown in Figure 5, click "Task Settings", and select "Distribute Address Book" to create an address book distribution task.

In step S1201, the user is prompted to set a schedule and enter "distribution to selected device" information on the address book distribution screen shown in FIG. 6 (A), and enters these information. Checking "distribution to selected device" is a check as to whether distribution is to be performed by selecting a device or by selecting address book data. Here, it is assumed that no check has been made, meaning that distribution is to be performed by selecting address book data.

In step S1202, it is determined that address book data is to be selected for distribution, and the address book data is displayed in steps S1203 and S1204. "Address Book 1", "Address Book 2", and "Address Book 3" are displayed as the address book data.

After that, similar steps S1001 to S1005 are performed, and an icon is displayed in the target device column of "Address Book 2," with the message "No device or device group set" displayed below. An example of this is shown in Figure 6 (B).

Steps S1206 to S1208 select the address book to be distributed, determine whether the Create button has been pressed to save the entered schedule and selected address book distribution task, and perform the save process.

This series of actions makes it possible to display an icon and a warning message on the "Address Book and Device Combination" screen, new creation screen, and "Address Book Distribution" if the address book and device are not linked.

<Application Examples>
So far, an embodiment has been described in which the linking setting between the address book and the device is encouraged. The device management server 1000 has a function for distributing setting information including network setting values and the like to the network devices to be managed, in addition to a function for distributing the address book. The device management server 1000 also has a setting monitoring function for periodically monitoring and distributing setting information, with the aim of maintaining the network devices to be managed at the settings desired by the administrator. When the setting monitoring function is enabled, the device management server 1000 needs to hold the settings desired by the administrator as monitored setting information.

In the case of the setting value distribution function, the device management server 1000 needs to link the setting value information to the network device or device group to which it is to be distributed. Even in the case of the setting monitoring function, the device management server 1000 needs to link the monitoring setting information to the network device or device group to which it is to be monitored.

Therefore, by using the same control as the address book in the first embodiment, the device management server 1000 displays an icon and a warning message even when the distribution setting value information is not linked to a network device or device group, as shown in FIG. 15(A). Similarly, the device management server 1000 displays an icon and a warning message even when the monitoring setting information is not linked to a network device or device group, as shown in FIG. 15(B).

Second Embodiment
In distributing an address book by specifying a device, if the address book is not associated with the selected device, it is possible to similarly display an icon and a warning message. This will be explained using the flowcharts shown in Figures 12(B) and 14(B), and this process will be supplemented with the example of the user interface of the first embodiment, and Figures 7(A) and 7(B). The processes shown in Figures 12 to 14 are realized by the CPU 10 executing device management software.

As in the first embodiment, it is assumed that several address books and several devices have been linked in advance.

Click the "Task" button shown in Figure 5, and under "Task Settings" create a task, select "Address book distribution" to create an address book distribution task.

The process shown in FIG. 14(B) is performed using the “Address Book Distribution” screen.

From step S1201 to step S1210, the processing steps are the same as those in FIG. 14(A) of the first embodiment, and the display and save functions are used by the function display unit 303 and the address book distribution unit 332. After step S1210, the process proceeds to step S1212.

In step S1212, the function display unit 303 displays an icon and a warning. For details, see the steps in FIG. 12(B). In step S1212 in FIG. 12(B), the following processing is executed.

In step S1006, the address book distribution unit 332 selects the device for which the icon and warning are to be displayed via the device data management unit 312.

In step S1007, the address book distribution unit 332 determines whether the target address book is set in the device selected in step S1006. If the address book distribution unit 332 determines that the target address book is set in the device selected in step S1006, it ends the process. On the other hand, if the address book distribution unit 332 determines that the target address book is not set in the device selected in step S1006, it advances the process to step S1003.

In step S1003, similar to the first embodiment, the function display unit 303 displays an icon.

In step S1004, similar to the first embodiment, the function display unit 303 determines whether the cursor is on the icon displayed in step S1003. If the function display unit 303 determines that the cursor is on the icon displayed in step S1003, the process proceeds to step S1005. On the other hand, if the function display unit 303 determines that the cursor is not on the icon displayed in step S1003, the process ends.

In step S1005, as in the first embodiment, the function display unit 303 displays a warning message.

This series of actions makes it possible to display an icon and a warning when distributing an address book to a specified device, if the pre-created address book is not linked to the device.

Here, we will provide further details by referring to the user interface examples shown in Figures 5 to 11.

As in the first embodiment, when distributing an address book, "Task Settings" is selected from the "Tasks" button included in the example user interface shown in FIG. 5, and then "Distribute Address Book" is selected, and an address book distribution task is created.

In step S1201, the address book distribution screen shown in FIG. 7(A) prompts the user to set a schedule and enter "distribution to selected device", and the user enters these. Checking "distribution to selected device" is a check as to whether distribution is to be performed by selecting a device, or by selecting address book data and distributing. Here, it is assumed that the check is selected, meaning that distribution is to be performed by selecting a device. In that case, the target device sheet can be entered.

In step S1202, it is determined that distribution will be performed by selecting a device, and in steps S1209 and S1210, a device list is displayed. "Device1", "Device2", and "Device3" are displayed as device data. Here, it is assumed that an address book has not been linked to "Device2" in advance.

In step S1006, it is assumed that "Device2" is selected, and in step S1007, it is determined whether there is linked data. Here, it is determined that there is no link.

In step S1003, an icon is displayed. An example of this icon is shown in FIG. 7(B). In FIG. 7(B), the icon is displayed at the right end of the "Device2" line.

In step S1004, it is determined whether the cursor is on the icon. Here, it is assumed that the user has moved the cursor over the icon, and this is determined to be the case.

In step S1005, a warning message is displayed. An example of this is shown in FIG. 7B. In FIG. 7B, the message "Address book not set" is displayed below the "Device2" icon.

Then, in step S1211 and steps S1207 to S1208, it is determined whether the Create button has been pressed to save the selection of the device to which the data is to be distributed, the input schedule, the selected address book distribution task, etc., and the save process is executed.

This series of actions makes it possible to display an icon and warning message even when a device is specified for "address book distribution" if the address book is not linked to the device.

Third Embodiment
In the delivery of the address book described in the first embodiment, if a device is not associated with the selected address book, a link to a screen for associating the device may be displayed in addition to an icon and a warning message. This will be described with reference to the flowcharts shown in Fig. 12(C) and Fig. 14(A), and the process will be supplemented with reference to the example of the user interface of the first embodiment, Fig. 8. The processes shown in Figs. 12 to 14 are realized by the CPU 10 executing device management software.

As in the first embodiment, it is assumed that several address books and several devices have been linked in advance.

From the "Task" button shown in Figure 5, select "Task Settings" and then select "Address Book Distribution" to create an address book distribution task.

In the "Address Book Distribution" screen display icon and warning display processing step S1205 shown in FIG. 14(A), this is shown in FIG. 12(C).

In steps S1001 to S1005, the address book distribution unit 332 and the function display unit 303 determine whether a device is linked to the selected address book, as in the first embodiment, display an icon and a warning message, and proceed to step S1008.

In S1008, the function display unit 303 displays a link to the edit screen.

Here, we will provide further details by referring to the user interface examples shown in Figures 5 to 11.

As in the first embodiment, when distributing an address book, "Task Settings" is selected from the "Tasks" button included in the example user interface shown in FIG. 5, and then "Distribute Address Book" is selected to create an address book distribution task.

In step S1201, the address book distribution screen shown in FIG. 6(A) prompts the user to set a schedule and enter "distribution to selected device" information, and the user enters the information. Here, as in the first embodiment, it is assumed that no check marks are selected, meaning that distribution will be performed by selecting the address book.

The address book data is displayed in steps S1202 to S1204, and an icon is displayed in the target device column of "Address Book 2" in steps S1001 to S1005, and the message "No device or device group has been set" is displayed at the bottom.

Then, in step S1008, a message "Go to address book and device combination screen" including a link to the correction screen is displayed. An example of this message is shown in FIG. 8. By pressing this, the user is taken to the previous "Address book and device combination" screen, where they can link the device.

As in the first embodiment, steps S1206 to S1208 select the address book to be distributed, determine whether the Create button has been pressed to save the entered schedule and the selected address book distribution task, and then execute the save process.

This series of operations makes it possible to display an icon and a warning message when the address book and device are not linked during "Address Book Distribution," as well as a link to a screen where the linking can be made to correct the issue.

<Other embodiments>
The present invention may be applied to a system consisting of multiple devices (e.g., a host computer, an interface device, a reader, a printer, etc.) or to an apparatus consisting of a single device (e.g., a copier, a facsimile machine, etc.). The object of the present invention can also be achieved by supplying a recording medium on which program code for realizing the functions of the above-mentioned embodiments is recorded to a system or apparatus, and having a computer in the system or apparatus read and execute the program code stored in the recording medium. In this case, the program code itself read from the recording medium realizes the functions of the above-mentioned embodiments, and the program code itself and the recording medium on which the program code is stored constitute the present invention.

The present invention also includes cases where an operating system (OS) running on a computer executes all or part of the actual processing based on the instructions of the program code, and the functions of the above-mentioned embodiments are realized by this processing. Furthermore, the present invention also applies to cases where program code read from a storage medium is written to memory on a function expansion card inserted into a computer or on a function expansion unit connected to a computer. In such cases, a CPU on the function expansion card or function expansion unit executes all or part of the actual processing based on the instructions of the written program code, and the functions of the above-mentioned embodiments are realized by this processing.

<Other embodiments>
The present invention can also be realized by a process in which a program for implementing one or more of the functions of the above-described embodiments is supplied to a system or device via a network or a recording medium, and one or more processors in a computer of the system or device read and execute the program. The present invention can also be realized by a circuit for implementing one or more of the functions, such as an ASIC (Application Specific Integrated Circuit).

The above describes a preferred embodiment of the present invention. However, the present invention is not limited to the above-described embodiment. In other words, the present invention includes embodiments in which various modifications have been made based on the spirit of the present invention, and these embodiments are not excluded from the scope of the present invention.

101 Device management server 102, 103, 110, 111 Device 105 Directory server 106, 107 Agent

Claims (5)

On the computer,
a first management means for managing device information of one or more network devices to be managed via a network;
a second management means for managing an address book including destinations for data transmission available on the network device;
a distribution means for distributing the address book managed by the second management means to a network device designated based on the device information managed by the first management means;
A means for providing notifications to users;
A program for achieving the above,
The first management means is capable of managing any one or more network devices as a device group,
the providing means provides the notification when a setting for linking a network device or a device group managed by the first managing means to an address book managed by the second managing means has not been executed.
A program characterized by: A processing means for selecting the network device for which an icon and a warning are to be displayed;
a first determination processing means for determining whether data is set in the network device for which the icon and the warning are to be displayed;
a first display processing means for displaying the icon;
a second determination processing means for determining whether or not a cursor is present at the position of the icon;
A second display processing means for displaying a message indicating the warning;
2. The program according to claim 1, further comprising: 3. The program according to claim 1, further comprising a third display processing unit for displaying a link to a correction screen. a first management means for managing device information of one or more network devices to be managed via a network;
a second management means for managing an address book including destinations for data transmission available on the network device;
a distribution means for distributing the address book managed by the second management means to a network device designated based on the device information managed by the first management means;
A means for providing notifications to users;
A management device comprising:
The first management means is capable of managing any one or more network devices as a device group,
the providing means provides the notification when a setting for linking a network device or a device group managed by the first managing means to an address book managed by the second managing means has not been executed.
A management device comprising: A method for controlling a management device, comprising:
managing device information of one or more network devices to be managed via a network, and managing any one or more network devices as a device group;
managing an address book containing destinations for data transmission available on the network device;
delivering the managed address book to a network device designated based on the managed device information ;
providing a notification to a user if a configuration linking a managed network device or device group to a managed address book has not been performed;
23. A method comprising :

Images