Program, Client, and System

The solution simplifies the setup of a printing environment by using an information acquisition unit, tool creation unit, notification unit, authentication registration unit, and test printing unit to configure a shared printer across different OS environments.

JP7707784B2Active Publication Date: 2025-07-15RICOH CO LTD
View PDF 5 Cites 0 Cited by

Patent Information

Application Number
JP2021148916
Authority / Receiving Office
JP · JP
Patent Type
Patents
Current Assignee / Owner
Filing Date
2021-09-13
Publication Date
2025-07-15
Estimated Expiration
2041-09-13

AI Technical Summary

Technical Problem

Conventional methods require numerous procedures on a client operating a second OS to set up a printing environment using a shared printer installed on a server with a first OS.

Method used

An information acquisition unit gathers necessary information for setting up a client with a second OS, a tool creation unit generates a tool for the second OS, and a notification unit sends guidance for setting, along with an authentication registration unit and a test printing unit to ensure accurate printer configuration.

Benefits of technology

The printing environment from a client with a second OS using a shared printer of a server with a first OS is set accurately with fewer procedures.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure 0007707784000002
    Figure 0007707784000002
  • Figure 0007707784000003
    Figure 0007707784000003
  • Figure 0007707784000004
    Figure 0007707784000004
Patent Text Reader

Abstract

To carry out accurate setting of a print environment from a client with an installed second OS utilizing a shared printer of a server with an installed first OS with less procedure.SOLUTION: A program causes a computer operating in a first OS (Operating System) to function as: an information acquisition unit which acquires, as information, information required for setting in a client with an installed second OS different from the first OS and a printer driver package of a shared printer set to be shared in the first OS; a tool creation unit which creates a tool for the second OS which reflects the information in a program operating in the client and places the tool in a shared folder for connection from the client; and a notification unit which receives a destination input for notification of guidance of the setting to the client and transmits the notification to a destination.SELECTED DRAWING: Figure 4
Need to check novelty before this filing date? Find Prior Art

Description

Technical Field

[0001] The present invention relates to a program , Ku client and a system.

Background Art

[0002] Conventionally, there has been disclosed a technique for performing printing from a client operating on a second OS different from a first OS by using a shared printer shared and set on a server operating on the first OS.

[0003] Also, Patent Document 1 discloses a technique for using a shared printer between a server operating on a second OS and a client operating on the second OS.

Summary of the Invention

Problems to be Solved by the Invention

[0004] However, in printing from a client operating on a second OS using a shared printer shared and set on a server operating on a conventional first OS, there is a problem that many procedures are required on the client side operating on the second OS.

[0005] The present invention has been made in view of the above, and an object thereof is to set a printing environment from a client installed with a second OS that accurately uses a shared printer of a server installed with a first OS with fewer procedures.

Means for Solving the Problems

[0006] In order to solve the above-described problems and achieve the object, the present invention provides an information acquisition unit that acquires, as information, a computer operating on a first operating system (OS), information necessary for setting in a client in which a second OS different from the first OS is installed, and a printer driver package of a shared printer shared-set in the first OS; a tool creation unit that creates and arranges a tool for the second OS in which the information is reflected in a program operating on the client in a shared folder for connecting from the client; and a notification unit that receives a destination input for notifying a setting guidance for the client and transmits a notification to the destination. An authentication registration unit that receives a username and password for authentication to connect to the server and registers them in the keychain function of the second OS; and a test printing unit that returns to the registration in the keychain function in the authentication registration unit when test printing fails after registration of the print queue. It is characterized by functioning as.

Effect of the Invention

[0007] According to the present invention, there is an effect that the printing environment from a client in which a second OS is installed using a shared printer of a server in which a first OS is installed can be accurately set with fewer procedures.

Brief Description of the Drawings

[0008]

Figure 1

Figure 2

Figure 3

Figure 4

Figure 5

Figure 6

Figure 7

Figure 8

Figure 9

Figure 10

Figure 11

Figure 12

Figure 13

DETAILED DESCRIPTION OF THE INVENTION

