Management apparatus, method of controlling management apparatus, and program

The management device addresses errors in configuration distribution tasks by comparing device models with template models and displaying warnings, ensuring compatible settings are applied, thus improving task creation convenience and accuracy.

JP2024164664APending Publication Date: 2024-11-27CANON KK
View PDF 1 Cites 0 Cited by

Patent Information

Application Number
JP2023080313
Authority / Receiving Office
JP · JP
Patent Type
Applications
Current Assignee / Owner
Filing Date
2023-05-15
Publication Date
2024-11-27

AI Technical Summary

Technical Problem

Existing device management systems face issues when creating configuration distribution tasks, as they may select devices that do not support the settings defined in the template, leading to errors.

Method used

A management device that compares the device model of the selected network devices with the template model during task creation, displaying warnings if they do not match, and allowing users to adjust selections to ensure compatibility.

Benefits of technology

This approach improves the convenience and accuracy of creating setting distribution tasks by preventing unsupported settings from being applied, thereby reducing errors and enhancing user experience.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure 2024164664000001_ABST
    Figure 2024164664000001_ABST
Patent Text Reader

Abstract

To improve the convenience in creating a task to distribute a setting with the utilization of a template.SOLUTION: A management apparatus for distributing a setting to a network device by executing a task comprises a template managing section 341 that manages a template corresponding to a device model of a network device for creating a task, a function control section 33 that creates a task to distribute a setting to the network device using the template, and a function display section 303 that, while creating a task, displays an alert screen based on a result of comparison between a device model corresponding to a template to be used in the task and a device model of a network device to which the setting is to be distributed.SELECTED DRAWING: Figure 10
Need to check novelty before this filing date? Find Prior Art

Description

[Technical field]

[0001] The present invention relates to a technique for managing network devices via a network. [Background technology]

[0002] Conventionally, there is known a device management device for acquiring and managing data such as operation information of image forming devices (hereinafter referred to as devices) such as printers and multifunction devices. The number of devices that can be managed by one management device is increasing due to an increase in the number of devices to be managed and from the viewpoint of cost reduction and maintenance of management servers. In order to continuously manage devices, the management device is capable of managing the status, device settings, firmware, etc., and acquiring and distributing them periodically. Patent Document 1 discloses a mechanism that considers the suitability of a password when distributing setting information to a device. The management device is also capable of creating a template that predetermines the format of acquisition and distribution, and issues an instruction for acquisition and distribution using this template. [Prior art documents] [Patent documents]

[0003] [Patent Document 1] JP 2019-53570 A Summary of the Invention [Problem to be solved by the invention]

[0004] When creating a device setting template in the device management device, the device model is selected. Also, when distributing device settings from the management device to a device, the device is selected. Even when creating a setting distribution task using a setting template in setting distribution, all devices in the device list can be selected as the distribution target, and any setting items in the template that are not supported by the device selected as the distribution target will result in an error.

[0005] An object of the present invention is to improve the convenience of creating a setting distribution task using a template. [Means for solving the problem]

[0006] In order to solve the above problems, the management device of the present invention is a management device that distributes settings to a network device by executing a task, and has: a management means for managing a template corresponding to a device model of the network device for creating a task; a task creation means for creating a task for distributing settings to the network device using the template; and a display means for displaying a warning screen based on a comparison result between the device model corresponding to the template used in the task and the device model of the network device to which the settings are distributed during task creation. Effect of the Invention

[0007] According to the present invention, it is possible to improve the convenience of creating a setting distribution task using a template. [Brief description of the drawings]

[0008] [Figure 1] FIG. 1 illustrates a configuration of a device management system. [Diagram 2] FIG. 2 is a diagram illustrating a hardware configuration of a device management server. [Diagram 3] FIG. 2 is a diagram illustrating a software configuration of a device management server. [Figure 4] FIG. 2 is a diagram illustrating a software configuration of a device. [Diagram 5] FIG. 13 is a diagram illustrating an example of a UI after device discovery. [Figure 6] FIG. 13 illustrates an example of a template selection screen. [Figure 7] FIG. 13 is a diagram illustrating an example of a device model selection screen. [Figure 8] FIG. 13 is a diagram illustrating an example of a selection screen for setting values. [Figure 9]FIG. 13 illustrates an example of a template confirmation screen. [Figure 10] 11 is a flowchart showing a process of creating a setting distribution task in the first embodiment. [Figure 11] 11 is a flowchart showing a process of creating a setting distribution task in the first embodiment. [Figure 12] FIG. 13 illustrates an example of a schedule selection screen. [Figure 13] FIG. 13 illustrates an example of a distribution device selection screen. [Figure 14] FIG. 13 is a diagram showing an example of a warning display. [Figure 15] 13 is a flowchart showing a warning process in the second embodiment. [Figure 16] FIG. 11 is a diagram showing an example of a warning display in the second embodiment. [Figure 17] 13 is a flowchart showing a display process of a distribution device selection screen in the third embodiment. [Figure 18] FIG. 13 is a diagram showing an example of a distribution device selection screen in the third embodiment. [Figure 19] 13 is a flowchart showing a display process of a distribution device selection screen in the fourth embodiment. [Figure 20] FIG. 13 is a diagram showing an example of a distribution device selection screen in the fourth embodiment. [Figure 21] 13 is a flowchart showing a warning process in the fifth embodiment. [Figure 22] FIG. 13 is a diagram showing an example of a warning display in the fifth embodiment. [Figure 23] 23 is a flowchart showing a display process of a distribution device selection screen in the sixth embodiment. [Figure 24] 23 is a flowchart showing a warning process in the sixth embodiment. [Diagram 25] 23A and 23B are diagrams illustrating an example of a distribution device selection screen and a warning screen in the sixth embodiment. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

[0009] (First embodiment) FIG. 1 is a diagram showing the configuration of a device management system. The device management system manages a plurality of network devices to be managed via a network, and provides various services to the network devices. In this embodiment, the network device is an image processing device, but is not limited to this. The network device may be any device capable of communication, and may be, for example, a printer, a multifunction device, an image forming device, a 3D printer, a notebook computer, a smartphone, or a smart home appliance.

[0010] In the device management system, a device management server 1000, which is a management apparatus that manages devices, and a plurality of devices 2000 to be managed are communicatively connected via a communication line 3000. The communication line 3000 may be configured to be capable of transmitting and receiving data, and any communication method may be used. For example, the communication line 3000 may be configured as any one of a LAN, a WAN, a cellular network such as LTE or 5G, a wireless network, a telephone line, a dedicated digital line, or a combination of these.

[0011] The device 2000 is an image processing device capable of network communication. For example, the device 2000 may be an MFP (Multifunction Peripheral) having a printing function and a scanning function, or may be a single-function printer having only a printing function. The device 2000 having a printing function receives print data received via a network, and prints it on actual paper using a known printing technology such as electrophotography or inkjet technology. The device 2000 having a scanning function reads a paper document via a scanner and converts it into image data.

[0012] The device management server 1000 is a management device that provides a device management service that manages a plurality of devices 2000 to be managed. In this embodiment, an example in which the device management service is provided by the device management server 1000 will be described, but the present invention is not limited to this. The device management service may be realized by one or a plurality of information processing devices, a virtual machine (cloud service) that uses resources provided by a data center including the information processing devices, or a combination of these. The device management service provided by the device management server 1000 can also be implemented as a Web-based application, and can also be used via a Web browser on a client terminal such as a PC.

[0013] FIG. 2 is a diagram showing a hardware configuration of the device of the device management server 1000. The device management server 1000 includes a CPU 10, a ROM 11, a RAM 12, a VC 14, a KBC 16, a DKC 18, a HDD 19, a disk drive 20, and a NIC 21. The CPU 10 controls the entire device management server 1000. The ROM 11 is a memory dedicated to reading data, and stores, for example, a basic control program of the device management server 1000. The RAM 12 is a memory capable of reading and writing data, and functions as a work area for the CPU 10. The DKC (disk controller) 18 controls access to a storage device such as the HDD 19. The HDD (Hard Disk Drive) 19 is an example of a storage device, and stores various programs, data, and the like. Note that, in this embodiment, an example will be described in which the information processing device includes an HDD 205 as a storage device, but this is not limited thereto, and other storage devices such as an SSD may be used. The disk drive 20 can be loaded with a storage medium that is an external medium such as a CD-ROM, a DVD, a magnetic tape, or an IC memory card. The CPU 10 uses the RAM 12 as a work area and executes programs stored in the ROM 11 or the HDD 19 to comprehensively control each component connected to the system bus 13 .

