JP2023005619A - Management program, management method, and management system - Google Patents

Abstract

To simplify driver installation.SOLUTION: A management program causes a control unit of a management apparatus 2 to execute model acquisition processing, installer determination processing, and installer extraction processing. The model acquisition processing acquires "printer model name" specifying a model. When acquiring the "printer model name", the installer determination processing determines whether a multiple-driver installer includes an installer for a printer driver corresponding to a specified model indicated by the "printer model name". The installer extraction processing extracts, when it is determined that the installer corresponding to the specified model is included in the multiple-driver installer, the installer corresponding to the specified model from the multiple-driver installer.SELECTED DRAWING: Figure 1

Description

The present disclosure relates to techniques for managing client devices.

Japanese Patent Application Laid-Open No. 2002-200003 describes a method for changing printer drivers of a plurality of client devices from a management device.
When changing the printer driver of the client device, generally an installer, which is a program for installing the printer driver on the client device, is required.

When a plurality of models are set for the printer, a printer driver corresponding to each of the plurality of models is required. Therefore, multiple installers are required for each of the multiple models.

Japanese Patent Application Laid-Open No. 2001-222400

A multiple driver installer is known that has multiple installers corresponding to multiple models. The multi-driver installer has a function of selecting an installer corresponding to the model indicated by the model identification information and executing the selected installer when model identification information indicating the model of the printer is input.

However, there is a problem that even if the multiple driver installer is downloaded to the client device, the printer driver corresponding to the printer model assigned to the client device cannot be automatically installed.

The present disclosure aims to simplify driver installation.

One aspect of the present disclosure is a management program used in a management system that manages client devices.
The management system includes a client device, a management device that manages the client device, a device that executes processing based on instructions from the client device, and a storage device. A storage device stores a multiple driver installer comprising multiple installers for installing respective multiple device drivers corresponding to multiple models of devices. A device driver is a program for controlling a device from a client device. An installer is a program for installing a device driver on a client device.

The management program is configured to cause a control unit provided in the management apparatus to execute model acquisition processing, installer determination processing, and installer extraction processing.
The model acquisition process acquires model identification information that identifies the model.

In the installer determination process, when the model identification information is acquired in the model acquisition process, it is determined whether or not the installer of the device driver corresponding to the specific model indicated by the model identification information is included in the multiple driver installer.

The installer extracting process extracts the installer corresponding to the specific model from the multiple driver installer when it is determined in the installer determination process that the installer corresponding to the specific model is included in the multiple driver installer.

In the management program of the present disclosure configured as described above, the user of the client device downloads the multiple driver installer to the client device, and then inputs the model identification information on the client device side to extract the installer. Installation of device drivers can be simplified because they are no longer necessary.

Another aspect of the present disclosure is a management method executed by a management device of a management system comprising a client device and a management device that manages the client device, comprising a model acquisition step, an installer determination step, and an installer extraction step. and

The management method of the present disclosure is a method executed by the management program of the present disclosure, and by executing the method, the same effects as those of the management program of the present disclosure can be obtained.
Yet another aspect of the present disclosure is a management system that includes a client device, a management device, a device, and a storage device. The management device is configured to execute model acquisition processing, installer determination processing, and installer extraction processing.

The management system of the present disclosure is a system controlled by the management program of the present disclosure, and can obtain the same effects as the management program of the present disclosure.

It is a figure which shows the structure of a management system. 3 is a block diagram showing the configuration of a management device and a shared server; FIG. 2 is a block diagram showing configurations of a client device and a printer; FIG. 3 is a diagram showing the configuration of an active directory; FIG. 4 is a diagram showing the configuration of organizational unit information; FIG. 4 is a flowchart showing client management processing according to the first embodiment; FIG. 10 is a diagram showing a specific example of parameters input in an input image such as a tissue unit; FIG. 4 is a diagram showing the configuration of a multi-driver installer; FIG. FIG. 4 is a diagram showing association between organizational unit information and first and second object information; 10 is a flowchart showing client management processing according to the second embodiment;

[First embodiment]
Embodiments of the present disclosure will be described below with reference to the drawings.
(1) Configuration of management system 1 The management system 1 of this embodiment is a system for managing a plurality of client devices 4 used in a company composed of a plurality of organizations. 2 , a shared server 3 , a plurality of client devices 4 , and a plurality of printers 5 . The management device 2, shared server 3, client device 4, and printer 5 are configured to communicate with each other via a local area network 6 (hereinafter, LAN 6) as an example of a network. The network may be a wide area network (hereinafter referred to as WAN) or may include LAN and WAN.

The management device 2 is a personal computer in this embodiment, and includes a control unit 11, a communication unit 12, a display unit 13, an input unit 14, and a storage unit 15, as shown in FIG.
The control unit 11 has a CPU 21 and a memory 22 . The CPU 21 executes programs stored in the memory 22 , thereby realizing various functions of the management device 2 . It should be noted that the various functions realized by the control unit 11 are not limited to being realized by executing a program, and a part or all of them may be realized using one or more pieces of hardware.

The memory 22 comprises semiconductor memory (eg, ROM, RAM and flash memory).
The communication unit 12 performs data communication with the shared server 3 , the client device 4 and the printer 5 via the LAN 6 .

The display unit 13 includes a display device (not shown) and displays various images on the display device. The input unit 14 has a keyboard and a mouse. The input unit 14 outputs input operation information for specifying an input operation performed by the user (that is, administrator) of the management device 2 via the keyboard and mouse.

The storage unit 15 includes auxiliary storage devices such as HDD and SSD, and stores various data. HDD is an abbreviation for Hard Disk Drive. SSD is an abbreviation for Solid State Drive. The storage unit 15 has an active directory 23 . The active directory 23 contains client devices 4 and printers 5 managed by the management system 1, identification information and authentication information of members belonging to the corporate organization, and access rights to the client devices 4 and printers 5 by the members. Equipped with a centralized management function.

The shared server 3 includes a control unit 31 , a communication unit 32 and a shared storage 33 .
The control unit 31 has a CPU 41 and a memory 42 . The CPU 41 executes programs stored in the memory 42 , thereby realizing various functions of the shared server 3 . It should be noted that the various functions realized by the control unit 31 are not limited to being realized by executing a program, and a part or all of them may be realized using one or a plurality of pieces of hardware. The memory 42 includes semiconductor memory (eg, ROM, RAM and flash memory) and stores programs and data.

The communication unit 32 performs data communication with the management device 2 , the client device 4 and the printer 5 via the LAN 6 .
The shared storage 33 includes auxiliary storage devices such as HDDs and SSDs, and stores various data. The shared storage 33 also stores a multiple driver installer 43, which will be described later.

The client device 4 is a personal computer in this embodiment, and includes a control unit 51, a communication unit 52, a display unit 53, an input unit 54, and a storage unit 55, as shown in FIG. Note that the client device 4 may be a mobile terminal such as a smart phone or a tablet.

The control unit 51 has a CPU 61 and a memory 62 . The CPU 61 executes programs stored in the memory 62 , thereby realizing various functions of the client device 4 . Various functions realized by the control unit 51 are not limited to being realized by executing a program, and a part or all of them may be realized using one or more pieces of hardware.

The memory 62 comprises semiconductor memory (eg, ROM, RAM and flash memory).
The communication unit 52 performs data communication with the management device 2 , the shared server 3 and the printer 5 via the LAN 6 .

The display unit 53 includes a display device (not shown) and displays various images on the display device. The input unit 54 has a keyboard and a mouse. The input unit 54 outputs input operation information for specifying input operations performed by the user of the client device 4 via the keyboard and mouse.

The storage unit 55 includes an auxiliary storage device such as an HDD and an SSD, and stores various data.
The printer 5 includes a control section 71 , a communication section 72 , a display section 73 , an input section 74 and a printing section 75 .

The control unit 71 has a CPU 81 and a memory 82 . The CPU 81 executes programs stored in the memory 82, thereby realizing various functions of the printer 5. FIG. It should be noted that the various functions realized by the control unit 71 are not limited to being realized by executing a program, and a part or all of them may be realized using one or more pieces of hardware. The memory 82 includes semiconductor memory (eg, ROM, RAM and flash memory) and stores programs and data.