[0009] Hereinafter, embodiments of a program, a server, a client, and a system will be described in detail with reference to the accompanying drawings.

[0010] FIG. 1 is a block diagram showing the overall configuration diagram of a printing system according to an embodiment. As shown in FIG. 1, the printing system includes one or more client personal computers (PCs) 300, a print server 400, and an image forming apparatus 100, which are connected via a network 500 such as the Internet. The print server 400 generally executes intermediate processing of print jobs. The image forming apparatus 100 executes print jobs. The image forming apparatus 100 is a multifunction device having at least two functions among a copy function, a printer function, a scanner function, and a facsimile function.

[0011] An outline of the printing process in the printing system will be described. Data created within an application equipped with a printing function operating on the client PC 300 is converted into a print job via a printer driver inside the client PC 300. The print job is transmitted from the client PC 300 to the image forming apparatus 100, and is edited and analyzed by a controller 910 (see FIG. 2) inside the image forming apparatus 100 and converted into printable raster data. The raster data is printed by a printer unit 932 (see FIG. 2) of the image forming apparatus 100.

[0012] Note that a print job may be sent from the client PC 300 to the print server 400, and after the print job is edited and necessary settings are made at the print server 400, the print job may be sent from the print server 400 to the image forming apparatus 100.

[0013] Alternatively, instead of sending a print job from the client PC 300, a document stored in the print server 400 in advance may be directly sent to the image forming apparatus 100.

[0014] Note that in the example of FIG. 1, one image forming apparatus 100 is illustrated in the printing system, but the present invention is not limited thereto, and the number and type of the image forming apparatuses 100 included in the printing system are arbitrary.

[0015] Next, the hardware configuration of the image forming apparatus 100 will be described.

[0016] FIG. 2 is a hardware configuration diagram of the image forming apparatus 100. As shown in FIG. 2, the image forming apparatus 100 includes a controller 910, a short-range communication circuit 920, an engine control unit 930, an operation panel 940, and a network I / F 950.

[0017] Among these, the controller 910 includes a CPU (Central Processing Unit) 901, which is the main part of a computer, a system memory (MEM-P) 902, a north bridge (NB) 903, a south bridge (SB) 904, an ASIC (Application Specific Integrated Circuit) 906, a local memory (MEM-C) 907, which is a storage unit, an HDD controller 908, and an HD 909, which is a storage unit, and is configured to connect between the NB 903 and the ASIC 906 via an AGP (Accelerated Graphics Port) bus 921.

[0018] Among these, the CPU 901 is a control unit that performs overall control of the image forming apparatus 100. The NB 903 is a bridge for connecting the CPU 901 to the MEM-P 902, the SB 904, and the AGP bus 921, and has a memory controller that controls reading and writing to the MEM-P 902, and a PCI (Peripheral Component Interconnect) master and an AGP target.

[0019] The MEM-P 902 consists of a ROM (Read Only Memory) 902a, which is a memory for storing programs and data for realizing the functions of the browser application and the controller 910, and a RAM (Random Access Memory) 902b, which is used as a memory for developing programs and data and for drawing during memory printing. Note that the programs stored in the RAM 902b may be provided in an installable or executable format as files recorded on a computer-readable recording medium such as a CD-ROM, a CD-R, or a DVD (Digital Versatile Disc).

[0020] SB904 is a bridge for connecting NB903 with PCI devices and peripheral devices. ASIC906 is an IC (Integrated Circuit) for image processing applications, which has hardware elements for image processing and serves as a bridge for connecting the AGP bus 921, PCI bus 922, HDD908, and MEM-C907 respectively. This ASIC906 consists of a PCI target and an AGP master, an arbiter (ARB) at the core of the ASIC906, a memory controller for controlling MEM-C907, multiple DMACs (Direct Memory Access Controllers) for performing operations such as rotation of image data by means of hardware logic, etc., and a PCI unit for performing data transfer via the PCI bus 922 between the scanner unit 931 and the printer unit 932. Note that interfaces for USB (Universal Serial Bus) or IEEE1394 (Institute of Electrical and Electronics Engineers 1394) may be connected to the ASIC906.

