• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 1622
  • Last Modified:

Cross Forest Mailbox Migration

Dear All,
I am now in the process of migrating my users to a new domain in a new forest with Exchange 2007 SP1 on windows server 2008 enviroment. The old domain is running Exchange 2003 on windows server 2003 enviroment.
I was successful in migrating the test user account to the new domain but I am facing problems with moving the mailboxes. The exchange shell says the movement was successfull but I get the following warning:

"WARNING: [user3] Though the mailbox has been moved to the target Exchange server, a problem occurred when adding the following user or group to ntSecurityDescriptor: 'CORP\Enterprise Admins'. 'Send As' and 'Personal Information' permissions might have been lost."

The problem is that this mailbox is displayed in Exchange 2007 as a linked mailbox and a new user is created in target AD. If the original migrated user is user3, after moving the mailbox I get the following additional account user31.

However, I cannot access the mailbox using outlook or OWA using any of the both accounts. Note that the user31 is disabled even if I enable it the problem still exist.
The following error is displayed when I use OWA:
"Outlook Web Access could not find a mailbox for domain\user3. If the problem continues, contact technical support for your organization and tell them the following: The mailbox may be stored on a Microsoft Exchange 2000 or Microsoft Exchange 2003 server, or the Active Directory user account was created recently and has not yet replicated to the Active Directory site where this Client Access server is hosted."

Note that my all servers are located on one site !!.
I tried it with 3 accounts and I get into the same problem. Please advice.

Thanks,
0
fuadsm
Asked:
fuadsm
1 Solution
 
SurajCommented:
You would not be able to do so since this user31 would have the logon name as MIGZ...........

Disable the linked mailbox and then reconnect the mailbox to the user account which has been migrated to the AD using the ADMT.

I think one cause of failing would be the migration of the account was not been done with keeping the SIDHistory. Since when you do a move mailbox after the AD account migration it should get reconnected to this AD account rather creating a new object in the AD.

You can follow the step I suggested and I am sure you would be able to get rid of the issue you are facing.

Before moving other users check if in case users are migrated along with the SID.

Thanks,
x-sam
0
 
fuadsmAuthor Commented:
You are absolutly correct this is what I tried before and solved my problem. I like your proffessional was of reading the quastion and the logs.
Thanks alot.
0

Featured Post

NEW Veeam Backup for Microsoft Office 365 1.5

With Office 365, it’s your data and your responsibility to protect it. NEW Veeam Backup for Microsoft Office 365 eliminates the risk of losing access to your Office 365 data.

Tackle projects and never again get stuck behind a technical roadblock.
Join Now