Printing In The Domain Services For Windows Environment; Setting Up Iprint; Special Handling For Iprint On Dsfw; Secure And Non-Secure Printing - Novell OPEN ENTERPRISE SERVER 2.0 SP2 - DOMAIN SERVICE FOR WINDOWS Manual

Printing in the Domain Services
1 7
for Windows Environment
Novell iPrint is the printing solution for Open Enterprise Server (OES) 2. This section describes
how Domain Services for Windows users can set up and use Novell
Section 17.1, "Setting Up iPrint," on page 199
Section 17.2, "Special Handling for iPrint on DSfW," on page 199
Section 17.3, "iPrint Clustering in a DSfW Environment," on page 200

17.1 Setting Up iPrint

With Domain Services for Windows, you set up iPrint in the same way as for any OES 2 Linux
installation. The Novell iPrint pattern is selected automatically when you select the Domain Services
for Windows pattern during the OES 2 server installation.
For instructions on how to install and configure iPrint on OES 2 Linux servers, see
iPrint on Your Server (http://www.novell.com/documentation/oes2/iprint_lx/data/akuji88.html)
the OES2: iPrint for Linux Administration Guide.

17.2 Special Handling for iPrint on DSfW

Use these sections to handle the specific conditions during iprint configuration on DSfW:
Section 17.2.1, "Secure and Non-Secure Printing," on page 199
Section 17.2.2, "Using a Common Driver Store in a DSfW partition," on page 200

17.2.1 Secure and Non-Secure Printing

iPrint supports both secure and non-secure printing.
For non-secure printing, users do not need to be authenticated in order to install and access printers
made available through iPrint. They simply use iPrint's browser-based tool to find a nearby printer
and install the necessary drivers for the selected printer.
For secure printing, only iPrint printers that the user has rights to can be installed using the browser-
based tool.
While accessing secure printer, if a user is not unique in the iprint client authentication window, then
that user needs to provide the complete context in either LDAP or Domain Controller based format
for the authentication window. For example, if the user administrator is present in user context for
both first domain controller as well as the Child Domain Controller (CDC), you need to provide the
complete context for the user who needs to be authenticated. Use one of the following format based
on the user context:
The LDAP format is "
The DC format is "
cn=person,cn=Users,dc=<context>,dc=<context>
cn=person,cn=Users,o=<context>,C=<context>

Printing in the Domain Services for Windows Environment

®
iPrint on DSfW.
"Setting Up
"
"
17
in
199