Valle angel's tripping spot     |   home
About Me   |   My Favorites   |   My Hobbies   |   Hobbie 2   |   My Resume   |   Photo Album   |   Favorite Links   |   Contact Me   |   Miscellaneous
Hobbie 2
Microsoft Windows 2000 and Active Directory: Acronyms and Terminology
access control entry (ACE)
An entry in an access control list (ACL) that contains the security identifier (SID) for a user or group and an access mask that allows, denies, or audits operations by users or groups.
access control list (ACL)
A description of security permissions applied to an object, property, or resource. An ACL usually includes membership (ACEs) and the permissions that each member has for each item.
Active Directory™
The Microsoft Windows® 2000 directory service that stores information about objects on the network and makes this information available for authorized administrators and users. Active Directory gives network users access to permitted resources anywhere on the network using a single logon process. It provides administrators with an intuitive hierarchical view of the network and a single point of administration for all network objects. This replaces the Security Accounts Manager (SAM) in Microsoft Windows NT® version 4.0. Active Directory consists of a forest, domains, organization units, containers, and objects. Different classes of objects can be represented within Active Directory including users, groups, computers, printers, and applications.
Active Directory Connector (ADC)
The service that replicates information, such as mailboxes, custom recipients, and distribution lists, between the Exchange Server 5.5 directory and Active Directory. ADC uses connection agreements to define individual configurations for replication. There are two versions of ADC, one for Windows 2000 and one for Exchange 2000.
Active Directory Service Interfaces (ADSI)
A directory service abstraction interface that allows programming languages compatible with the Component Object Model (COM), such as Visual Basic, VBScript, JavaScript, C, and C++ to make common directory calls to an underlying directory service.  ADSI providers include Lightweight Directory Access Protocol (LDAP), NDS, Bindery, and Windows NT (SAM). Programmers and system administrators normally use ADSI to automate or script the bulk manipulation of directory entries.
Collaboration Data Objects (CDO) for Windows 2000
 A high-level application programming interface (API) that allows applications to programmatically access Simple Mail Transfer Protocol (SMTP) and Network News Transfer Protocol (NNTP) protocol stacks on a computer running Windows 2000. For example, an automated mailer routine can e-mail Web pages containing reports to employees. CDO for Windows 2000 is included with the Windows 2000 operating system and its services are supplied from the Cdosys.dll file.

connection agreement
Used by the Active Directory Connector (ADC) to control replication between an Exchange 5.5 or earlier site and Active Directory. The standard recipient connection agreement replicates Exchange recipient objects (mailboxes, distribution lists, custom recipients, and public folder proxies) and Active Directory objects (users, groups, contacts, and public folder proxies) between the Exchange 5.5 directory and Active Directory. Connection agreements define the server names to be contacted for replication, the object classes to replicate, the target containers, and the replication schedule.
contact
An Active Directory object that represents a user who does not have a Windows logon account or a mailbox. For example, a contact may represent a user outside of the organization. A contact in Windows 2000 is equivalent to a custom recipient in earlier versions of Exchange.
domain controller
A server that authenticates users for a domain. There must be at least one domain controller in each domain within the forest. Each domain controller holds a complete replica of the domain-naming context that the server is a member of, and a complete replica of, the configuration and schema naming contexts for the forest. A domain controller can be promoted and demoted through the dcpromo utility.

domain mode
An Active Directory domain can be in either mixed-mode or native-mode. In mixed-mode, the domain is restricted to limitations, such as the limitation to 40,000 objects, imposed by the Windows NT 4.0 domain model. However, Windows 2000 domain controllers and Windows NT 4.0 backup domain controllers can co-exist seamlessly within the domain without problems. Switching to native-mode, which is irreversible, allows the directory to scale up to millions of objects and overcome the constraints of the legacy SAM, but requires that all domain controllers be upgraded to Windows 2000. A domain in native-mode allows for rich-group creation and nesting, which is advantageous to Exchange 2000.
Note that Windows NT 4.0 member servers can still exist within a native-mode domain. Additionally, clients do not have to be upgraded before the domain mode is switched.
Domain Name System (DNS)
A major standards-based protocol that allows clients and servers to resolve names into Internet Protocol (IP) addresses and vice versa. Windows 2000 extends this concept by supplying a Dynamic DNS (DDNS) service that enables clients and servers to automatically register themselves in the database without needing administrators to manually define records.
domain tree
A collection of domains that have a contiguous namespace, such as microsoft.com, dog.microsoft.com, and cat.microsoft.com. Domains within the forest that do not have the same hierarchical domain name are located in a different domain tree. A disjoint namespace is the term used to describe the relationship between different domain trees in the forest.
enterprise
See forest.
forest (also known as enterprise)
A collection of domains and domain trees. The implicit name of the forest is the name of the first domain installed. All domain controllers within a forest share the same configuration and schema naming contexts. To join an existing forest, the dcpromo utility is used. The first domain within the forest cannot be removed.