[0021] MEM-C907 is a local memory used as a copy image buffer and a code buffer. HD909 is a storage for accumulating image data, font data used at the time of printing, and forms. HD909 controls the reading or writing of data to / from HD909 according to the control of the CPU901. The AGP bus 921 is a bus interface for a graphics accelerator card proposed for speeding up graphic processing. By directly accessing MEM-P902 with high throughput, the graphics accelerator card can be made faster.

[0022] Also, the short-range communication circuit 920 is provided with a short-range communication circuit 920a. The short-range communication circuit 920 is a communication circuit such as NFC or Bluetooth (registered trademark).

[0023] Furthermore, the engine control unit 930 is composed of a scanner unit 931 and a printer unit 932. Also, the operation panel 940 includes a panel display unit 940a such as a touch panel that displays current setting values, selection screens, etc. and receives inputs from the operator, and an operation panel 940b composed of a numeric keypad that receives setting values of conditions related to image formation such as density setting conditions and a start key that receives a copy start instruction. The controller 910 controls the entire image forming apparatus 100, for example, controls drawing, communication, inputs from the operation panel 940, etc. The scanner unit 931 or the printer unit 932 includes an image processing part such as error diffusion and gamma conversion.

[0024] Note that the image forming apparatus 100 can sequentially switch and select the document box function, copy function, printer function, and facsimile function by using the application switching key on the operation panel 940. When the document box function is selected, it becomes the document box mode, when the copy function is selected, it becomes the copy mode, when the printer function is selected, it becomes the printer mode, and when the facsimile mode is selected, it becomes the facsimile mode.

[0025] Also, the network I / F 950 is an interface for data communication using the network 500. The short-range communication circuit 920 and the network I / F 950 are electrically connected to the ASIC 906 via the PCI bus 922.

[0026] Note that the program executed by the image forming apparatus 100 of the present embodiment may be stored on a computer connected to a network such as the Internet and provided by downloading it via the network. Also, the program executed by the image forming apparatus 100 of the present embodiment may be configured to be provided or distributed via a network such as the Internet.

[0027] Also, the program executed by the image forming apparatus 100 of the present embodiment may be configured to be provided by being pre-embedded in a ROM or the like.

[0028] Next, the hardware configurations of the client PC 300 and the print server 400 will be described.

[0029] FIG. 3 is a hardware configuration diagram of the client PC 300 and the print server 400. As shown in FIG. 3, the client PC 300 and the print server 400 are constructed by a computer, and as shown in FIG. 3, they include a CPU 501, a ROM 502, a RAM 503, an HD 504, an HDD (Hard Disk Drive) controller 505, a display 506, an external device connection I / F (Interface) 508, a network I / F 509, a bus line 510, a keyboard 511, a pointing device 512, a DVD-RW (Digital Versatile Disk Rewritable) drive 514, and a media I / F 516.

[0030] Among these, the CPU 501 controls the operations of the entire client PC 300 and the print server 400. The ROM 502 stores programs used for driving the CPU 501 such as the IPL. The RAM 503 is used as a work area for the CPU 501.

[0031] The HD 504 stores various data such as programs (including the OS (Operating System)). The HDD controller 505 controls reading and writing of various data to and from the HD 504 according to the control of the CPU 501. Note that the OS is system software that controls the operation of the computer. Note that the difference between the client PC 300 and the print server 400 is due to the different OSs stored in the HD 504.

[0032] The print server 400 stores a first OS in the HD 504. The first OS is, for example, Windows (registered trademark). The print server 400 exhibits the functions of the print server 400 when the CPU 501 operates according to the first OS.

[0033] The client PC 300 operates with a second OS different from the first OS. The second OS is, for example, Mac OS (registered trademark). The client PC 300 exhibits the functions as the client PC 300 when the CPU 501 operates according to the second OS.