The communication unit 72 performs data communication with the management device 2 , the shared server 3 and the client device 4 via the LAN 6 .
The display unit 73 has a display device (not shown) and displays various images on the display device. The input unit 74 includes a touch panel installed on the display screen of the display unit 73 and switches installed around the display screen of the display unit 73 . The input unit 74 outputs input operation information for specifying the input operation performed by the user via the touch panel and the switches.

The printing unit 75 has a printing mechanism of inkjet technology or electrophotographic technology, and can print an image on a print medium. The printing unit 75 may have a thermal printing mechanism.
(2) Active Directory 23
The active directory 23 stores a management program 91 as shown in FIG. The active directory 23 is also provided with an installation setting storage area 92 for storing installation setting information set for the client device 4 in order to install the printer driver on the client device 4 .

The installation setting storage area 92 includes an organizational unit storage area 93 and a group policy storage area 94 .
The organizational unit storage area 93 stores a plurality of organizational unit information 93a. FIG. 4 shows organizational unit information 93a of the first organizational unit and organizational unit information 93a of the second organizational unit. The organizational unit information 93a indicates the correspondence between the members belonging to the organization and the client devices 4 used by the members. In FIG. 4, the members of the first organizational unit are 32 users from the first user to the 32nd user, and the members of the second organizational unit are 13 users from the 33rd user to the 45th user. be.

The group policy storage area 94 stores a plurality of first object information 94a and a plurality of second object information 94b.
The first object information 94 a is information specifying the IP address of the printer 5 . The second object information 94b is information specifying the installer of the printer driver.

As shown in FIG. 5, the organizational unit information 93a includes "organizational unit", "user" and "computer" as setting items.
A character string for identifying an organization is set in the "organizational unit". FIG. 5 shows “OU_KAIHATSUBU_1G” and “OU_KAIHATSUBU_2G” as “organizational units”. Note that OU is an abbreviation for Organization Unit. "KAIHATSUBU_1G" is a character string indicating the first group of the development department, and "OU_KAIHATSUBU_2G" is a character string indicating the second group of the development department.

"User" is set with the name of a member belonging to the organization. FIG. 5 shows “AAAAAA, BBBBBB”, “CCCCCCC, DDDD”, etc. as “users” belonging to “KAIHATSUBU_1G” of “organizational unit”. In "AAAAAAA, BBBBBB", "AAAAAAA" is a surname and "BBBBBB" is a given name.

In "computer", a character string for identifying the client device 4 used by each member belonging to the organization is set. FIG. 5 shows “ABCD1234001”, “ABCD1234002”, etc. as “computers” belonging to “KAIHATSUBU_1G” of the “organizational unit”. "ABCD1234001" is the client device 4 assigned to "AAAAAAA, BBBBBB" of the "user". "ABCD1234002" is the client device 4 assigned to "CCCCCCC, DDDD" of the "user".

(3) Processing Executed by Management Apparatus 2 Next, procedures of client management processing executed by the control unit 11 of the management apparatus 2 will be described. The client management process is executed by activating the management program 91 stored in the active directory 23 by the administrator's input operation. Processing performed among the management device 2, the shared server 3, the client device 4 and the printer 5 will be described in detail below.

When the client management process is executed, the CPU 21 of the control unit 11, as shown in FIG. is displayed on the display screen of the display unit 13 .

FIG. 7 is a diagram showing specific examples of the "organizational unit", "printer IP address" and "printer model name" that are input in S10.
For example, if the "organizational unit" is "development department first group", "OU_KAIHATSUBU_1G" is entered as the "organizational unit" and "192.168.100.101" is entered as the "printer IP address". and "MFC-L1234 series" is entered as the "printer model name".

