JP2007034445A - Device management program, computer-readable recording medium storing the same, and device management method - Google Patents

Abstract

<P>PROBLEM TO BE SOLVED: To prevent a device management program from being used for managing only devices of the other company. <P>SOLUTION: The device management program for managing a plurality of devices connected to a network makes a computer execute steps of retrieving the kinds of the plurality of devices (S01); setting an own company device of the plurality of devices as a device to be managed (S06 executed when YES in S04); and setting, on condition that the own company device is set as the device to be managed the other company device as the device to be managed (S06 executed when YES in S05). <P>COPYRIGHT: (C)2007,JPO&INPIT

Description

  The present invention relates to a device management program, a computer-readable recording medium storing a device management program, and a device management method, and in particular, a device management program for managing devices connected to a network, and a computer read storing a device management program The present invention relates to a possible recording medium and a device management method.

  2. Description of the Related Art Conventionally, a form in which devices such as a printer, a scanner, and a copying machine are connected to a network is generally used. In this usage pattern, a device management program is installed and executed in a computer in order to monitor the state of each of a plurality of devices and to control the devices. This type of device management program enables device status monitoring and control regardless of the device manufacturer. The device management program is generally distributed by downloading from the Internet, and is available to many people. Typically, device manufacturers produce and distribute device management programs to monitor and control their devices.

