Yes I’m able to login to those mailboxes on target successfully. The only thing is you have to make sure “Change password on next logon” is unchecked for the migrated user on target. By default , it will be checked.
I was following your instructions when i came unstuck. the amdt ran and then when i ran
Enable-MailUser -Identity sdeneystest -ExternalEmailAddress “email@example.com” it had an error:
This task does not support recipients of this type. The specified recipient corp.nextdigital.com/Users/sdeneystest is o
f type UserMailbox. Please make sure that this recipient matches the required recipient type for this task.
+ CategoryInfo : InvalidArgument: (corp.nextdigital.com/Users/sdeneystest:ADObjectId) [Enable-MailUser],
+ FullyQualifiedErrorId : 43991306,Microsoft.Exchange.Management.RecipientTasks.EnableMailUser
It appears it has already linked the user object with the legacy mailbox in the 2003 domain. Any ideas?
Try to run Get-User cmdlet. You may see the migrated user displayed with error/warning.
If yes, then remove the user account from target forest.
Try to migrate user account from source forest to target forest again.
Important: While migrating using ADMT, make sure you exclude the properties like
-> msexch**** ( starts with msexch)
Once migrated the user account, Try to run Get-User cmdlet. You may see the migrated user displays without error/warning.
Then continue the move mailbox.
All the Best :)
It Turns out we had duplicate serrer names. When the command contacted to the GC in the source domain, it was referencing a server called exchange. it then used that in netbios, but that resolved to a different server in the target domain, which had been setup only as a cas server. But thanks for your input as it helped
I’m looking to follow these instructions in the future and am currently in the planning stage. I’m yet to install my target forest. What I need to know is can I get away with just a single trust to move the mailboxes or do I need a 2 way forest trust ? It’s likely we are only going to be able to open a 2 way trust between the source (A) and the target (B) for a number of short periods. Is this going to cause us any issues going forward ? Unfortuneatly this is non negotiable as a result of secuirty requirements between the AD forests and going forward we are only allowed to create a 1 way forest trust with (B) trusting (A) (A forest can access B forest but not vice versa).
I was hoping we could ADMT all users and groups upfront with the appropriate mail attributes. I believe you can do this with just a one-way trust and then create the 2 way trust for a limited time to move the mailboxes required. The 2 way trust would then be broken and the original 1 way trust re-established. This process would be replicated for future mail migrations.
Is this possible ?. Any help would be appreciated. Thanks.
Comment by MigrationPlanner — April 1, 2010 @ 8:25 am
I was able to run Prepare-MoveRequest with no problems. Now when trying to run New-MoveRequest I get an error with TargetDatabase name. I enter my database name of Mailbox Database 0193130497 and the error comes back Mailbox database does not exist.
Any help would be greatly appreciated.
Comment by Carey Roscrow — April 25, 2010 @ 5:17 am
hey i have one quick question about the procedure you had.
im planning to use ADMT just like what you have written above. i believe by migrating user object with ADMT, mailbox attributes are going to be migrated together. i would like to delete mailbox attribute migrated with ADMT. and then, migrate mailbox attribute with the cmdlet of exch 2010.
in that case, is there any other required cmdlet other than what you have mentioned above?
detailed explanation will be appreciated.
I used ADMT 3.1 to migrate the users from an AD 2003 environment to a Windows 2008 R2 environment
After ADMT all users are logging into the new domain, I set the External Associated Account in the source domain so the new target domain accounts had access.
Next step is to migrate / move the mailboxes
When I run the
I was expecting the AD 2008 User object to become mail enabled,
what I am finding is that a new user account is created that is mail-enabled??
Here is the syntax I am using :
./Prepare-MoveRequest.Ps1 -Identity “Distinguished name of User from SourceForest”
-TargetMailUserOU “Distinguished name of OU in TargetForest” -UseLocalObject
Would it be less painful to script exmerge and import the pst files?
You could exmerge and import the pst files. But you may have problems while replying the old emails back. You may have to change the x400 after importing the pst. Apart from that you will be good. All the Best :)
ADMT 3.1 is out, does not run on Windows 2008 R2 64 bit, will work on Windows 2008 64 bit nicely. MS is working on ADMT 3.2 which they say will run on 2008 R2.
I used the Prepare-MoveReqest.Ps1 script. Mailboxes moved nicely. I told users they would have to setup delegates once again.
We had some Rooms and things that were setup via Outlook with Calendar options for auto accept. I changed them into Exchange 2010 Rooms with the Set-CalendarProcessing for AutoAccept however some of them are not processing the AutoAccept. Seems like permissions on the mailbox itself or Add-MailboxFolderPermission -identity Calendar -User Default -AccessRights Author – seemed to have correct for some but now all.
Did anyone see that?
I tried Add-MailboxFolderPermission with Anonymous but that it now allowing it.
I have followed your instructions and have excluded HomeMDB, MTA and MsExch attributes and have migrated the users. But when i try the MailEnableUser command then it throws the same error as the one menitoned above in the blog.
Error: This task does not support recipients of this type. The specified recipient is of type UserMailbox. Please make sure that this recipient matches the required recipient type for this task.
Comment by Rajiv Lochen — June 15, 2010 @ 11:23 am
I have a question……….I’m testing this process with a email box with about 600MB size and I was wondering how long it is suppose to take for the “Move Request Status” menu to show “Completed”? Any ideas?
Hi, thanks for this great post.I tried to move my exchange 2010 domain a to exchange 2010 domain B and its working. But after i add new exchange on same organization with server B i tried to move another mail box than failed. Please help
I have a domain with a Windows Server 2003 R2 and a Exchange 2003 and I need to migrate all users and their mail boxes to other domain in other forest with a Windows Server 2008 R2 and a Exchange 2010.
I know that only ADTM 3.2 works with Windows Server 2008 R2.
In this tutorial it is never mentioned the version of the Windows Server on the target domain, is it relevant or not?
After this migration can I turn of the trust?
I am studding this migration for quit a wile and what I read led me to install ADTM 3.2 and SQL in target domain because of version of my Windows.
I am using your method which works great. (I’ve even used that gui script to migrate the mailboxes in my lab.) What I need is the ability to communicate across the forest until the move is done. There are too many to move in a weekend.
We have two domains both have accounts created in them
DomainA – user logins
DomainB – Exchange hosted but has an account for each user in DomainA
We want to migrate from Exch2003 in DomainB to a new setup of Exc2010 in DomainA.
here is the kicker we cant move the accounts over due to them already having accounts in both domains and the users logins are exactly the same Is there a way to migrate the mailbox over and reattach it to the account in domainA?
Thanks ahead of time for any help and feel free to email me if needed,
Hi, first of all thanks for this great tutorial.
I have a problem whith my environment, I just have migrated users in cross forest from server 2003 and exchange 2003 to server 2008 r2 and exchange 2010, but my target forest has two child domains:
Exchange 2010 is member of contoso.com and the users are in child domain.
The user’s migration was fine, but when I try to migrate the mailbox’s I got an error.
When I run enable-mailuser it shows that the user didn´t find it in the domain controller of the parent domain.
The question is: is it possible to add a parameter at the script in order to find the user in the child domain controller?
Is it not possible, how can I do the mailbox migration of users?
Comment by Juan Roja — September 16, 2010 @ 2:26 pm
Good post Sathish,
I just need to know how the mail will flow to/from old exchange 2003 and Exchange 2010 during the transition period, if the exchange organization name (@mycompany.com) is same.
Do I need any configuration or connectors between 2 servers?