In 1972, Ray Tomlinson of the Bolt, Beranek, and Newman (BBN) Corporation developed the first email program, which utilized the Network Control Protocol (NCP). NCP was one of the first networking protocols, and was implemented in the Department of Defense’s (DoD’s) Advanced Research Projects Agency network (ARPAnet). The purpose of this program was to allow the exchange of messages between linked sites on the ARPAnet to create a faster way to communicate. A few years later, a group headed by Vinton Cerf, from Stanford, and Bob Kahn, from the Defense Advanced Research Projects Agency (DARPA), developed a new network protocol known as the Transmission Control Protocol/Internet Protocol (TCP/IP). This protocol allowed diverse computer networks to interconnect and communicate.

With the development and standardization of TCP/IP, the Internet was born, allowing vast networks to interconnect and communicate. Over the years, as the Internet began its metamorphosis, the first email standards, such as UUCP (Unix-to-Unix Copy), were developed to provide the ability to send text messages using the American Standard Code for Information Interchange (ASCII) character set. With these standards, messages couldn’t use non-English symbols, such as accents and other diacritical marks. Additionally, these standards were incapable of transmitting files, such as images, sounds, and documents consisting of multiple fonts and text styles.

As the Internet grew, new standards were developed to accommodate the ever-growing need for seamless communication. Standards, such as UUEncode/UUDEcode, which were used to send non-ASCII files (such as executables and images), required a high level of expertise from their users. To solve these and other problems, the Multipurpose Internet Mail Extensions (MIME) standard was proposed in RFC 1521. MIME allows multiple character sets, embedded pictures, and binary documents (even sound and video) to be sent via most existing email systems.

Within the past six to eight years, the Internet has been commercialized and is now one of the fastest-growing resources for information. Government studies indicate that, by the year 2000, there will be over 500,000 host servers on the Internet. These studies also show that by that same year, there will be close to 5,000,000 intranet servers. Although the growth of the Internet is incredible, it is the underlying growth rate of intranets that drives the need for effective communication.

In their earliest stages, email programs were designed to provide basic communication. At that time, the need for sophisticated messaging systems had not yet emerged. The technology required to connect multiple systems was still in its developmental stages. However, internetworking technologies quickly improved, and allowed a multitude of hardware platforms as well as network operating systems to connect and interact.

As technology improved and more corporations began implementing intranets, the need to develop messaging systems that were capable of communicating within the intranet’s confines, as well as with the Internet, began to develop. The need for messaging systems of greater capabilities was directly related to improvements in internetworking technologies. It is this ever-increasing need for communication that Microsoft has endeavored to meet, with a variety of products, the latest of which is MS Exchange.

As networks grew in size and complexity, Microsoft recognized the need for greater functionality and began engineering a new messaging system from the ground up, intended to replace MS Mail. Thus, today Microsoft offers its Exchange Server, perhaps one of the most powerful messaging systems in the industry, capable of servicing any business, regardless of its size. Likewise, Microsoft has replaced its original, underpowered MS Mail client software with a new generation of powerful, friendly Outlook email clients.

The continuing evolution of messaging systems has effectively changed the way we communicate. Factors, such as distance and transit times, are no longer a consideration. As email continues to increase in popularity and ease-of-use, it is becoming a preferred method for communication. Today, you can send an email message clear across the world within a few hours. You can post information on a server that can be viewed by everyone or specifically targeted audiences within your corporation. You now have the ability to effectively communicate with your colleagues in offices located in other cities, states, and countries. In the past few years, Microsoft has made strides in the software industry that have had a large impact on electronic commerce, making it more efficient, cost effective, and accurate.

During the development of Microsoft Exchange, one of the greatest concerns was the ability to provide a complete communications solution. Nowadays, it is rare to find a single operating system capable of encompassing all the functions of a single corporation. Typically, within a single large corporation you will find several operating systems, such as DOS, Windows 3.x, Windows 95, Windows NT Workstation, Macintosh, and some derivative of Unix. You might also find several network operating systems, such as NetWare, Banyan Vines, and Windows NT. Exchange Server is designed to communicate with all of these effectively.