[0034] The display 506 displays various information such as a cursor, menu, window, characters, or images. The external device connection I / F 508 is an interface for connecting various external devices. The external devices in this case are, for example, a USB (Universal Serial Bus) memory, printer, and the like. The network I / F 509 is an interface for performing data communication using the network 500. The bus line 510 is an address bus, data bus, etc. for electrically connecting each component such as the CPU 501 shown in FIG. 3.

[0035] Also, the keyboard 511 is a type of input means having a plurality of keys for input of characters, numerical values, various instructions, etc. The pointing device 512 is a type of input means for performing selection and execution of various instructions, selection of a processing target, movement of a cursor, etc. The DVD-RW drive 514 controls reading or writing of various data with respect to the DVD-RW 513 as an example of a removable recording medium. Note that it is not limited to DVD-RW, and it may be DVD-R or the like. The media I / F 516 controls reading or writing (storage) of data with respect to the recording medium 515 such as a flash memory.

[0036] The programs executed by the client PC 300 and the print server 400 in the present embodiment are provided by being recorded on a computer-readable recording medium such as a CD-ROM, flexible disk (FD), CD-R, DVD (Digital Versatile Disk) in an installable format or an executable format file.

[0037] Alternatively, the programs executed by the client PC 300 and the print server 400 of the present embodiment may be stored on a computer connected to a network such as the Internet and provided by being downloaded via the network. Further, the programs executed by the client PC 300 and the print server 400 of the present embodiment may be configured to be provided or distributed via a network such as the Internet.

[0038] Alternatively, the programs executed by the client PC 300 and the print server 400 of the present embodiment may be configured to be provided by being pre-installed in a ROM or the like.

[0039] Next, the functions exhibited when the CPU 501 of the print server 400 operates according to a program operating on the first OS will be described.

[0040] Here, FIG. 4 is a functional block diagram showing the functional configuration of the print server 400. As shown in FIG. 4, the print server 400 includes tools 404 for the first OS. The tools 404 for the first OS generally execute processes such as downloading the printer driver 406 for the second OS, creating the shared folder 402, creating the tools 405 for the second OS and placing them in the shared folder 402, and notifying with the mail app 403 based on user input and information on the shared printer 401.

[0041] Here, the shared printer 401 is registered by registering the printer driver (print queue registration) of the image forming apparatus 100, which is created and shared using an existing function provided by the first OS.

[0042] The shared folder 402 is created using an existing function provided by the first OS. The tools 404 for the first OS place the printer driver 406 for the second OS and the tools 405 for the second OS in the shared folder 402.

[0043] The mail application 403 is an application that can create, send, and receive general emails. The tool 404 for the first OS uses the mail application 403 to send notification emails. Note that the tool 404 for the first OS may also send emails by commands or programs without using the mail application 403.

[0044] As shown in FIG. 4, the tool 404 for the first OS includes an information acquisition unit 4041, a tool creation unit 4042, an information storage unit 4043, and a notification unit 4044.

[0045] The information acquisition unit 4041 acquires information on the shared printer 401 of the print server 400, the IP address of the print server 400, and the package of the printer driver 406 for the second OS. The information acquisition unit 4041 stores the acquired information such as the information on the shared printer 401 of the print server 400, the IP address of the print server 400, and the package of the printer driver 406 for the second OS in the information storage unit 4043.

[0046] More specifically, the information acquisition unit 4041 acquires the following information and stores it in the information storage unit 4043. The information storage unit 4043 stores information such as the IP address of the print server 400, the host name of the print server 400, the shared printer name, the shared folder name, the destination email address, option settings, and default print setting values.

[0047] [Table 1]

[0048] The tool creation unit 4042 creates the tool 405 for the second OS and the shared folder 402 using the information stored in the information storage unit 4043. The tool creation unit 4042 places the tool 405 for the second OS and the package of the printer driver 406 for the second OS in the shared folder 402.

[0049] The notification unit 4044 creates and sends a notification email to the user of the client PC 300 based on the information (notification destination email address) stored in the information storage unit 4043.

