JP2018194910A - Information processing device, driver installation method and program - Google Patents

Abstract

To generate a print queue of a driver provided by a manufacturer of a device, while deleting the print queue of a general-purpose driver provided by an OS, generated associating with the device.SOLUTION: An information processing device comprises: registration means which registers a driver provided by a manufacturer of a device; acquisition means which acquires PnP-X ID by using UUID of the device and a print port name of the information processing device; deletion means which deletes a print queue, when the print queue of the driver installed in the information processing device is allocated to a print port in which the PnP-X ID was acquired, and the driver corresponding to the print queue does not correspond to the registered driver; and generation means which generates the print queue of the registered driver which is assigned to a WSD communication port.SELECTED DRAWING: Figure 6

Description

  The present invention relates to a device driver installation technique.

  The types of device drivers installed on the computer can be roughly classified into two types. One is a driver provided by the device manufacturer, which is called an Outbox driver. The other is a driver provided by the OS, and these are called Inbox drivers. In general, the Outbox driver has a better function than the Inbox driver, and the device manufacturer recommends using the Outbox driver.

  The Windows (registered trademark) OS provides a PnP-X (Plug and Play Extension for Network Connected Device) function. The Windows OS detects a device based on its PnP-X function, and automatically installs an Inbox driver associated with the device in the computer. In other words, the Inbox driver is automatically installed in the computer simply by connecting the computer and the device via a network.

  When installing the Outbox driver after the Inbox driver is installed, automatic device detection is not performed by the PnP-X function. Therefore, the user may delete the Inbox driver and then install the Outbox driver. In this case, for example, the Inbox driver can be deleted by applying the method of Patent Document 1. Patent Document 1 discloses a technique for selectively deleting a printer driver installed in a computer by referring to unique deletion information added to the printer driver.

Japanese Patent No. 3346997

  The latest OS, Windows 10 (registered trademark), is equipped with a standard driver for Microsoft Mobile Print (hereinafter referred to as “MMP”), and this MMP driver has a specification common to all device manufacturers.

  Therefore, when installing the Outlook driver after deleting the MMP driver, there is a problem that even the print queue of the MMP driver associated with another device with a different manufacturer is deleted unintentionally.

  The present invention has been made in view of the above problems. In other words, an object is to generate a print queue for a driver provided by a device manufacturer while deleting a print queue for a general-purpose driver provided by an OS generated in association with the device.

  An information processing apparatus according to the present invention includes a registration unit that registers a driver provided by a device manufacturer, an acquisition unit that acquires a PnP-X ID using the UUID of the device and a print port name of the information processing apparatus, The print queue of the driver installed in the information processing apparatus is assigned to the print port from which the PnP-X ID has been acquired, and the driver corresponding to the print queue does not match the registered driver And deleting means for deleting the print queue, and generating means for assigning and generating a print queue of the registered driver to a WSD communication port.

  According to the present invention, it is possible to generate a print queue for a driver provided by a device manufacturer while deleting a print queue for a general-purpose driver provided by an OS that is generated in association with a device.

2 is a configuration example of an information processing system in the first embodiment. 3 is a hardware configuration example of a computer according to the first embodiment. 3 is a hardware configuration example of a device according to the first embodiment. 3 is a functional configuration example of software in the first embodiment. 4 is a flowchart illustrating a processing procedure of a driver installer in the first embodiment. 6 is a flowchart illustrating a print queue generation procedure according to the first exemplary embodiment. 10 is a flowchart illustrating a print queue generation procedure according to the second embodiment. 6 is a diagram illustrating an example of a device setting confirmation window according to Embodiment 1. FIG.

[Embodiment 1]
Hereinafter, embodiments for carrying out the present invention will be described with reference to the drawings. However, the configuration described in this embodiment is merely an example, and is not intended to limit the scope of the present invention.

(Configuration of information processing system)
FIG. 1 is a block diagram illustrating a configuration example of an information processing system according to the present embodiment. The information processing system 1 according to the present embodiment includes a computer 100 and devices 200 and 400. As shown in FIG. 1, the subnetwork A to which the computer 100 and the device 200 belong and the subnetwork B to which the device 400 belongs are connected via a router 300. The computer 100 is an information processing apparatus such as a PC (personal computer) or a tablet. The devices 200 and 400 are peripheral devices such as a printer, a copier, a facsimile machine, a scanner, etc., or an apparatus having a composite function thereof. The devices 200 and 400 support the TCP / IP protocol and also support WSD (Web Services on Devices), which is a network protocol of the Microsoft Windows OS standard. The configuration of the information processing system 1 is an example, and is not limited to the configuration of the information processing system 1 of FIG. For example, the number of computers and devices belonging to each of the subnetwork A and the subnetwork B is not limited to the configuration of the information processing system 1 in FIG. 1 and may be plural.