However, for example, the device management program of company A can be used to monitor and control the device of company B. As a technique for preventing this, a technique for permitting the use of a device management program on condition of licensing is known (for example, Patent Document 1 and Patent Document 2). According to the use permission of the device management program by licensing, the use of the program can be restricted. However, a system for distributing the program, a system for managing users, etc. must be constructed, and the system construction cost In addition, there is a problem that management costs are required.
JP 2001-84137 A JP 2002-276350 A

  The present invention has been made to solve the above-described problems, and one of the objects of the present invention is a device management program that prevents the device from being used to manage only devices other than a predetermined type of device, To provide a computer-readable recording medium storing a device management program and a device management method.

  Another object of the present invention is to provide a device management program capable of limiting the number of devices other than a predetermined type of device, a computer-readable recording medium storing the device management program, and a device management method. That is.

  Still another object of the present invention is to provide a device management program that enables management with added value only for a predetermined type of device, a computer-readable recording medium storing the device management program, and a device management method. It is to be.

  In order to achieve the above object, according to one aspect of the present invention, a device management program is a device management program for managing a plurality of devices connected to a network, and searches for a plurality of device types. A step, a step of setting a first type of devices among the plurality of devices as a management target device, and a step of setting the first type of devices as a management target device. And causing a computer connected to the network to execute a step of setting a second type device different from the one type as a management target device.

  According to the present invention, the first type device is set as a management target device, and the second type device is set as a management target device on condition that the first type device is set as a management target device. Set to For this reason, in order for the second type device to be a managed device, it is necessary that the first type device is connected to the network. Therefore, the first type device is connected to the network. It is possible to prevent the device management program from being used without being performed. As a result, it is possible to provide a device management program that is prevented from being used to manage only devices other than a predetermined type of device.

  Preferably, in the step of setting the second type device as the management target device, the number of the second type devices set as the management target device is set to the number of the first type device set as the management target device. Including the step of limiting the number of units according to the number.

  According to the present invention, the second type device is limited to the number corresponding to the number of the first type devices and is set as the management target device. Therefore, in order to set the second type of device as the management target device, it is necessary that the number of the first type of devices corresponding to the number of devices be connected to the network. As a result, it is possible to provide a device management program capable of limiting the number of devices that manage devices other than a predetermined type of device.

  Preferably, the number of devices of the first type is stored for a predetermined period, and the number of devices searched as the first type by the search step is smaller than the stored number, the stored number is Further, the computer is caused to execute a step of calculating the number to be limited based on the computer.

  According to the present invention, even if the first type device is turned off, for example, the first type of device that is managed from the number of first type devices that are actually connected to the network. The number of two types of devices is calculated. As a result, it is possible to prevent a device that has been managed by a device other than a predetermined type from suddenly disappearing from being managed.

  According to another aspect of the present invention, the device management program is a management program for managing a plurality of devices connected to a network, the step of searching for a plurality of device types, and among the plurality of devices The step of setting the first type device as the target device of the first management and the second type device different from the first type among the plurality of devices have fewer management functions than the first management. And setting the second management target device to a computer connected to the network.

  According to the present invention, the first type device is set as a first management target device, and the second type device is set as a second management target device having fewer management functions than the first management. Is done. For this reason, the management function can be made different between the first type device and the second type device. As a result, it is possible to provide a device management program that enables management with increased added value only for a predetermined type of device.

  According to still another aspect of the present invention, a computer-readable recording medium storing the above-described device management program.

  According to still another aspect of the present invention, a device management method is a device management method for managing a plurality of devices connected to a network, the step of searching for a plurality of device types, and a plurality of devices A first type of device as a management target device, and a second type of device different from the first type of the plurality of devices according to the number of the first type of devices And making the computer connected to the network execute the step of setting the device to be managed by limiting the number of devices.

  According to the present invention, it is possible to provide a device management method that prevents managing only devices other than a predetermined type of device.

  According to still another aspect of the present invention, a device management method is a device management program for managing a plurality of devices connected to a network, the step of searching for a plurality of device types, and a plurality of devices Of setting the first type of device as the first management target device, and managing the second type of device different from the first type of the plurality of devices rather than the first management And setting a second management target device with a small number of computers to a computer connected to the network.

  According to the present invention, it is possible to provide a device management method that enables management with added value only for a predetermined type of device.

  Hereinafter, embodiments of the present invention will be described with reference to the drawings. In the following description, the same parts are denoted by the same reference numerals. Their names and functions are also the same. Therefore, detailed description thereof will not be repeated.

  FIG. 1 is a diagram showing an overall outline of a device management system according to one embodiment of the present invention. Referring to FIG. 1, a device management system 1 includes a device management apparatus 100 connected to a network 2, company devices 3A and 3B, and other company devices 4A, 4B, 4C, 4D and 4E.

  The device management apparatus 100 is a general computer, and a device management program of company A is installed as an application program. This device management program is acquired by downloading to the device management apparatus 100 from a manufacturer's web (Web) server connected to the Internet. Here, company A is called its own company, and companies other than company A are called other companies. Therefore, the company devices 3A and 3B are devices manufactured or sold by the company A, and the devices 4A, 4B, 4C, 4D and 4E of other companies are devices manufactured or sold by companies other than the company A.

  In-house devices 3A and 3B and other companies' devices 4A, 4B, 4C, 4D, and 4E are multi-function peripherals (scanners for reading originals, images on recording media such as paper based on image data). It includes an image forming apparatus and a facsimile machine for forming, and has an image reading function, a copying function, and a facsimile transmission / reception function. In-house devices 3A, 3B and other companies' devices 4A, 4B, 4C, 4D, 4E have different device types, and here, the types are different from each other. In-house devices 3A and 3B and other companies' devices 4A, 4B, 4C, 4D, and 4E are not limited to MFPs, and are, for example, scanner devices, printers, copiers, facsimile devices, personal computers that generate image data, and the like. Also good. In FIG. 1, the alphanumeric characters described in the company's devices 3A and 3B and the other company's devices 4A, 4B, 4C, 4D, and 4E respectively represent the company's device 3A and 3B and the other company's devices 4A, 4B, 4C, 4D, and 4E. It is a model name as identification information for identification.

  The network 2 is a local area network (LAN), and the connection form may be wired or wireless. The network 2 is not limited to a LAN, and may be a wide area network (WAN) such as the Internet, a network using a general public line, or the like.

  FIG. 2 is a block diagram showing a hardware configuration of the device management apparatus according to one embodiment of the present invention. Referring to FIG. 1, a device management apparatus 100 includes a central processing unit (CPU) 101 that is connected to a bus 120, and a ROM (Read Only Memory) 103 that records a boot-up program to be executed by the CPU 101. A RAM (Random Access Memory) 105 for loading a program to be executed and for storing data during program execution, a hard disk drive (HDD) 107 for storing data in a nonvolatile manner, and an IC A card interface (I / F) 109 to which the card 108 is attached, an input unit 111 and a display unit 113 that serve as an interface with a user, and a communication I / F 115 for connecting the device management apparatus 100 to the network 2 are included. .

  The device management apparatus 100 stores the installed device management program of company A in the HDD 107, and the CPU 101 loads the device management program stored in the HDD 107 into the RAM 105 and executes it. Note that the CPU 101 may load the device management program recorded on the IC card 108 attached to the card I / F 109 into the RAM 105 and execute it. Furthermore, a device management program may be downloaded from another computer connected to the network 2 and stored in the HDD 107, and the device management program may be loaded into the RAM 105 and executed. The device management program here includes not only a program directly executable by the CPU 101 but also a program in a source program format, a compressed program, an encrypted program, and the like.

  The recording medium for storing the device management program is not limited to the IC card 108, but is a flexible disk, cassette tape, optical disk (CD-ROM (Compact Disc-ROM) / MO (Magnetic Optical Disc / MD (Mini Disc) / MD (Mini Disc) / DVD). (Digital Versatile Disc)), a medium carrying a fixed program such as an optical card, a mask ROM, an EPROM (Erasable Programmable ROM), an EEPROM (Electronically Erasable and Programmable ROM), or the like.

  The input unit 111 is an input device such as a keyboard or a mouse. The display unit 113 is a liquid crystal display device or a cathode ray tube (CRT). The communication I / F 115 is a communication interface for connecting the device management apparatus 100 to the network 2. Thereby, the device management apparatus 100 can communicate with other in-house devices 3A, 3B and other companies' devices 4A, 4B, 4C, 4D, 4E. The device management apparatus 100 and other company devices 3A and 3B and other company's devices 4A, 4B, 4C, 4D, and 4E are shown as being connected via the network 2, but a serial interface or a parallel interface is used. May be directly connected. The communication I / F 115 uses an interface corresponding to the connection form between the device management apparatus 100 and the other company devices 3A and 3B and other company devices 4A, 4B, 4C, 4D, and 4E.

  FIG. 3 is a block diagram showing an overview of the functions of the CPU of the device management apparatus. With reference to FIG. 3, the CPU 101 includes a device search unit 10 for searching for devices connected to the network 2, and a determination unit 12 for determining the type of device obtained by the search by the device search unit 10. , A limiting unit 14 for limiting the devices to be managed based on the determination result by the determining unit 12, and a management unit 16 for managing the devices within a range limited by the limiting unit 14.

  The device search unit 10 is connected to the communication I / F 115 and searches for devices connected to the network 2. For device search, SNMP (Simple Network Management Protocol) is used to check the response of the device by SNMP broadcast or SNMP PING (Packet Internet Grouper) of IP (Internet Protocol) address within a predetermined range. The device search unit 10 detects company devices 3A, 3B and other company devices 4A, 4B, 4C, 4D, 4E connected to the network 2.

  The determination unit 12 determines the type of device detected by the device search unit 10. The types here include a first type that is a device manufactured or sold by company A and a second type other than that. The type can be determined from the sysObjectID of the MIB (Management Information Base) possessed by each of the devices 3A and 3B and the devices 4A, 4B, 4C, 4D, and 4E. The devices whose types are determined are registered and managed in the device management list. Although the device management list will be described later, the device management list is stored in the HDD 107, read out, and displayed on the display unit 113. By specifying each device displayed in the device management list, a detailed setting screen is displayed, and various setting values of the specified device can be confirmed or changed.

  The restriction unit 14 restricts management of devices of other companies in accordance with the number of devices determined by the determination unit 12 as in-house devices. The limit is the number of managed devices. More specifically, the number of other company's devices to be managed is limited to a factor multiple of the number of company devices detected by the device search unit 10. Here, the coefficient is “2”. The coefficient is not limited to “2” and can be arbitrarily determined. The coefficient is not limited to an integer and may be a fraction. Since two company devices 3A and 3B are connected to the network 2, the number of devices of other companies that can be managed is four (2 (units) × 2 (coefficients)). Since five devices 4A, 4B, 4C, 4D, and 4E are connected to the network 2, one of them cannot be managed.

  The management unit 16 is connected to the communication I / F 115, the display unit 113, and the input unit 111. Further, the management unit 16 receives the limited number of devices of other companies that can be managed from the limiting unit 14. The management unit 16 manages a limited number of devices selected from the company devices 3A and 3B and the other company devices 4A, 4B, 4C, 4D, and 4E. Management includes display of a device list, display of a detailed setting screen, and change of various setting values of the device. The display of the device list includes display of the device status.

  FIG. 4 is a flowchart showing a flow of management device determination processing executed by the device management apparatus according to the present embodiment. Referring to FIG. 4, device management apparatus 100 searches for a device connected to network 2 by confirming a device response by SNMP broadcast or SNMP PING of an IP address in a predetermined range using SNMP. (Step S01). Then, it receives the sysObjectID of the MIB from each detected device, determines whether or not the device is a company device manufactured or sold by company A, and determines the number of company devices (step S02). Here, because the company devices 3A and 3B are connected to the network 2, the number of company devices is determined to be “2”.