If the "organizational unit" is "sales department second group", "OU_KAIHATSUBU_2G" is entered as the "organizational unit", and "192.168.102.105" and "192.168.102.105" are entered as the "printer IP address". 192.168.102.106” is entered, and “MFC-L1238 series” and “MFC-L1234 series” are entered as the “printer model name”. Note that "192.168.102.105" for "IP address of printer" is entered with "MFC-L1238 series" for "model name of printer", and "192.168.105" for "IP address of printer" is entered. 102.106”, the “printer model name” “MFC-L1234 series” is input.

Next, as shown in FIG. 6, the CPU 21 determines whether or not the "organizational unit", "printer IP address" and "printer model name" have been input from the input unit 14 in S20.

Here, if the "organizational unit", "printer IP address" and "printer model name" have not been input, the CPU 21 repeats the process of S20 to obtain the "organizational unit", "printer IP address", and "printer IP address". Wait until the "address" and "printer model name" are entered. Then, when the "organizational unit", "printer IP address" and "printer model name" are input, the CPU 21 selects the model specified by the input "printer model name" (hereinafter referred to as "printer model name") in S30. input model) is stored in the shared storage 33 or not.

Here, when the single driver installer corresponding to the input model is stored in the shared storage 33, the CPU 21 proceeds to S70. On the other hand, if the single driver installer corresponding to the input model is not stored in the shared storage 33, the CPU 21 determines in S40 whether the multiple driver installer 43 corresponding to the input model is stored in the shared storage 33. determine whether

The multi-driver installer 43 comprises, for example, a plurality of single-driver installers 43a, 43b, 43c, as shown in FIG. The plurality of single driver installers 43a, 43b, and 43c are installers for installing different first, second, and third model printer drivers, respectively.

The file names of the single driver installers 43a, 43b and 43c are respectively "driver_model1.msi", "driver_model2.msi" and "driver_model3.msi". That is, the single driver installers 43a, 43b, 43c are ".msi files". On the other hand, the multiple driver installer 43 is a ".exe file".

Specifically, the CPU 21 reads the “.inf file” included in the multiple driver installer 43 from the multiple driver installer 43 and identifies the model that the multiple driver installer 43 is compatible with. The “.inf file” stores information indicating the models supported by the multiple driver installer 43 . Then, the CPU 21 determines whether or not the input model exists among the models supported by the multiple driver installer 43 .

In S40, if the multiple driver installer 43 corresponding to the input model is not stored in the shared storage 33, the CPU 21 downloads the single driver installer corresponding to the input model in S50, as shown in FIG. A message to the effect that extraction is not possible is displayed on the display unit 13, and the client management process ends.

On the other hand, if the multiple driver installer 43 corresponding to the input model is stored in the shared storage 33, the CPU 21 extracts the single driver installer corresponding to the input model from the multiple driver installer 43 in S60, Save in the shared storage 33 and proceed to S70.

After proceeding to S70, the CPU 21 determines whether or not the "organizational unit" corresponding to the input "organizational unit" (hereinafter referred to as "input organizational unit") is stored in the active directory 23 or not.

Here, when the "organizational unit" corresponding to the input organizational unit is stored in the active directory 23, the CPU 21 proceeds to S90. On the other hand, if the "organizational unit" corresponding to the input organizational unit is not stored in the active directory 23, the CPU 21 creates organizational unit information 93a corresponding to the input organizational unit in S80, and stores the information in the active directory 23. , and proceeds to S90. Specifically, the CPU 21 creates organizational unit information 93a by acquiring information indicating "users" and "computers" belonging to the input organizational unit via the input unit 14. FIG.

After proceeding to S90, the CPU 21 determines whether the second object information 94b of the single driver installer corresponding to the input model is stored in the active directory 23 or not.

As shown in FIG. 9, the first object information 94a and the second object information 94b have "object name" and "contents" as setting items.
A character string for identifying the first object information 94a and the second object information 94b is set in the "object name".

In the "contents" of the first object information 94a, the path of the file describing the IP address of the printer 5 (hereinafter referred to as address file) and the path of the address file storage destination are set. "C:\○○\PRINTER_IP_PARAM1.txt" in FIG. “C:\××\PRINTER_IP_PARAM1.txt” in FIG.

