System, management device, and method

Abstract

To provide a system, a management device, and a method that, for specific distribution data such as an address book, can urge a user to surely execute linking between the distribution data and network devices or a device group to which the data is distributed.SOLUTION: A program causes a computer to realize first management means that manages device information of one or more network devices to be managed, second management means that manages an address book including addresses for data transmission that can be used by the network devices, distribution means that distributes the address book to a network device designated on the basis of the device information; and providing means that provides a notification to a user. The first management means can manage one or more arbitrary network devices as a device group. The providing means provides the notification when settings to link the network devices or the device group to the address book are not executed.SELECTED DRAWING: Figure 1

Description

[Technical field]

[0001] The present invention relates to a system, a management device and a method. [Background technology]

[0002] Conventionally, there are known device management systems and management devices for acquiring and managing data related to operation information of image forming devices (hereinafter referred to as devices) such as printers and multifunction peripherals. In recent years, there has been an increase in the number of devices that can be managed by one management device, from the viewpoints of an increase in devices to be managed and cost reduction and maintenance related to management servers.

[0003] The device management system and management device can manage address books and the like that contain multiple pieces of destination information such as status, setting values, 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 of the network devices that are the subject of management via the network.

[0004] Furthermore, Patent Document 1 discloses a technology for monitoring whether a network device is configured as intended by an administrator by comparing setting values ​​contained in monitoring data with setting information obtained from the network device being monitored. [Prior art documents] [Patent documents]

[0005] [Patent Document 1] JP 2016-153992 A Summary of the Invention [Problem to be solved by the invention]

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

[0007] For example, in the case of distributing an address book, when adding or editing destination information to be distributed, it may be desirable to hold the already distributed address book on the system side, edit the contents of the address book, and redistribute it, rather than distributing a different address book. This is because, due to restrictions such as memory and functionality of the network device of the distribution destination, it may not be possible to hold multiple address books or to remotely edit an already distributed address book. If a different address book is distributed, in some cases, the distribution itself may fail, which may prevent the intended use of the address book by the user of the distribution destination. Therefore, in the 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 the data is to be distributed should be managed in advance. In addition, such linking should be performed, particularly, when a data distribution task is created.

[0008] Therefore, an object of the present invention is 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 distribution is to be performed. [Means for solving the problem]

[0009] 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 providing means for providing a notification to a user, wherein the first management means is also capable of managing any one or more network devices as a device group, and the providing means provides the notification when a setting has not been performed to link the address book managed by the second management means to a network device or device group managed by the first management means. Effect of the Invention

[0010] According to the present invention, it is possible to encourage specific distribution data, such as an address book, to be linked reliably with a network device or device group to which the data is to be distributed. [Brief description of the drawings]

[0011] [Figure 1] 1 is a block diagram showing an example of a configuration of a device management system according to an embodiment. [Diagram 2] FIG. 2 is a block diagram illustrating an example of a hardware configuration of a device management server according to the embodiment. [Diagram 3] FIG. 2 is a block diagram showing an example of a software module configuration of a device management server according to an embodiment. [Figure 4] FIG. 2 is a block diagram showing an example of a configuration of a device according to an embodiment. [Diagram 5] FIG. 4 is a diagram illustrating an example of a user interface according to the embodiment. [Figure 6]FIG. 4 is a diagram illustrating an example of a user interface according to the embodiment. [Figure 7] FIG. 4 is a diagram illustrating an example of a user interface according to the embodiment. [Figure 8] FIG. 4 is a diagram illustrating an example of a user interface according to the embodiment. [Figure 9] FIG. 4 is a diagram illustrating an example of a user interface according to the embodiment. [Figure 10] FIG. 4 is a diagram illustrating an example of a user interface according to the embodiment. [Figure 11] FIG. 4 is a diagram illustrating an example of a user interface according to the embodiment. [Figure 12] 10 is a flowchart illustrating an example of a process executed by a device management system according to an embodiment. [Figure 13] 10 is a flowchart illustrating an example of a process executed by a device management system according to an embodiment. [Figure 14] 10 is a flowchart illustrating an example of a process executed by a device management system according to an embodiment. [Figure 15] 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. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

