Exchange Server Forums

Forums | Register | Login | My Profile | Inbox | RSS RSS icon | My Subscription | My Forums | Address Book | Member List | Search | FAQ | Ticket List | Log Out

crossorg move-mailbox cmd error

Users viewing this topic: none

Logged in as: Guest
  Printable Version
All Forums >> [Microsoft Exchange 2007] >> Migration >> crossorg move-mailbox cmd error Page: [1]
Login
Message << Older Topic   Newer Topic >>
Limited time MSExchange.org offer! -- 1.Sep.2008 1:00:00 PM
TechGenix and SolarWinds have partnered to provide free copies of SolarWinds Exchange Monitor to all visitors who join the MSExchange.org Forums. SolarWinds Exchange Monitor is a handy desktop dashboard that continuously monitors Microsoft Exchange to deliver real-time insight into Exchange services, mail queue sizes, and host server health. Learn more about Exchange Monitor and the free offer!
crossorg move-mailbox cmd error - 13.Nov.2008 11:13:23 AM   
listlow

 

Posts: 12
Joined: 18.Oct.2008
Status: offline
HiAll,
 
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
 
SourceDC=hd2k3_dc01.hdm.old (windows 2003 32bit)
SourceEx=hd2k3_32exh01.hdm.old (windows 2003 32bit with Exchange 2003 32bit)

TargetDC=hd2k3_dc02.hdasia.local (windows 2003 32bit)

TargetEx=HD2K8-64EXH01.hdasia.local (windows 2008 64bit with Exchange 2007 64bit)
 
PS CMD :-
 
$s=Get-Credential
$t=Get-Credential
 
Get-Mailbox -DomainController hd2k3_dc01.hdm.old -Credential $s -Identity "mail1@hdm.old" | move-mailbox -TargetDatabase "CN=Mailbox Database,CN=First Storage Group,CN=InformationStore,CN=HD2K8-64EXH01,CN=Servers,CN=Exchange Administrative Group (FYDIBOHF23SPDLT),CN=Administrative Groups,CN=HDAsia,CN=Microsoft Exchange,CN=Services,CN=Configuration,DC=HDAsia,DC=local" -SourceForestGlobalCatalog hd2k3_dc01.hdm.old -GlobalCatalog hd2k3_dc02.hdasia.local -DomainController hd2k3_dc02.hdasia.local -SourceMailboxCleanupOptions none -SourceForestCredential $s -TargetForestCredential $t -Confirm:$false


Error Msg :-
 
An Active Directory error 0x51 occurred when trying to check server 'hd2k3_dc02
.hdasia.local:389' suitability: 'The LDAP server is unavailable.'.

 
Appreciate for the reply.


Post #: 1
RE: crossorg move-mailbox cmd error - 13.Nov.2008 4:18:25 PM   
Naddy

 

Posts: 134
Joined: 22.Oct.2008
Status: offline
try this:-
below is an example:-

Move-Mailbox -TargetDatabase "Target Server\First Storage Group\Mailbox Database" -Identity john -GlobalCatalog <fqdn> -SourceForestGlobalCatalog <fqdn> -NTAccountOU "OU=OrgUnit01,DC=<name>,DC=com" -SourceForestCredential $SourceCredential -TargetForestCredential $TargetCredential -IgnorePolicyMatch:$true

(in reply to listlow)
Post #: 2
RE: crossorg move-mailbox cmd error - 14.Nov.2008 1:59:10 AM   
listlow

 

Posts: 12
Joined: 18.Oct.2008
Status: offline
Naddy, thanks for replied.
 
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.
 
Appreciate for the reply.

(in reply to Naddy)
Post #: 3
RE: crossorg move-mailbox cmd error - 14.Nov.2008 2:11:48 PM   
Naddy

 

Posts: 134
Joined: 22.Oct.2008
Status: offline
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

http://technet.microsoft.com/en-us/library/cc164366.aspx

(in reply to listlow)
Post #: 4
RE: crossorg move-mailbox cmd error - 15.Nov.2008 11:56:08 AM   
listlow

 

Posts: 12
Joined: 18.Oct.2008
Status: offline
Naddy,

Sure thing, here you go the cmdlet for moving in bulk.

$s=Get-Credential
$t=Get-Credential
Get-Content “C:\mailbox.txt” | Get-Mailbox -DomainController hd2k3_32dc01.hdm.old -Credential $s | move-mailbox -TargetDatabase "CN=Mailbox Database,CN=First Storage Group,CN=InformationStore,CN=HD2K8-64EXH01,CN=Servers,CN=Exchange Administrative Group (FYDIBOHF23SPDLT),CN=Administrative Groups,CN=HDAsia,CN=Microsoft Exchange,CN=Services,CN=Configuration,DC=HDAsia,DC=local" -SourceForestGlobalCatalog hd2k3_32dc01.hdm.old -GlobalCatalog hd2k3_32dc02.hdasia.local -DomainController hd2k3_32dc02.hdasia.local -SourceMailboxCleanupOptions none -SourceForestCredential $s -TargetForestCredential $t -Confirm:$false

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?

Appreciates for the reply.


(in reply to Naddy)
Post #: 5
RE: crossorg move-mailbox cmd error - 17.Nov.2008 2:58:19 PM   
Naddy

 

Posts: 134
Joined: 22.Oct.2008
Status: offline
Thank You for giving me the cmdlet.

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.

The best tool is to run Exbpa.

(in reply to listlow)
Post #: 6

Page:   [1] << Older Topic    Newer Topic >>
All Forums >> [Microsoft Exchange 2007] >> Migration >> crossorg move-mailbox cmd error Page: [1]
Jump to:

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
 Reply to Message
 Post New Poll
 Submit Vote
 Delete My Own Post
 Delete My Own Thread
 Rate Posts