[0014] The VC (video controller) 14 is an output interface and controls the display on the display device 15. The display device 15 is a display that displays the output from the device management server 1000 to the user, and is, for example, an LCD (Liquid Crystal Display). The KBC (keyboard controller) 15 is an input interface and controls the input to the device management server 1000 from the operation unit 17. The operation unit 17 is an input device that accepts input from the user, and is, for example, a keyboard or a pointing device. The display device 15 and the operation unit 17 may be realized by an integrated touch panel. By associating input coordinates and display coordinates on the touch panel, it is possible to configure a GUI that makes it seem as if the user can directly operate the screen displayed on the touch panel. The NIC (network interface board) 21 is a communication controller. The device management server 1000 is connected to the communication line 3000 via the NIC 21, and performs data communication with devices on the communication line 3000.

[0015] 3 is a diagram showing the software configuration of the device management server 1000. The device management server 1000 has a UI control unit 30, a device control unit 31, a schedule control unit 32, a function control unit 33, a template control unit 34, and a communication unit 35, which are software modules. The software module configuration is realized by the CPU 10 reading out a program stored in a memory (ROM 11 or HDD 19) into the RAM 12 and executing it.

[0016] The UI control unit 30 has a device display unit 301, a schedule display unit 302, a function display unit 303, and a template display unit 304. The device display unit 301 controls the UI of the device control unit 31, and further accepts user operations on the UI. The schedule display unit 302 controls the UI of the schedule control unit 32, and further accepts user operations on the UI. The function display unit 303 controls the UI of the function control unit 33, and further accepts user operations on the UI. The template display unit 304 controls the UI of the template control unit 34, and further accepts user operations on the UI.

[0017] The device control unit 31 manages information on devices for which the device management service is provided. The device control unit 31 includes a device connection unit 311, a device data management unit 312, and a device data storage unit 313. The device connection unit 311 searches for devices, collects information from devices, and issues setting instructions to devices. An example of the function of the device connection unit 311 is a device search function for the device 2000 using SNMP, 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 / changing device information such as MIB (Management Information Base) security policy information via the communication line 3000. In addition, the device connection unit 311 acquires device information such as a device name, a product name, and an IP address as a result of the device search, and stores the device information in the device data storage unit 313. The device data management unit 312 manages the data in the device data storage unit 313. In addition, the device data management unit 312 manages information on settings (setting items and setting values) that can be reflected for each device or for each device model of the device. The device data storage unit 313 stores device information and the like. The device data storage unit 313 is a data recording medium such as a database that runs on the HDD 19.

[0018] The schedule control unit 32 manages the schedule of the services provided by the device management service. The schedule control unit 32 has a schedule management unit 321 and a schedule storage unit 322. 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. The schedule storage unit 322 stores the schedule generated by the schedule management unit 321. The schedule storage unit 322 is a data recording medium such as a database that runs on the HDD 19.

[0019] The function control unit 33 controls the distribution of settings to the device. The function control unit 33 has a device setting distribution unit 331. The device setting distribution unit 331 controls the distribution of settings to the device based on an input from the function display unit 303 or a schedule specified in a distribution task. The device setting distribution unit 331 also functions as a task creation means that creates a setting distribution task together with the schedule management unit 321 and the function display unit 303 that controls the display. When performing distribution based on an input from the function display unit 303, a template created in advance and stored in the template storage unit 342 is used.

[0020] The template control unit 34 creates and manages templates. The template control unit 34 has a template creation unit 343, a template management unit 341, and a template storage unit 342. The template creation unit 343 creates templates based on a user's instruction. In the device management server 1000, a user can create a template at will and generate a task using the template. The template management unit 341 manages templates and stores them in the template storage unit 342. The template management unit 341 manages templates created by a user and templates prepared by a vendor in order to create a task. The template storage unit 342 is a data recording medium such as a database that runs on the HDD 19. The communication unit 35 controls communication with external devices on the network, such as the device 2000.

[0021] 4 is a diagram showing a software configuration of the device 2000. The configuration of the software modules is realized by the CPU of the device 2000 executing a program stored in the memory. The device 2000 has, as software modules, an information control unit 40 for managing a plurality of dynamically changing information groups, and a communication unit 41. The information control unit 40 has a counter information management unit 401, an MIB information management unit 403, a power information management unit 405, a status information management unit 407, a firmware information management unit 409, and a setting value information management unit 411. In addition, the information control unit 40 has a counter storage unit 402, an MIB information storage unit 404, a power information storage unit 406, a status information storage unit 408, a firmware information storage unit 410, and a setting value information storage unit 412 as storage areas for data corresponding to each management unit.

[0022] A counter information management unit 401 manages the number of printed pages, etc., and stores this in a counter storage unit 402. A MIB information management unit 403 manages the MIB information, which is the above-mentioned device information, and stores this in a 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. A status information management unit 407 manages device status information, such as online, offline, error, etc., and stores this in a status information storage unit 408.

[0023] The firmware information management unit 409 manages information such as the configuration and version of the firmware of the device 2000, and stores it in the firmware information storage unit 410. The firmware information management unit 409 also manages firmware and information distributed for version upgrades, and stores them in the firmware information storage unit 410. The setting value information management unit 411 manages various device-related setting values, such as settings for device printing and network-related settings, and stores them in the setting value information storage unit 412. Data managed by each management unit is transmitted to the device management server 1000 by SNMP or other protocols in response to a request from the device management server 1000. The communication unit 41 controls communication with external devices on the network, such as the device management server 1000. The communication unit 41 may be connected to the communication line 3000 by any method, such as wireless LAN, a network card (LAN card), or a wired cable.

[0024] First, a device search will be described with reference to FIG. 5. FIG. 5 is a diagram showing an example of a UI after device search. A search screen 500 is displayed by selecting a device tab 501 on the device management screen. In addition to the device tab 501, a setting tab 502 and a firmware tab 503 are selectably displayed on the device management screen. The search screen 500 is a UI provided by the UI control unit 30 of the device management server 1000. When managing devices, the device management server 1000 first searches for devices. The device management server 1000 searches for devices to be managed on the network. An algorithm for searching devices is, for example, SNMP, but any search method is acceptable. A device search may be performed at the user's command each time, or may be performed periodically by setting a schedule.

[0025] A search button 504 is displayed on the search screen 500. When the search button 504 is pressed, a search setting screen (not shown) is displayed. The user sets search settings on the search setting screen and issues an instruction to search for devices. On the search setting screen, for example, the network range and search method for searching for devices, IP addresses to be excluded from the search range, etc. can be set. The device management server 1000 searches for devices according to the search settings specified by the user.

[0026] After the device search, a device list 505 showing the search results is displayed on the search screen 500. The device list 505 displays device information of the searched devices. The device information includes, for example, the device name, the product name, the IP address, the serial number, and the like. The device information displayed on the device list 505 includes, for example, the device information of the devices acquired in the current search and the device information acquired in the previous search and stored in the device data storage unit 313. The device data management unit 312 manages the devices displayed on the device list 505, i.e., all managed devices searched for up to now, in the device list.

[0027] In order to manage network devices, the device management server 1000 manages the acquisition of the status of the network devices, distribution of settings to the network devices, firmware updates, etc. In this embodiment, distribution of settings to network devices by the device management server 1000 will be described. As part of device management, the device management server 1000 distributes settings to managed network devices and manages the settings of the network devices. The device management server 1000 distributes settings to the network devices by creating a task for distributing the settings and executing the created task. When distributing settings, a combination of setting items and their setting values ​​is distributed. When creating a task, a template can be used.