If your corporation has offices worldwide, Exchange Server supports many ways to connect to these sites. Exchange Server can use any wide area network (WAN) connectivity that supports TCP/IP, IPX/SPX (Internetwork Packet Exchange/Sequenced Packet Exchange), or NetBEUI (Network BIOS Extended User Interface) network protocols. You can configure Exchange to use Windows NT Server’s Remote Access Service (RAS) to allow connectivity with remote users. Exchange Server also supports data encryption. It can be configured so users can encrypt messages using public keys, to make transmission of their messages more secure.

In the following sections, you’ll explore the various features of Microsoft Exchange Server. This includes an in-depth look at the components that make up Exchange Server, how mail is sent and received through Exchange, and how to set up Exchange clients. In addition, you’ll explore the client/server architecture upon which Exchange is based. Finally, we take a look at some of the features that are new to Exchange Server 5.5.

Exchange Server Concepts

Exchange Server is made up of several components that create and manage objects within the system. These objects are the messaging system resources and can be servers, mailboxes, public folders, address books, and so forth. The way these objects are structured and organized is part of the Exchange architecture. Exchange is organized hierarchically, grouping objects and items by class, order, rank, and so on. Each of these objects is a member of the hierarchy tree: The highest-ranked object in the Exchange hierarchy sits at the top of the tree. This object represents the family patriarch. Below the patriarch are other objects that represent children, with their own children situated below them, and so forth.

The three objects that constitute the main structure in the Exchange hierarchy are:

Organizations

Sites

Servers

Exchange Servers are computers that run the Windows NT operating system and the Exchange Server software. Residing on these servers are the mailboxes, public and private folders, data, and other information that comprises a site. Each of the site’s servers inherits configuration parameters from the site, while at the same time, each one can be configured individually. For example, recipients within a site can be administered at the site level; however, they may also be administered from their home servers (the server where their mail accounts were created).

In the sections that follow, you’ll learn more about the core components that make up Exchange Server, and how they interoperate to handle message retrieval and delivery services.

There are several vital components that provide functionality to Exchange Server. They are referred to as the core components and are files that take the form of executables (EXEs) and Dynamic Link Libraries (DLLs) files. These core components are sometimes called services, because many of them run as services on the Microsoft Windows NT Server operating system. The following elements are considered core components for Exchange Server:

Directory Service (DS)

Information Store

Message Transfer Agent (MTA)

System Attendant (SA)

Directory Service

The primary purpose of the directory is to provide a centralized location for objects within the Exchange environment. This allows users and administrators to locate a system’s resources easily so that they may use or administer them. Objects stored in the Exchange directory have properties, also called attributes, which define characteristics for types of objects. For example, an object can be a user (such as John Smith) or an entire Exchange organization (Best); each type of object has a different collection of associated attributes. Furthermore, objects also have associated permissions, which determine their access characteristics. As shown in Figure 1.2, the object Marie Deloris can take properties such as first name, last name, job title, email address, and numerous others.

Information Store

The Information Store creates and manages the message database on an Exchange Server. This database stores information such as email messages, electronic forms, spreadsheets, word processor documents, graphics images, audio files, and many other items from almost any application. Users can access the information within the Information Store through their mailboxes and folders in their client applications. The Information Store is comprised of two main databases:

Message Transfer Agent (MTA)

The Message Transfer Agent (MTA) handles routing for all messages, whether such messages are routed within the same site, between different sites, or to
so-called foreign sites (which means that they’re routed to non-Exchange servers). Additionally, the MTA uses components known as connectors. Connectors manage the actual connection to other systems as well as the transfer of data, and the MTA handles all routing functions. The primary functions of the MTA include:

Originator/Recipient Addressing