(Computer hardware configuration)
FIG. 2 is a block diagram illustrating a hardware configuration example of the computer 100 according to the present embodiment. The computer 100 includes a CPU 101, a RAM 102, a ROM 103, a graphic controller 104, a display unit 105, and an auxiliary storage device 106. Further, the computer 100 includes an external connection interface 107 (hereinafter referred to as “I / F”) and a network I / F 108, and each component is connected via a bus 109 so as to be communicable. The CPU 101 includes an arithmetic circuit and controls the computer 100 as a whole. The CPU 101 reads out the program stored in the ROM 103 or the auxiliary storage device 106 to the RAM 102 and executes various processes. The ROM 103 stores system software such as BIOS used for controlling the computer 100. The graphic controller 104 generates a screen to be displayed on the display unit 105. The display unit 105 is configured by an LCD (liquid crystal display) or the like, and displays a screen generated by the graphic controller 104. The display unit 105 may have a touch screen function. In that case, a user instruction accepted through the display unit 105 can be handled as an input to the computer 100. The auxiliary storage device 106 has a function as a storage area, and stores an OS (Operating System), a device driver for controlling various devices, an application program for executing various processes, and the like. The auxiliary storage device 106 is an example of a storage device, and can be configured by an SSD (solid state drive) or the like in addition to the HDD (hard disk drive). The device driver stored in the auxiliary storage device 106 includes driver software used for controlling various devices including the devices 200 and 400. Examples of such driver software include a scanner driver, a printer driver, and a facsimile driver. The external connection I / F 107 is an interface for connecting various devices to the computer 100. For example, a pointing device such as a keyboard and a mouse can be connected via the external connection I / F 107. The network I / F 108 communicates with the devices 200 and 400 via the network based on the control of the CPU 101.

  The auxiliary storage device 106 according to the present embodiment also stores a driver installer necessary for installing driver software (hereinafter simply referred to as “driver”) on the target device. In the present embodiment, the target device means a device that is a target for installing the device. This driver installer has a device search function based on the TCP / IP protocol and a device search function based on the WSD protocol. In the present embodiment, the driver installer has a configuration including a device search function based on the TCP / IP protocol and a device search function based on the WSD protocol. However, the embodiment is not limited to the configuration described above. In another embodiment, the auxiliary storage device 106 may store a dedicated module having a device search function by the TCP / IP protocol and a dedicated module having a device search function by the WSD. In that case, the device search may be executed by calling these dedicated modules from the device driver or application.

(Device hardware configuration)
FIG. 3 is a block diagram illustrating a hardware configuration example of the devices 200 and 400 in the present embodiment. The devices 200 and 400 include a CPU 201, a RAM 202, a ROM 203, a graphic controller 204, a display unit 205, and an operation unit 206. Furthermore, the devices 200 and 400 include a network I / F 207 and a printing unit 208, and each component unit is communicably connected via a bus 209. The CPU 201 includes an arithmetic circuit and controls the devices 200 and 400 in an integrated manner. The CPU 201 reads a program stored in the ROM 203 to the RAM 202 and executes various processes. The ROM 203 stores programs and data used for controlling the devices 200 and 400. The graphic controller 204 generates a screen to be displayed on the display unit 205. The display unit 205 is configured by an LCD (Liquid Crystal Display) or the like, and displays a screen generated by the graphic controller 204. The operation unit 206 includes a touch panel, hardware keys, and the like, and can accept user instructions. A network I / F 207 communicates with an external device via a network based on the control of the CPU 201. The printing unit 208 forms characters and images on a recording medium such as paper based on a print job transmitted from the computer 100 and image data read by the devices 200 and 400 themselves. The configuration of the devices 200 and 400 shown in FIG. 3 is a configuration in the case where the devices 200 and 400 are printers. When the devices 200 and 400 are scanners, the devices 200 and 400 further include a reading unit that reads characters and images formed on a recording medium such as paper.

