Export (0) Print
Expand All

Introduction to the Exchange 2003 Interoperability and Migration Guide

 

Topic Last Modified: 2006-03-07

These topics were created to help messaging administrators and consultants to connect and migrate non-Exchange messaging systems to Microsoft® Exchange Server 2003. These topics describe the process by which you design an efficient Exchange 2003 interoperability and migration strategy. Furthermore, these topics include prerequisites and actual procedures for connecting Exchange 2003 to common non-Exchange messaging platforms, including, but not limited to, Novell GroupWise. Connector components including Exchange Connector for Novell GroupWise, Exchange Calendar Connector, and general connectors based on SMTP and X.400 are described. The Exchange Migration Wizard, the fundamental tool for migrating user data, is discussed at length. There is also a troubleshooting topic to consult if you encounter issues with interoperability and migration.

These topics are designed to be both a quick reference and a hands-on resource for a variety of interoperability and migration scenarios, so that you can read the topics that interest you and skip the others. However, if you are a system consultant who specializes in migrating all non-Microsoft messaging platforms to Exchange 2003, you might find it worthwhile to read these topics from start to finish.

importantImportant:
Microsoft continues to update the tools that support interoperability between Lotus Notes R5/R6, Exchange Server 2003, and Windows Server 2003 Active Directory. Updated tools for Lotus Notes replace the Exchange Connector, Calendar Connector, and Migration Wizard that ship with Exchange Server 2003 (including Service Pack2). For more information about the tools, guidance and additional resources that are available to download, see Resources for Moving to the Microsoft Collaboration Platform. These tools provide additional functionality and address several issues that customers reported with older versions.

These topics provide detailed answers to the following questions:

  • What is the fastest route to a consolidated Exchange 2003 organization?

  • Which migration strategy is most suitable for my company?

  • What prerequisites are necessary for a successful migration to Exchange 2003?

  • What are the individual stages for connecting my existing messaging system to my new Exchange 2003 organization?

  • How do I synchronize recipient information between the Active Directory® directory service and other directory services?

  • How can my Novell GroupWise users share calendaring information with Exchange 2003 users?

  • How can I use the Exchange Migration Wizard to migrate private and public user data and directory information?

  • What are the best approaches to troubleshooting problems with connectivity, directory synchronization, or the Exchange Migration Wizard?

These topics are designed for messaging administrators and consultants who plan to migrate an existing messaging environment to Exchange 2003. Migration often includes an element of interoperability with foreign messaging systems. Therefore, system integrators who are preparing to connect Exchange 2003 to non-Exchange messaging systems but are not planning to migrate to Exchange 2003 will also find valuable information. The following professionals will obtain the maximum benefits from these topics:

  • Application service providers (ASPs) who want to migrate their messaging system to Exchange 2003.

  • IT architects who design and deploy Exchange 2003 in environments where a non-Exchange messaging system is already in place.

  • IT consultants who assist customers in migrating from non-Exchange messaging systems to Exchange 2003.

  • Messaging and system administrators who are responsible for implementing and managing messaging technology.

Before reading these topics, familiarize yourself with the following terms.

advanced queuing engine

A core component of the SMTP transport subsystem in Microsoft® Exchange Server 2003. It passes the messages from message queue to message queue, invoking event sinks, such as categorizer and routing engine, as needed to transfer the messages to their destinations.

body part

Defines the content type of an X.400 message. A single message can include multiple body parts for the actual message and message attachments. Body parts are identified by an object identifier.

bridgehead server

A computer that connects servers using a connector so that information can be passed from one server to another. In Exchange 2003 and Exchange 2000 Server, a bridgehead server is a connection point from a routing group to another routing group, remote system, or other external system.

categorizer

An internal component of the SMTP transport subsystem in Exchange 2003 that processes all messages that pass through the server. The categorizer resolves sender and recipient information against Active Directory, expands distribution lists, checks restrictions, applies per-sender and per-recipient limits, and bifurcates messages if multiple copies must be created (for example, if recipients require different message formats).

checksum

A calculated value that is used to test data for the presence of errors that can occur when data is transmitted or when it is written to disk. The checksum is calculated for a given chunk of data by sequentially combining all of the bytes of data with a series of arithmetic or logical operations. After the data is transmitted or stored, a new checksum is calculated in the same way using the (possibly faulty) transmitted or stored data. If the two checksums do not match, an error has occurred, and the data should be transmitted or stored again. Checksums cannot detect all errors, and they cannot be used to correct erroneous data.

connector

A component that enables information to flow between two systems. For example, connectors support message transfer, directory synchronization, and calendar querying between Exchange and other messaging systems. When two systems are in place, the basic user experience is maintained on both messaging systems. The exchange of mail and other information between Exchange and other messaging systems is transparent to the user, even if the two systems function differently.