Message format translation

Message routing

The MTA is modeled after the X.400 standard (which is discussed in the section entitled "Exchanging Mail" later in this chapter) and, as such, uses the Originator/Recipient Addressing scheme. If messages are routed to an X.400 messaging system, the MTA changes the format of such messages from the native Exchange format, known as the Microsoft Database Exchange Format (MDBEF), to a native X.400 format, known as the Interpersonal Message (IPM) format.

The ability to translate messages to the IPM format allows Exchange clients to exchange mail with X.400 mail users. When an MTA receives a message to be forwarded, it first determines the route that the message must travel to reach its destination. It then examines the message recipient’s Distinguished Name (DN). If that address does not resolve the next route, it then examines the Originator/Recipient Address. The MTA compares the address with the routing information contained within the Exchange Server’s Gateway Address Routing Table (GWART). Because there may be several possible paths available, administrators can assign values to such different paths, where these values are called costs. Costs allow priorities to be assigned to different routes, and the MTA can be instructed to factor cost into its routing decisions.

Thus, when an MTA encounters multiple possible paths between a sending and a receiving server, it automatically chooses the path with the lowest cost. If the MTA cannot resolve the specified address, it sends the message originator a report known as a non-delivery report (NDR). This alerts the user or administrator who created the message that it is undeliverable, and provides valuable feedback when messages cannot be sent because of addressing or other reachability problems.

System Attendant (SA)

The System Attendant (SA) is an Exchange service that runs in the background. It monitors and logs most Exchange Server processes, and builds and maintains a routing table for the site to which it belongs. The SA logs information, such as tracking information that includes the routes that messages take, and indicates whether or not messages are received at their destinations. The SA also compiles the routing tables for the entire site. This is the table that the MTA uses when it determines which route to assign to outgoing messages.

In addition to these functions, the SA monitors the connection between servers, verifies such connections, and, at the same time, checks on Exchange services running on other servers. The SA sends test messages between itself and other servers to execute these checks. In addition, whenever new user accounts are created, the SA is responsible for generating their underlying email addresses.

In the following section, we put together all the various pieces of Exchange Server that we’ve discussed thus far. It is essential to understand these underlying components, and their interrelationships, to grasp the power of Exchange Server fully and completely.

Exchanging Mail

The process of exchanging email resembles using the postal service to exchange letters. When users send email, the Exchange Server assumes the role of the post office. Exchange Server is responsible for processing end-user requests and routing mail to the appropriate destination. The only information end users must know is the destination address for their messages (unlike the post office, Exchange automatically knows each user’s return address).

When a client uses Exchange Server to send a message, that message is first delivered to the Information Store, which holds all messages to be sent or received on an Exchange Server. The Information Store occupies a database that is the primary system database for Exchange (SYSTEM.EDB). The Information Store cannot be manipulated or directly accessed by users or administrators. Instead, the Information Store acts like the post office, and is comprised of two main components–a public Information Store and a private Information Store–which, as we discussed earlier, are also databases.

After the Information Store receives a message, it then decides where that message should be delivered. It does this by searching the directory. As mentioned earlier, the directory incorporates both a directory database and a Directory Service. The directory database (DIR.EDB) manages all objects in the organization and makes its information available to appropriate users, administrators, and system processes. The Directory Service manipulates information within the directory database. It also processes directory requests from users and other applications. In addition, the Directory Service also supports other important functions:

It maintains the directory objects stored within the directory database and displays them in a hierarchical tree structure.

It sends replication notifications to directories on other servers and receives directory replication notifications from other servers.

It provides an interface between Exchange clients and the directory database.

It enforces rules to control the structure and contents of the directory database.

After the directory has verified the necessary information, the message is handed off to the MTA, which is responsible for delivering that message. The MTA also ensures that the message is delivered to its destination successfully. Thus, the MTA is an object that routes messages within a system, as well as to gateways that connect to outside email systems. The MTA provides resolution for external addresses, and, if necessary, can even convert message formats to ensure compatibility with destination email services. The MTA uses four components to route data to other email systems and servers:

