Running Exchange 2007 SP2, one Exchange org, one AD domain/forest, seperate BES 4.1.7 domains for UK and USA. The CEO is moving from London to New York, associated mailbox servers are LON-EXMB01 and NY-EMBX01, associated BES servers are LON-BES01 and NY-BES01. We have a set outage for the mbx move and then his PA's on either side will need access again. I want to make sure there no hiccups so had some questions: i. Is it better to use EMC or Powershell to move the mbx ii. I know sometimes mbx moves fail for whatever reason, is there anyway to run a 'test now' type thing to see if we'll encounter an error before we do iii. If we do encounter a problem, are there log files we can check and where? iv. Any recommended options that will lessen the chance of failure v. After the mbx is moved, how long until the PA's on either side can access the mbx as part of their profile? Will they need to change anything on their client? vi. If we do run into problems, what are the best troubleshooting steps? vii. In terms of BES, I assume the best options are to delete the account on the London server and create a new one on NY. Should this be done before or after the mbx move?

i. It doesn't matter. But real men use PowerShell. The EMC just issues a PowerShell command. ii. No. Consider setting the -BadItemLimit argument to something like 10 so a single corrupt item doesn't kill the mailbox move in the middle. iii. Look at the result of the move, although there won't be a whole lot there. iv. Make sure the CEO and his delegates have logged off and shut down their computers and mobile devices. But that shouldn't be strictly necessary. v. Say 15 minutes. Give or take. They shouldn't need to change anything. vi. Use Bing or Google and search the errors you receive. vii. I would delete the London account before the move and create the New York one after the move has completed.Ed Crowley MVP "There are seldom good technological solutions to behavioral problems."