Contoso, Ltd. has an Exchange Server 2010 environment. Fabrikam, Inc. has an Exchange Server
2007 environment. Contoso acquires Fabrikam. Contoso plans to migrate the email accounts of the
Fabrikam employees to the existing Contoso Exchange Server environment. Fabrikam employees will
have new Contoso email addresses and will also maintain their existing Fabrikam email addresses for
a period of time. You need to recommend a solution for ensuring that replies to email messages sent
by Fabrikam employees prior to the migration are directed to the migrated mailboxes. What should
you recommend?
A.
In the Exchange Management Console (EMC) in the Contoso Exchange Server environment, set
the primary email address to the Fabrikam email address.
B.
After the mailbox migration, run the Update-EmailAddressPolicy cmdlet for each email address
policy.
C.
Export the legacyExchangeDN attributes from the Fabrikam mailboxes and add them as custom
X500 addresses on the new Contoso mailboxes.
D.
In the Exchange Management Console (EMC) in the Contoso Exchange Server environment, add
the Fabrikam domain name to the Accepted Domains list as an authoritative domain.
Explanation:
Things you need to know if you are moving from an external Exchange environment to Rackspace’s
Hosted Exchange 2007. An Exchange server uses an internal addressing scheme that routes
messages between mailboxes it hosts. These addresses are known as LegacyExchangeDN addresses
or they are sometimes referred to as x500 addresses. When you send and receive messages on your
current providers Exchange service these LegacyExchangeDN addresses are saved with sent and
received messages in your inbox. They are also saved within your AutoComplete cache in Outlook.
When you reply to or forward existing emails that are migrated over to our system, without first
importing the x500 addresses, a bounce will likely be returned if Outlook uses the old x500 address.
The bounce will resemble the following non-delivery report:
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Diagnostic information for administrators:
Generating server: IAD2HUB06.mex02.mlsrvr.com
IMCEAEX-_O=FIRST+20ORGANIZATION_OU=FIRST+20ADMINISTRATIVE
[email protected]
#550 5.1.1 RESOLVER.ADR.ExRecipNotFound; not found ##
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
If you still have access to your old Exchange server, you or your current provider will need to export
your LegacyExchangeDN and provide the CSV file to us via a support ticket. We will then get our
Exchange engineering specialists to upload the LegacyExchangeDN export into our environment. This
will ensure that when you reply to or forward existing messages, even if the x500 is referenced, it
will deliver to the correponding mailbox. For a quick reference the following can be keyed into a
Exchange server to retrieve the legacy data: