Coexistence During Migration

Migration	<<	>>

Coexistence During Migration

The most important elements of coexistence are mail connectivity and directory synchronization. Microsoft Exchange Server includes features to make this easy.

Connectivity

There are many options for connecting Microsoft Exchange Server computers with Microsoft Mail postoffices.

Situation Solution Impact

Both on a LAN or WAN MS Mail connector, LAN option None

Remote location, currently connected asynchronously MS Mail connector, async option None

Remote location, currently connected over the Internet with SMTP gateway Replace the SMTP gateway with Internet Mail Service in the Microsoft Exchange Server site Update address space on Internet Mail Service to include remote postoffices

Remote location currently connected over AT&T with the AT&T gateway Replace the AT&T gateway with the Internet Mail Service in the Microsoft Exchange Server site or move the AT&T gateway to the Connector postoffice Reconfigure the postoffice/AT&T gateway

Currently backboned over PROFS Move the PROFS gateway to the Connector postoffice, or install Control Data Systems Rialto PROFS/OV Connector for Microsoft Exchange Server.

Situation	Solution	Impact
Both on a LAN or WAN	MS Mail connector, LAN option	None
Remote location, currently connected asynchronously	MS Mail connector, async option	None
Remote location, currently connected over the Internet with SMTP gateway	Replace the SMTP gateway with Internet Mail Service in the Microsoft Exchange Server site	Update address space on Internet Mail Service to include remote postoffices
Remote location currently connected over AT&T with the AT&T gateway	Replace the AT&T gateway with the Internet Mail Service in the Microsoft Exchange Server site or move the AT&T gateway to the Connector postoffice	Reconfigure the postoffice/AT&T gateway
Currently backboned over PROFS	Move the PROFS gateway to the Connector postoffice, or install Control Data Systems Rialto PROFS/OV Connector for Microsoft Exchange Server.

Directory Synchronization

Directory synchronization is important because the directory has major changes made to it with each phase of migration. If directory synchronization is planned, it can prevent undeliverable mail (except for mail addressed from PABs and PALs). You have several options:

Add Microsoft Exchange Server sites as requestor postoffices.
Reconfigure directory synchronization to point to one or more Microsoft Exchange Server sites.
Migrate the directory synchronization postoffice first and have Microsoft Exchange Server handle the synchronization process.
Move a postoffice each day or week to a directory synchronization server and have a server in the site act as a requestor.
Reconfigure directory synchronization on a site-by-site basis to make upgrading custom recipients to mailboxes easier.

The first option takes the least amount of time to configure. The directory synchronization server postoffice adds the Microsoft Exchange Server site as a requestor postoffice. You create a directory exchange requestor in your enterprise and configure it.

All options except for the first require administration on all postoffices that currently participate in directory synchronization. The benefit from this choice is having the directory synchronization server processes running on the Microsoft Exchange Server. The advantages include:

Multithreaded support.
Windows NT memory management.
Data is local to the process; no files are read over the network. This reduces network traffic and makes the T-2 process time smaller.
Updates are processed as they are received, not in one big batch, reducing the T-2 process time to sending updates. This can dramatically impact the speed of the directory synchronization process.

The third option combines the ease of the first option with the reliability of Windows NT from the second option. However, proper planning is required. When the first server is installed in the site, the local postoffice name is changed in the connector to match the name of the directory synchronization server.

The users on the directory synchronization server postoffice are migrated to Microsoft Exchange Server or moved to other servers with the Move User utility. This happens after T3 but before T1 in the directory synchronization process.

For MS Mail (PC) postoffices, there are no routing or addressing changes. Every postoffice must send a full list of addresses and request a full list of addresses using the Config-Dir-Sync-Requestor Import and Export commands in the Microsoft Mail Administrator program. The External program INI files have to be updated so MS Mail (PC) externals and MTAs don't deliver mail to the old postoffice. All mail sent to migrated users is delivered to their new Microsoft Exchange Server mailboxes. No configuration changes for directory synchronization are needed on any of the postoffices except to export and import addresses.

The order and planning of how you handle migration of the directory synchronization server to Microsoft Exchange Server is important. Part of migration is maintaining the global address list in postoffices and Microsoft Exchange Server computers as accurately as possible.

Consider the following:

When do you want mail delivered to the new mailbox instead of the old one?
Do you want to remove the old mailbox from directory synchronization or delete it?
When do changes in the postoffice need to be sent for directory synchronization?
How soon after migration does the user begin using Microsoft Exchange Server instead of Microsoft Mail?
Does your directory synchronization plan consider upgrading custom recipients to mailboxes?

There are several ways to plan directory synchronization. You can:

Maintain your current setup, and add Microsoft Exchange Server as one requestor.
Maintain your current setup, and add each site as one requestor.
Designate each site as a directory synchronization server.
Designate one site as a directory synchronization server.

