Microsoft KB Archive Search

Notice: This website is an unofficial Microsoft Knowledge Base (hereinafter KB) archive and is intended to provide a reliable access to deleted content from Microsoft KB. All KB articles are owned by Microsoft Corporation. Read full disclaimer for more details.

  1. Home
  2. Warning of undefined recipient type of a user after the linked mailbox is moved from an Exchange Server 2007 forest to an Exchange Server 2010 forest

Warning of undefined recipient type of a user after the linked mailbox is moved from an Exchange Server 2007 forest to an Exchange Server 2010 forest

View products that this article applies to.

Symptoms

Consider the following scenario:
  • You create a remote legacy move request to move a linked mailbox from a remote Exchange Server 2007 forest to an Exchange Server 2010 forest.
  • The move request is finished successfully.
  • You try to manage the mailbox from the remote Exchange Server 2007 forest. For example, you run the Get-recipient cmdlet in the remote Exchange Server 2007 forest to manage the mailbox.
In this scenario, you receive the following warning message:
Warning:
Object Domain/Users/LinkedMailbox has been corrupted and it is in an inconsistent state. The following validation errors have occurred:

Warning:
The value of property 'RecipientTypeDetails', 33554432, is not defined in the Enum type 'RecipientTypeDetails'.


Notes
  • The value of property "RecipientTypeDetails" should be 128. This means that it is a Mail User type.
  • The value of property "RecipientTypeDetails" 33554432 means that it is a Linked User type.

↑ Back to the top

Cause

This issue occurs because the Mailbox Replication Service (MRS) stamps the recipient type of the user as Linked User if the user’s mailbox is a linked mailbox. This recipient type cannot be recognized by the remote Exchange Server 2007forest.

↑ Back to the top

Resolution

To resolve this issue, install the following update rollup:
2645995 Description of Update Rollup 1 for Exchange Server 2010 Service Pack 2

↑ Back to the top

Status

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

↑ Back to the top

More Information

For more information about recipients, visit the following Microsoft website:
General information about recipients
For more information about the New-MoveRequest cmdlet, visit the following Microsoft website:
General information about the New-MoveRequest cmdlet
For more information about the Get-Mailbox cmdlet, visit the following Microsoft website:
General information about the Get-Mailbox cmdlet
For more information about how to create a remote legacy move request, visit the following Microsoft website:
General information about how to create a remote legacy move request

↑ Back to the top

Keywords: kbqfe, kbfix, kbsurveynew, kbexpertiseinter, kb

↑ Back to the top

Article Info
Article ID : 2649735
Revision : 1
Created on : 1/7/2017
Published on : 2/13/2012
Exists online : False
Views : 407