A mailbox that was moved from an Exchange Server 2007 server to an Exchange Server 2010 server cannot be accessed by using Outlook

In a Microsoft Exchange Server 2007 and Microsoft Exchange Server 2010 mixed environment, you move a mailbox from an Exchange Server 2007 server to an Exchange Server 2010 server. In this situation, a user cannot access this mailbox by using Microsoft Office Outlook for a while. Additionally, you may find the following error messages in the Application event log on the server which the mailbox was originally located on:

Event Type: Error
Event Source: MSExchangeIS Mailbox Store
Event Category: General
Event ID: 1205
Description:
Failed to create the mailbox of /o=<organization>/ou=<Administrative Group>/cn=Recipients/cn=<user> with error 0x50c.

Event Type: Error
Event Source: MSExchangeIS Mailbox Store
Event Category: Logons
Event ID: 1022
Description:
Logon Failure on database "<mailbox store>" - Windows account <domain>\<user>; mailbox /o=<organization>/ou=<Administrative Group>/cn=Recipients/cn=<user>.
Error: 1292
Client Machine: <FQDN of client machine>
Client Process: OUTLOOK.EXE
Client ProcessId: 0
ClientApplicationId: N/A

Note This problem mostly occurs in an environment where Exchange Server 2007 and Exchange server 2010 are in different Active Directory sites.

This problem occurs because the Exchange Server 2007 server and the Exchange Server 2010 server connects to different Domain Controllers and Active Directory replication delay occurs. When the Outlook client connects to the Exchange Server 2007 server which the profile originally pointed to, the server returns an error which indicates that it is not the correct mailbox server. In this case, Exchange Server 2007 provides a new server name to the Outlook client. However, because of the Active Directory replication delay, Exchange Server 2007 obtains the old server name from Mailbox Cache Information (MBI). Therefore, the Outlook client still connects to the old server.

To resolve this problem, install the following update rollup:

Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.