[0050] Next, the functions of the second OS tool 405 created by the first OS tool 404 and executed on the client PC 300 will be described.

[0051] Here, FIG. 5 is a functional block diagram showing the functional configuration of the client PC 300. As shown in FIG. 5, the client PC 300 uses the second OS tool 405. The second OS tool 405 is arranged in the shared folder 402 of the print server 400. By executing the second OS tool 405, the client PC 300 sets the printing environment on the second OS side.

[0052] The second OS tool 405 installs the package (installer) of the second OS printer driver 406 arranged in the shared folder 402 of the print server 400.

[0053] The second OS tool 405 uses the mail app 302 that can create and send and receive general emails to receive and make the notification email viewable.

[0054] As shown in FIG. 5, the second OS tool 405 includes an installation unit 4051, a queue registration unit 4052, an authentication registration unit 4053, a setting reflection unit 4054, and a test printing unit 4055.

[0055] The installation unit 4051 installs the second OS printer driver 406 arranged in the shared folder 402 of the print server 400.

[0056] The queue registration unit 4052 registers the print queue of the shared printer 401 of the print server 400 for constructing the printing environment.

[0057] The authentication registration unit 4053 registers the authentication username and password for connecting to the print server 400 in the keychain function (a function for recording and managing accounts and password information) of the second OS.

[0058] The setting reflection unit 4054 acquires the default values (initial values) of the option (peripheral device) settings and print settings of the shared printer 401 of the print server 400 from the information storage unit 4043, and reflects and sets them in the print queue of the client PC 300.

[0059] After the print queue registration in the setting reflection unit 4054 and the authentication registration in the authentication registration unit 4053, the test printing unit 4055 performs test printing. If the test printing fails, the test printing unit 4055 returns to the authentication registration step in the authentication registration unit 4053.

[0060] Next, the operation flow (external flow) of the user of the print server 400 and the processing flow (internal flow) of the tool 404 for the first OS will be described.

[0061] Here, FIG. 6 is a sequence diagram showing the processing flow of the tool 404 for the first OS.

[0062] First, the user of the print server 400 starts the tool 404 for the first OS of the print server 400 (S1-1). Here, the tool format is assumed to be a general format (executable file format (.exe), batch file format (.bat), etc.).

[0063] Next, the user of the print server 400 inputs the necessary information to the UI (information input screen P1) displayed by the tool 404 for the first OS (S1-2). Here, FIG. 7 is a diagram showing an example of the information input screen P1. As shown in FIG. 7, the user of the print server 400 inputs the "shared folder path", "printer driver URL of the second OS", and "notification destination email address" as the necessary information to the information input screen P1.

[0064] Next, the user of the print server 400 presses the "Create Notification Content" button B1 on the information input screen P1 (S1-3).

[0065] When S1-1 to S1-3 are executed, the first OS tool 404 creates a shared folder 402, downloads a printer driver package, creates a second OS tool 405, and places them in the shared folder 402 based on the necessary information input from the information input screen P1. This will be described in detail below.

[0066] First, the information acquisition unit 4041 of the first OS tool 404 acquires various information (S2-1). For example, when the first OS is Windows, the information acquisition unit 4041 can acquire information (IP address, host name, shared printer name) of the registered shared printer 401 using commands installed in Windows such as Powershell. Powershell can acquire the IP address using the GetHostAddress command, and the host name and shared printer name using commands such as get-WmiObject. Also, when the first OS is Windows, the information acquisition unit 4041 acquires the option settings and print setting default values of the shared printer 401 from the information storage unit 4043 using commands installed in Windows such as Powershell (Get-PrintConfiguration command, etc.).

[0067] Next, the information acquisition unit 4041 of the first OS tool 404 downloads the printer driver package for the second OS (S2-2). More specifically, the information acquisition unit 4041 downloads the printer driver package (installer) for the second OS published on a web page on the Internet from the download URL. For example, when the first OS is Windows, the information acquisition unit 4041 can download it using commands installed in Windows such as Powershell (Invoke-WebRequest command of Powershell, etc.).