[0028] The template for setting distribution will be described. By creating and saving a template of the setting to be distributed, it becomes possible to distribute the same setting easily. This can reduce the effort required for the user to perform the setting and the occurrence of setting errors due to manual setting. The template includes a combination of setting items and their setting values, and information on the device model. The template may be created by the user or may be prepared in advance by the vendor. The template creation unit 343 creates a template for creating a task for distributing the setting according to the user's instruction. Then, the template management unit 341 stores the created template in the template storage unit 342 and manages it to create a task. The template management unit 341 can also change some setting values ​​of the managed template to update the template.

[0029] Here, the creation of a template will be described. FIGS. 6 to 9 show transitions of the template creation screen. FIG. 6 is a diagram showing an example of a template selection screen. When detecting the pressing of the setting tab 502, the function display unit 303 displays a template selection screen 600. A delivery button 601 and a template area 602 are displayed on the template selection screen 600. A create button 603, a display button 604, a delete button 605, and a template list 606 are displayed on the template area 602. When the create button 603 is pressed, the device management server 1000 starts creating a template. FIG. 6(A) shows the template selection screen before the creation of template 3. In the template area 602 of FIG. 6(A), template 1 and template 2 are displayed so as to be selectable. When creating a template, a device model is first selected, and then settings that can be reflected in the selected device model are selected. When detecting the pressing of the create button 603, the UI control unit 30 displays a device model selection screen.

[0030] FIG. 7 is a diagram showing an example of a device model selection screen. Since the setting items and setting values ​​that can be distributed differ depending on the device model, a device model is first specified in creating a template for creating a setting distribution task. In the device model selection screen 700, for example, a list of all device models that can be targets of the device management service provided by the device management server 1000 is displayed in a device model list 701. The device models displayed in the device model list 701 may be limited to device models corresponding to network devices currently managed in the device management server 1000. In addition, in the device model list 701, the device models may be narrowed down by name or network range. In narrowing down the devices using the network range, for example, it is possible to narrow down the devices by specifying an IP address or a network card (LAN card, LAN board) attached to the device 2000. The user selects a device model in the device model list 701 and presses a next button 703. In the example shown in FIG. 7, "MFP1" is selected as the device model. When the UI control unit 30 detects the pressing of the next button 703, it acquires information on the device model selected in the device model list 701 and displays a setting value selection screen. When the back button 702 is pressed on the device model selection screen 700 , the UI control unit 30 displays the template selection screen 600 .

[0031] FIG. 8 is a diagram showing an example of a setting value selection screen. The setting value selection screen 800 is a screen for selecting a template name and a setting, which is a combination of a setting item and a setting value. The setting value selection screen 800 displays a template name 801, a setting item list 802, setting value candidates 803, a back button 804, and a next button 805. The template name 801 specifies the name of the template being created. For example, the name of the template generated by the template management unit 341 is displayed in the template name 801, but the user can also input a name. The setting item list 802 displays a list of setting items that can be set in the selected device model. The setting item list 802 displays setting items that can be distributed to the device 2000 to be managed, such as items related to print settings, items related to scan settings, and items related to security settings. When a setting item is selected in the setting item list 802, setting value candidates corresponding to the selected item are displayed in the setting value candidates 803. The user selects a desired setting value from the setting values ​​displayed in the setting value candidates 803. In addition, in the setting value candidates 803, recommended settings may be displayed so that they can be recognized by the user. In addition, in the setting value candidates 803, setting values ​​that cannot be set for the selected device model may be hidden and only settable values ​​may be displayed, or setting values ​​that cannot be set for the selected device model may be displayed in an unselectable state. In addition, values ​​such as a user name and a password may be input as setting values. In the example shown in FIG. 8, a state in which "Template 3" is selected as the template name, and "On" of "Print Setting 3" is selected as the setting item and setting value is shown. In addition, in the setting value selection screen 800, the user can select multiple setting items and select setting values ​​for each setting item. The user selects the template name and template settings and presses the Next button 805. When the UI control unit 30 detects the pressing of the Next button 805, it acquires the template name and settings selected in the setting value selection screen 800 and displays a template confirmation screen. In addition, when the Back button 804 is pressed, the device model selection screen 700 is displayed.

[0032] FIG. 9 is a diagram showing an example of a template confirmation screen. The template confirmation screen 900 is a screen for confirming the contents of the template to be created. The template confirmation screen 900 displays a template name 901 and a setting 902. The template confirmation screen 900 may also display a device model corresponding to the template selected on the device model selection screen 700. The template name 901 displays the template name specified in the template name 801 on the setting value selection screen 800. The setting 902 displays the setting that is a combination of the setting item and the setting value selected on the setting value selection screen 800. When the UI control unit 30 detects that the template creation button 904 is pressed, the template creation unit 343 creates a template with the contents displayed on the template confirmation screen 900. Then, the template management unit 341 saves the created template in the template storage unit 342. In the example shown in FIG. 9, a template is created with the template name “Template 3”, “Print setting 3” set to “On”, and “Device operation setting 1” set to “On”. When the back button 903 is pressed, the setting value selection screen 800 is displayed.

[0033] Next, the process of creating a task (setting distribution task) for distributing settings to a device will be described. In this embodiment, a template for creating a task is used to create a setting distribution task. FIGS. 10 and 11 are flowcharts showing the process of creating a setting distribution task in the first embodiment. The process of creating a setting distribution task is started, for example, by detecting pressing of the setting button 601. The process of creating a setting distribution task is realized by the CPU 10 of the device management server 1000 executing a program stored in memory (ROM 11 or HDD 19).

[0034] In S1001, the function display unit 303 displays a UI for prompting the user to select a template and accepts the template selection by the user. FIG. 6B shows an example of the UI for prompting the user to select a template, which is displayed in S1001. The template selection screen 600, which is a UI for prompting the user to select a template, is displayed by selecting the setting tab 502. FIG. 6B shows the template selection screen after the template 3 is created. When the distribution button 601 is pressed, the device management server 1000 starts creating a setting distribution task. If a template is selected in the template list 606 by the user when the distribution button 601 is pressed, the device management server 1000 starts creating a setting distribution task based on the selected template. In the example shown in FIG. 6B, the template 3 is selected in the template list 606. If a template is not selected by the user when the distribution button 601 is pressed, it is also possible to create a setting distribution task without using a template, but this will not be described in this embodiment.

[0035] In the template area 602, a create button 603, a display button 604, a delete button 605, and a template list 606 are displayed. When the create button 603 is pressed, the device management server 1000 starts creating a template. When the display button 604 is pressed with a template selected in the template list 606, the device management server 1000 displays the contents of the selected template. When the delete button 605 is pressed with a template selected in the template list 606, the device management server 1000 deletes the selected template from the template storage unit 342. In the template list 606, templates stored in the template storage unit 342 are displayed in a selectable list. In the example shown in FIG. 6B, template 1, template 2, and template 3 are displayed in the template list 606, and template 3 is selected. In S1001, the user selects a template to be used from the displayed template list 606 on the template selection screen 600, and presses the distribute button 601. When the device management server 1000 detects that the user has pressed the distribution button 601 , it acquires information about the template selected in the template list 606 .

[0036] In S1002, the function display unit 303 displays a UI for prompting the user to select whether to perform scheduled delivery or not, and accepts the user's selection of either scheduled delivery or immediate delivery. FIG. 12 shows an example of a UI display for prompting the user to select whether to perform scheduled delivery or not. FIG. 12 shows an example of a schedule selection screen. A schedule selection screen 1200 displayed in S1002 displays immediate delivery and scheduled delivery as selectable. The user selects schedule 1202 for scheduled delivery, and selects immediate 1201 for immediate delivery, and presses a next button 1204. In scheduled delivery, a task is created specifying the date and time to deliver firmware, so that firmware can be updated at a time when the device is not in use, such as outside business hours. When the next button 1204 is pressed, the device management server 1000 performs the process of S1003. When the back button 1203 is pressed, the device management server 1000 returns to the process of S1001 and displays the template selection screen 600.