And the limit value used as the upper limit of the number of devices which can manage another company's device is determined according to following Formula (1).
Limit value = number of company devices x coefficient (1)
Here, the limit value “4” is determined with the coefficient = 2.

  Then, a process for determining whether or not each device detected in step S01 is a management device to be managed is executed. In step S04, a device to be determined is selected from the devices detected in step S01, and it is determined whether or not the device to be determined is a company device. If the device to be discriminated is an in-house device, the process proceeds to step S06. In step S06, the company device is registered in the device list as a management device, and the process proceeds to step S08.

  In step S05, it is determined whether the number of other companies registered as management devices is equal to or less than a limit value. If the number of devices of other companies registered as management devices is less than the limit value, the process proceeds to step S06, and even devices of other companies are registered in the device list as management devices. At this time, the number of devices of other companies registered as management devices is counted up. Thereafter, the process proceeds to step S08.

  In step S05, if the number of other companies registered as management devices exceeds the limit value, the process proceeds to step S07. In step S07, another company's device to be determined is registered in the unmanaged device. Then, the process proceeds to step S08. In step S08, it is determined whether or not there is a device to be determined next, and if it exists, the process returns to step S04, and if not, the process ends.

  FIG. 5 is a flowchart showing the flow of the company device number determination process executed in step S02 of FIG. With reference to FIG. 5, first, the number C1 of company devices is calculated (step S11). The number of company devices calculated here is the total number of company devices searched for devices in step S01 in FIG. Therefore, when the step S01 of FIG. 4 is executed, the company device that is not powered on is not detected, and therefore is not included in the company device number C1. In the present embodiment, since two in-house devices 3A and 3B are connected to the network 2, the in-house device number C1 calculated in step S11 is 2 at the maximum and may be 1 or 0. .

  In step S12, the past company device number C2 is read. This past company device number is stored in a predetermined area of the HDD 107 in step S18 described later. Then, an elapsed time (storage time) after the company device number C2 is stored is compared with a threshold value T (step S13). If the storage time is smaller than the threshold value, the process proceeds to step S14, but if larger, the process proceeds to step S16. The storage time is calculated from the time when the company device number C2 is stored and the current time. As will be described later, the past in-house device number C2 is the maximum number of in-house devices detected up to a certain point in time. This is because when there is an in-house device that is not turned on when step S01 in FIG. 4 is executed, the number of devices of other companies permitted as a management target is calculated by the above equation (1), which is small. This is to prevent this from happening. Therefore, in step S14, the in-house device number C1 is compared with the past in-house device number C2, and if C1 <C2, the in-house device number used in the above formula (1) is set to the past in-house device number C2. (Step S15). On the other hand, if C1 <C2, the number of company devices used in the above formula (1) is set to the company device number C1 calculated in step S11 (step S16), and the past company device number C2 is calculated in step S11. The in-house device number C1 is set (step S17), and the in-house device number C2 is stored in a predetermined area of the HDD 107. In step S14, it is determined that C1 <C2 is not satisfied, and the process proceeds to step S16. (1) When a company device is newly connected to the network 2, (2) the company device number C1 and the past company device number C2 are This is the case.

  In this way, the number of devices of other companies permitted as a management target is calculated from the maximum number of company devices detected up to a certain point in time. This is to prevent the number of devices of other companies permitted as a management target from being reduced even if there is the number of in-house devices that are not turned on when step S01 in FIG. 4 is executed. However, in order to cope with the case where the number of company devices is disconnected from the network 2 when step S01 of FIG. 4 is executed, the maximum value of the number of company devices detected up to a certain point in time up to the threshold value T. Is valid.

  FIG. 6 is a diagram illustrating an example of a device list generated by the device management apparatus according to the present embodiment. This device list is generated by executing the device determination process and stored in a predetermined area of the HDD 107. The device list is read from the HDD 107 and displayed on the display unit 113 in response to a user inputting a display instruction from the input unit 111.

  With reference to FIG. 6, the device list includes an operating state, a model name, an IP address, an installation location, and a counter for each of a plurality of devices connected to the network 2. The operating state includes information indicating whether the managed device is a non-managed device. When the device is a management device, one of a standby state (Ready), a low toner amount (Toner Low), a printing state (Printing), and a failure state (Error) is displayed. The If the device is an unmanaged device, the operation status is displayed as unmanaged. In the figure, it is shown that another company's device 4E of model name S262 is an unmanaged object. The model name includes identification information for identifying the device, and the company device and the device of another company. The device marked with “*” in the figure indicates that it is a company device. The counter indicates the number of sheets printed by the device. For the non-management target device 4E, the operating status and model name are displayed in the device list, but the IP address, installation location, and counter information are not displayed.

