Google
Search WWW Search msexchangetips.blogspot.com

Monday, February 07, 2011

The critical property 'LegacyExchangeDN' is missing in the MailUser object

When performing a new-moverequest you receive the following error:

The critical property 'LegacyExchangeDN' is missing in the MailUser object 'migrateme3'.
+ CategoryInfo : InvalidArgument: (corp.dom/GALSync/FromILM/migrateme3:MailboxOrMailUser
IdParameter) [New
-MoveRequest], RecipientTaskException
+ FullyQualifiedErrorId : 9DC9C0BA,Microsoft.Exchange.Management.RecipientTasks
.NewMoveRequest


The issue is you used ADMT to migrate the user first then ran prepare-moverequest. The issue is that prepare-moverquest although says it is sucessful did not properly convert it into a mail enabled user. The script failed to stamp the legacyexchangeDN as well as the target address. If you manually add the legacyexchagneDN you then run into the error below:

Cannot find a recipient that has mailbox GUID 'f41a2905-8ea2-4ff3-a56f-4ed8739a2622'.
+ CategoryInfo : NotSpecified: (0:Int32) [New-MoveRequest], RemotePermanentException
+ FullyQualifiedErrorId : B5053E67,Microsoft.Exchange.Management.RecipientTasks.
NewMoveRequest

I'm still investigating this as prepare-moverequest is supposedly supported after Exchange 2010 SP1 with the overwritelocalobject parameter. The workaround in the meantime that I have if you want to use ADMT first:

1.Use ADMT to migrate all user accounts
2.Prepare-moverequest on all accounts (legacyexchangedn or targetaddress is still missing)
3.Use script to add targetaddress of mailnickname@company.com on all migrated accounts, I use admodify, but you can use powershell etc.
4.Update-recipient on all migrated accounts. This will stamp the legacyexchangedn
5.New-moverequest succeeds



James Chong
MCITP | EA | EMA; MCSE | M+, S+
Security+, Project+, ITIL
msexchangetips.blogspot.com

3 Comments:

Anonymous Anonymous said...

Hi James,

I have followed your methods/advice of moving a mail enabled user to a new exchange 2010org,
But at the step of using new-moverequest to migrate the users mailbox i am getting a error in the exchange management shell saying "user doesn't have a primary mailbox"
Which is true i guess as at that point only the prepare-moverequest and ADMT to move the user with merge option has been run.
But how do i assign a primary mailbox ?

Thanks Ben
benm@robertsonsdesign.com.au

5:55 PM  
Blogger Johnny Mac said...

Hello, I also experienced an issue performing a cross forest migration from Exchange 2003 to 2010 SP1. With Exchange 2007 you could migrate the AD account using ADMT. You could then mail-enable the account. Once mail enabled you could use the preparemoverequest.ps1 to add the legacy X.500 address, and then move the mailbox.

With Exchange 2003 you could not mail-enable the account as it states the account is a type of UserMailbox. To get around this I would not use ADMT. I would prepare the mailbox which would create the AD account. I would then move the mailbox to 2010, and then use ADMT to merge the AD accounts. The recipients could send mail but couldn't receive mail. I then cleared the target address using ADSI and everything works.

Regards,

John
john@shellstar.net

5:51 PM  
Blogger Sharad said...

Hi James,

I am also facing the same issue after migrating user account using ADMT.

Please advise.

9:50 AM  

Post a Comment

<< Home

xml:lang="en" lang="en"> MS Exchange Tips: The critical property 'LegacyExchangeDN' is missing in the MailUser object