[0037] In S1003, the function display unit 303 displays a UI to prompt the user to select a device (distribution device) to which the settings are to be distributed. The function display unit 303 displays a list of devices to be selected on a screen (distribution device selection screen) for allowing the user to select a device to which the settings are to be distributed. The function display unit 303 may display all devices found in the device list, or may determine the devices to be displayed according to the template selected in S1001. In this embodiment, an example in which all devices found in the search, that is, all devices to be managed, are displayed will be described. Details of the process of S1003 in the first embodiment will be described with reference to FIG. 11(A).

[0038] FIG. 11A is a flowchart showing a display process of a distribution device selection screen in the first embodiment. In S701, the function display unit 303 performs a process of displaying all devices already searched for, that is, all devices in the device list, on the distribution device selection screen. An example of the distribution device selection screen is shown in FIG. 13. FIG. 13 is a diagram showing an example of the distribution device selection screen. A device list 1301, a back button 1302, and a next button 1303 are displayed on the distribution device selection screen 1300. The device list 1301 displays a list of candidates of devices to which settings are to be distributed so that they can be selected. In the first embodiment, all devices that have been searched for, that is, all devices to be managed, are displayed on the device list 1301. In the example shown in FIG. 13, "Device1" whose product name (device model) is "MFP4", "Device2" whose product name is "MFP4", and "Device3" whose product name is "SFP2" are displayed on the device list 1301. The user selects a distribution device to which settings are to be distributed from the devices displayed on the device list 1301. When a next button 1303 is pressed with a device selected in the device list 1301, the device management server 1000 performs the process of S1004. When a back button 1302 is pressed, the device management server 1000 returns to the process of S1002 and displays the schedule selection screen (FIG. 12).

[0039] In S1004, the function display unit 303 and the device setting distribution unit 331 determine whether or not to issue a warning based on the distribution device, and perform processing to display the warning if it is determined that a warning should be issued. The function display unit 303 compares the device model of the template with the device model of the selected distribution device, and displays a warning screen based on the comparison result. The comparison here is whether or not the device model of the template is the same as the device model of the selected distribution device. Details of the processing of S1004 in the first embodiment will be described with reference to FIG. 11(B). FIG. 11(B) is a flowchart showing the warning processing in the first embodiment. In S1111, the function display unit 303 acquires information on the distribution device selected in the device list 1301 of the distribution device selection screen 1300. In the example shown in FIG. 13, "Device2" with the product name "MFP4" is selected.

[0040] In S1112, the device setting distribution unit 331 determines whether the device model of the template selected in S1001 is the same as the distribution device. The device model corresponds to the product name (model name). For example, the template 3 selected in S1001 is created with the device model "MFP1", but the product name of the distribution device selected in S1003 is "MFP4", and the device setting distribution unit 331 determines that the device models are not the same. If the device model of the template is the same as the distribution device, the process returns to the flowchart of FIG. 10 and performs the process of S1005. That is, if the device model of the template is the same as the distribution device, no warning display is performed. On the other hand, if the device model of the template is not the same as the distribution device, the process of S1113 is performed. In S1113, the function display unit 303 displays a warning. This process makes it possible to display a warning when the device model of the template is different from the distribution device, and the user can notice that the device model of the template is different from the distribution device by the warning during task creation, immediately after selecting the distribution device. If necessary, immediately after selecting a distribution device, it is possible to go back and reselect a template or distribution device.

[0041] An example of a warning display will be described with reference to FIG. 14. FIG. 14 is a diagram showing an example of a warning display. A warning display screen 1400 displays a message display area 1401, a back button 1402, and an OK button 1403. For example, the message display area 1401 displays a message indicating that the template device and the distribution device are different. Furthermore, a message indicating that the setting value may not be reflected due to the difference in device model may be displayed. The warning display screen 1400 may be a pop-up superimposed on the distribution device selection screen 1300, or may be a screen displayed next to the distribution device selection screen 1300. When the back button 1402 is pressed, the device management server 1000 returns to the process of S1003 and displays the distribution device selection screen 1300. On the other hand, when the OK button 1403 is pressed, the device management server 1000 performs the process of S1005.

[0042] If the device models of the template and the distribution device are the same, or if the user who received the warning display indicating that the device models of the template and the distribution device are different selects to proceed with the process, the process of S1005 is performed. In S1005, the device setting distribution unit 331 determines whether the distribution setting set in S1002 is scheduled distribution. If it is scheduled distribution, the processes of S1007 and S1008 are performed. On the other hand, if it is not scheduled distribution, that is, if it is immediate distribution, the process of S1006 is performed.

[0043] First, the process when immediate distribution is selected will be described. In S1006, the device setting distribution unit 331 performs a process of immediately distributing the setting values ​​based on the template selected in S1001 to the device selected in S1003. When the device models of the template and the distribution device are the same, the device setting distribution unit 331 distributes the setting values ​​of all the setting items set in the template. On the other hand, when the device models of the template and the distribution device are different, the device setting distribution unit 331 distributes only the setting values ​​of the setting items supported by the distribution device among the setting items set in the template. For example, suppose that Template 3 is selected in S1001, and the settings according to Template 3 are “Print Setting 3” “On” and “Device Operation Setting 1” “On”. Suppose that Device 2 having a product name (device model) of MFP4 is selected as the distribution device in S1004, and that MFP4 supports “Print Setting 3” but does not support “Device Operation Setting 1”. In this case, a setting for setting “Print Setting 3” supported by MFP4 to “On” is distributed to Device 2. Note that a distribution confirmation screen for confirming the distribution contents may be displayed between S1005 and S1006, and the device setting distribution unit 331 may perform distribution only if the user instructs distribution on the distribution confirmation screen. Also, even in the case of immediate distribution, a task of a schedule to be executed immediately may be created and saved, and the device setting distribution unit 331 may distribute the settings based on the task.

[0044] Next, a process when schedule distribution is selected will be described. In S1007, the function display unit 303 accepts the setting of the date and time for distributing firmware. Specifically, the function display unit 303 displays a UI for prompting the user to input the date and time of schedule distribution, and accepts the input of the distribution date and time by the user. In S1008, the schedule management unit 321 creates and saves a task for setting value distribution. The schedule management unit 321 creates a distribution task based on the template selected in S1001, the distribution device selected in S1004, and the date and time input in S1006. Then, the schedule management unit 321 saves the created distribution task in the schedule storage unit 322. The distribution task includes the distribution device, the settings (combination of setting items and their setting values) set using the template, and the distribution date and time. Since the template settings are saved in the distribution task, if the device model targeted by the template is different from the device model of the distribution device, there is a possibility that the distribution task will include settings that are not supported by the distribution device via a warning screen. In other words, only when the user confirms the warning screen and agrees, the distribution task can include settings that are not supported by the distribution device. The distribution task may also include information about the template used to create the task. In the case of distribution processing based on the distribution task, as in the case of immediate distribution, only the template settings supported by the distribution device are distributed, and unsupported settings are not distributed. Note that, between S1007 and S1008, a distribution confirmation screen for confirming the contents of the distribution task may be displayed, and the schedule management unit 321 may perform processing to save the task only when the user instructs distribution on the distribution confirmation screen.

[0045] As described above, according to this embodiment, if the device model of the template and the distribution device are different, the user can be aware of this in advance by a warning. Therefore, if necessary, it is possible to go back and reselect the template and distribution device. This makes it possible to improve the convenience of creating a setting distribution task using a template.

[0046] Second embodiment In the first embodiment, even if the device model of the template and the distribution device are different, it is possible to create an immediate distribution and a distribution task in which the device model of the template and the distribution device are different after confirming a warning screen. In the second embodiment, when the device model of the template and the distribution device are different, immediate distribution and saving of the distribution task are not possible. For this reason, in this embodiment, when the device model of the template and the distribution device are different, reselection of the distribution device or reselection of the template is prompted, and transition to the next screen is not possible until the device model of the template and the distribution device are the same.