[0068] Next, the tool creation unit 4042 of the first OS tool 404 creates a shared folder 402 (S2-3). More specifically, the tool creation unit 4042 creates the shared folder 402 at the path specified in the UI (information input screen P1). For example, when the first OS is Windows, the tool creation unit 4042 can be created by commands installed in Windows such as Powershell. Specifically, Powershell can create a folder with New-Item and set sharing with New-SmbShare.

[0069] Next, the tool creation unit 4042 of the first OS tool 404 creates a second OS tool 405 (S2-4). More specifically, the tool creation unit 4042 creates a program that performs environment setting processing for using the shared printer 401 on the client PC 300 side where the second OS is installed. In the present embodiment, when the second OS is Mac OS, the file format of the program is assumed to be a shell script format that can execute commands on Mac OS. As a method of creating the program, a template file of the second OS tool 405 may be prepared and created by means such as replacing the acquired information.

[0070] Note that the tool creation unit 4042 may directly reflect the information stored in the information storage unit 4043 in the file of the program of the second OS tool 405. Alternatively, the tool creation unit 4042 may be described in a general format such as csv or xml in a file separate from the program file and read by the tool. For example, in the case of installing a driver package (.pkg), the tool creation unit 4042 may prepare a template with the following command and replace the "DRIVER_PACKAGE" part with the name of the package downloaded in S2-2. sudo / usr / sbin / installer - pkg DRIVER_PACKAGE

[0071] Next, the tool creation unit 4042 of the first OS tool 404 places the package and the second OS tool 405 in the shared folder 402 and displays a completion message (S2-5). For example, when the first OS is Windows, the tool creation unit 4042 can be placed using a Windows-mounted command such as Powershell (such as the Move-Item command).

[0072] Here, FIG. 8 is a diagram showing an example of the information input screen P1. As shown in FIG. 8, when the first OS tool 404 completes creating the notification content, it pops up and displays a completion message on the information input screen P1.

[0073] Next, after the user of the print server 400 presses the "OK" button B3 of the pop-up display P on the information input screen P1, the user presses the "Notification Execution" button B2 (S1-4). Thereby, the user of the print server 400 instructs the transmission of an email notification to the user of the client PC 300.

[0074] When S1-4 is executed, the notification unit 4044 of the first OS tool 404 creates and sends a notification email (S2-6). For example, when the first OS is Windows, the notification unit 4044 can send a notification using a Windows-mounted command such as Powershell (such as the New-Object System.Net.Mail.MailMessage command).

[0075] The notification unit 4044 of the first OS tool 404 describes the following in the notification email for the user of the client PC 300 on which the second OS is installed. · The IP address of the print server 400 · The shared folder name of the print server 400 · The execution procedure of the second OS tool 405 (connect to the shared folder 402 according to the general procedure of the second OS, double-click the second OS tool 405 to execute, etc.)

[0076] Next, the operation flow (external flow) of the user of the client PC 300 and the processing flow (internal flow) of the tool 405 for the second OS will be described.

[0077] Here, FIG. 9 is a sequence diagram showing the processing flow of the tool 405 for the second OS.

[0078] First, the user of the client PC 300 opens the notification email and accesses the shared folder 402 (S3-1). The user of the client PC 300 on which the second OS is installed opens the received notification email with the general email app 302, and uses the IP address of the print server 400 and the shared folder name described in the notification email to access the shared folder 402 of the print server 400 by general means of the second OS.

[0079] Next, the user of the client PC 300 executes the tool 405 for the second OS in the shared folder 402 (S3-2).

[0080] When S3-1 to S3-2 are executed, the installation part 4051 of the tool 405 for the second OS requests the input of the administrator password (S4-1). This is because when executing the printer driver installation, the input of the administrator password is required, so the administrator password is received from the user of the client PC 300 before execution. Here, FIG. 10 is a diagram showing an example of the password input screen P3. As shown in FIG. 10, the password input screen P3 requests the input of the administrator password.