The "contents" of the second object information 94b is set with the path of the single driver installer. “¥¥Share¥ΔΔ¥Installer1.msi” in FIG. 9 is the path of the single driver installer stored in the shared storage 33 .

In S90, if the second object information 94b of the single driver installer corresponding to the input model is stored in the active directory 23, the CPU 21 proceeds to S110 as shown in FIG. On the other hand, if the second object information 94b of the single driver installer corresponding to the input model is stored in the active directory 23, the CPU 21 sets the path of the single driver installer corresponding to the input model in S100. The second object information 94b is created and stored in the active directory 23, and the process proceeds to S110.

In S110, the CPU 21 creates an address file that specifies the input "printer IP address" (hereinafter referred to as the input IP address), and furthermore, the created address file path and save destination path are set. First object information 94a is created. Then, the CPU 21 saves the created address file and the first object information 94a in the active directory 23, and shifts to S120.

In S120, the CPU 21 associates the organizational unit information 93a of the input organizational unit with the first object information 94a of the input IP address and the second object information 94b of the single driver installer corresponding to the input model. End management processing. Specifically, as shown in FIG. 9, the CPU 21 adds "group policy" as a setting item to the organizational unit information 93a, and adds the object information of the first and second object information 94a, 94b to this "group policy". Set first name.

In FIG. 9, as indicated by arrows L1 and L2, first object information 94a whose "object name" is "GP_PRINTER_IP_PARAM_1" and " is associated with the second object information 94b whose object name is "GP_PRINTER_INSTLLER_1".

In S120, if there are a plurality of second object information items 94b of the single driver installer corresponding to the input model, the CPU 21 selects the second object information item 94b of the single driver installer with the latest version, and selects the second object information item 94b. The obtained second object information 94b is associated with the organizational unit information 93a of the input organizational unit.

(4) Installation of Printer Driver in Client Device 4 Next, the procedure for installing the printer driver by the client device 4 will be described.
First, the client device 4 logs into the active directory 23 of the management device 2 . By logging into the active directory 23, the client device 4 obtains from the active directory 23 the first and second object information 94a, 94b associated with the organizational unit information 93a of the organizational unit to which the client device 4 belongs.

Then, the client device 4 refers to the acquired second object information 94b, downloads the single driver installer from the shared storage 33, and activates the downloaded single driver installer.

Further, the client device 4 acquires the address file from the storage unit 15 of the management device 2 by referring to the first object information 94a.
Then, the client device 4 uses the IP address described in the obtained address file to perform the installation. The printer driver is thereby installed in the client device 4 .

(5) Effect The management program 91 configured as described above is used in the management system 1 that manages the client device 4 .

The management system 1 includes a client device 4 , a management device 2 that manages the client device 4 , a printer 5 that executes processing based on instructions from the client device 4 , and a shared server 3 . The shared server 3 stores a multiple driver installer 43 comprising multiple single driver installers 43a, 43b, 43c for installing multiple printer drivers corresponding to multiple models of the printer 5, respectively.

The management program 91 is configured to cause the control unit 11 of the management device 2 to execute model acquisition processing, installer determination processing, and installer extraction processing.
The model acquisition process acquires the “printer model name” that identifies the model.

In the installer determination process, when the "printer model name" is acquired in the model acquisition process, the printer driver installer corresponding to the specific model indicated by the "printer model name" is included in the multiple driver installer 43. determine whether there is

The installer extracting process extracts the installer corresponding to the specific model from the multiple driver installer 43 when it is determined in the installer determination process that the installer corresponding to the specific model is included in the multiple driver installer 43 .

Such a management program 91 allows the user of the client device 4 to download the multiple driver installer 43 to the client device 4 and then input the "printer model name" on the client device 4 side to extract the installer. installation of the printer driver can be simplified.

The management program 91 also causes the control unit 11 to send registration information that associates the second object information 94b for accessing the installer extracted in the installer extraction process with the organizational unit information 93a that identifies the client device 4 to the active directory. 23 is configured to execute registration processing. This allows the client device 4 to easily obtain the second object information 94b for accessing the installer from the active directory 23. FIG.