(Software function configuration)
FIG. 4 is a block diagram showing a software functional configuration of the computer 100 in the present embodiment. The function of each block shown in FIG. 4 is realized by the CPU 101 reading the program code of the application (driver installer) 110 into the RAM 102 and executing it.

  The application 110 searches for a device connected to the network, and installs a driver associated with the device selected by the user from the searched devices in the computer 100. If the device selected by the user is a printer, the application 110 installs the printer driver 122 in the computer 100. If the device selected by the user is a scanner, the scanner driver 123 is installed in the computer 100. The utility 124 is installed in the computer 100 as appropriate according to the type of device selected by the user.

  The device detection unit 111 acquires device driver information from the driver INF file 121. The driver information includes a driver name.

  The TCP / IP device search unit 112 searches for a device connected to the computer 100 via the network using the TCP / IP protocol. The application 110 displays information on the device detected by the search on the display unit 105. In the present embodiment, a device name, an IP address, a MAC address, and the like are displayed on the display unit 105 as information about the device. Information regarding these devices is information that can be used to identify the target device. Further, the application 110 registers, in the computer 100, a driver used for controlling the selected device among the information on the device displayed on the display unit 105.

  The WSD device search unit 113 searches for a selected device from devices connected to the same subnetwork as the subnetwork to which the computer 100 belongs by the WSD protocol. According to the WSD specification, the search using the WSD protocol cannot search for devices from the subnetwork beyond the router 300. Therefore, referring to FIG. 1 as an example, the WSD device search unit 113 can search for the device 200 connected to the sub-network A, but cannot search for the device 400 connected to the sub-network B. If the WSD device search unit 113 detects a device connected to the same subnetwork as the subnetwork to which the computer 100 belongs, the application 110 determines that communication with the device is possible using the WSD protocol.

  The UUID acquisition unit 114 acquires the UUID of the device detected by the WSD device search unit 113.

  The Inbox driver detection unit 115 acquires a list of print ports included in the computer 100, and acquires a PnP-X ID from the port monitor using the UUID and the print port name. Next, the Inbox driver detection unit 115 acquires a list of print queues already installed in the computer 100, and determines whether each print queue is assigned to the print port from which the PnP-X ID has been acquired. In this embodiment, it is determined whether or not the print queue is allocated to the WSD communication port by determining whether or not the PnP-X ID is allocated to the acquired print port. Further, the Inbox driver detection unit 115 determines whether or not the driver corresponding to the print queue matches the driver registered by the application 110. The PnP-X ID is an abbreviation for PnP-X Identifier, and is an identifier that uniquely identifies a device detection result by the PnP-X function.

  If the driver does not match the registered driver, the WSD device registration unit 116 deletes the target device from the association database (association database) that is controlled by the OS and used for device management. When the target device is deleted from the association database, the OS deletes the print queue of the Inbox driver (a general-purpose driver provided by the OS) associated with the target device.

  The WSD device registration unit 116 registers the target device again in the OS database. When the target device is registered again in the OS database, the PnP-X function of the OS is triggered, and the print queue of the registered driver is assigned to the WSD communication port and generated.