Exchange Site Connector

Remote Access Service (RAS) Connector

X.400 Connector

Internet Mail Connector

Each of these components is explained in the sections that follow.

Exchange Site Connector

Remote Access Service (RAS) Connector

The RAS Connector is used between sites that do not have a permanent connection between them. It provides a way to connect using asynchronous communications, such as a regular dial-up phone connection, ISDN, or X.25. It is this connector that allows remote servers and users to communicate with Exchange Server.

X.400 Connector

The Exchange Server X.400 Connector is based on the X.400 standard, developed by the International Telegraph and Telephone Consultative Committee (CCITT). X.400 is a set of standards related to the exchange of electronic messages. These messages can take the form of voice mail, faxes, telexes, or email. This standard was developed to enable the creation of a global electronic messaging network. The goal for electronic messaging through the X.400 standard is to make it possible to send an electronic message from anywhere in the world to almost anywhere in the world, just as you can place a phone call from almost anywhere, to almost anywhere. X.400 defines a series of protocols at the application level, and is dependent on other protocols, such as the X.25 protocol for actual physical transportation of data. X.400 standards are referred to by their year of official adoption, and by a specified color. To date, X.400 versions include the following:

1984 "Red Book"

1988 "Blue Book"

1992 "White Book"

As this standard applies to Exchange Server, the X.400 Connector connects sites that support only low bandwidth connections, or that use existing X.400 backbones (such as public X.400 systems). Exchange Server supports the following X.400 protocols, with the following related transports:

Transport Protocol, Class 0 (TP0)/X.25

Transport Protocol, Class 4 (TP4)/Connectionless Network Protocol (CLNP)

Transmission Control Protocol/Internet Protocol (TCP/IP)

To achieve a global messaging system, a standard numbering system was created for X.400. This numbering system had to be capacious enough to accommodate the entire world’s population. The address scheme that X.400 uses is called the Originator/Recipient Addressing (O/R Addressing) scheme. This scheme uses a hierarchical format and consists of countries, communication providers, corporations or organizations, and several other categories. These categories are called fields and are represented in Table 1.1.

The Originator/Recipient Address (see Figure 1.3) specifies an unambiguous path to a location within an X.400 network, where the recipient is located. It does not specify the path the message must take, only a path to where the recipient is located.

Internet Mail Connector

The Internet Mail Connector allows users to communicate with other users on the Internet. This occurs through the use of the Simple Mail Transfer Protocol (SMTP). Exchanging mail between such users is transparent to Exchange users, because the SMTP protocol is built into Exchange Server.

To ensure that the post office is working efficiently and that all email is being routed correctly, the System Attendant monitors the Information Stores. Additionally, it monitors connections between servers to make sure that messages sent from a sending server are received at the target server. The System Attendant is a service that must be running for Exchange messaging processes to run. In addition, the SA also performs several important functions:

It creates email addresses for new message recipients to ensure that email gets to the correct mailbox on the correct server.

If the messaging tracking feature is enabled, the SA logs the information needed to track messages.

For example, if you have a company that has multiple offices in two different locations, an Exchange Server at each location can service its own site. In this case, the two site servers represent the entire enterprise. The directory information on these servers is shared and can be replicated to the other sites. This provides accurate information for the entire enterprise. As shown in Figure 1.5, each site within an enterprise can have its own Exchange Server, which is managed locally. The directory on these servers contains the information for the entire enterprise, and it’s automatically replicated between them.

Also, you may have offices in multiple locations yet use only one organization server for the entire enterprise. This is not the most efficient method, because all users at the second location must traverse a WAN link to access the Exchange Server. For example, you could have a company with multiple locations and only one Exchange Server located at one of its locations. This server would be the organization server by default. The users at any location other than the one where the organization server resides can still access this server, but they must traverse the WAN to do so. As shown in Figure 1.6, the organization is administrated from one server, even though there are multiple locations. This allows for centralized management and ease of administration, at the cost of communications efficiency and slower access for remote users.