<Modification>
In the device management apparatus described above, the number of devices of other companies to be managed is limited. However, the device management apparatus in the modified example limits the function of managing devices of other companies. For this reason, both in-house devices and devices from other companies are managed devices.

  The overall outline of the device management system in the modified example is the same as that shown in FIG. 1, and the hardware configuration of the device management apparatus is the same as that shown in FIG. Therefore, description is not repeated here.

  The function of the CPU of the device management apparatus in the modification is the same as that shown in FIG. 3 except for the function of the management unit 16. In the device management apparatus 100 according to the modification, the management unit 16 restricts the function of managing other company devices when the number of company devices and the number of other company devices are in a predetermined relationship. The predetermined relationship is when the number of devices of other companies is equal to or greater than the number of devices of the company multiplied by a coefficient (here, “2”).

  FIG. 7 is a flowchart showing a flow of function restriction processing executed by the device management apparatus according to the modification. Referring to FIG. 7, steps S01 to S03 are the same as steps S01 to S03 of the management device determination process shown in FIG. When the limit value is calculated in step S03, the process proceeds to step S21. In step S21, it is determined whether the number of devices of other companies is smaller than the limit value. If true, the process proceeds to step S22, and if false, the process proceeds to step S23. In step S22, the management function of another company's device is restricted. Specifically, management functions that can be managed by the company's own device are not enabled for devices of other companies. In step S23, all the other company's devices are managed by the same management function as the company device. For this reason, the restriction of the management function of the other company device once the management function is restricted is released.

  FIG. 8 is a diagram illustrating an example of a device list generated by the device management apparatus according to the modification. Referring to FIG. 8, in the device management apparatus 100 according to the modified example, the company device and the other company's device are managed, and unlike the one shown in FIG. And counter information is displayed.

  When the device list is displayed on the display unit 113 and the user designates a device using the input unit 111, a detailed setting screen for confirming and changing the setting value of the device is displayed on the display unit 113. The user can change the setting value by operating the input unit 111. However, in the device management apparatus according to the modified example, when the management function of another company's device is restricted, the user does not display the detailed setting screen of the other company's device or displays the detailed setting screen but the setting value You can't make changes.

  FIG. 9 is a diagram illustrating an example of a detailed setting screen displayed on the device management apparatus. Referring to FIG. 9, the detailed setting screen includes a model name, a nickname, an installation location, an administrator name, a system up time, a total memory, a storage table, a panel language, and a paper feed tray. And a reset button. FIG. 9 shows a detailed setting screen displayed when the device list shown in FIG. 8 is displayed and the company device 3A is designated. As the model name and installation location, the model name and installation location of the company device 3A are displayed. These are the same information registered in the device list. The nickname can be arbitrarily given to the company's device 3A by the user, and here is a second group printer. The person in charge is the name of the person in charge who manages the company device 3A. The system up time is an elapsed time after the power is turned on to the company device 3A. The total memory is the size of the memory installed in the company device 3A. The storage table is information related to storage (memory or HDD) installed in the company device 3A. Here, the memory sizes of the RAM and the printer RAM are shown. The panel language displays the language used for the screen displayed on the display unit 113 by the company device 3A. The paper feed tray (default) indicates a paper feed tray set by default. “Reset” is a button for setting each setting value to an initial value.

  The detailed setting screen shown in FIG. 9 is displayed for the company devices 3A and 3B without any limitation. The detailed setting screens of the other company's devices 4A, 4B, 4C, 4D, and 4E are displayed when the management function of the other company's device is not restricted, but are not displayed when the management function of the other company's device is restricted. .

  As described above, the device management apparatus 100 according to the present embodiment sets the own devices 3A and 3B as managed devices, and sets the number of other companies' devices 4A, 4B, 4C, 4D, and 4E set as managed devices. , It is limited to a factor multiple of the number of company devices 3A, 3B set in the management target device. For this reason, in order for a device of another company to be a managed device, the number of devices in-house corresponding to the number of devices must be connected to the network 2, so the number of devices managed by other companies should be limited. And can encourage the purchase of their own devices.

  In addition, the number of company devices detected in the past is stored for a predetermined time T. If the number of company devices detected next is smaller than the stored number, the number of devices to be limited based on the stored number Therefore, even if the power of the company device is turned off, the number of devices of other companies to be managed is calculated from the number of company devices actually connected to the network 2. For this reason, it is possible to prevent a device that has been managed by another company's device from being suddenly excluded from being managed.

  In the modified device management apparatus 100, the devices 3A, 3B and other companies 'devices 4A, 4B, 4C, 4D, 4E are set as managed devices, but the number of other companies' devices 4A, 4B, 4C, 4D, 4E is set. If it is more than a factor multiple of the number of company devices 3A, 3B, it is limited to management with fewer management functions than managing other company devices 4A, 4B, 4C, 4D, 4E. For this reason, management with increased added value can be made possible only for the company device, and the purchase of the company device can be promoted.

  The embodiment disclosed this time should be considered as illustrative in all points and not restrictive. The scope of the present invention is defined by the terms of the claims, rather than the description above, and is intended to include any modifications within the scope and meaning equivalent to the terms of the claims.