[0012] A program according to an embodiment causes a computer to realize a first management means, a second management means, a distribution means, and a providing 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 providing means provides a notification to a user. The first management means is also capable of managing any one or more network devices as a device group. The providing means provides the notification when a setting is not executed to link the address book managed by the second management means with the network device or device group managed by the first management means.

[0013] Furthermore, 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.

[0014] Moreover, the program according to the embodiment further causes the computer to realize a third display processing means for displaying a link to a correction screen.

[0015] A management device according to an 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 in 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 is also capable of managing 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 a device group managed by the first management means to the address book managed by the second management means has not been executed.

[0016] A method according to an embodiment is executed by a first management means, a second management means, a distribution means, and a providing 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 providing means provides a notification to a user when a setting for linking a network device or a device group managed by the first management means to the address book managed by the second management means has not been executed.

[0017] Hereinafter, specific examples of the above-mentioned program, management device, and method will be described with reference to the drawings.

[0018] <System configuration> Fig. 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, an agent 106, an agent 107, a device 102, a device 103, a device 110, and a device 111. The agent 106 and the agent 107 are sometimes referred to as agent applications. Note that, hereinafter, the device management application 101 is referred to as a device management server 1000. Also, hereinafter, the device 102, the device 103, the device 110, and the device 111 are collectively referred to as a device 2000.

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

[0020] The device management server 1000, the agent 106, the device 102, and the device 103 are connected to each other via a network 104. The agent 107, the device 110, and the device 111 are connected to each other via a network 108. The networks 104 and 108 are connected to each other via a router 109. Note that hereinafter, the networks 104 and 108 are collectively referred to as a communication line 3000. The router 109 may be configured to, for example, permit communication between the agent 107 and the device management server 1000, while blocking communication with the devices 110 and 111 on the network 108.

[0021] 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.

[0022] The following description will be given taking 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 for the device 102, etc. The device 102 and the device management server 1000 do not communicate directly, and communication is performed between the device management server 1000 and the agent 106 and between the agent 106 and the device 102.

[0023] 1 illustrates agents 106 and 107, devices 102, 103, 110, and 111, but is not limited to this. For example, even if a dozen agents manage tens of thousands of devices, the configuration and operation are similar to those described in this embodiment.

[0024] Here, the device management server 1000 is a server on which a UI control unit 30, a device control unit 31, a schedule control unit 32, and a function control unit 33 shown in FIG.

[0025] <Hardware configuration of device management server> 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 an HDD (Hard Disk Drive) 19. Each component of the device management server 1000 is connected via a system bus 13.

[0026] 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 is capable of mounting 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.

[0027] <Device management server software configuration> 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 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.

[0028] 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.

[0029] The UI control unit 30 manages the UI control of the device control unit 31, schedule control unit 32, and function control unit 33 by a device display unit 301, a schedule display unit 302, and a function display unit 303, respectively. It is also possible to implement it as a web-based application, in which case it can be used via a web browser.

[0030] The device connection unit 311 has a function of searching for devices, collecting information from devices, and executing settings. An 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.

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

[0032] The schedule management unit 321 cooperates with each function of the function control unit 33 , generates and manages a schedule input from the schedule display unit 302 , and stores the schedule in the schedule storage unit 322 .

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

[0034] 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 store schedule lists, device lists, function information, and the like.

[0035] <Device software configuration> Fig. 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 the device 2000.

[0036] The device 2000 has an information control unit 40 as a software module for managing multiple dynamically changing information groups. 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 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.

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

[0038] <Device discovery and address book distribution flow> Fig. 5 to Fig. 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 delivery will be described with reference to Fig. 5 to Fig. 11.

[0039] 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 or the like, but any method can be used. Figure 5 shows an example of the UI after the search. After the device search is set 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.

[0040] By selecting the "Task" button shown in Figure 5, you can also make settings related to address book distribution. Figure 6 (A) shows an example of the UI that is displayed when the task type "Address Book Distribution" 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 the task.

[0041] Linking an address book with a device can be done 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.

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

[0043] Figures 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 Figures 12 to 14. Each step shown in Figures 12 to 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.

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

[0045] As described above, when managing devices, the device management server 1000 first searches for the devices. This device search may be performed each time, or may be performed periodically according to a set schedule.

[0046] When distributing an address book, as explained above, the "Address book and device combination" in the "Address book" section of the "Data" shown in Figure 5 is displayed, and the address book is linked to the device.