[0047] The setting distribution task creation process in the second embodiment will be described with reference to Fig. 10, Fig. 11(A), and Fig. 15. The flow of the setting distribution task creation process in this embodiment is the same as that in the first embodiment, except for the details of the process of S1004. Only the differences from the first embodiment will be described below, and the same configurations and processes as those in the first embodiment will be denoted by the same reference numerals and will not be described again. The setting distribution task creation process is realized by the CPU 10 of the device management server 1000 executing a program stored in memory (ROM 11 or HDD 19).

[0048] S1001 to S1003 in the second embodiment are the same as those in the first embodiment. In S1003, the process shown in Fig. 11(A) is performed. In S1004, the function display unit 303 and the device setting distribution unit 331 determine whether or not to issue a warning based on the distribution device, and perform a process to display the warning if it is determined that a warning should be issued. Furthermore, if a warning is to be displayed, that is, if the device model of the template and the distribution device are not the same, the device setting distribution unit 331 does not allow the process to proceed to S1005.

[0049] The details of the process of S1004 in the second embodiment will be described with reference to Fig. 15. Fig. 15 is a flowchart showing the warning process in the second embodiment. In S1501, the function display unit 303 acquires information on a distributing device selected in the device list 1301 of the distributing device selection screen 1300. In the example shown in Fig. 13, "Device2" with the product name "MFP4" is selected as the distributing device.

[0050] In S1502, the device setting distribution unit 331 determines whether the device model of the template selected in S1001 is the same as the distribution device. The device model corresponds to the product name. For example, the template 3 selected in S1001 is created with the device model "MFP1", but the product name of the distribution device selected in S1003 is "MFP4", and the device setting distribution unit 331 determines that the device models are not the same. If the device model of the template is the same as the distribution device, the process returns to the flowchart of FIG. 10 and the process of S1005 is performed. In other words, if the device model of the template is the same as the distribution device, no warning is displayed. On the other hand, if the device model of the template is not the same as the distribution device, the process of S1503 is performed.

[0051] In S1503, the function display unit 303 displays a warning. This process makes it possible to display a warning when the device model of a template created in advance is different from the distribution device, and the user can be made aware of the fact that the device model of the template is different from the distribution device before creating a task by the warning. Then, if necessary, it becomes possible to go back and reselect the template or distribution device.

[0052] An example of a warning display in the second embodiment will be described with reference to FIG. 16. FIG. 16 is a diagram showing an example of a warning display in the second embodiment. A message display area 1601 and a back button 1602 are displayed on the warning display screen 1600. The message display area 1601 displays a message that the template device and the delivery device are different, and further displays a message prompting the user to change the template or the delivery device. The warning display screen 1600 may be a pop-up superimposed on the delivery device selection screen 1300, or may be a screen displayed next to the delivery device selection screen 1300. When the back button 1602 is pressed, the device management server 1000 returns to the process of S1003 and displays the delivery device selection screen 1300. Note that instead of the back button 1432 for returning to the delivery device selection screen 1300, a button for returning to the template selection screen 600 to change the template may be displayed. Also, both a back button and a button for returning to the template selection screen 600 may be displayed on the delivery device selection screen 1300. The warning display screen 1600 does not display a button for proceeding with the process, for example, a button corresponding to the OK button 1403 of the warning display screen 1400 in the first embodiment. That is, the warning display screen 1600 does not display a button (button other than the back button) for transitioning to a screen other than the delivery device selection screen 1300 or the template selection screen 600. By preventing the user from proceeding as long as the warning display screen 1600 is displayed, the second embodiment is configured such that a delivery task cannot be created or immediate delivery cannot be executed when the device model of the template and the delivery device are different.

[0053] Due to the process of S1004 in the second embodiment, the processes from S1005 onwards are executed only when the device model of the template and the distribution device match. In distributing device settings in this embodiment, if the device model of a template created in advance differs from the distribution device, a warning is displayed and distribution is not permitted, and the settings can be distributed only when the device model of the template and the distribution device match.

[0054] As described above, according to this embodiment, if the device model of the template and the distribution device are different, a warning is displayed. On the displayed warning screen, only a button for returning to the screen for changing the template or distribution device is displayed as a button for screen transition, so that if the device model of the template and the distribution device are different, saving of the task is not possible. This makes it possible to save the distribution task only when the device model of the template and the distribution device are the same, and it is possible to prevent the creation of a distribution task including settings that cannot be distributed.

[0055] Third embodiment In the first embodiment, when selecting a distribution device, all managed devices are displayed as selection candidates for the distribution device. However, the selection candidates for the distribution device include devices that do not match the device model of the selected template. Therefore, in the present embodiment, it is possible to display only devices that are the same as the device model of the selected template as selection candidates for the distribution device, making it easier to select a distribution device that matches the device model of the template.

[0056] The setting distribution task creation process in the third embodiment will be described with reference to Fig. 10 and Fig. 17. The flow of the setting distribution task creation process in this embodiment is the same as that in the first embodiment, except for the details of the process of S1003. Only the differences from the first embodiment will be described below, and the same configurations and processes as those in the first embodiment will be denoted by the same reference numerals and will not be described again. The setting distribution task creation process is realized by the CPU 10 of the device management server 1000 executing a program stored in memory (ROM 11 or HDD 19).

[0057] S1001 and S1002 in the third embodiment are the same as those in the first embodiment. In S1003, the process shown in FIG. 17 is performed. FIG. 17 is a flowchart showing the display process of the delivery device selection screen in the third embodiment. In S1701, the function display unit 303 displays the delivery device selection screen including the selection of the same device model display. FIG. 18 is a diagram showing an example of the delivery device selection screen in the third embodiment. In the delivery device selection screen 1800 displayed in the third embodiment, it is possible to select whether the devices to be displayed in the device list 1802 are all devices that have been searched or the same devices as the device model of the template. In the example shown in FIG. 18, a check box 1801 for displaying the same devices as the device model of the template is displayed, and when the check box 1801 is selected, the same devices as the device model of the template are displayed in the device list 1802. For example, when the template selected in S1001 is template 3 and the device model corresponding to template 3 is MFP1, only Device 1, which is MFP1, is displayed in the device list 1802 among Devices 1 to 3. On the other hand, when the check box 1801 is not selected, all the devices that have been searched are displayed in the device list 1802. The display of the device list 1802 when all the devices that have been searched are displayed is similar to the device list 1301 shown in FIG. 13. Note that, as long as the user can switch the devices to be displayed in the device list 1802 between all devices and devices that match the device model of the template, the display method is not important. The back button 1803 and the next button 1804 of the distribution device selection screen 1800 have the same functions as the back button 1302 and the next button 1303 of the distribution device selection screen 1300. Note that the device list 1802 of the distribution device selection screen 1800 displayed in S1701 may be displayed with the check box 1801 selected or may be displayed with the check box 1801 not selected.

[0058] In S1702, function display unit 303 determines whether or not the display of the same device as the template model is selected. Function display unit 303 determines whether or not the display of the same device as the template model is selected based on whether or not check box 1801 is selected. If check box 1801 is selected, that is, if the display of the same device as the template model is selected, the process of S1704 is performed. On the other hand, if check box 1801 is not selected, that is, if the display of the same device as the template model is not selected, the process of S1703 is performed.

[0059] In S1703, the function display unit 303 performs processing to display all devices that have already been searched on the delivery device selection screen 1800. In S1704, the function display unit 303 displays only devices that are the same as the device model of the template on the delivery device selection screen 1800. The function display unit 303 compares the device model of the template with devices in a device list that lists all the searched devices, and displays the same devices in the device list 1802. For example, when the devices in the device list are Devices 1 to 3, only Device 1, which is the same MFP1 as the device model of the template, is displayed.