Further, the registration process further associates and registers the organizational unit information 93a and the first object information 94a. Thereby, the client device 4 can easily obtain the IP address of the printer 5 by accessing the active directory 23 .

Further, the management program 91 causes the control unit 11 to execute an error notification process for notifying the same when the installer determination process determines that the installer corresponding to the specific model is not included in the multiple driver installer 43 . It is configured. Thereby, the management program 91 can make the user of the client device 4 aware of the fact that there is no installer corresponding to the specific model.

Further, in the registration process, when a plurality of installers corresponding to the specific model are extracted, the second object information 94b and the organizational unit information 93a of the installer with the latest version among the plurality of installers corresponding to the specific model are registered. Associate. As a result, the management program 91 can install the latest version of the printer driver on the client device 4 .

Also, the second object information 94b is set for each of a plurality of models. As a result, it is not necessary to provide the second object information 94b for each client device 4, and the storage capacity for storing the second object information 94b can be reduced.

In the embodiment described above, the shared server 3 corresponds to a storage device, the printer driver corresponds to a device driver, the "printer model name" corresponds to model identification information, and S10 and S20 are model acquisition processing and model acquisition processing. corresponds to a step.

Also, S40 corresponds to the installer determination process and the installer determination step, and S60 corresponds to the installer extraction process and the installer extraction step.
The second object information 94b corresponds to access information, the organizational unit information 93a corresponds to client identification information, the active directory 23 corresponds to an information management service, and S110 and S120 correspond to registration processing.

The first object information 94a corresponds to address information, and S50 corresponds to error notification processing.
[Second embodiment]
A second embodiment of the present disclosure will be described below with reference to the drawings. In addition, in the second embodiment, portions different from the first embodiment will be described. The same code|symbol is attached|subjected about a common structure.

The management system 1 of the second embodiment differs from that of the first embodiment in that client management processing is changed.
As shown in FIG. 10, the client management process of the second embodiment differs from that of the first embodiment in that the processes of S50 and S120 are omitted and the processes of S35, S65 and S125 are added.

That is, in S30, if the single driver installer corresponding to the input model is not stored in the shared storage 33, the CPU 21 proceeds to S40. On the other hand, if the single driver installer corresponding to the input model is stored in the shared storage 33, the CPU 21 confirms the version of the single driver installer stored in the shared storage 33 in S35, and transition to It should be noted that in S35, if there are a plurality of single driver installers corresponding to the input model, the CPU 21 confirms the version of each of the plurality of single driver installers.

Also, in S40, if the multiple driver installer 43 corresponding to the input model is not stored in the shared storage 33, the CPU 21 proceeds to S70.
Further, when the process of S60 ends, the CPU 21 checks the version of the single driver installer saved in S60 in S65, and proceeds to S70. It should be noted that in S65, if there are a plurality of single driver installers saved in S60, the CPU 21 confirms the version of each of the plurality of single driver installers.

When the process of S110 ends, the CPU 21 adds the first object information 94a of the input IP address and the second object of the single driver installer corresponding to the input model to the organizational unit information 93a of the input organizational unit in S125. information 94b, and the client management process ends.

In S125, if there are a plurality of second object information items 94b of the single driver installer corresponding to the input model, the CPU 21 selects the newest single driver installer based on the version confirmation results in S35 and S65. and associates the selected second object information 94b with the organizational unit information 93a of the input organizational unit.

In the embodiment described above, S110 and S125 correspond to registration processing.
An embodiment of the present disclosure has been described above, but the present disclosure is not limited to the above embodiment, and can be implemented in various modifications.

For example, in the above embodiment, the version is confirmed by analyzing the single driver installer. However, version information may be registered in advance in a table or the like for each of a plurality of single driver installers, and the single driver installer with the latest version may be selected by referring to this table.

Moreover, in the above-described embodiment, the device of the present disclosure is the printer 5 . However, the device of the present disclosure may be a multifunction machine, a copier, and a facsimile having a scanner function for reading an image from an original.