Given this organizational division, Exchange Server is scalable and can accommodate both large and small companies. The hierarchical scalability of Exchange Server also simplifies the task of administration and centralizes client management.

Exchange Clients

Exchange Server must run on a Windows NT Server computer; however, the network and clients can run on a variety of network operating systems, including Windows NT, NetWare, and Banyan Vines.

For Exchange Server to coexist in a Novell NetWare environment, the following requirements must be met:

Gateway and Client Services For NetWare (GSNW and CSNW) must be installed. To optimize the performance of email delivery on Exchange Servers using the IPX/SPX protocol, you must install GSNW (on Windows NT Server installing GSNW also automatically installs CSNW).

File scan on NetWare servers must be enabled. If you plan to store any email data on a NetWare server, you must enable file scan on that server. Because Microsoft Outlook does not support specific file operations for NetWare servers, file scan must be enabled on the shares where the data is stored to make them accessible.

Microsoft Exchange Server is a client/server system. Client/server means that processing takes place on both client and server computers. This is a key advantage of the client/server architecture–which is sometimes called distributed processing. Here is an example of what occurs in distributed computer processing: A client sends a request to the server, then the server processes the request and returns some result to the client. Depending on the request a client makes, the server could also send data back to the client for processing. This occurs if the client request requires a local process to execute (such as moving email files from the server to a local directory, or from a local directory to the server). One disadvantage of a client/server model is that servers carry a disproportionate share of the processing load; this usually imposes greater requirements on the server hardware platform and related system components (such as RAM, disk space, network connections, and so forth).

When a user reads a message, the client program issues a Messaging Application Programming Interface (MAPI) instruction. The client-side RPC protocol transfers this instruction to the server where the message physically exists. The server-side RPC protocol receives the request, executes it, and sends the message
back to the client (which is viewed on the screen). RPC clients make requests, and RPC servers make replies; hence, RPC is also known as a request/reply protocol.

Microsoft’s MAPI provides a standard application programming interface (API) for client/server messaging interaction. To better understand MAPI, let’s first go over what an API is. All programs include certain built-in functions. Other programs, through the use of specific instructions, can invoke these functions. Such specific instructions that permit one program to tell another program what to do define an API. Several years ago, most client/server messaging products included their own APIs to support client/server interaction. Unfortunately, this also meant that client applications would only work with whatever messaging system its API invoked. Likewise, if a user needed to connect to multiple messaging systems (such as Lotus Notes, Microsoft Exchange, cc:Mail, and so on), that user would have to install multiple client applications (see Figure 1.8) to gain access to all of them.

Microsoft Cluster Server MS Cluster Server provides fault tolerance for hardware in the event of a system failure. A cluster includes an active node and a secondary node. The active node acts as the primary mail server to processes and route messages on a network. Both active and secondary nodes monitor each other constantly. If the active node experiences a hardware failure, the secondary node assumes the role of the primary mail server without interrupting mail service or dropping client connections. MS Cluster Server is installed on the active node first, then on the secondary node. When the cluster is established, setup detects that Exchange Server is installed on the active node and adds the Exchange Server resources, such as the System Attendant, the directory, and the Information Store, to the secondary node. By doing so, this enables the active node to failover to the secondary node. Failover protection ensures that another server always remains available, and mail service need never be interrupted.

Enhanced security policies Multiple password policies can be set to prevent changes to the Key Management Server without authorization from administrator(s). The Key Management Server provides data security and integrity as well as proof of origin for messages. It allows users to encrypt messages and to sign their messages digitally, raising overall confidentiality within an organization. By setting multiple password policies for the Key Management administrator’s account, it reduces the chances of unauthorized changes being made to the Key Management Server configuration. To make a change in the Key Management Server configuration, an administrator must supply two valid passwords.

