Novell Doc: NDK: Novell eDirectory Schema Reference

Printer
Cartridge Default Queue Host Device Memory Network Address Restriction Notify Operator	Page Description Language Print Server Printer Configuration Queue Status Supported Typefaces

Inherited from Top
ACL Audit:File Link Authority Revocation auxClassCompatibility Back Link Bindery Property CA Private Key CA Public Key Certificate Revocation Certificate Validity Interval creatorsName Cross Certificate Pair DirXML-Associations Equivalent To Me	GUID Last Referenced Time masvAuthorizedRange masvDefaultRange masvProposedLabel modifiersName Obituary objectVersion Other GUID Reference Revision rbsAssignedRoles rbsOwnedCollections Used By

Inherited from Device
Description L (Locality Name) Network Address O (Organization Name) OU (Organizational Unit Name) Owner	See Also Serial Number SvcInfo SvcType SvcTypeID

Default ACL Template

Object Name	Default Rights	Affected Attributes	Class Defined For
[Creator]	Supervisor	[Entry Rights]	Top

Remarks

For help in understanding the class definition template, see Reading Class Definitions.

The Host Device attribute is used in this class to denote the computer (or other device) to which the printer is attached.

The Print Server attribute identifies the print servers that manage this device.

The Supported Typefaces and Page Description Language attributes are included to aid a search for printers with a particular set of capabilities. The contents of these attributes are statically maintained by an administrator, rather than being dynamically updated from printer feedback.

The Queue attribute identifies the associated queues through which this printer can be accessed.

The L (Locality Name) attribute can be used to identify the physical location of a device. For example, if the device were a printer, the locality might be "Building D, Section 24, by Ed Bender’s desk."

The O (Organization Name) and the OU (Organizational Unit Name) attributes may already be present in the device’s distinguished name. They are repeated here to aid searching when an organization spans multiple subtrees in the eDirectory tree. However, eDirectory does not automatically add these attributes even though they may be present in the device’s distinguished name. Additional values for the organization name or organizational unit name can be useful when a device is "co-owned" by multiple organizations.