Exchange store driver

A component in Exchange 2003 that enables the SMTP service to communicate with the Microsoft Exchange Information Store service.

foreign domain

A directory object that defines a messaging environment that is external to the local messaging system and uses different message formats and communication protocols. Foreign domains are used for addressing and routing purposes. The external messaging system is usually connected to the local messaging system using a gateway connector.

foreign messaging system

A messaging system that uses different message formats and communication protocols than the local messaging system. For example, Novell GroupWise is a foreign messaging system for Exchange 2003.

hub and spoke topology

A topology in which a central node performs all routing for the other nodes in the environment. The central routing node is the hub, and the connections to all other nodes are the spokes.

infrastructure

A physical structure that builds the foundation of a network. For example, the physical structure of a computer network consists of cables, hubs, switches, routers, servers, and other resources that form the communication infrastructure of a company.

Internet Security and Acceleration (ISA) Server

A software application from Microsoft Corporation to increase the security and performance of Internet access for businesses. ISA Server provides an enterprise firewall and high-performance Web cache server to securely manage the flow of information from the Internet through the enterprise's internal network.

local delivery queue

A repository for messages that are awaiting local delivery to mailboxes in a mailbox store on the Exchange server through the Exchange store driver.

mail exchanger (MX) record

A database entry in a Domain Name System (DNS) zone that points to an SMTP host that is responsible for message transfer to an Internet domain.

post-categorization queue

A special message queue in the advanced queuing engine of the SMTP transport subsystem of Exchange 2003 for messages after they have been categorized. Messages in this queue might be delivered locally or passed to the routing engine to determine the next hop on the transfer path.

pre-categorization queue

A throttling queue in the advanced queuing engine for messages that are waiting for categorization by the categorizer.

pre-submission queue

A special message queue in the advanced queuing engine of the SMTP transport subsystem of Exchange 2003 that represents the entry point for all messages into the advanced queuing engine. Messages in this queue have not been processed yet.

queue manager

A component of the SMTP transport subsystem in Exchange 2003 that maintains the link queues in the transport subsystem.

routing engine

A component of the SMTP transport subsystem in Exchange 2003 that determines the next hop for messages on the transfer path to remote destinations.

smart host

An SMTP host that forwards e-mail messages on behalf of other SMTP hosts and Internet clients to the next hop on the way to their destinations. Internet service providers (ISPs) often provide their customers with a central smart host that handles message transfer across the Internet. If a smart host is designated, the Exchange server needs only to transmit messages to the smart host, and does not require a direct connection to the mail exchanger (MX) host of the destination domain. A smart host is also called a relay host, and a smart host that accepts messages from any source on the Internet and relays them to other destinations on the Internet is called an open relay. Open relays are often sources of unsolicited commercial e-mail (spam).

SMTP protocol engine

A component of the SMTP transport subsystem in Exchange 2003 that communicates through SMTP with remote hosts and Internet clients.

topology

The physical arrangement or layout of a network infrastructure. The topology of a network can consist of local area network (LAN) connections, metropolitan area network (MAN) connections, and wide area network (WAN) connections, and the devices that connect these networks.

For additional definitions of Exchange 2003 terminology, see the Exchange Server 2003 Glossary (http://go.microsoft.com/fwlink/?LinkId=24625).

It is assumed that readers of these topics are familiar with the key concepts and features of Exchange 2003 and Microsoft Office Outlook® 2003. Readers must also be comfortable with planning and designing an Exchange 2003 organization, as outlined in Planning an Exchange Server 2003 Messaging System (http://go.microsoft.com/fwlink/?LinkId=47584).

These topics cover the following Exchange 2003 components:

  • Exchange Connector for Novell GroupWise, for connecting an Exchange 2003 organization to an existing Novell GroupWise environment and synchronizing directories.

  • Exchange Calendar Connector, to allow Exchange users access to Novell GroupWise users, and to allow Novell GroupWise users access to calendar information of Exchange users.

  • The Exchange 2003 SMTP service and SMTP connector, for connecting an Exchange 2003 organization to an existing Internet-based messaging host.

  • The Exchange Migration Wizard, for migrating user and directory data from Microsoft Mail for PC Networks, Lotus cc:Mail, Novell GroupWise, Internet messaging systems, and Internet directories.

  • Command-line Active Directory tools, for implementing semi-automated directory synchronization, which is useful in various directory synchronization scenarios covered in these topics.

Aside from the resources cited in these topics, the following resources may be useful in your implementation of Microsoft Exchange Server 2003.

 
Was this page helpful?
(1500 characters remaining)
Thank you for your feedback

Community Additions

ADD
Show:
© 2014 Microsoft