Trusted messages sent between organizations This allows users to verify the source of messages sent from other organizations.

New database structure for the public Information Store, private Information Store, and directory With the new database structure, the Information Store is limited only by your hardware’s capacity. The database engine has been enhanced, and provides more robust data storage capabilities. Its enhancements include better caching schemes for quicker updates to transaction logs. Copying of the transaction logs into the database is performed sequentially and is more dynamic, and requires fewer threads to be spawned to carry out those copy commands. This increases overall performance and can be beneficial for balancing server loads.

Ability to set deleted item retention period for Information Stores, mailboxes, and public folders If using Microsoft Outlook version 8.03 or later, users can retrieve deleted items in mailboxes and public folders by using the Recover Deleted Items command.

Incorporates ability to restrict users access to address book views If you have multiple companies on a single Exchange Server, you can restrict users in one company from viewing the address book of another company.

Supports multiple and differential offline address books This allows users to download differential entries in offline address books, so only the changes in the offline address books that have occurred since the last download will be downloaded.

Supports MIME Hypertext Markup Language (MHTML) This enables the MIME encapsulation of aggregate documents, such as an HTML document with inline pictures.

Migration of Lotus cc: Mail DB8 The Lotus cc: Mail source extractor supports Lotus cc: Mail version 5.x (DB6), version 6, and version 8 (DB8).

Microsoft Exchange Chat service Exchange Server now includes chat services that enable users to chat with each other online and in real time.

Supports Internet Message Access Protocol version 4 (IMAP4) This is the email protocol that enables users to retrieve email messages from their Inbox and retrieve Microsoft Exchange public folder information.

All in all, these new capabilities add significantly to Exchange Server’s capabilities, and also to user’s abilities to exchange and interact with a broader variety of materials than ever before.

application programming interface (API)–A set of instructions that allow one program to invoke the functions of a second program.

child objects–Objects located within parent objects. The permissions granted to a child object are inherited from its parent.

connector–An object that sets the properties for a given connection. Every established connection uses connectors to communicate with the messaging system.

container–An Exchange Server object that holds other objects. Mailbox objects are placed in a recipient’s object. This means that the recipient’s object is also a container.

directory–Holds information about the organization’s resources and users, such as servers, mailboxes, public folders, and distribution lists. The directory and its contents get replicated automatically to all servers within the same site.

directory database–The database that contains all the information about the objects in your Exchange Server.

Directory Service–The service that manipulates the information contained within the directory database. This service processes requests from users and applications.

distributed processing–Computing activity that is distributed on both client and server computer systems, as clients make requests for services, and servers attempt to satisfy them.

enterprise–The corporate organization.

Information Store–Contains the messages in users’ mailboxes and public folders. The Information Store’s two main components are the public Information Store and the private Information Store.

Message Transfer Agent (MTA)–The component responsible for routing messages to their destinations. The MTA provides addressing and routing information for sending messages.

Messaging Application Programming Interface (MAPI)–A series of APIs designed specifically for messaging.

object–A messaging system resource, such as a server, mailbox, public folder, or address book, that is listed in the directory.

organization–The largest administrative unit in Microsoft Exchange Server, usually consisting of one or more sites. Organizations provide services for an entire group.

parent object–An object that contains other objects. An object is a parent to all the objects within it; all objects contained within it are its child objects, or children.

parent-child relationship–The relationship that exists between a parent object and a child object. The relationship is dictated by permissions, which are inherited from parent to child.

permissions–A set of rules that controls access to objects, such as containers within a system. These rules dictate which users can access an object and how those users may manipulate it.

private Information Store–The component of the Information Store that contains user mailboxes and messages.

public Information Store–The component of the Information Store that contains public files, folders, and messages.