[0047] The process shown in FIG. 13 is performed using the "Address Book and Device Combination" screen.

[0048] In step S1101, the function display unit 303 displays a UI for prompting the selection of 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.

[0049] In step S 1102 , the address book distribution unit 332 acquires existing address book data from the function information storage unit 333 .

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

[0051] In step S1104, the function display unit 303 displays an icon and a warning, which will be described in detail later with reference to FIG.

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

[0053] In step S1106, the function display unit 303 displays a UI for prompting input of the address book and device.

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

[0055] In step S 1108 , the address book distribution unit 332 stores the created address book in the function information storage unit 333 .

[0056] The process shown in FIG. 12A shows an example of detailed processing of step S1104 shown in FIG.

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

[0058] 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 proceeds to step S1003.

[0059] In step S1003, the function display unit 303 displays an icon.

[0060] 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.

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

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

[0063] The process shown in FIG. 14(A) is executed using the "Address Book Distribution" screen.

[0064] In step S1201, the function display unit 303 displays a UI for prompting input as to whether to select a schedule and a device.

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

[0066] In step S 1203 , the address book distribution unit 332 acquires the existing address book data from the function information storage unit 333 .

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

[0068] In step S1205, the function display unit 303 displays an icon and a warning. Details of step S1205 are shown in each step of FIG.

[0069] In step S1206, function display unit 303 selects the address book to be distributed in accordance with the user's instructions.

[0070] 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.

[0071] 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 the process ends.

[0072] In step S 1209 , the address book distribution unit 332 acquires the device information from the device data storage unit 313 via the device data management unit 312 .

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

[0074] In step S1211, the function display unit 303 selects a device to which the content is to be distributed in accordance with a user instruction.

[0075] This series of operations makes it possible to display an icon and a warning when a device is not associated with a previously created address book during delivery of the address book by specifying the address book.

[0076] Here, further details will be provided with reference to the user interface examples shown in FIGS.

[0077] First, for advance association, "Address Book" is selected from the "Data" button in the user interface shown in Figure 5, and "Address Book and Device Combination" is displayed. Figure 11 shows an example of "Address Book and Device Combination."

[0078] In step S1101, it is determined whether or not new creation has been selected, and it is determined here that new creation has not been selected.

[0079] In steps S1102 and S1103, "Address Book 1," "Address Book 2," and "Address Book 3" are displayed as existing address book data.

[0080] In step S1001, it is assumed that "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 device and device group for the target device are 0, that is, there is no link.

[0081] An icon is displayed in step S1003. An example of the icon is shown in Fig. 9B. The icon is displayed in the target device column of "Address Book 2".

[0082] 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 it is determined that the user has moved the cursor over the icon.

[0083] 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 is set" is displayed.

[0084] Also, when the user presses "Create new", it is determined in step S1101 that it is a new creation, and in step S1105, a new creation screen is displayed. An example of this new creation screen is shown in Fig. 10(A). Here, the target address book is edited.

[0085] As in the previous example, it is assumed that this new address book is selected in step S1001, and it is determined in step S1002 whether or not there is a linked device. Here, it is assumed that there is no link with a device, and so it is determined.

[0086] 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.

[0087] 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 it is determined that the user has moved the cursor over the icon.

[0088] 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.

[0089] Through steps S1106 to S1108, the new address book created here, Address Book 4, is saved and thereafter displayed in the address book list as shown in FIG. 9(A).

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

[0091] In step S1201, the user is prompted to set a schedule and enter "distribution to selected device" 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, i.e., distribution is to be performed by selecting address book data.

[0092] 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. As the address book data, "Address Book 1", "Address Book 2", and "Address Book 3" are displayed.

[0093] Thereafter, by performing similar steps from step S1001 to step S1005, an icon is displayed in the target device column of "Address Book 2" and the message "No device or device group is set" is displayed below. An example of this is shown in Figure 6(B).

[0094] In steps S1206 to S1208, the address book to be distributed is selected, and in order to save the input schedule and the selected address book distribution task, it is determined whether the Create button has been pressed, and a save process is performed.

[0095] This series of operations 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.

[0096] <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 setting values ​​desired by the administrator. When the setting monitoring function is enabled, the device management server 1000 needs to hold the setting values ​​desired by the administrator as monitored setting information.

[0097] 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 be the distribution target. 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 be the monitoring target.