[0081] Next, the user of the client PC 300 inputs the administrator password to the UI (password input screen P3) displayed by the tool 405 for the second OS (S3-3).

[0082] Next, the installation section 4051 of the tool 405 for the second OS installs the printer driver (S4-2). For example, when the second OS is Mac OS, the installation of the printer driver package is executed by a shell command (installer) or the like.

[0083] Next, the queue registration section 4052 of the tool 405 for the second OS checks whether the host name is valid (S4-3). Specifically, the queue registration section 4052 checks whether the host name of the print server 400 is available. For example, when the second OS is Mac OS, it can be checked with a Mac OS command (such as ping).

[0084] Here, the host name is a name that identifies the print server 400 defined separately from the IP address. Whether it is possible to specify the print server 400 by the host name from the client PC 300 depends on the environment in which the print server 400 is constructed (it is possible if it is registered and managed by a DNS (Domain Name System) server, etc.). Therefore, the queue registration section 4052 checks whether the host name is available.

[0085] Next, when the host name of the print server 400 is available, the queue registration section 4052 of the tool 405 for the second OS creates a print queue by specifying the print server 400 by the host name (S4-4-A). For example, when the second OS is Mac OS, a print queue can be created with a Mac OS lpadmin command or the like. By specifying the print server 400 by the host name in this way, there is an advantage that the shared printer 401 can be used without being affected even if the IP address of the print server 400 changes.

[0086] On the other hand, when the host name of the print server 400 is not available, the queue registration section 4052 of the tool 405 for the second OS creates a print queue by specifying the print server 400 by the IP address (S4-4-B).

[0087] Next, the authentication registration unit 4053 of the second OS tool 405 receives the input of the username and password for authentication for connecting from the user of the client PC 300 to the print server 400 on which the first OS is installed, and registers them in the keychain function (S4-5). For example, when the second OS is Mac OS, the authentication information for the print server 400 is registered in the keychain function (a function for storing and managing authentication information) installed in Mac OS. The registration can be performed using the security command installed in Mac OS.

[0088] Here, FIG. 11 is a diagram showing an example of the keychain registration screen P4. As shown in FIG. 11, the keychain registration screen P4 requests the input of the username and password.

[0089] Next, the setting reflection unit 4054 of the second OS tool 405 reflects the option settings in the print queue (S4-6). More specifically, the setting reflection unit 4054 reflects the "option settings" acquired by the print server 400 on which the first OS is installed in the registered print queue. For example, when the second OS is Mac OS, it can be reflected using the lpoptions command installed in Mac OS.

[0090] Next, the setting reflection unit 4054 of the second OS tool 405 reflects the print settings in the print queue (S4-7). More specifically, the setting reflection unit 4054 reflects the "default print setting values" acquired by the print server 400 on which the first OS is installed in the registered print queue. For example, when the second OS is Mac OS, it can be reflected using the lpoptions command installed in Mac OS.

[0091] After registering the print queue, the test printing unit 4055 of the second OS tool 405 executes test printing (S4-8). The test printing unit 4055 displays a confirmation UI for the test printing result (test printing result input screen P5). Here, FIG. 12 is a diagram showing an example of the test printing result input screen P5. As shown in FIG. 12, the test printing result input screen P5 requests the input of the test printing result (success or failure).

[0092] If the test printing result input by the user of the client PC 300 is "success", the test printing unit 4055 proceeds to S4-9. If the test printing result input by the user of the client PC 300 is "failure", the test printing unit 4055 returns to S4-5 and waits for the re-entry of authentication information (user name and password).

[0093] In S4-9, the queue registration unit 4052 of the second OS tool 405 performs a completion display of the settings (S4-9). Here, FIG. 13 is a diagram showing an example of the setting completion display screen P6. As shown in FIG. 13, as shown in FIG. 8, when the settings are completed, the queue registration unit 4052 displays that the settings have been completed.

