iPrint has the following implementation caveats:
Section 6.7.1, Cluster Failover Between Mixed Platforms Not Supported
Section 6.7.2, Printer Driver Uploading on OES 2 Linux Might Require a CUPS Administrator Credential
Section 6.7.5, iPrint Client for Linux Doesn't Install Automatically
Section 6.7.6, iPrint Disables CUPS Printing on the OES 2 Linux Server
Clustered iPrint services can only fail over to the same OES 2 platform (Linux or NetWare).
A PPD is the Linux equivalent of a printer driver on Windows.
There are two versions of the iPrint Client: high security and low security. By default, end users and administrators install the high-security client when using the iPrint Printer List Web page.
This means that administrators are prompted for a CUPS administrator credential when uploading PPDs. However, the prompt doesn’t specify that a CUPS administrator credential is needed and the root user credential does not work.
Uploading PPD printer drivers from a Linux workstation requires a Mozilla*-based browser. Only the
button works for uploading drivers. Non-Mozilla-based browsers, such as Konqueror, cannot be used to upload drivers.Uploading PPD printer drivers from a Windows workstation requires Internet Explorer* 5.5 or later. Other browsers running on Windows do not work for uploading drivers.
Windows printer drivers cannot be uploaded by using Mozilla-based or other browsers on any platform.
The iManager plug-ins are different for each server platform. Therefore, if you have both OES 2 Linux and OES 2 NetWare servers running iPrint services, you need two instances of iManager to manage iPrint—one on each platform.
Users who are used to installing the Windows iPrint Client expect to choose an Linux: iPrint Client
in the OES 2 SP2: iPrint for Linux Administration Guide.
iPrint uses CUPS to render print jobs before sending the print job to the Print Manager. For performance and scalability, printing from the server itself is disabled during the OES installation of iPrint.