(Processing procedure of driver installer)
FIG. 5 is a flowchart showing the processing procedure of the driver installer in this embodiment. The processing of the flowchart shown in FIG. 5 is performed by the CPU 101 developing the program code of the application 110 in the RAM 102 and executing it. Each symbol S below means a step in the flowchart. The same applies to the flowcharts of FIG. 6 and subsequent figures.

  In step S <b> 501, the device detection unit 111 acquires device driver information from the driver INF file 121. The driver information includes a driver name.

  In S502, the TCP / IP device search unit 112 searches for a device connected to the same subnet as the subnet to which the computer 100 belongs by using the TCP / IP protocol. Further, the TCP / IP device search unit 112 searches for a device connected to the subnet beyond the router 300.

  In step S <b> 503, it is determined whether or not a device matching the device name acquired from the driver INF file 121 has been detected by device search using the TCP / IP protocol. If a matching device is detected (S503: YES), the process proceeds to S504. If no matching device is detected (S503: NO), the process proceeds to S512.

  In step S <b> 504, information related to the device detected in step S <b> 503 is displayed on the display unit 105. In the present embodiment, a device name, an IP address, a MAC address, and the like are displayed on the display unit 105 as information about the device. Information regarding these devices is information that can be used to identify the target device. When a plurality of devices are detected in S503, information regarding the plurality of devices is displayed in a list.

  In step S <b> 505, a driver used to control the selected device among the information on the device displayed on the display unit 105 is registered in the computer 100. In the present embodiment, a device is selected based on a user instruction input to the display unit 105 having a touch panel function. In the present embodiment, an Outlook driver provided by the manufacturer of the device 200 is registered in the computer 100.

  In step S506, the WSD device search unit 113 searches for the device selected in step S505 from the devices connected to the same subnet as the subnet to which the computer 100 belongs, using the WSD protocol.

  In S507, it is determined whether or not the device selected in S505 is detected from a device connected to the same subnet to which the computer 100 belongs by device search using the WSD protocol. When a device is detected (S507: YES), the process proceeds to S508. When a device is not detected (S507: NO), it transfers to S510.

  If a device is detected (S507: YES), it is determined that communication using the WSD protocol is possible between the computer 100 and the device. In step S508, a communication port used for communication with the device is determined as a WSD communication port capable of communication using the WSD protocol.

  In step S509, the UUID acquisition unit 114 acquires the UUID of the device detected in step S507.

  In step S600, the application 110 generates a driver print queue used for controlling the device detected in step S507. Details of S600 will be described later. When the process of S600 is completed, the process of this flowchart is terminated.

  If no device is detected (S507: NO), it is determined that communication using the WSD protocol is impossible between the computer 100 and the device. In step S510, a communication port used for communication between the computer 100 and the device is determined as a TCP / IP communication port capable of communication using the TCP / IP protocol.

  In step S511, the application 110 generates a print queue for the driver used for controlling the device detected in step S507. More specifically, the application 110 creates the driver print queue registered in S505 by assigning it to the TCP / IP communication port. When the process of S511 is completed, the process of this flowchart is terminated.

  If no device matching the driver information is detected by device search using the TCP / IP protocol (S503: NO), a device setting confirmation window is displayed on the display screen of the display unit 105 in S512.

  FIG. 8 is a diagram showing an example of a device setting confirmation window in the present embodiment. The confirmation window 801 of the present embodiment includes a message indicating that a device that matches the driver information (device name) acquired from the driver INF file 121 has not been detected. When the input to the retry button 802 in the confirmation window 801 is accepted (S513: YES), the process returns to S502 again. On the other hand, when the input to the cancel button 803 in the confirmation window 801 is accepted (S513: NO), the processing of this flowchart is terminated.

(Print queue creation procedure)
FIG. 6 is a flowchart showing details of the print queue generation procedure (S600) in the present embodiment. Hereinafter, this will be described in detail with reference to FIG.

  In step S <b> 601, the Inbox driver detection unit 115 acquires a list of print ports included in the computer 100.

  In step S602, it is determined whether or not processing has been completed for all print ports. If processing has not been completed for all print ports (S602: NO), the process proceeds to S603. If the processing has been completed for all the print ports (S602: YES), the processing loop of S602 to S603 is exited and the process proceeds to S604.

  In step S603, the PnP-X ID is acquired from the port monitor using the UUID acquired in step S509 and the print port name of the computer 100. The process of acquiring the PnP-X ID from the port monitor is performed for each processing loop from S602 to S603 from the print port name described at the top of the list to the print port name described at the bottom of the list. It is executed in order. When the process of S603 ends, the process returns to the determination process of S602 again. In the present embodiment, it is assumed that the port monitor function is provided by the OS of the computer 100.

  In step S604, a list of print queues already installed in the computer 100 is acquired. Specifically, when various drivers are installed in the computer 100, a list of print queues generated by the installer is acquired.

  In step S605, it is determined whether the processing has been completed for all print queues. If the processing has not been completed for all the print queues (S605: NO), the process proceeds to S606. If the processing has been completed for all the print queues (S605: YES), the processing loop of S605 to S607 is exited and the process proceeds to S610.

  In S606, it is determined whether the print queue is assigned to the print port from which the PnP-X ID has been acquired. The determination processing of S606 is executed in order for each processing loop of S605 to S607 from the print queue name described at the top of the list to the print queue name described at the bottom of the list. In this embodiment, it is determined whether or not the print queue is assigned to the WSD communication port by determining whether or not the PnP-X ID is assigned to the acquired print port. When the print queue is assigned to the print port from which the PnP-X ID has been acquired (S606: YES), the process proceeds to S607. If not assigned (S606: NO), the process returns to the determination process of S605 again.

  In step S607, the Inbox driver detection unit 115 determines whether the driver corresponding to the print queue matches the driver registered in step S505. If the driver matches the registered driver (S607: YES), the process returns to the determination process of S605 again. On the other hand, if the driver does not match the registered driver (S607: NO), the process loops from S605 to S607 is exited and the process proceeds to S608.

  In step S608, the WSD device registration unit 116 deletes the target device from the OS database.

  In S609, when the target device is deleted from the OS database (S608), the print queue of the Inbox driver (a general-purpose driver provided by the OS) associated with the target device is deleted by the OS. In order to delete the print queue of the Inbox driver, a method of directly specifying the name of the print queue to be deleted can be considered, but this method is not applied in this embodiment. This is because the name of the print queue can be freely changed, and the print queue to be deleted may not be specified by the name of the print queue.

  In step S610, the WSD device registration unit 116 registers the target device in the OS database again.

  In S611, when the target device is registered again in the OS database (S610), the PnP-X function of the OS is triggered, and the driver print queue registered in S505 is assigned to the WSD communication port and generated. When the process of S611 is completed, the process of this flowchart is terminated, and the process returns to the flowchart of FIG.

  As described above, according to the driver installation method of the present embodiment, the print queue is generated in consideration of the characteristics of the general-purpose driver provided by the OS. Therefore, the driver installation method of the present embodiment can generate a driver print queue provided by the device manufacturer while deleting the general-purpose driver print queue provided by the OS, which is generated in association with the device. .

