A programming layer built on top of OLE DB that allows high-level programming languages such as Visual Basic and VBScript to access an underlying data store through a common query language. In this instance, a data store can be Active Directory, the Exchange 2000 store, or a SQL database.
The service that replicates information between the Exchange Server 5.5 directory and Active Directory. Replicated objects include mailboxes, custom recipients, distribution lists, and site configuration information. ADC uses Connection Agreements (CAs) to define individual configurations for replication. The Exchange 2000 ADC is also used to allow Exchange 5.x and Exchange 2000 servers to coexist within the same Exchange site.
Note that two versions of the ADC exist; one for Windows 2000 and one for Exchange 2000. For more information, see “PT101 – Deploying the Active Directory Connector.”
A collection of Exchange 2000 servers than can be administered as a single unit. An administration group can include zero or more policies, routing groups, public folder trees, monitors, servers, conferencing services, and chat networks. When security settings (permissions) are applied to an administration group, all child objects in the DS tree inherit the same Access Control Lists (ACLs) as the administration group node. Note that an administration group does not define the routing topology for messages; this is handled by routing groups.
A nominated server that acts as a message transfer point between Exchange 2000 routing groups. This term can also refer to the computer hosting a directory replication connector.
An application programming interface (API) that allows users and applications to access data objects within an Exchange server. CDO defines the concept of different object classes including messages (IPM.Note), posts (IPM.Post), appointments (IPM.Appointment), and tasks (IPM.Task). Message stores and folder hierarchies can also be manipulated through CDO 1.21
CDO 1.21 is included with Exchange Server 5.5 and its services are supplied from the CDO.DLL file.
CDO for Windows 2000 is defined in the Windows 2000 section earlier in this document.
An API that is a superset of CDO for Windows 2000. In addition to gaining programmatic access to the Simple Mail Transfer Protocol (SMTP) and Network News Transfer Protocol (NNTP) stacks, CDO for Exchange 2000 provides support for the creation and manipulation of message items, appointments, and contact cards.
CDO for Exchange 2000 is included with Exchange 2000 and its services are supplied from the CDOEX.DLL file.
An API that allows administrators to programmatically access management information on an Exchange 2000 server, including databases and mailboxes. Services are supplied out of EMO.DLL file.
The network service that coordinates the booking of virtual resources for online meetings in the Exchange Conference Service. Each site (not domain) normally has an active Conferencing Management Service to allow fast connection for data conferencing users.
Conference Technology Provider - CTP
A provider of data conferencing services such as real-time video, audio, and telephony integration.
A special Connection Agreement implemented as part of the Active Directory Connector that replicates configuration naming context data from downlevel Exchange 5.x sites to administration groups in Active Directory and vice versa. ConfigCAs work in conjunction with the Site Replication Service.
The configuration of information to replicate using the Active Directory Connector. Configuration information includes the servers that participate in the replication; which object classes (mailbox, custom recipient, distribution list and user, contact, and group) to replicate; containers and organization units to use for object placement; and the activity time schedule.
An extension to the Hypertext Transfer Protocol 1.1 (HTTP/1.1) that allows for the manipulation (readinf and writing) of objects and attributes on a Web server. Exchange 2000 natively supports WebDAV. Although not specifically designed for the purpose, DAV allows for the control of data using a filing system-like protocol. DAV commands include Lock, Unlock, Propfind and Proppatch. For more information, see “PT105 – Understanding Exchange 2000 Storage Technology.”
The Exchange 2000 component that provides directory lookup services for components such as SMTP, Message Transfer Agent (MTA), and the store. Client requests use the DSProxy service for directory access. For more information, see “PT102 – Exchange 2000 Directory Access and Integration with Windows 2000.”
The Exchange 2000 component that can proxy (and refer) Messaging Application Programming Interface (MAPI) DS requests from Outlook clients to Active Directory for Address Book lookup and name resolution. For more information, see “PT102 – Exchange 2000 Directory Access and Integration with Windows 2000.”
See EXIPC
A piece of code that is activated by a defined trigger, such as the reception of a new message. The code is normally written in any COM-compatible programming language such as Visual Basic, VBScript, JavaScript, C, or C++. Exchange 2000 supports the following event sinks:
transport
protocol
store
Event sinks on the store can be synchronous (code executes as the event is triggered) or asynchronous (code executes sometime after the event).
A service that allows users to meet in virtual rooms on the Exchange server. Exchange Conferencing Services defines the use of a Conferencing Management Service to coordinate the room bookings and a T.120 Multipoint Control Unit (MCU) for the actual connection of clients to a conferencing session.
When clustering, you allocate different resources (such as Storage Groups) to an EVS. Upon node failure, an EVS can be moved from the failed node to one of the remaining nodes.
A queuing layer that allows the IIS and store processes (Inetinfo.exe and Store.exe) to shuttle data back and forth very quickly. This is required to achieve the best possible performance between the protocols and database services on an Exchange 2000 server. Conventional applications require the processor to switch contexts when transferring data between two processes.
Exchange Server 5.5 incorporated protocols such as NNTP, Post Office Protocol 3 (POP3), and Internet Messaging Access Protocol (IMAP) directly into the Store.exe process, so data transfer was very efficient. The Exchange 2000 architecture separates the protocols from the database for ease of management and to support future architectures.
Formerly known as JET, the ESE is a method that defines a very low-level API to the underlying database structures in Exchange Server. Other databases, such as the Active Directory database (Ntds.dit), also use ESE. Exchange 2000 uses ESE98, whereas Exchange 5.5 and Active Directory use the older ESE97 interface.
An Exchange 2000 configuration in which clients access a bank of protocol servers (the front-end) for collaboration information, and these in-turn, communicate with the data stores on separate servers (the back-end) to retrieve the physical data. A front-end/back-end configuration allows for a scalable, single point of contact for all Exchange-related data.
A collection of Exchange services including, but not limited to virtual servers (that is, instances of Internet Message Access Protocol 4 (IMAP4), SMTP, POP3, NNTP, HTTP, RVP), storage space, and real-time collaboration facilities that exist to serve the needs of a single company. A hosted organization is normally used by Internet Service Providers to host multiple companies on the same physical computer. However, a hosted organization is not limited to a single Exchange 2000 server.
See Distributed Authoring and Versioning.
See Web Storage System
The Exchange 2000 service that allows for real-time messaging and collaboration between users. Clients generally use the MSN Messenger client to log on to Instant Messaging and subscribe to other users. For more information, see “PT106 – Deploying Real-Time Collaboration Services in Exchange 2000.”
The standards-based protocol clients use to interact with an Instant Messaging server. IMPP is being developed by leading vendors, including Microsoft and Lotus. The Instant Messaging service in Exchange 2000 uses a Microsoft published protocol called RVP while IMPP is being ratified.
A standard-based protocol for accessing mailbox information. IMAP4 is considered to be more advanced than POP3 because it supports basic online capabilities and access to folders other than the Inbox. Exchange Server 5.x and Exchange 2000 both support IMAP4.
Defines the low-level access to underlying database structures in Exchange Server 4.0 and 5.0. JET was superceded with ESE in Exchange Server 5.5 and Exchange 2000 .
The algorithm used to propagate routing status information between Exchange 2000 servers. Based on “Dijkstra’s algorithm”, link state information is transferred between routing groups using the X-LINK2STATE command verb over SMTP and within a routing group using a Transmission Control Protocol (TCP) connection to port 691.
A mechanism to replicate directory information through a messaging transport. This term applies to Exchange 5.x inter-site directory replication, and additionally, Active Directory replication through SMTP.
An instance of a database implemented in Exchange server. A single MDB is normally identified as being public or private depending on the type of data that it stores. A single Exchange 2000 server can accommodate up to 24 active MDBs.
The component in all versions of Exchange Server that transfers messages between servers using the X.400 protocol.
The API that is used by Microsoft messaging applications such as Outlook to access collaboration data. MAPI, or more specifically, MAPI Remote Procedure Calls (RPC), is also used as the transport protocol between Outlook clients and Exchange servers.
A store that contains metadata such as that used by IIS to obtain its configuration data. The metabase can be viewed through utilities such as Metaedit.
A component in Exchange 2000 that reads data from Active Directory and transposes it into the local IIS metabase. The metabase update service allows the administrator to make remote configuration changes to virtual servers without a permanent connection to each system.
Data about data. In relation to Exchange, this term can be used in the context of Active Directory, but can also be used to describe the structure within the store or the MTA.
An Exchange 5.x site that also contains Exchange 2000 servers.
A reference to the T.120 protocol that allows clients to connect to data conferencing sessions. MCUs can communicate with each other to transfer conferencing information.
Part of the DSProxy process that can accept Outlook client directory requests and pass them to an address book provider.
A standards-based protocol that includes simple command verbs to transfer USENET messages between clients and servers, and between servers. NNTP uses Transmission Control Protocol/Internet Protocol (TCP/IP) port 119.
An API that allows low-level programming languages such as C and C++ to access dissimilar data stores through a common query language. OLE DB is seen as the replacement for Open Database Connectivity (ODBC). Data stores such as those in Exchange 2000 and SQL Server allow for OLE DB access, which makes application development easier and faster.
High-level programming languages such as Visual Basic can use ADO to issue queries through OLE DB.
The Web browser interface to Exchange Server mailbox and public folder data. The Outlook Web Access client in Exchange Server 5.x uses Active Server Pages to render collaboration data into HTML, whereas the Outlook Web Access Client in Exchange 2000 uses native access to the store.
A collection of configuration settings that can be applied to objects of the same class in Active Directory. In relation to Exchange 2000, this may include mailbox thresholds and deleted item retention.
A standards-based protocol for simple access to Inbox data. All versions of Exchange server except version 4.0 support POP3. POP3 uses TCP/IP port 110 for client to server access.
A collection of virtual servers that are used as the primary connection point for users in an organization. The farm abstracts the connection protocols from the location of the back-end data, which allows users to access information without having to know its physical location.
A collection of public folders created under the same hierarchical namespace. Previous releases of Exchange server used only a single tree (called: All Public Folders), whereas multiple trees can be defined in Exchange 2000. Each tree is a unit of hierarchy replication and can be replicated to one or more Public MDBs. A Public MDB can host only one tree. MAPI clients such as Outlook can only access a single tree called All Public Folders, whereas other clients such as a Web browser or a networking client using the Microsoft Web Storage System can access any tree that is defined.
This is part of the Exchange System Attendant and is responsible for keeping Address Lists up-to-date and creating proxy addresses for users.
A reliable synchronous protocol that transfers data between clients and servers, and between servers. Outlook clients use MAPI RPC for accessing mailboxes and public folders, and Exchange 2000 servers communicate with the Exchange Server 5.x MTA using RPC (in a mixed-vintage organization).
In real-time collaboration, a user object in Active Directory that represents a facility. A resource is used by Outlook users for booking meetings and data conferences. Resources are stored in the “System \ Exchange” Organization Unit in the Active Directory.
A collection of Exchange 2000 servers that can transfer messaging data to one another in a single-hop without going through a bridgehead. In general, Exchange servers within a single routing group have high-bandwidth, resilient network links between each other.
Additionally, a routing group defines the boundary for public folder access.
A connector in Exchange 2000 that connects routing groups to one another. An RGC is uni-directional and can have separate configuration properties (such as allowable message types over the connection). Routing Group Connectors use the concept of local and remote bridgeheads to dictate which servers in the routing groups can communicate over the link. The underlying message transport for an RGC is either SMTP or RPC and it uses link state information to route messages efficiently.
A component in Exchange 2000 that builds link state information.
The Microsoft published protocol that is used between the MSN Messenger service and the Instant Messaging server that is implemented on Exchange 2000. RVP uses an extended subset of HTTP-DAV with an Extensible Markup Language (XML) payload to send subscriptions and notifications between Instant Messaging clients and servers.
The metadata (data about data) that describes how objects are used within a given structure. In relation to Exchange, this term may be used in the context of Active Directory, but it can also be used to describe the structure within the store or the MTA.
A major standards-based protocol that allows for the transfer of messages between different messaging servers. SMTP is defined under RFC821 and uses simple command verbs to facilitate message transport over TCP/IP port 25.
See Event Sink.
The updated version of the Exchange Server 5.5 Knowledge Consistency Checker (KCC) that works in conjunction with (and is part of) the Exchange Site Replication Service to ensure that knowledge consistency of sites, administration groups and Active Directory domains is maintained when interoperating between Exchange 2000 and Exchange 5.5. When changes are detected in either environment, the SCC may create new Connection Agreements (disabled) for the ADC.
A directory service (similar to the directory used in Exchange Server 5.5) implemented in Exchange 2000 to allow the integration with downstream Exchange 5.x sites using both RPC and mail-based replication. The SRS works in conjunction with the Active Directory Connector to provide replication services from Active Directory to the Exchange 5.x Directory Service.
A collection of Exchange databases on an Exchange 2000 server that share the same ESE instance and transaction log. Individual databases within a storage group can be mounted and dismounted. Each Exchange 2000 server can architecturally host up to 16 storage groups, although only 4 can be defined through the Exchange System Manager.
The generic name given to the storage subsystem on an Exchange server. This term is used interchangeably to describe the Store.exe process and Exchange databases.
One of the core Exchange 2000 services that performs miscellaneous functions (usually related to directory information) such as generation of address lists, offline Address Books, and directory lookup facilities.
A standards-based protocol used with Exchange Data Conferencing. Clients such as Microsoft NetMeeting are T.120 compatible.
A shortcut pointer to a physical storage location. Virtual roots are normally defined to allow users and applications to connect with a short ”friendly” path instead of navigating a complex hierarchy.
Internet Information Server (IIS) uses the concept of virtual roots to expose resources provided by a Web Server.
An instance of any service type normally implemented in IIS. For example, a virtual server can be an instance of:
FTP
IMAP
Instant Messaging (RVP)
HTTP
NNTP
POP
SMTP
An Exchange 2000 server can host multiple virtual servers of the same type on each computer. Each virtual server can have its own configuration properties, such as bound IP addresses, port number, and authentication type.
See Distributed Authoring and Versioning.
The database architecture in Exchange 2000. Previous releases of Exchange only exposed data such as public folders through MAPI, whereas Exchange 2000 exposes all of its data through MAPI, HTTP, OLE DB and Win32 layers.
This means that an object stored in a public folder can be retrieved and manipulated through a Web browser or a standard client with a network redirector. The Exchange 2000 store exposes itself to the operating system as an installable filing system, which means that the underlying data can be accessed through a drive letter, and in turn, this drive and its folders can be shared via a universal naming convention (UNC) path to allow other clients to connect to the data.
(Source: Microsoft's whitepaper "Microsoft Windows 2000 and Microsoft Exchange 2000 Server Terminology Primer")