global catalog
A server that holds a complete replica of the configuration and schema naming contexts for the forest, a complete replica of the domain naming context in which the server is installed, and a partial replica of all other domains in the forest. The global catalog has a record of  every object in the forest and has representations for them in its directory. It may not have information about all attributes, such as job title and physical address, for objects in other domains. Attributes that are tagged for replication to the global catalog are assigned through the Active Directory Schema Manager Microsoft Management Console (MMC) snap-in. There is only one policy for global catalog attribute replication in the forest. A global catalog monitors port 3268 for LDAP queries that are global to the forest, and port 389, which standard domain controllers use for local domain queries.
A domain controller can be made into a global catalog by selecting a check box in the Active Directory Sites and Services MMC snap-in. A global catalog can be changed into a domain controller by clicking to clear the check box.
Group
An object defined in Active Directory that contains members of other objects such as users, contacts, and possibly other groups. A group may be of type distribution or security, depending on the requirement, and have a scope of local, domain, or universal. This is similar to a distribution list in Exchange Server 5.5. For more information about groups and how they should be used in conjunction with Exchange 2000, refer to the “Exchange 2000 Internals: Group Objects” white paper at http://www.microsoft.com/exchange/techinfo/reskit.htm.
Lightweight Directory Access Protocol (LDAP)
A network protocol designed to work on TCP/IP stacks to extract information from a hierarchical directory such as X.500. It is useful for searching through data to find a particular piece of information.  LDAP version 2.0 allows for reading the contents of a directory database, whereas LDAP version 3.0 (defined under RFC 2251) allows users and applications to both read and write to a directory database.
naming context
A self-contained section of a directory hierarchy that has its own properties, such as replication configuration and permissions structure. Active Directory includes the domain, configuration, and schema naming contexts. Exchange Server 5.5 also uses naming contexts: organization, address book views, site, configuration, and Schema.
Namespace
A logical collection of resources that can be managed as a single unit. Within Active Directory, a domain defines a namespace.
Schema
The metadata that describes the use of objects within a given structure. In Active Directory, the schema governs the type of objects that can exist and the mandatory and optional attributes of each object. Windows 2000 Active Directory has an extensible schema that allows third parties to create their own object classes.
Schemas also exist for other components such as the message transfer agent and information store in Exchange Server.
security principal
A user who can log on to a domain and has access to network resources. In Active Directory, a user object is a security principal.
A non-security principal is an object represented in Active Directory that cannot access resources within the enterprise.
site
A collection of IP subnets. All computers that are in the same site should have high-speed network connections between them. Unlike an Exchange site, an Active Directory site does not include a unit of namespace. For example, multiple sites may exist within a single domain, and a single site may also span multiple domains.
user
In Active Directory, this is a security principal who can log on to the domain. A user may have either an e-mail address or an Exchange mailbox, or both, making the object either mail-enabled or mailbox-enabled.
user principal name (UPN)
A multi-valued attribute of each user object that the system administrator can set. A UPN allows the underlying domain structure and complexity to be hidden from users. For example, although 50 domains may exist within a forest, users log on easily, as if they were in the same domain. For consistency purposes, system administrators can make the UPN and users' SMTP address the same.
A user can log on to Active Directory by doing any one of the following:
Specifying the user name and domain name
Using the convention of username@domain-name in the user box
Using his or her UPN, such as [email protected]
Exchange 2000 Server: Acronyms and Terminology
ActiveX® Data Objects (ADO)
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 Web Storage System, or a SQL Server database.
Active Directory Connector (ADC)
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 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.
There are two versions of the ADC, one for Windows 2000 and one for Exchange 2000.
administrative group
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 permissions, are applied to an administration group, all child objects in the Directory Service (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.
Bridgehead server
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.
Collaboration Data Objects 1.21 (CDO 1.21, also known as active messaging and OLE messaging)
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), and appointments (IPM.Appointment). 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, which is installed with Microsoft Outlook 98 and above.
Collaboration Data Objects (CDO) for Windows 2000
CDO for Windows 2000 is defined in the Windows 2000 section earlier in this document.
Collaboration Data Objects (CDO) for Exchange 2000
An API that is a superset of CDO for Windows 2000. In addition to gaining programmatic access to 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, which is installed with Exchange 2000 Server.
CDO for System Management (previously known as Exchange Management Objects, EMO)
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, which is installed with Exchange 2000 Server.
Conference Management Service (CMS)
The network service that coordinates the booking of virtual resources for online meetings in the Exchange Conference Service. Each site, not domain, usually 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.
Configuration Connection Agreement
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. Configuration connection agreements work in conjunction with the Site Replication Service.
connection agreement
The configuration of information to replicate using the Active Directory Connector. Configuration information includes the servers that participate in the replication; object classes: mailbox, custom recipient, distribution list and user, contact, and group, to be replicated; containers and organization units to use for object placement; and the activity time schedule.
Distributed Authoring and Versioning (DAV, also known as WebDAV)
An extension to the Hypertext Transfer Protocol 1.1 (HTTP/1.1) that allows for the reading 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 protocol like a filing system. DAV commands include Lock, Unlock, Propfind, and Proppatch.
DSAccess
The Exchange 2000 component that provides directory lookup services for components such as SMTP, Message Transfer Agent (MTA), and the information store process. Client requests use the DSProxy service for directory access.
DSProxy
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.
Epoxy
See EXIPC
event sink
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 runs as the event is triggered) or asynchronous (code runs sometime after the event).
Exchange Conferencing Services (ECS)
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.
Exchange Virtual Server (EVS)
When clustering, you allocate different resources, such as storage groups, to an EVS. In the event of node failure, an EVS can be moved from the failed node to one of the remaining nodes.
EXIPC (previously known as Epoxy)
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 that data transfer was efficient. The Exchange 2000 architecture separates the protocols from the database for ease of management and to support future architectures.
Extensible Storage Engine (ESE, also known as JET)
Previously 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.
front-end and back-end
An Exchange 2000 configuration in which clients access a bank of protocol servers, the front-end, for collaboration information, which in turn, communicate with the data stores on separate servers, the back-end, to retrieve the physical data. A front-end and back-end configuration allows for a scalable, single point of contact for all Exchange-related data.
hosted organization (also known as virtual server, virtual machine, virtual organization)
A collection of Exchange services including 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 (ISPs) to host multiple companies on the same physical computer. A hosted organization is not limited to a single Exchange 2000 server.