[0060] When the check box 1801 is selected in S1701 to select the same device model display, the function display unit 303 displays only devices that match the device model of the template in the device list 1802. When a distribution device is selected from among the devices that match the device model of the displayed template, no warning is displayed in the process of S1004, and the process of immediate distribution or schedule task creation can proceed. The process of S1004 in the third embodiment may be the same as that of the first embodiment (FIG. 11(B)) or that of the second embodiment (FIG. 15). The process of S1005 and subsequent steps in the third embodiment is the same as that of the first embodiment. In the present embodiment, an example has been described in which only devices that match the device model of the template are displayed as distribution device selection targets, and different devices are not displayed, but the present invention is not limited to this. For example, devices that are different from the device model of the template may be displayed in a non-selectable state on the device selection screen. That is, it is sufficient that only devices that match the device model of the template are displayed in a selectable state on the device selection screen. In addition, in the present embodiment, an example has been described in which the user can switch the display of selectable devices in the device list 1802 by selecting the check box 1801, but the present invention is not limited to this. For example, the check box 1801 may not be displayed on the distribution device selection screen 1800, and when a template is selected, the function display unit 303 may display only devices that are the same as the template model.

[0061] As described above, according to this embodiment, in the display of distribution devices, only devices that have the same device model as the template are displayed, and a device that has the same device model as the template can be selected. This makes it possible to distribute settings based on the template to devices that support the settings of the template.

[0062] (Fourth embodiment) In the first and second embodiments, all managed devices are displayed on the distribution device selection screen. In the third embodiment, the distribution device selection screen is configured to be able to switch between displaying all managed devices and displaying only devices that have the same device model as the template. In the fourth embodiment, an example will be described in which devices that have the same device model as the template and devices that are different are displayed in a distinguishable manner on the distribution device selection screen.

[0063] The setting distribution task creation process in the fourth embodiment will be described with reference to Fig. 10 and Fig. 19. The flow of the setting distribution task creation process in this embodiment is the same as that in the first embodiment, except for the details of the process of S1003. Only the differences from the first embodiment will be described below, and the same configurations and processes as those in the first embodiment will be denoted by the same reference numerals and will not be described again. The setting distribution task creation process is realized by the CPU 10 of the device management server 1000 executing a program stored in memory (ROM 11 or HDD 19).

[0064] S1001 and S1002 in the fourth embodiment are the same as those in the first embodiment. In S1003, the process shown in Fig. 19 is performed. Fig. 19 is a flowchart showing the display process of the delivery device selection screen in the fourth embodiment. In S1701, the function display unit 303 displays the delivery device selection screen that displays devices that are the same as the device model of the template and devices that are different from the device model of the template. Fig. 20 shows an example of the delivery device selection screen that displays devices that are different from the device model of the template so that the user can distinguish between the same device and devices that are different from the device model of the template.

[0065] FIG. 20 is a diagram showing an example of a delivery device selection screen in the fourth embodiment. A delivery device selection screen 2010 is provided with a same device display area 2001, which is a first area, and a different device display area 2002, which is a second area. The function display unit 303 compares the template model with the devices in the device list, and displays the same devices as the device model of the template in the same device display area 2001. On the other hand, the function display unit 303 compares the template model with the devices in the device list, and displays the devices different from the device model of the template in the different device display area 2002. That is, the function display unit 303 displays the devices that are not displayed in the same device display area 2001 among all the devices in the device list in the different device display area 2002. For example, when the device model of the template is MFP1, "Device1" with the device model "MFP1" is displayed in the same device display area 2001. On the other hand, "Device2" with "MFP4" and "Device3" with "SFP2" are displayed in the different device display area 2002. It should be noted that a back button 2003 and a next button 2004 on the distribution device selection screen 2010 have the same functions as the back button 1302 and the next button 1303 on the distribution device selection screen 1300 .

[0066] The process of S1004 in the fourth embodiment may be the same as that in the first embodiment (FIG. 11(B)) or the second embodiment (FIG. 15). The process of S1005 and subsequent steps in the fourth embodiment are the same as those in the first embodiment.

[0067] In displaying delivery devices, it is possible to distinguish between "Device1", which is the same device as the device model of the template, and "Device2" and "Device3", which are different devices. This allows the user to select a delivery device after recognizing the differences and similarities with the device model of the template. According to this embodiment, in displaying delivery devices, it is possible to display in separate areas devices that are the same as the device model of the template and devices that are different. This allows the user to select a device after recognizing the differences and similarities with the device model of the template.

[0068] Fifth embodiment In the first and second embodiments, the warning display only indicates that the distribution device is different from the device model of the template. With only this display content, the user cannot confirm what settings are not reflected due to the difference in device. Therefore, in this embodiment, the warning display indicates unsupported settings in addition to the difference in device.

[0069] The setting distribution task creation process in the fifth embodiment will be described with reference to Fig. 10 and Fig. 21. The flow of the setting distribution task creation process in this embodiment is the same as that in the first embodiment, except for the details of the process of S1004. Only the differences from the first embodiment will be described below, and the same configurations and processes as those in the first embodiment will be denoted by the same reference numerals and will not be described again. The setting distribution task creation process is realized by the CPU 10 of the device management server 1000 executing a program stored in memory (ROM 11 or HDD 19).

[0070] S1001 to S1003 in the fifth embodiment are the same as those in the first embodiment. In S1003, the process shown in FIG. 11(A) is performed. Note that, for S1003, the same process as in the third and fourth embodiments may be performed. In S1004, the function display unit 303 and the device setting distribution unit 331 determine whether or not to issue a warning based on the device model of the template and the distribution device, and perform a process of displaying the warning if it is determined that a warning should be issued. In this embodiment, when a warning is displayed in S1004, the template settings that are not reflected in the distribution device because the device model of the template and the distribution device are different are also displayed.

[0071] Details of the process of S1004 in the fifth embodiment will be described with reference to Fig. 21. Fig. 21 is a flowchart showing warning processing in the fifth embodiment. In S2101, the function display unit 303 acquires information on a distributing device selected in the device list 1301 of the distributing device selection screen 1300. In the example shown in Fig. 13, "Device2" with the product name "MFP4" is selected as the distributing device.

[0072] In S2102, the device setting distribution unit 331 determines whether the device model of the template selected in S1001 is the same as the distributing device. The device model corresponds to the product name, and the device setting distribution unit 331 compares the device model of the template with the product name of the distributing device. For example, the template 3 selected in S1001 is created with "MFP1" as the device model, but the product name of the distributing device selected in S1003 is "MFP4", and the device setting distribution unit 331 determines that the device models are not the same. If the device model of the template is the same as the distributing device, the process returns to the flowchart of FIG. 10 and the process of S1005 is performed. In other words, if the device model of the template is the same as the distributing device, no warning is displayed. On the other hand, if the device model of the template is not the same as the distributing device, the process of S2104 is performed.

[0073] In S2104, the function display unit 303 displays a warning. This process makes it possible to display a warning when the device model of a template created in advance is different from the distribution device, and the user can be made aware of the fact that the device model of the template is different from the distribution device before creating a task by the warning. Then, if necessary, it becomes possible to go back and reselect the template or distribution device.

[0074] An example of a warning display in the fifth embodiment will be described with reference to FIG. 22. FIG. 22 is a diagram showing an example of a warning display in the fifth embodiment. A warning display screen 2200 displays a message display area 2201, an unsupported setting list 2202, a back button 2203, and an OK button 2204. The message display area 2201 displays a message that the device of the template and the distribution device are different. The unsupported setting list 2202 displays settings (setting items and their setting values) of the template that are not supported by the distribution device and therefore will not be distributed, that is, settings that will not be reflected in the distribution device. The settings that will not be distributed can be specified by comparing the settings that can be reflected in the device managed by the device data management unit 312 with the settings of the template. For example, assume that template 3 is selected as the template and “Device 2” is selected as the distribution device. Template 3 is created using “MFP1” as the device model, and has settings of “Print Settings 3” and “Device Operation Settings 1”. The product name of “Device2” is “MFP4”, and it supports “Print Setting 3”, but does not support “Device Operation Setting 1”. In this case, the unsupported setting list 2202 displays the setting item “Device Operation Setting 1” and its setting value “ON”. By checking the unsupported setting list 2202, the user can check the settings of the template that cannot be reflected in the distribution device immediately after selecting the distribution device. In the present embodiment, an example in which only the settings that are not reflected in the distribution device are displayed has been described, but this is not limited thereto. In addition to the list of settings that are not reflected, a list of settings that are reflected in the distribution device may also be displayed. When the back button 2203 is pressed, the device management server 1000 returns to the process of S1003 and displays the distribution device selection screen 1300. On the other hand, when the OK button 2204 is pressed, the device management server 1000 performs the process of S1005. The process from S1005 onwards is the same as that in the first embodiment.

