I am testing moving the mailbox across the forest with below environment, somehow i encountered some error that unable to resolve by using powershell cmd. was thinking the cmd was not complete, please help to review the cmd and advise. TQ
btw, I have made some changes on previous ps cmd posted here and it work fine and I even enhanced with get-content to allow moving mailbox in bulk. An issue resolved but another is raised, the user id can not be resolve during of setting up email account on client machine, the user id is an old id that migrated from old domain to new domain. The error I got is "the action could not be completed, the name could not be matched to a name in the address list". was not sure whether i have missed some process during the overall migration, please help to review the migration steps below and advise me a proper method.
steps taken :- 1.) create trust relationship between old domain and new domain. 2.) use ADMT tool migrate user id over new domain. 3.) use move-mailbox cmd migrate mailbox over to new exchange server 4.) setup client machine with logged in migrated user id. 5.) setup email account on outlook 2003.
Good to see that u have moved Mialboxes in bulk, i would appreciate if you can paste the cmdlet which worked.....
If i am no wrong you have migrated from Exchange 2003 to Exchange 2007. 1) what about Public folders migration. 2) check if the Mailbox database is pointing the correct address list, 3) check the Legacyexchangedn value of the users. 4) Do you see any other OU in active directory users and conputers which was created after using ADMT tool.? 5) Best technet article to follow:- http://technet.microsoft.com/en-us/library/bb288905.aspx
c:\mailbox.txt where it contain all user email addresses in the form of following example. e.g user@domain.com user2@domain.com
Answered to your below point :- 1.) Do not have public folder, hence no public folder migration needed. 2.) You're right, the address list is very important and i found out the mailbox database's address list was empty after migration process, therefore I updated the address list and on client machine was able to get back the mailbox. Yet, I found out why was address list empty, it was due to the mailbox was in hidden to cause the stamping process skipped during the move mailbox. 3.) Yes, this could be important for after moved validation of user mailbox. 4.) Yes, the users were successful migrate over to new domain. 5.) thanks for the link.
Since the migration process has reach to end and after completed the mailbox migration process, there should be list of verification or user acceptance test should take place to end the whole process.
Questions are :- 1.) what normally should verify in such migration? 2.) what user acceptance test should cover beside ensuring user email? 3.) how do we ensure the each migration process? is there a tool or output log which we can capture for verification of each process?
After migration Basically you need to check the Internal and External Mailflow(both incoming and outgoing). check if the users are able to download OAB, if there are able to view the Schedule + freebusy information. Try this with both outlook and OWA.
|
My Subscription |
My Forums |
Address Book |
Member List |
Search |
FAQ |
Ticket List |
Log Out
Printable Version
All Forums >> [Microsoft Exchange 2007] >> Migration >> crossorg move-mailbox cmd error 
crossorg move-mailbox cmd error - 
RE: crossorg move-mailbox cmd error - 
New Messages
No New Messages
Hot Topic w/ New Messages
Hot Topic w/o New Messages
Locked w/ New Messages
Locked w/o New Messages
Post New Thread