It is a figure which shows the whole device management system outline | summary in one of embodiment of this invention. It is a block diagram which shows the hardware constitutions of the device management apparatus in one of embodiment of this invention. It is a block diagram which shows the outline | summary of the function of CPU of a device management apparatus. It is a flowchart which shows the flow of the management device determination process performed with the device management apparatus in this Embodiment. It is a flowchart which shows the flow of the company device number determination process performed by step S02 of FIG. It is a figure which shows an example of the device list produced | generated by the device management apparatus in this Embodiment. It is a flowchart which shows the flow of the function restriction | limiting process performed with the device management apparatus in a modification. It is a figure which shows an example of the device list produced | generated by the device management apparatus in a modification. It is a figure which shows an example of the detailed setting screen displayed with a device management apparatus.

Explanation of symbols

  2 Network, 3A, 3B In-house device, 4A, 4B, 4C, 4D, 4E Other company's device, 10 Device search unit, 12 Discrimination unit, 14 Restriction unit, 16 Management unit, 100 Device management device, 108 IC card, 109 card I / F, 111 input unit, 113 display unit, 120 bus, 115 communication I / F.

Claims (7)

A device management program for managing a plurality of devices connected to a network,
Searching for a plurality of device types;
Setting a first type device among the plurality of devices as a managed device;
On the condition that the first type device is set as the management target device, a second type device different from the first type among the plurality of devices is set as the management target device. A device management program that causes a computer connected to the network to execute the step.   The step of setting the second type device as a management target device includes the step of setting the number of the second type devices to be set as the management target device in the first type set in the management target device. The device management program according to claim 1, comprising a step of limiting the number of devices according to the number of devices. Storing the number of devices of the first type set in the managed device for a predetermined period;
If the number of devices retrieved as the first type by the retrieval step is smaller than the stored number, the computer further executes a step of calculating the limited number based on the stored number. The device management program according to claim 2. A device management program for managing a plurality of devices connected to a network,
Searching for a plurality of device types;
Setting a first type of device among the plurality of devices as a first management target device;
Setting a second type of device different from the first type among the plurality of devices as a second management target device having a management function smaller than that of the first management. A device management program that runs on a connected computer.   The computer-readable recording medium which memorize | stored the device management program in any one of Claims 1-4. A device management method for managing a plurality of devices connected to a network,
Searching for a plurality of device types;
Setting a first type device among the plurality of devices as a managed device;
On the condition that the first type device is set as the management target device, a second type device different from the first type among the plurality of devices is set as the management target device. A device management method for causing a computer connected to the network to execute the step. A device management program for managing a plurality of devices connected to a network,
Searching for a plurality of device types;
Setting a first type of device among the plurality of devices as a first management target device;
Setting a second type of device different from the first type among the plurality of devices as a second management target device having a management function smaller than that of the first management. A device management method that is executed by a connected computer.

Images