Remote Procedure Call (RPC)–A protocol for starting programs on a different computer, feeding them input, and accepting their output. This allows computers to spread the processing load among a number of computers.

site–A server or series of servers that communicate with each other using the same directory information.

System Attendant (SA)–A service that must be running for messaging processes to run. The SA is a maintenance service that runs in the background.

Windows NT domain–A grouping of network servers and other computers that share common security and user account information. Users log on to the domain, not individual servers in the domain. Once logged on to the domain, the user has access to the network resources within the domain.

1. When a user sends a message using Exchange Server, where is the message first received for processing?

a. Message Transfer Agent

b. Information Store

c. System Attendant

d. Directory

2. Which of the following make up the Information Store? (Choose all that apply.)

a. Key Management Server

b. Private Information Store

c. Directory Service

d. Public Information Store

3. When you send a message using Exchange Server, what component is responsible for looking up the recipient information for routing the message?

a. Public Information Store

b. Private Information Store

c. Directory Service

d. Message Transfer Agent (MTA)

4. In which component are the user mailboxes and messages kept on an Exchange Server?

a. Directory Service

b. Public Information Store

c. Information Stores

d. Private Information Store

5. The System Attendant is a that monitors messaging processes and ensures email is getting routed correctly.

a. Service

b. Runtime

c. Procedure call

d. Process

6. Exchange Server is which type of messaging system?

a. Front end/back end

b. Application/client

c. Client/server

7. What are the two major components of client/server architecture?

a. High end

b. Front end

c. Low end

d. Back end

8. The front end is loaded on the server system. True or False?

9. The back end provides the main administrative tasks, as well as basic messaging services. True or False?

10. What is the Remote Procedure Call (RPC) protocol?

a. Protocol designed specifically for client/server communication.

b. The interface the user interacts with.

c. A protocol used specifically for Microsoft Networking.

d. The process by which the System Attendant monitors the messaging system.

11. The directory consists of two main components: the and the .

12. On which network environments can Microsoft Exchange Server coexist? (Choose all that apply.)

a. Banyan Vines

b. Novell NetWare

c. Windows NT

d. Unix

13. On which platforms can you currently install the Outlook client? (Choose all that apply.)

a. Apple Macintosh

b. Windows 95, 3.x

c. Windows NT 3.1, 3.51, 4

d. Windows NT 3.51, 4

14. To achieve automatic directory replication, site servers that belong within the same organization musts also belong to the same .

15. Which type of Exchange Server can control and manage other servers within the same enterprise?

a. Site Server

b. Administrative Server

c. Exchange Server

d. Primary Site Server

16. The component that allows Exchange Server to connect with other existing systems and acts as the translator between these systems is known as the .

a. Messaging Application Programming Interface (MAPI)

b. Exchange Site Connector

c. Remote Procedure Call

d. Information Store

17. What is the purpose of the X.400 Connector?

a. To develop a standard numbering system

b. To develop a series of standardized transport protocols

c. To create a global electronic messaging network

d. To develop the Originator/Recipient Addressing scheme

18. Which of the following transports of the X.400 Connector does Exchange Server currently support? (Choose all that apply.)

a. TP0/X.25

b. TP1/X.25

c. TP4/CLNP

d. TCP/IP

19. Connectors do not have to be used with Exchange Server version 5.5. True or False?

20. The type of RPC being made depends on the network protocols being used. True or False?

1. Your company has two locations–London and New York. You want to implement Exchange Server as your messaging environment.

Required result:

Optional desired result:

Proposed solution:

a. The proposed solution provides the required result and the optional desired result.

b. The proposed solution provides only the required result.

c. The proposed solution does not provide the required result.

2. You have several employees in your corporation who will be traveling to a remote location and working there for an extended period of time. As such, they will be setting up a server at the remote location.

Required result:

Proposed solution:

a. The proposed solution is a fair representation of Exchange Server’s capabilities.

b. The proposed solution is not a fair representation of Exchange Server’s capabilities.