Device

Represents physical units that can communicate (such as a modem or a printer). At least one of the L (Locality Name), Serial Number, or Owner attributes should be included with the object entry. The choice depends on the type of device.

Type:Effective

NDS Operational:Yes

LDAP Name

device

ASN.1 ID

2.5.6.14

Class Flags

Class Flags	Setting
Container	Off
Effective	On
Nonremovable	On
Ambiguous Naming	Off
Ambiguous Container	Off
Auxiliary Class	Off

Class Structure

Rule	Class/Attribute	Defined For
Super Classes	Top	Device
Containment	domain Organization Organizational Unit	Device Device Device
Named By	CN (Common Name)	Device

Rule

Class/Attribute

Defined For

Super Classes

Top

Device

Containment

domain

Organization

Organizational Unit

Device

Named By

CN (Common Name)

Device

Mandatory Attributes

Device	Inherited from Top
CN (Common Name)	Object Class

Optional Attributes

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

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

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 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 OU (Organizational Unit Name) 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 or organizational unit can be useful when a device is “co-owned” by multiple organizations.

In versions of NDS previous to NDS eDirectory 8.5, device is a non-effective class.