Cool Solutions

Create iPrint Printers From a CSV File


August 16, 2012 3:54 pm






Download create-printers-from-csv-1

The Create Printers From CSV script was designed to allow administrators to be able to create iPrint printers quickly by using a CSV file instead of iManager.

Step #1 – Install and download the latest version of the Create Printers From CSV script utility.

    Note: Create Printers From CSV script supports OES 2 and 11.
    1. Download create-printers-from-csv-1.0.tgz
    2. Open a Terminal window and type “su”.
    3. Enter root’s password.
    4. Extract the script from the tarball.

      #tar –xzvf create-printers-from-csv-1.0.tgz
    5. cd to the Printer-Import folder.

      #cd Printer-Import
    6. Make the script executable.

      #chmod 755

    Step #2 – Create a CSV file with your favorite spreadsheet application.

    1. Open up the Printer-Import.csv file.
    2. Add printers to the file as shown in the example CSV file.

      The Columns must be in the following order:
      • Printer Name
      • DNS or IP of Printer
      • The container of where the printer should be created
      • The location of the printer
      • The description of the printer
    3. Save the file as .csv (comma-delimited).
    4. Copy the saved CSV file to the same location of the script (should still be found in the Printer-Import folder on the server).

    Step #3 – Run the Create Printers From CSV Script utility.

    1. On the terminal run the script to start the import process

    2. When the script is executed it will ask the remaining questions to make the import is successful.
0 votes, average: 0.00 out of 50 votes, average: 0.00 out of 50 votes, average: 0.00 out of 50 votes, average: 0.00 out of 50 votes, average: 0.00 out of 5 (0 votes, average: 0.00 out of 5)
You need to be a registered member to rate this post.

Tags: ,
Categories: Cool Tools, iPrint, Open Enterprise Server, Technical

Disclaimer: This content is not supported by Micro Focus. It was contributed by a community member and is published "as is." It seems to have worked for at least one person, and might work for you. But please be sure to test it thoroughly before using it in a production environment.