[0098] 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 a 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 a device group, as shown in Fig. 15(B).

[0099] Second Embodiment In distributing an address book by specifying a device, if the address book is not linked to 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 examples 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.

[0100] As in the first embodiment, it is assumed that some address books and some devices are linked in advance.

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

[0102] The process shown in FIG. 14(B) is executed using the "Address Book Distribution" screen.

[0103] 14A in the first embodiment, 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.

[0104] 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 process is executed.

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

[0106] 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, the process ends. 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, the process proceeds to step S1003.

[0107] In step S1003, similarly to the first embodiment, the function display unit 303 displays an icon.

[0108] In step S1004, similarly 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.

[0109] In step S1005, similarly to the first embodiment, the function display unit 303 displays a warning message.

[0110] This series of operations makes it possible to display an icon and a warning when an address book is distributed to a specified device and the device is not associated with a previously created address book.

[0111] Here, further details will be provided with reference to the user interface examples shown in FIGS.

[0112] 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.

[0113] In step S1201, the user is prompted to set a schedule and enter "distribution to selected device" on the address book distribution screen shown in Fig. 7(A), and 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, in other words, distribution is to be performed by selecting a device. In that case, the target device sheet can be entered.

[0114] In step S1202, it is determined that distribution is to be performed by selecting a device, and in steps S1209 and S1210, a device list is displayed. "Device 1", "Device 2", and "Device 3" are displayed as device data. Here, it is assumed that an address book has not been linked to "Device 2" in advance.

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

[0116] 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.

[0117] 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 it is determined that the user has moved the cursor over the icon.

[0118] In step S1005, a warning message is displayed. An example of this is shown in Fig. 7(B). In Fig. 7(B), the message "Address book not set" is displayed below the "Device2" icon.

[0119] Thereafter, 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 distribution is to be performed, the input schedule, the selected address book distribution task, and the like, and a save process is executed.

[0120] This series of operations makes it possible to display an icon and a warning message even during device-specific "address book distribution" if the address book and device are not linked.

[0121] <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 an example of the user interface of the first embodiment and Fig. 8. The processes shown in Figs. 12 to 14 are realized by the CPU 10 executing device management software.

[0122] As in the first embodiment, it is assumed that some address books and some devices are linked in advance.

[0123] From the "Task" button shown in FIG. 5, "Task Settings" is selected, and then "Address Book Distribution" is selected to create an address book distribution task.

[0124] In step S1205 for processing icons and warnings displayed on the "Delivery of address book" screen shown in FIG. 14(A), the process is shown in FIG. 12(C).

[0125] 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, and display an icon and a warning message, and the process proceeds to step S1008.

[0126] In S1008, the function display unit 303 displays a link to the correction screen.

[0127] Here, further details will be provided with reference to the user interface examples shown in FIGS.

[0128] 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.

[0129] In step S1201, the user is prompted to set a schedule and enter "distribution to selected device" on the address book distribution screen shown in Fig. 6(A), and enters these. Here, as in the first embodiment, it is assumed that no checks are made, that is, distribution is performed by selecting the address book.

[0130] 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, with the message "No device or device group is set" displayed below.

[0131] Then, in step S1008, a message "To the 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 the user can associate the device.

[0132] As in the first embodiment, in steps S1206 to S1208, an address book to be distributed is selected, and in order to save the input schedule and the selected address book distribution task, it is determined whether the Create button has been pressed, and a save process is executed.

[0133] Through this series of operations, if the address book and device are not linked during "Address Book Distribution", an icon and warning message are displayed, as well as a link to a screen for making the link to correct the error.

[0134] <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 that realizes 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 storage medium. In this case, the program code itself read from the storage medium realizes the functions of the above-mentioned embodiments, and the program code itself and the storage medium on which the program code is stored constitute the present invention.

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

[0136] <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).

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

[0138] 101 Device Management Server 102,103,110,111 devices 105 Directory Server 106,107 Agent

Claims

1. 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:

2. 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. 3. The program according to claim 1, further comprising a third display processing unit for displaying a link to a correction screen.

4. 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:

5. 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; Manage an address book containing destinations for data transmission available on the network device; 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; providing a notification to a user when a setting for linking a network device or a device group managed by the first management means to an address book managed by the second management means has not been executed; A method comprising:

Images