[0075] According to this embodiment, when the device model of the template created in advance is different from the device to which the template is to be distributed, it is possible to display the settings that the device does not support in addition to the warning. This allows the user to check whether the desired settings will be distributed before creating or distributing a task, and if necessary, to go back and reselect the template or distribution device.

[0076] Sixth embodiment In the sixth embodiment, when multiple devices are selected as distribution devices, a process of distributing only the common settings of those devices will be described. The process of creating a setting distribution task in the sixth embodiment will be described with reference to Figs. 10, 23, and 24. Only the differences from the first embodiment will be described below, and the same configurations and processes as those in the first embodiment will be denoted by the same reference numerals and will not be described again. The process of creating a setting distribution task is realized by the CPU 10 of the device management server 1000 executing a program stored in memory (ROM 11 or HDD 19).

[0077] S1001 to S1002 in the sixth embodiment are the same as those in the first embodiment. In S1003, the process shown in Fig. 23 is performed. In S1003, the function display unit 303 displays a UI for prompting the selection of a device (distribution device) to which the setting is to be distributed. Details of the process of S1003 in this embodiment will be described with reference to Fig. 23.

[0078] FIG. 23 is a flowchart showing a display process of a distribution device selection screen in the sixth embodiment. In S2301, the function display unit 303 displays a distribution device selection screen including a selection of displaying the same device model. FIG. 25(A) is a diagram showing an example of a distribution device selection screen in the sixth embodiment. A check box 2501 for common setting distribution, a device list 2502, a back button 2503, and a next button 2504 are displayed on a distribution device selection screen 2500 displayed in the sixth embodiment. The check box 2501 for common setting distribution is a check box for selecting whether or not to distribute only common settings when multiple devices are selected as distribution devices. The device list 2502 displays all devices that have been searched. The user can select one or more devices in the device list 2502. In the example shown in FIG. 25(A), "Device1" with a product name of "MFP1" and "Device2" with a product name of "MFP4" are selected as distribution devices, and the check box 2501 for common setting distribution is selected. In this case, only settings common to "Device1" and "Device2" are to be distributed. Note that a back button 2503 and a next button 2504 on the distribution device selection screen 2500 have the same functions as the back button 1302 and the next button 1303 on the distribution device selection screen 1300. When the next button 2504 is pressed, the device management server 1000 performs the process of S1004.

[0079] Details of the process of S1004 in this embodiment will be described with reference to Fig. 24. Fig. 24 is a flowchart showing warning processing in the sixth embodiment. In S2401, the function display unit 303 acquires information on a distribution device selected in the device list 2502 of the distribution device selection screen 2500. In the example shown in Fig. 25(A), "Device1" with the product name "MFP1" and "Device2" with the product name "MFP4" are selected as distribution devices.

[0080] In S2402, the device setting distribution unit 331 determines whether or not a plurality of devices are selected as distribution devices. If a plurality of devices are selected as distribution devices, the device setting distribution unit 331 performs processing of S2403. On the other hand, if a plurality of devices are not selected as distribution devices, the device setting distribution unit 331 performs processing of S2404.

[0081] In S2403, the device setting distribution unit 331 determines whether or not a setting is made to distribute only the common settings when multiple devices are selected. Specifically, the device setting distribution unit 331 determines that a setting is made to distribute only the common settings when the check box 2501 for distributing common settings on the distribution device selection screen 2500 is checked. If it is determined that a setting is made to distribute only the common settings, the device setting distribution unit 331 performs processing of S2406. On the other hand, if it is determined that a setting is not made to distribute only the common settings, the device setting distribution unit 331 performs processing of S2404.

[0082] In S2404, the device setting distribution unit 331 judges whether the device model of the template selected in S1001 is the same as the distribution device. The process of S2404 is the same as the process of S1502 in the first embodiment. If there are multiple distribution devices, it is judged whether each distribution device is the same as the device model of the template. If all distribution devices are the same as the device model of the template, no warning is displayed and the process of S1005 is performed. On the other hand, if there is a distribution device different from the device model of the template, the process of S2405 is performed. In S2405, the function display unit 303 displays a warning. The process of S2405 is the same as the process of S1503 in the first embodiment. In S2405, a distribution device different from the device model of the template may be specified and information that can identify the device may be displayed. In addition, settings that are not distributed may also be displayed.

[0083] When multiple devices are selected as distribution devices and only the settings common to the multiple distribution devices are selected to be distributed, the device management server 1000 performs the process of S2406. In S2406, the function display unit 303 displays a warning that only the common settings will be distributed. An example of the warning displayed in S2406 is shown in FIG. 25B. FIG. 25B is a diagram showing an example of the warning display in the sixth embodiment. For example, a common settings list 2511, a back button 2512, and an OK button 2513 are displayed on the warning display screen 2510. The common settings list 2511 displays common settings (setting items and setting values) to be distributed to all of the multiple devices selected as distribution devices. That is, among the settings of the template, settings supported by all the specified distribution devices are displayed as common settings in the common settings list 2511. For example, the setting items of template 3 are "print settings 3" and "device operation settings 1" as shown in FIG. 9. "Device 1" supports "print settings 3" and "device operation settings 1". On the other hand, "Device2" supports "Print Setting 3" but does not support "Device Operation Setting 1". Therefore, among the settings of template 3, the common setting of "Device1" and "Device2" selected as the delivery device is "Print Setting 3", and when only the common setting is delivered, only the setting of "Print Setting 3" is delivered. In this case, the common setting list 2511 displays the setting item "Print Setting 3" which is a common setting and its setting value "ON". If there is no common setting, the setting may not be displayed in the common setting list 2511, or a message indicating that there is no common setting may be displayed instead of the common setting list 2511. In addition, in the present embodiment, an example in which only the common setting to be delivered is displayed has been described, but this is not limited thereto. For example, among the settings of the template, settings that are not delivered may also be displayed together. If the back button 2512 is pressed, the function display unit 303 returns to S1003 and displays the delivery device selection screen 2500, which is the previous screen. If the OK button 2513 is pressed, the process of S2407 is performed.

[0084] In S2407, the device setting distribution unit 331 determines to distribute only the common settings to the distribution devices, and returns to the process of S1005. For example, when the distribution devices are "Device1" and "Device2", the device setting distribution unit 331 determines to distribute the common setting, the setting item "Print Setting 3", and its setting value "On". When the process of S2407 is completed, the process returns to the process of S1005.

[0085] S1005 to S1008 are the same as in the first embodiment. In S1005, the device setting distribution unit 331 judges whether the distribution setting set in S1002 is scheduled distribution. If it is scheduled distribution, the processes of S1007 and S1008 are performed. On the other hand, if it is not scheduled distribution, that is, if it is immediate distribution, the process of S1006 is performed.

[0086] In S1006, the device setting distribution unit 331 performs a process of immediately distributing the setting value based on the template selected in S1001 to the device selected in S1003. When multiple devices are selected as distribution devices on the distribution device selection screen 2500 and the user has specified that only the common settings be distributed, the device setting distribution unit 331 determines in S2407 to distribute only the common settings to the distribution devices. When the device setting distribution unit 331 has determined that only the common settings be distributed to the distribution devices, the device setting distribution unit 331 distributes only the common settings to the multiple distribution devices based on the template. For example, when distributing only the common settings to the distribution devices, the device setting distribution unit 331 immediately distributes the setting item "Print Setting 3" which is a common setting to "Device1" and "Device2" and its setting value "On". On the other hand, when multiple devices are selected as distribution devices on the distribution device selection screen 2500 and the user has not specified that only the common settings be distributed, the device setting distribution unit 331 distributes to each distribution device based on the template. In other words, if it has not been decided to distribute only the common settings to the distribution devices, the device setting distribution unit 331 determines which settings of the template are supported for each distribution device, and distributes them to each distribution device. For example, the device setting distribution unit 331 immediately distributes the settings of "Print Setting 3" and "Device Operation Setting 1" to "Device 1", and the setting of "Print Setting 3" to "Device 2".