[Embodiment 2]
According to the first embodiment, the print queue of the driver (Outbox driver) provided by the device manufacturer is generated while deleting the print queue of the general-purpose driver (Inbox driver) provided by the OS generated in association with the device. be able to. However, the method of the first embodiment causes a problem in the following use cases. In other words, when a plurality of Outbox drivers are already installed and a part of the plurality of Outbox drivers is updated, the print queue of the non-update target Outbox driver is deleted. In view of the above problem, the driver installation method according to the second exemplary embodiment can update the update target Outlook driver while holding the print queue of the non-update target Outlook driver. Hereinafter, the description of the parts common to the first embodiment will be simplified or omitted, and the following description will focus on the points peculiar to the present embodiment.

(Print queue creation procedure)
Since S601 to S605 are the same as those in the first embodiment, description thereof is omitted.
In S701, the determination result in S606 is stored in a storage area such as the auxiliary storage device 106. That is, the print queue name assigned to the print port from which the PnP-X ID has been acquired is stored for each processing loop of S605 to S702. The print queue name stored in S701 is referred to in the determination process in S703 described later.

Since S607 is the same as that of the first embodiment, description thereof is omitted.
In S <b> 702, the determination result in S <b> 607 is stored in a storage area such as the auxiliary storage device 106. In other words, the print queue name determined to match the registered driver (for example, the Outbox driver) is stored for each processing loop of S605 to S702. The print queue name stored in S702 is referred to in the determination process in S703 described later. If the processing has been completed for all the print queues (S605: YES), the process proceeds to S703 to determine whether or not to delete the target device from the OS database.

  In step S703, the determination result stored in step S701 is referred to, and it is determined whether there is at least one print queue assigned to the print port for which the PnP-X ID has been acquired. If there is at least one print queue that satisfies the conditions (S703: YES), the process proceeds to S704. If there is no print queue that satisfies the conditions (S703: NO), S704 to S609 are skipped and the process proceeds to S610.

In S704, the determination result stored in S702 is referred to, and it is determined whether or not any driver corresponding to the print queue satisfying the condition in S703 matches the driver registered in S505. If none of them matches the registered driver (S704: YES), the process proceeds to S608. If there is a print queue that matches the registered driver (S704: NO), S608 to S609 are skipped and the process proceeds to S610.
Since S608 to S611 are the same as those in the first embodiment, description thereof is omitted. When the process of S611 is completed, this flowchart is ended, and the process returns to the flowchart of FIG.

  As described above, according to the driver installation method of the present embodiment, it is possible to update the update target Outlook driver while holding the print queue of the non-update target Outlook driver.

  Hereinafter, the case where the update target GDI driver and the non-update target XPS driver are already installed in the computer 100 will be described as a specific example for the target device 200. Both the GDI driver and the XPS driver are Outbox drivers, and these print queues are assigned to the WSD communication port. In this case, in the method of the first embodiment, it is determined that the non-update target XPS driver does not match the registered driver (S607: NO), and therefore the XPS driver print queue is determined to be the deletion target print key. . On the other hand, in the method of the present embodiment, the determination process (S703 to S704) taking into account a plurality of Outbox drivers (including GDI drivers and XPS drivers) is executed, so the print queue of the XPS driver to be updated is deleted The print key is not determined. With this configuration, the technique of this embodiment can update the update target Outlook driver while holding the print queue of the non-update target Outlook driver.