Installable Filing System (IFS)
A storage technology that functions as a filing system. It makes mailboxes and public folders available as traditional folders and files through standard Win32® processes, such as Microsoft Internet Explorer and the command prompt.
instant messaging (IM)
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.
Instant Messaging Presence Protocol (IMPP)
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.
Internet Messaging Access Protocol version 4 (IMAP4)
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.
Joint Engine Technology (JET)
Defines the low-level access to underlying database structures in Exchange Server 4.0 and 5.0. JET was replaced by ESE in Exchange Server 5.5 and Exchange 2000.
link state algorithm (LSA)
The algorithm propagates 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.
mail-based replication (MBR)
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.
Message Database (MDB)
An instance of a database implemented in Exchange server. A single Message Database is usually identified as being public or private depending on the type of data that it stores. A single Exchange 2000 server can accommodate up to 20 active Message Databases.
Message Transfer Agent (MTA)
The component in all versions of Exchange Server that transfers messages between servers using the X.400 protocol.
Messaging Application Programming Interface (MAPI)
The API that is used by Microsoft messaging applications such as Microsoft 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.
metabase
A database that contains metadata such as that used by IIS to obtain its configuration data. The metabase can be viewed through utilities such as Metaedit.
metabase update service
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.
metadata
Data about data. In Exchange, this term is used to describe features of Active Directory and to describe the structure within the store or the MTA.
mixed-mode site
An Exchange 5.x site that also contains Exchange 2000 servers.
Multipoint Control Unit (MCU)
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.
Name Service Provider Interface  (NSPI)
Part of the DSProxy process that accepts Outlook client directory requests and passes them to an address book provider.
Network News Transfer Protocol (NNTP)
A standards-based protocol that includes simple command verbs to transfer USENET messages between clients and servers, and between servers. NNTP uses TCP/IP port 119.
OLE DB
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.
Outlook Web Access
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.
policy
A collection of configuration settings that can be applied to objects of the same class in Active Directory. In Exchange 2000, this may include mailbox thresholds and deleted item retention. You can use policies to simplify the administration of Exchange. You can define a policy that controls the configuration of some or all settings across a server or other objects in an Exchange organization. After policies are defined and implemented, editing the policy and applying the changes will change the configuration of all servers and objects covered by the policy.
Post Office Protocol version 3 (POP3)
An Internet protocol that allows a user to download mail from his or her inbox on a server to the client computer where messages are managed. This protocol works well for computers that are unable to maintain a continuous connection to a server. All versions of Exchange server except version 4.0 support POP3. POP3 uses TCP/IP port 110 for client to server access.
protocol farm
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.
public folder connection agreement (PFCA)
A connection agreement in ADC that is responsible for replicating Public Folder proxy objects between the Exchange 5.5 directory and Active Directory. These objects are necessary for sending e-mails directly to the folder. Each PFCA is hard-coded to be two-way, and will replicate between the site naming context in Exchange 5.5 and the Microsoft Exchange System Objects container in the Active Directory domain. It is customary to create one PFCA for each Exchange 5.5 site in the organization.
public folder tree (also known as public folder root and top level hierarchy, TLH)
A collection of public folders created under the same hierarchical namespace. Previous releases of Exchange server used a single tree called All Public Folders,  but 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 Message Databases. A public Message Database 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.
Recipient Update Service  (previously known as RUS)
This is part of the Exchange System Attendant and is responsible for keeping address lists up-to-date and creating proxy addresses for users.