As mailboxes are migrated during phased migration, they need to be removed from directory synchronization. If you are migrating an entire postoffice, the directory synchronization server removes the postoffice during the process. If you are migrating a partial postoffice and deleting migrated mailboxes, deleting the mailbox removes it from directory synchronization. If you are migrating a partial postoffice and retaining the migrated mailboxes, you must mark the mailbox as not included in directory synchronization using the Local command on the Modify menu in the MS Mail (PC) Administrator program.

Schedule+

During coexistence, sometimes individuals in your organization will use different versions of Microsoft Outlook and Schedule+. Most features in these two programs are compatible. However, if you upgrade Microsoft Mail users to the 16-bit version of Microsoft Outlook with the MS Mail information service, these users must use the Microsoft Outlook Calendar version. You should consider the extra features of this version when determining whether to use the MS Mail information service with your existing postoffices.

The following table describes the features available for each version.

Note Meeting requests and confirmations are translated among all versions, with the exception of attachments, which version 1.0 does not support.

	Sender on postoffice with Schedule+ 1.0	Sender on postoffice with Outlook Calendar or Schedule+ 7.0	Sender on postoffice with Outlook
Recipient on postoffice with Schedule+ 1.0	There is existing functionality.	Attachments sent with meeting request are unavailable to other person. You can't give other person access privileges to schedule file. You can't designate other person as a delegate. You can access other person's calendar if given permission. You can view free and busy with permission.	Attachments sent with meeting request are unavailable to other person. You can't give other person access privileges to schedule file. You can't designate other person as a delegate. You can't access other person's calendar. You can view free and busy information.
Recipient on postoffice with Outlook Calendar or Schedule+ 7.0	You can give other person access privileges to schedule file. You can't designate other person as a delegate. You can't access other person's calendar. You can't view free and busy information.	Existing functionality, as well as the following new features: You can send attachments with meeting requests. You can have multiple delegates, as long as they are on the same version, and are on the same postoffice. Time zone support. New views, contacts.	Attachments sent with meeting request are available to other person. You can't give other person access privileges to schedule. You can't designate other person as a delegate. You can't view other person's calendar. You can view free and busy information.
Recipient on Microsoft Exchange Server computer with Outlook Calendar or Schedule+ 7.0	You can't give other person access privileges to schedule. You can't designate other person as delegate. You can't access other person's calendar. You can view free and busy with permission if Schedist and the Free/Busy gateway are configured.	Attachments sent with meeting request are available to other person. You can't give other person access privileges to schedule. You can't designate other person as a delegate. You can't access other person's calendar. You can see free/busy with permission if Schedist and the Free/Busy gateway are configured.	Attachments sent with meeting request are available to other person. You can't give other person access privileges to schedule. You can't designate other person as delegate. You can see free/busy information with permission if Schedist and the Free/Busy gateway are configured.
Recipient on postoffice with Outlook	You can't give other person access privileges to schedule. You can't designate other person as delegate. You can't access other person's calendar. You can view free and busy information, but not to the granularity of the Outlook "Tentative" and "Out of Office" states.	Attachments sent with meeting request are available to other person. You can't give other person access privileges to schedule. You can't designate other person as a delegate. You can't access other person's calendar. You can view free and busy information, but not to the granularity of the Outlook "Tentative" and "Out of Office" states.	Attachments sent with meeting request are available to other person. You can't give other person access privileges to schedule. You can't access other person's calendar. You can't designate other person as delegate. You can view free and busy information, the including the Outlook "Tentative" and "Out of Office" states.
Recipient on Microsoft Exchange Server computer with Outlook	You can't give other person access privileges to schedule. You can't designate other person as delegate. You can't access other person's calendar. You can view free and busy information if Schedist and the Free/Busy gateway are configured, but not to the granularity of the Outlook "Tentative" and "Out of Office" states.	Attachments sent with meeting request are available to other person. You can't give other person access privileges to schedule. You can't designate other person as a delegate. You can't access other person's calendar. You can see free and busy information with permission if Schedist and the Free/Busy gateway are configured.	Attachments sent with meeting request are available to other person. You can't give other person access privileges to schedule. You can't access other person's calendar. You can't designate other person as delegate. You can view free and busy information, including the Outlook "Tentative" and "Out of Office" states.

Sender on postoffice with Schedule+ 1.0

Sender on postoffice with Outlook Calendar or Schedule+ 7.0

Sender on postoffice with Outlook

Recipient on postoffice with Schedule+ 1.0

There is existing functionality.

Attachments sent with meeting request are unavailable to other person.

You can't give other person access privileges to schedule file.

You can't designate other person as a delegate.

You can access other person's calendar if given permission.

You can view free and busy with permission.

Attachments sent with meeting request are unavailable to other person.

You can't give other person access privileges to schedule file.

You can't designate other person as a delegate.

You can't access other person's calendar.

You can view free and busy information.

Recipient on postoffice with Outlook Calendar or Schedule+ 7.0

You can give other person access privileges to schedule file.

You can't designate other person as a delegate.

You can't access other person's calendar.

You can't view free and busy information.

Existing functionality, as well as the following new features:

You can send attachments with meeting requests.

You can have multiple delegates, as long as they are on the same version, and are on the same postoffice.

Time zone support.

New views, contacts.

Attachments sent with meeting request are available to other person.

You can't give other person access privileges to schedule.

You can't designate other person as a delegate.

You can't view other person's calendar.

You can view free and busy information.

Recipient on Microsoft Exchange Server computer with Outlook Calendar or Schedule+ 7.0

You can't give other person access privileges to schedule.

You can't designate other person as delegate.

You can't access other person's calendar.

You can view free and busy with permission if Schedist and the Free/Busy gateway are configured.

Attachments sent with meeting request are available to other person.

You can't give other person access privileges to schedule.

You can't designate other person as a delegate.

You can't access other person's calendar.

You can see free/busy with permission if Schedist and the Free/Busy gateway are configured.

Attachments sent with meeting request are available to other person.

You can't give other person access privileges to schedule.

You can't designate other person as delegate.

You can see free/busy information with permission if Schedist and the Free/Busy gateway are configured.

Recipient on postoffice with Outlook

You can't give other person access privileges to schedule.

You can't designate other person as delegate.

You can't access other person's calendar.

You can view free and busy information, but not to the granularity of the Outlook "Tentative" and "Out of Office" states.

Attachments sent with meeting request are available to other person.

You can't give other person access privileges to schedule.

You can't designate other person as a delegate.

You can't access other person's calendar.

You can view free and busy information, but not to the granularity of the Outlook "Tentative" and "Out of Office" states.

Attachments sent with meeting request are available to other person.

You can't give other person access privileges to schedule.

You can't access other person's calendar.

You can't designate other person as delegate.

You can view free and busy information, the including the Outlook "Tentative" and "Out of Office" states.

Recipient on Microsoft Exchange Server computer with Outlook

You can't give other person access privileges to schedule.

You can't designate other person as delegate.

You can't access other person's calendar.

You can view free and busy information if Schedist and the Free/Busy gateway are configured, but not to the granularity of the Outlook "Tentative" and "Out of Office" states.

Attachments sent with meeting request are available to other person.

You can't give other person access privileges to schedule.

You can't designate other person as a delegate.

You can't access other person's calendar.

You can see free and busy information with permission if Schedist and the Free/Busy gateway are configured.

Attachments sent with meeting request are available to other person.

You can't give other person access privileges to schedule.

You can't access other person's calendar.

You can't designate other person as delegate.

You can view free and busy information, including the Outlook "Tentative" and "Out of Office" states.

The following table describes the features that are available for each version.

Note Meeting requests and confirmations are translated among all versions, with the exception of attachments, which version 1.0 does not support.

	Sender on Microsoft Exchange Server computer with Outlook Calendar or Schedule+ 7.0	Sender on Microsoft Exchange Server computer with Outlook
Recipient on postoffice with Schedule+ 1.0	Attachments sent with meeting request are unavailable to other person. You can't give other person access privileges to schedule. You can't designate other person as a delegate. You can't access other person's calendar. You can view free and busy information with permission if Schedist and the Free/Busy gateway are configured.	Attachments sent with meeting request are unavailable to other person. You can't give other person access privileges to schedule. You can't designate other person as a delegate. You can't access other person's calendar. You can view free and busy information if Schedist and the Free/Busy gateway are configured.
Recipient on postoffice with Outlook Calendar or Schedule+ 7.0	Attachments sent with meeting request are available to other person. You can't give other person access privileges to schedule. You can't designate other person as a delegate. You can't access other person's calendar. You can view free and busy information with permission if Schedist and the Free/Busy are gateway configured.	Attachments sent with meeting request are available to other person. You can't give other person access privileges to schedule. You can't designate other person as a delegate. You can't access other person's calendar. You can see free and busy information if Schedist and Free/Busy gateway are configured.
Recipient on Microsoft Exchange Server computer with Outlook Calendar or Schedule+ 7.0	There is complete functionality.	Attachments sent with meeting request are available to other person. You can give other person access privileges to schedule file if he or she has the Outlook driver for Schedule+ 7.x installed. You can't designate other person as delegate. You can view free and busy information.
Recipient on postoffice with Outlook	Attachments sent with meeting request are available to other person. You can't give other person access privileges to schedule. You can't designate other person as a delegate. You can't access other person's calendar. You can view free and busy information, but not to the granularity of the Outlook "Tentative" and "Out of Office" states.	Attachments sent with meeting request are available to other person. You can't give other person access privileges to schedule. You can't access other person's calendar. You can't designate other person as delegate. You can view free and busy information, including the Outlook "Tentative" and "Out of Office" states.
Recipient on Microsoft Exchange Server computer with Outlook	Attachments sent with meeting request are available to other person. You can give other person access privileges to schedule. You can't designate other person as a delegate. You can access other person's calendar if you have the Outlook driver for Schedule+ 7.x installed. You can view free and busy information with permission if Schedist and the Free/Busy gateway are configured.	There is complete functionality.