[0094] As described above, according to this embodiment, a tool for the first OS is prepared, and information and a printer driver package necessary for setting the client PC 300 on which the second OS is installed are collected by executing the tool for the first OS 404. Then, a tool for the second OS 405 that reflects the information and printer driver package necessary for setting the client PC 300 is generated, placed in the shared folder 402, and notified to the client PC 300 on which the second OS is installed. After that, by connecting to the shared folder 402 on the client PC 300 side and executing the tool for the second OS, the setting can be completed. Thereby, the printing environment from the client PC 300 on which the second OS is installed using the shared printer 401 of the print server 400 on which the first OS is installed can be accurately set with fewer procedures.

[0095] In each of the above embodiments, Windows is taken as an example of the first OS, and Mac OS is taken as an example of the second OS, but the present invention is not limited thereto.

[0096] In each of the above embodiments, an example in which the image forming apparatus 100 of the present invention is applied to a multifunction peripheral having at least two functions among a copying function, a printer function, a scanner function, and a facsimile function is described. However, the present invention can be applied to any image forming apparatus such as a copier, a printer, a scanner device, and a facsimile device.

Explanation of Reference Numerals

[0097] 300 Client 400 Server 4041 Information Acquisition Unit 4042 Tool Creation Unit 4044 Notification Unit 4051 Installation Unit 4052 Print Queue Registration Unit 4053 Authentication Registration Unit 4055 Test Printing Unit

Prior Art Documents

Patent Documents

[0098]

Patent Document 1

Claims

1. A computer operating on a second OS, an installation unit that uses the received administrator password to install a printer driver package of a shared printer shared and set on a server operating on a first OS different from the second OS; a print queue registration unit that registers a print queue for printing with the IP address of a server on which a first OS different from the second OS is installed; an authentication registration unit that receives a user name and password for authentication for connecting to the server and registers them in the keychain function of the second OS; a test printing unit that returns to the registration in the keychain function in the authentication registration unit when a test print fails after the registration of the print queue; A program for functioning as.

2. When the host name of the information acquired on the server side is available, the print queue registration unit registers the print queue with the host name instead of the IP address. The program according to claim 1.

3. The print queue registration unit acquires the option configuration of the shared printer from the shared printer and sets it in the print queue. The program according to claim 1 or 2.

4. The print queue registration unit acquires the initial value of the print settings of the shared printer from the shared printer and sets it in the print queue. The program according to any one of claims 1 to 3.

5. In a client operating on a second OS, an installation unit that uses the received administrator password to install a printer driver package of a shared printer shared and set on a server operating on a first OS different from the second OS; a print queue registration unit that registers a print queue for printing with the IP address of a server on which a first OS different from the second OS is installed; an authentication registration unit that receives a user name and password for authentication for connecting to the server and registers them in the keychain function of the second OS; a test printing unit that returns to the registration in the keychain function in the authentication registration unit when a test print fails after the registration of the print queue; A client characterized by comprising.

6. In a system including a server operating on a first OS and a client operating on a second OS different from the first OS, The server is An information acquisition unit that acquires, as information, the information necessary for setting in the client and the printer driver package of the shared printer shared-set in the first OS; A tool creation unit that creates and arranges a tool for the second OS in which the information is reflected in a program operating on the client in a shared folder for connecting from the client; A notification unit that receives a destination input for notifying a setting guidance for the client and transmits a notification to the destination; comprising; The client includes: An installation unit that installs a printer driver package of the shared printer shared-set in the server using the received administrator password; A print queue registration unit that registers a print queue for printing with the IP address of the server; An authentication registration unit that receives a user name and password for authentication for connecting to the server and registers them in a keychain function possessed by the second OS; A test printing unit that returns to registration in the keychain function in the authentication registration unit when test printing fails after registration of the print queue; comprising; A system characterized by the above.

Citation Information

Patent Citations

  • Information processor, printer setting method for the same, program, and recording medium

    JP2004038296A

  • Printing system, device and method for automatic installation of printer

    JP2009059362A

  • Information processor, program, and recording medium

    JP2011233020A

  • Print queue name management program

    JP2012221396A

  • Information processing apparatus, and information processing system

    JP2018101842A