A plurality of functions possessed by one component in the above embodiment may be implemented by a plurality of components, or a function possessed by one component may be implemented by a plurality of components. Also, a plurality of functions possessed by a plurality of components may be realized by a single component, or a function realized by a plurality of components may be realized by a single component. Also, part of the configuration of the above embodiment may be omitted. Also, at least part of the configuration of the above embodiment may be added or replaced with respect to the configuration of the other above embodiment.

In addition to the management device 2 described above, a system having the management device 2 as a component, a program for causing a computer to function as the management device 2, a non-transitional physical recording medium such as a semiconductor memory in which this program is recorded, management The present disclosure can also be implemented in various forms, such as methods.

DESCRIPTION OF SYMBOLS 1... Management system, 2... Management apparatus, 3... Shared server, 4... Client apparatus, 5... Printer, 11... Control part, 43... Multiple driver installer, 91... Management program

Claims (8)

A management program used in a management system that manages a client device,
The management system includes:
the client device;
a management device that manages the client device;
a device that executes processing based on instructions from the client device;
A device driver is a program for controlling the device from the client device, and an installer is a program for installing the device driver in the client device, and each of the plurality of device drivers corresponding to the plurality of models of the device. a storage device storing a plurality of driver installers comprising a plurality of said installers for installing
The management program causes a controller provided in the management device to:
a model acquisition process for acquiring model identification information for identifying the model;
When the model identification information is obtained in the model obtaining process, it is determined whether or not the installer of the device driver corresponding to the specific model indicated by the model identification information is included in the multiple driver installer. an installer judgment process to
an installer extracting process for extracting the installer corresponding to the specific model from the multiple driver installer when the installer determining process determines that the installer corresponding to the specific model is included in the multiple driver installer. A management program that is configured to run. The management program according to claim 1,
to the control unit,
a registration process for registering, in an information management service, registration information that associates access information for accessing the installer extracted in the installer extraction process with client identification information that identifies the client device; management program. The management program according to claim 2,
The management program in which the registration processing further associates and registers the client identification information and the address information of the device. The management program according to any one of claims 1 to 3,
to the control unit,
A management program configured to, when the installer determination process determines that the installer corresponding to the specific model is not included in the multiple driver installer, execute an error notification process for notifying that effect. The management program according to claim 2,
In the registration process, when a plurality of the installers corresponding to the specific model are extracted, the access information of the installer having the latest version among the plurality of installers corresponding to the specific model, and the client identification A management program that associates information with. The management program according to claim 2,
A management program in which the access information is set for each of the plurality of models. A management method executed by the management device of a management system comprising a client device and a management device that manages the client device,
The management system further comprises:
a device that executes processing based on instructions from the client device;
A device driver is a program for controlling the device from the client device, and an installer is a program for installing the device driver in the client device, and each of the plurality of device drivers corresponding to the plurality of models of the device. a storage device storing a plurality of driver installers comprising a plurality of said installers for installing
The management method is
a model acquisition step of acquiring model identification information that identifies the model;
When the model identification information is obtained in the model obtaining step, it is determined whether or not the installer of the device driver corresponding to the specific model indicated by the model identification information is included in the multiple driver installer. an installer decision step to
an installer extracting step of extracting the installer corresponding to the specific model from the multiple driver installer when the installer determining step determines that the installer corresponding to the specific model is included in the multiple driver installer. Prepared management method. a client device;
a management device that manages the client device;
a device that executes processing based on instructions from the client device;
A device driver is a program for controlling the device from the client device, and an installer is a program for installing the device driver in the client device, and each of the plurality of device drivers corresponding to the plurality of models of the device. a storage device storing a plurality of driver installers comprising a plurality of said installers for installing
The management device
a model acquisition process for acquiring model identification information for identifying the model;
When the model identification information is obtained in the model obtaining process, it is determined whether or not the installer of the device driver corresponding to the specific model indicated by the model identification information is included in the multiple driver installer. an installer judgment process to
an installer extracting process for extracting the installer corresponding to the specific model from the multiple driver installer when the installer determining process determines that the installer corresponding to the specific model is included in the multiple driver installer. A management system that is configured to run.

Images