Print Server Administration User’s Guide
◊Service only currently mounted forms Only services printer queue jobs that use a form that the printer already has. Jobs using other forms will be left in the queue to be served by other printers.
◊Minimize form changes across print queues Reorders jobs across all of the print queues the printer serves in order to minimize the number of form changes required.
Setting up Novell NetWare 4.x Printing
HyperNet Fastprint network print servers support both the Bindery server database used with NetWare 3.x networks, and the NetWare Directory Services (NDS)
Additional information about NetWare printing may be found in the previous chapter.
NetWare Directory Services
NetWare version 3.x stores information about users, file server volumes, print servers, print queues, and other objects in a database called the Bindery. NetWare server administration programs (such as SYSCON, PCONSOLE, and so on) modify entries in the Bindery to manage the operation of the file server.
The main disadvantage of the Bindery database is that it is limited to a single server. Networks with a large number of servers can become difficult to manage, because each server has to be configured separately. In large enterprises, this can result in disorganization as each department tries to administer its own NetWare servers, each in a different way. It can become troublesome or impossible to coordinate the administration of file servers across the entire enterprise.
For this reason, NetWare version 4.x introduced NetWare Directory Services, which allows administration on a global, as well as a local scale. NDS organizes objects not by file server, but by administrative domain.
The Network Directory Services database stores “objects” in a tree structure. Branches in the tree represent different regional offices, divisions, departments, or other ways of dividing administrative responsibility.
Objects, such as users, servers, server volumes, print servers, print queues, etc., can be placed anywhere within the tree structure. The whole tree structure is shared by all servers using the same tree. Changing a setting in the tree affects all servers, making it less necessary to manage servers individually.
For compatibility with existing NetWare 3.x clients and servers, NetWare 4.x provides Bindery emulation, which exposes objects in the server’s context as Bindery objects.
EtherP Admin Administration | 23 |
