4.9 Upgrading to Novell iPrint

You can upgrade from a queue-based print system, Novell Distributed Print Services™, or an existing iPrint system to iPrint. The first step is to upgrade your print server’s operating system or install a new server running NetWare OES. For more information on upgrading and installing the operating system, see the OES NetWare Installation Guide.

Once the server where you are going to run iPrint is running NetWare OES, you can begin the process of upgrading your existing print system to iPrint. See following sections:

IMPORTANT:When upgrading a NetWare 5.1 or 6.0 server with the Novonyx Web Server installed to NetWare 6.5 or OES NetWare, the document root is not updated. The document root from the Novonyx Web Server is copied to Apache’s httpd.conf file instead of the document root for the Apache Web server. If iPrint does not work, edit the Apache configuration file (sys:\apache2\conf\httpd.conf) and change the DocumentRoot to the Apache document root (sys:\apache2\htdocs). You might need to change other entries in the .conf file.

4.9.1 Upgrading Existing iPrint Systems

To upgrade a NetWare 5.1 or NetWare 6 server running iPrint, choose your upgrade method for the operating system and run the upgrade. For more information on upgrade methods, see the OES NetWare Installation Guide.

IMPORTANT:When you upgrade or apply a Support Pack, the existing iprint.ini file is saved as iprint.bak and the new iprint.ini is copied over. If you made changes to the iprint.ini file, you must delete the new iprint.ini file from the Support Pack and rename iprint.bak to iprint.ini. If you want new functionality included with the latest iprint.ini, you should duplicate the settings in iprint.bak in the new iprint.ini.

When upgrading iPrint from NetWare 5.1 or NetWare 6, the custom maps are copied from sys:/login/ippdocs/ to sys:/apache2/htdocs/ippdocs on the NetWare 6.5 server. The map files are also flagged read only. To modify the maps, you need to manually remove the read only attribute.

IMPORTANT:When upgrading a NetWare 5.1 or 6.0 server with the Novonyx Web Server installed to NetWare 6.5 or OES NetWare, the document root is not updated. The document root from the Novonyx Web Server is copied to Apache’s httpd.conf file instead of the document root for the Apache Web server. If iPrint does not work, edit the Apache configuration file (sys:\apache2\conf\httpd.conf) and change the DocumentRoot to the Apache document root (sys:\apache2\htdocs). You might need to change other entries in the .conf file.

4.9.2 Upgrading from NDPS to iPrint

To upgrade from Novell Distributed Print Services (NDPS®) 2.0 or Enterprise NDPS, choose your upgrade method for the operating system and run the upgrade. For more information on upgrading, see the OES NetWare Installation Guide.

After the operating system is upgraded to OES for NetWare, complete the following tasks to migrate from print queues:

  1. Set up DNS.
  2. Enable iPrint on your Printers.
  3. Distribute the iPrint Client.
  4. Edit the UpgradeNDPSPrinters entry in iprint.ini.

    The next time users start their computer, the iPrint printers are installed and the NDPS printers are removed.

4.9.3 Migrating from Print Queues

You can make the transition gradually from queues to Novell iPrint because the Print Manager (ndpsm.nlm) and the Print Server (pserver.nlm) can run simultaneously on a server.

After installing a server running OES for NetWare, complete the following tasks to migrate from print queues:

  1. Set up DNS.
  2. Create a Broker.
  3. Create a Print Manager.
  4. Create a Printer Agent for each printer.
  5. Associate Printer Agents to Queues.
  6. Distribute the iPrint Client.
  7. Edit the UpgradeQMSPrinters entry in iprint.ini.

    The next time users start their computers, the iPrint client identifies the installed or captured queue and installs the corresponding iPrint printer, then removes the installed queue printer. If a queue cannot be resolved immediately, the iPrint client periodically reattempts to identify the queue object and the corresponding iPrint Printer.

    If you are capturing queues using a login script, you can remove the capture statements after all of your users’ printers have been migrated.

  8. After all queues have been migrated to iPrint, you can delete the Print Server, Printer, and Print Queue objects, and unload pserver.nlm from the server.