[0087] In S1007, the function display unit 303 accepts the setting of the date and time for distributing the firmware. In S1008, the schedule management unit 321 creates and saves a task for distributing the setting values. In this embodiment, the schedule management unit 321 creates a distribution task based on the template selected in S1001, the distribution device selected in S1004, the selection of whether to distribute only the common settings, and the date and time input in S1006. Then, the schedule management unit 321 saves the created distribution task in the schedule storage unit 322. When multiple devices are selected as distribution devices on the distribution device selection screen 2500 and distribution of only the common settings is specified, the schedule management unit 321 creates a distribution task for distributing only the common settings to multiple distribution devices based on the template. That is, when the device setting distribution unit 331 has determined in S2407 to distribute only the common settings to the distribution device, the schedule management unit 321 creates a distribution task for distributing only the common settings to multiple distribution devices based on the template in accordance with the determination. For example, when distributing only common settings to a distribution device, the schedule management unit 321 creates a distribution task that distributes the setting item "Print Setting 3" and its setting value "On", which are common settings, to "Device1" and "Device2". On the other hand, when multiple devices are selected as distribution devices and it is not specified to distribute only common settings, the schedule management unit 321 creates a distribution task that distributes based on the template according to the support of each distribution device. In other words, when it is not determined to distribute only common settings to a distribution device, the schedule management unit 321 creates a distribution task that determines the supported settings of the template for each distribution device and distributes them to each distribution device. For example, the device setting distribution unit 331 creates a distribution task that distributes the settings of "Print Setting 3" and "Device Operation Setting 1" to "Device1" and the setting of "Print Setting 3" to "Device2".

[0088] As described above, according to the present embodiment, it is possible to display a warning when the device model of a template created in advance is different from the distribution device. The warning display allows the user to notice that the device model of the template is different from the distribution device before creating a task, and allows the user to go back and reselect the template or distribution device if necessary. In addition, when multiple distribution devices are selected, it is possible to select whether or not to distribute only the settings common to the distribution devices. Then, when only the common settings are distributed, the common settings to be distributed are displayed as a warning, so that the user can check the distribution contents before creating a task, and can go back and reselect the template or distribution device if necessary.

[0089] (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 will realize 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.

[0090] The present invention also includes a case where an operating system (OS) running on a computer performs 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 performs 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.

[0091] 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 storage 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 (e.g., ASIC) that implements one or more of the functions.

[0092] The disclosure of this embodiment includes the following configuration of a management device. (Configuration 1) A management device that distributes a configuration to a network device by executing a task, A management means for managing a template corresponding to a device model of a network device for creating a task; A task creation means for creating a task for distributing a configuration to a network device using the template; A management device comprising: a display means for displaying a warning screen based on a comparison result between a device model corresponding to a template used in a task and a device model of a network device to which settings are to be distributed during creation of the task. (Configuration 2) The template includes information on a device model of a network device and a combination of setting items and their setting values; The management device according to configuration 1, characterized in that the warning screen is displayed immediately after accepting selection of a template and a network device to which settings are to be distributed when a device model corresponding to the template and a device model of a network device to which settings are to be distributed are not the same. (Configuration 3) 3. The management device according to configuration 1 or 2, wherein the warning screen displays settings of the template that are not supported by the network device to which the template is to be distributed. (Configuration 4) The warning screen displays a message prompting the user to change the template or the network device to be distributed, along with a button to return to the template or network device selection screen, and no buttons for screen transitions other than the back button are displayed; The management device according to any one of configurations 1 to 3, wherein the task creation means is capable of saving a task when a template or a network device to which settings are distributed is changed and a device model corresponding to the template and a device model of a network device to which settings are distributed become identical. (Configuration 5) A management device as described in any one of configurations 1 to 3, characterized in that when multiple network devices are selected as network devices to which settings are to be distributed, the warning screen displays common settings of the template to be used that are supported by all of the multiple network devices. (Configuration 6) In creating a task, after accepting the selection of a template, a screen for selecting a network device to which settings are to be distributed displays network devices of the same device model as the device model corresponding to the template and network devices of a different device model in a distinguishable manner, as described in any one of configurations 1 to 5. (Configuration 7) In creating a task, after accepting the selection of a template, a management device according to any one of configurations 1 to 5 is characterized in that, on a screen for selecting a network device to which settings are to be distributed, network devices of the same device model as the device model corresponding to the template are displayed as selectable, and network devices of different device models are not displayed or are displayed in an unselectable state. (Configuration 8) A creating means for creating a template for creating a task, the creation means accepts a selection of a device model of a network device, accepts a selection of configuration items supported by the device model, accepts a selection of configuration values ​​corresponding to the configuration items, and creates a template including information on the selected device model and a combination of the configuration items and their configuration values; 8. The management device according to any one of configurations 1 to 7, wherein the management means manages the created template in order to create a task. (Configuration 9) 9. The management apparatus according to any one of configurations 1 to 8, wherein the network device includes a printer or a multifunction peripheral.

[0093] Although the preferred embodiments of the present invention have been described above, the present invention is not limited to these embodiments, and various modifications and changes are possible within the scope of the gist of the present invention.

Claims

1. A management device that distributes a configuration to a network device by executing a task, A management means for managing a template corresponding to a device model of a network device for creating a task; A task creation means for creating a task for distributing a configuration to a network device using the template; A management device comprising: a display means for displaying a warning screen based on a comparison result between a device model corresponding to a template used in a task and a device model of a network device to which settings are distributed during creation of the task.

2. The template includes information on a device model of a network device and a combination of setting items and their setting values; 2. The management device according to claim 1, wherein the warning screen is displayed immediately after accepting selection of a template and selection of a network device to which settings are to be distributed, when a device model corresponding to the template and a device model of a network device to which settings are to be distributed are not the same.

3. 2. The management apparatus according to claim 1, wherein the warning screen displays settings of the template that are not supported by the network device to which the template is to be distributed.

4. The warning screen displays a message prompting the user to change the template or the network device to be distributed, along with a button to return to the template or network device selection screen, and no buttons for screen transitions other than the back button are displayed; The management device according to claim 1, characterized in that the task creation means is capable of saving the task when the template or the network device to be distributed is changed and the device model corresponding to the template and the device model of the network device to which the settings are distributed become identical.

5. The management device according to claim 1, characterized in that when multiple network devices are selected as network devices to which settings are to be distributed, the warning screen displays common settings of the template to be used that are supported by all of the multiple network devices.

6. The management device according to claim 1, characterized in that, in creating a task, after accepting a selection of a template, a screen for selecting a network device to which settings are to be distributed displays network devices of the same device model as the device model corresponding to the template and network devices of a different device model in a distinguishable manner.

7. The management device according to claim 1, characterized in that, in creating a task, after accepting a selection of a template, a screen for selecting a network device to which settings are to be distributed displays network devices of the same device model as the device model corresponding to the template in a selectable state, and network devices of a different device model are not displayed or are displayed in an unselectable state.

8. A creating means for creating a template for creating a task, the creation means accepts a selection of a device model of a network device, accepts a selection of configuration items supported by the device model, accepts a selection of configuration values ​​corresponding to the configuration items, and creates a template including information on the selected device model and a combination of the configuration items and their configuration values; 2. The management apparatus according to claim 1, wherein the management means manages the created template in order to create a task.

9. The management apparatus according to claim 1 , wherein the network device includes a printer or a multifunction peripheral.

10. A method for controlling a management device that distributes a configuration to a network device by executing a task, comprising the steps of: managing a template corresponding to a device model of a network device for creating a task; creating a task to distribute a configuration to a network device using the template; A method for controlling a management device, comprising: a step of displaying a warning screen based on a comparison result between a device model corresponding to a template used in a task and a device model of a network device to which settings are to be distributed during creation of the task.

11. A program for causing a computer of a management device to execute each step according to claim 10.

Citation Information

Patent Citations

  • Management device, method for controlling management device, and program

    JP2019053570A