(Other examples)
The present invention supplies a program that realizes one or more functions of the above-described embodiments to a system or apparatus via a network or a storage medium, and one or more processors in a computer of the system or apparatus read and execute the program This process can be realized. It can also be realized by a circuit (for example, ASIC) that realizes one or more functions.

1. Information processing system 100 Computer 200 Device 400 Device 110 Application (installer)
111 ·· Device detection unit 112 · · TCP / IP device search unit 113 · · WSD device search unit 114 · · UUID acquisition unit 115 · · Inbox driver detection unit 116 · · WSD device registration unit

Claims (12)

An information processing apparatus,
A registration means for registering a driver provided by the device manufacturer;
Obtaining means for obtaining a PnP-X ID using the UUID of the device and the print port name of the information processing apparatus;
The print queue of the driver installed in the information processing apparatus is assigned to the print port from which the PnP-X ID has been acquired, and the driver corresponding to the print queue does not match the registered driver Deleting means for deleting the print queue;
An information processing apparatus comprising: a generation unit configured to allocate and generate a print queue of the registered driver to a WSD communication port. An information processing apparatus,
A registration means for registering a driver provided by the device manufacturer;
Obtaining means for obtaining a PnP-X ID using the UUID of the device and the print port name of the information processing apparatus;
When there is at least one print queue assigned to the print port from which the PnP-X ID has been acquired and none of the drivers corresponding to the print queue match the registered driver, A deletion means for deleting the print queue;
An information processing apparatus comprising: a generation unit configured to allocate and generate a print queue of the registered driver to a WSD communication port.   The deletion unit is configured to delete the print queue of the driver associated with the device in response to deletion of information indicating the device from a database used for managing the device. Or the information processing apparatus according to 2;   The said generation means allocates the print queue of the said registered driver to the said WSD communication port, and produces | generates according to the information which shows the said device being registered into the said database. Information processing device.   The information processing apparatus according to any one of claims 1 to 4, wherein the acquisition unit acquires the PnP-X ID from a port monitor that is a function provided by an OS of the information processing apparatus. A method for installing a driver in an information processing apparatus,
A registration step for registering a driver provided by the device manufacturer;
An acquisition step of acquiring a PnP-X ID using the UUID of the device and the print port name of the information processing apparatus;
The print queue of the driver installed in the information processing apparatus is assigned to the print port from which the PnP-X ID has been acquired, and the driver corresponding to the print queue does not match the registered driver Deleting the print queue; and
A driver installation method comprising: generating a print queue of the registered driver by assigning it to a WSD communication port. A method for installing a driver in an information processing apparatus,
A registration step for registering a driver provided by the device manufacturer;
An acquisition step of acquiring a PnP-X ID using the UUID of the device and the print port name of the information processing apparatus;
When there is at least one print queue assigned to the print port from which the PnP-X ID has been acquired and none of the drivers corresponding to the print queue match the registered driver, A delete step to delete the print queue;
A driver installation method comprising: generating a print queue of the registered driver by assigning it to a WSD communication port. A program for causing an information processing apparatus to function.
A registration means for registering a driver provided by the device manufacturer;
Obtaining means for obtaining a PnP-X ID using the UUID of the device and the print port name of the information processing apparatus;
The print queue of the driver installed in the information processing apparatus is assigned to the print port from which the PnP-X ID has been acquired, and the driver corresponding to the print queue does not match the registered driver Deleting means for deleting the print queue;
A program for causing an information processing apparatus to function as an information processing apparatus including: a generation unit that allocates and generates a print queue of the registered driver to a WSD communication port. A program for causing an information processing apparatus to function.
A registration means for registering a driver provided by the device manufacturer;
Obtaining means for obtaining a PnP-X ID using the UUID and print port name of the device;
When there is at least one print queue assigned to the print port from which the PnP-X ID has been acquired and none of the drivers corresponding to the print queue match the registered driver, A deletion means for deleting the print queue;
A program for causing an information processing apparatus to function as an information processing apparatus including: a generation unit that allocates and generates a print queue of the registered driver to a WSD communication port.   9. The deletion unit is configured to delete the print queue of a driver associated with the device in response to deletion of information indicating the device from a database used for managing the device. Or the program of 9.   11. The generation unit according to claim 10, wherein when the information indicating the device is registered in the database, the generation unit allocates and generates a print queue of the registered driver to the WSD communication port. Program.   The program according to any one of claims 8 to 11, wherein the acquisition unit acquires the PnP-X ID from a port monitor that is a function provided by an OS of the information processing apparatus.

Images