object: (1) A set of attributes, each with its associated values. Two attributes of an object have special significance:
- Identifying attribute: A designated single-valued attribute appears on every object; the value of this attribute identifies the object. For the set of objects in a replica, the values of the identifying attribute are distinct.
- Parent-identifying attribute: A designated single-valued attribute appears on every object; the value of this attribute identifies the object's parent. That is, this attribute contains the value of the parent's identifying attribute, or a reserved value identifying no object. For the set of objects in a replica, the values of this parent-identifying attribute define a tree with objects as vertices and child-parent references as directed edges with the child as an edge's tail and the parent as an edge's head.
Note that an object is a value, not a variable; a replica is a variable. The process of adding, modifying, or deleting an object in a replica replaces the entire value of the replica with a new value.
As the word replica suggests, it is often the case that two replicas contain "the same objects." In this usage, objects in two replicas are considered the same if they have the same value of the identifying attribute and if there is a process in place (replication) to converge the values of the remaining attributes. When the members of a set of replicas are considered to be the same, it is common to say "an object" as shorthand referring to the set of corresponding objects in the replicas.
(2) In Active Directory, an entity consisting of a set of attributes, each attribute with a set of associated values. For more information, see [MS-ADTS].
(4) A DCOM object, as specified in [MS-DCOM] section 1.1.
object class: (1) A predicate defined on objects that constrains their attributes. Also an identifier for such a predicate.
(2) A set of restrictions on the construction and update of objects. An object class can specify a set of must-have attributes (every object of the class must have at least one value of each) and may-have attributes (every object of the class may have a value of each). An object class can also specify the allowable classes for the parent object of an object in the class. An object class can be defined by single inheritance; an object whose class is defined in this way is a member of all object classes used to derive its most specific class. An object class is defined in a classSchema object.
object class inheritance: The process of defining one object class in terms of its variations from an existing object class. The may-have, must-have, and possible superiors restrictions of an object class are all inherited.
object exporter: An object container (for example, process, machine, thread) in an object server. Object exporters are callable using RPC interfaces, and they are responsible for dispatching calls to the objects they contain.
object exporter identifier (OXID): A 64-bit number that uniquely identifies an object exporter within an object server.
objectGuid: (1) The attribute on an object whose value is a GUID that uniquely identifies the object. The value of objectGuid is assigned when an object is created and is immutable thereafter. The integrity of both object references between naming contexts (NCs) and of replication depends on the integrity of the objectGuid attribute.
Object ID: See ObjectID.
ObjectID: A unique identifier that represents the identity of a file within a file system volume. For more information, see [MS-DLTM].
object identifier (OID): (1) In the context of an object server, a 64-bit number that uniquely identifies an object.
(2) In the context of a directory service, a number identifying an object class or attribute. Object identifiers are issued by the ITU and form a hierarchy. An OID is represented as a dotted decimal string (for example, "126.96.36.199"). For more information on OIDs, see [X660] and Appendix A of [RFC3280]. OIDs are used to uniquely identify certificate templates available to the certificate authority (CA). Within a certificate, OIDs are used to identify standard extensions as covered in section 4.2.1.x of [RFC3280] as well as non-standard extensions.
(3) In the Lightweight Directory Access Protocol (LDAP), a sequence of numbers in a format specified by [RFC1778]. In many LDAP directory implementations, an OID is the standard internal representation of an attribute. In the directory model used in this specification, the more familiar ldapDisplayName represents an attribute.
(5) A variable-length identifier from a namespace administered by the ITU. Objects, protocols, and so on, that make use of ASN.1 or Basic Encoding Rules (BER), Distinguished Encoding Rules (DER), or Canonical Encoding Rules (CER) encoding format leverage identities from the ITU. For more information, see [ITUX680].
object reference: An attribute value that references an object. Reading a reference gives the distinguished name (DN) of the object. An object reference allows the object to be accessed by entities outside the object's exporter.
object remote procedure call (ORPC): A remote procedure call whose target is an interface on an object. The target interface (and hence object) is identified by an interface pointer identifier (IPID).
object resolver: A service in an object server that supports instantiating objects, obtaining remote procedure call (RPC) binding information for object exporters, and managing object lifetimes. Object resolvers may be reachable via well-known or dynamic RPC endpoints.
object server: An execution environment that contains a particular object resolver service and its associated object exporters.
OBJREF: The marshaled form of an object reference.
OEM character: See original equipment manufacturer (OEM) character.
OEM character set: See original equipment manufacturer (OEM) character set.
OEM code page: See original equipment manufacturer (OEM) code page.
OID: See object identifier.
OleTx: A comprehensive distributed transaction manager processing protocol that uses the protocols specified in the following document(s): .
one-way authentication: An authentication mode in which only one party verifies the identity of the other party.
one-way function (OWF): The calculation of a hash of the password using the Rivest-Shamir-Adleman (RSA) MD4 function. OWF is used to refer to the resulting value of the hash operation.
online: An operational state applicable to volumes and disks. In the online state, the volume or disk is available for data input/output (I/O) or configuration.
operating system upgrade: The action of replacing the existing operating system on a computer with a later version of the operating system while maintaining the original configuration and data of that computer.
opportunistic lock (oplock): A mechanism designed to allow clients to dynamically alter their buffering strategy in a consistent manner to increase performance and reduce network use. The network performance for remote file operations may be increased if a client can locally buffer file data, which reduces or eliminates the need to send and receive network packets. For example, a client may not have to write information into a file on a remote server if the client knows that no other process is accessing the data. Likewise, the client may buffer read-ahead data from the remote file if the client knows that no other process is writing data to the remote file.
There are three types of Oplocks:
- Exclusive Oplock allows a client to open a file for exclusive access and allows the client to perform arbitrary buffering.
- Batch Oplock allows a client to keep a file open on the server even though the local accessor on the client machine has closed the file.
- Level II Oplock indicates that there are multiple readers of a file and no writers. Level II Oplocks are supported if the negotiated SMB Dialect is NT LM 0.12 or later.
When a client opens a file, it requests the server to grant it a particular type of Oplocks on the file. The response from the server indicates the type of Oplocks granted to the client. The client uses the granted Oplocks type to adjust its buffering policy.
optical media drive: A drive that controls the positioning, reading, and writing of removable media on optical disks such as CD-ROMs and DVDs.
original equipment manufacturer (OEM) character: An 8-bit encoding used in MS-DOS and Windows operating systems to associate a sequence of bits with specific characters. The ASCII character set maps the letters, numerals, and specified punctuation and control characters to the numbers from 0 to 127. The term "code page" is used to refer to extensions of the ASCII character set that map specified characters and symbols to the numbers from 128 to 255. These code pages are referred to as OEM Character sets. For more information, see [MSCHARSET].
original equipment manufacturer (OEM) character set: A character encoding used where the mappings between characters is dependent upon the code page configured on the machine, typically by the manufacturer.
original equipment manufacturer (OEM) code page: A code page used to translate between non-Unicode encoded strings and UTF-16 encoding strings.
originating write: An update operation that should be replicated to other replicas. The originating write is changing the server state. The inputs of the operation are the DSNAME of the object, the old value of replication metadata, and the list of modified attributes and values. The result of the operation is the new replication metadata stamped on the object.
originator GUID: A GUID that is associated with each replica member. All change orders produced by a given replica member carry the replica member's originator GUID, which is saved in the IDTable. The Originator GUID is not the same as member GUID, which is the objectGuid of the NT File Replication Service (NTFRS) member object in Active Directory. For more information, see [MS-ADTS].
ORPC extension: An out-of-band (not part of the explicit method signature), GUID-tagged binary large object (BLOB) of data that is sent or received in an object remote procedure call (ORPC) call.
OSF-DCE: The Distributed Computing Environment from the Open Software Foundation. It consists of multiple components, including remote procedure call (RPC), that have been integrated to work closely together.
OUT channel: An outbound HTTP response or an outbound TCP/IP connection between two network nodes acting in one of the roles defined by a protocol. An OUT channel is independent from the underlying transport and can be based on an HTTP or HTTPS response or on a TCP connection.
OUT channel recycling: The set of mechanisms involved in closing an open OUT channel N and opening a new OUT channel N+1. The opening and subsequent closing occur as part of the sequence of channels forming a virtual OUT channel.
outbound: Network traffic flowing from the server to the client.
outbound connection: For a given replica member, a component of the NT File Replication Service (NTFRS) member object in Active Directory that identifies outbound partners. An outbound connection exists for each outbound partner.
outbound log (OutLog): A table in the File Replication Service(FRS) database that stores pending change orders to be sent to outbound partners. The changes can originate locally or come from an inbound partner. These change orders are eventually sent to all outbound replica partners.
outbound partner: The partner that receives change orders, files, and folders.
outbound proxy: A network node that acts as proxy for outbound traffic between a client and a server.
outbound trust: A relationship where the primary domain trusts another domain to perform operations such as name lookups and authentication.
out-of-band policy application: A protocol exchange between a client and server in which policy enforcement occurs for some subset of Group Policy settings from Group Policy objects (GPOs) encountered during some previous policy application exchange. This is referred to as "out-of-band" because, unlike policy application, an out-of-band policy application retrieves settings separately from GPO retrieval.
OXID resolution: The process of obtaining the remote procedure call (RPC) binding information required to communicate with the object exporter.