Remote Procedure Calls (RPC)
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-mode organization.
resource
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 Active Directory.
routing group
A collection of Exchange servers that have full-time, reliable connections. Messages sent between any two servers within a routing group go directly from source to destination. Routing groups are optional and are not visible in System Manager unless they are enabled. Additionally, a routing group defines the boundary for public folder access.
routing group connector (RGC)
A connector in Exchange 2000 that connects routing groups to one another. A RGC is unidirectional and can have separate configuration properties, such as allowable message types over the connection. Routing group connectors use the concept of local and remote bridgehead servers to dictate which servers in the routing groups 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.
routing service
A component in Exchange 2000 that builds link state information.
RVP (Note that this name is preliminary and may change)
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 WebDAV with Extensible Markup Language (XML) that is used to send subscriptions and notifications between Instant Messaging clients and servers.
Schema
The metadata that describes how objects are used within a given structure. In relation to Exchange, this term is used in reference to Active Directory, and to describe the structure within the store or the Message Transfer Agent (MTA).
Simple Message Transfer Protocol (SMTP)
The de facto standard protocol for Internet e-mail, SMTP transfers e-mail from server to server and from e-mail system to e-mail system. A typical SMTP session begins with an HELO (or ELHO) command from the sender, followed by negotiation between sender and receiver and a series of commands. In Exchange 2000, SMTP is the native transport protocol.
sink
See event sink.
Site Consistency Checker (SCC, also known as the SKCC)
The updated version of the Exchange Server 5.5 Knowledge Consistency Checker (KCC) that works in conjunction with the Exchange Site Replication Service to ensure that knowledge consistency of sites, administration groups and Active Directory domains is maintained when operating between Exchange 2000 and Exchange 5.5. When changes are detected in either environment, the SCC adjusts existing configuration connection agreements.
Site Replication Service (SRS)
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.
storage group
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 connected and disconnected. Each Exchange 2000 server architecture can host up to 16 storage groups, although only 4 can be defined through the Exchange System Manager.
Store
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.
system attendant
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.
T.120
The International Telecommunications Union (ITU) T.120 standard is made up of a suite of communication and application protocols developed and approved by the international computer and telecommunications industries. Using these protocols, developers can create compatible products and services for real-time, multipoint data connections and conferencing. With T.120-based programs, multiple users can participate in conferencing sessions over different types of networks and connections.
virtual root
A mapping between a specific path or name and a physical storage location; a local file directory network share or redirection to another URL. For HTTP, a virtual root defines a mapping between a URL path and a physical storage location. For NNTP a virtual root defines a mapping between a news group name and a physical storage location.
Virtual server
A collection of services that appear to clients as a physical server. It is an instance of a protocol service with a defined set of IP address and port combinations and an independent collection of configuration properties. A virtual server typically includes all of the resources necessary to run a particular application, including a network name resource and an IP address resource.
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.
Web Distributed Authoring and Versioning (WebDAV)
See Distributed Authoring and Versioning.
Web Storage System
The database architecture in Exchange 2000. Previous releases of Exchange 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 Information 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 through a universal naming convention (UNC) path to allow other clients to connect to the data.


For more information consult http://www.microsoft.com/exchange/