After a migration, when creating an Outlook Profile, the Check Name fails because it reverts to a (4330518)

After a migration, when creating an Outlook Profile, the Check Name fails because it reverts to a

After a migration it may be a requirement to change from source to target Outlook Profiles manually. When this is attempted the Outlook Check Name functionality fails because the Exchange server changes to a different value from what was specified.
 

This problem can occur if the Exchange Provider registry key is set to a specific GC (Global Catalog Server) or to the closest GC. This registry key may have been set to eliminate excessive network traffic that can occur when the Exchange Server and the GC are located in a Site that is remote from the Outlook Client. If this registry value is set, when a new Outlook profile is created it is forced to resolve it's mailbox against the closet GC or a specific GC. The GC would then direct it to it's Exchange server entries, and not allow the check name to resolve on other servers not contained on the GC.

To resolve this issue open Regedit and delete the Exchange Provider registry key which can be found in the following location:

HKEY_CURRENT_USER\Software\Microsoft\Exchange\Exchange Provider

Additional information regarding the Exchange Provider registry key can be found in Microsoft Knowledge Base Article 319206: "How to configure Outlook to a specific global catalog server or to the closest global catalog server"

http://support.microsoft.com/?kbid=319206

SYMPTOMS

In some situations, you may notice excessive network traffic when Microsoft Outlook attempts to contact the global catalog server.

This article describes how to configure Outlook to a specific global catalog server or to the closest global catalog server.

Note If the global catalog server and the Exchange Server computer are in the same site as the Outlook client, you do not need to make this registry setting. The normal referral mechanism provides the best performance.