I had to move the user with the biggest mailbox in our org (the most senior guy in the company) to our new Exchange 2010 server, after moving 90 others without incident. I have moved this guy, but his Outlook 2007 client is unable to connect, giving the error "Cannot start microsoft office outlook. Unable to open the Outlook window. The set of folders could not be opened". OWA was very reluctant to get going too, giving a permissions error to begin with, then saying it was being moved, and finally let him in after a few hours. His iPhone is now connecting perfectly too, but his Outlook is not. I've tried making a new profile on another PC and it gives the same error. I've noticed when creating a new mail profile when I click "check names" that it resolves his name but it's against the old server. Does this mean it's an OAB issue? It would have to be one of the directors!

OWA is now saying that his mailbox is being moved and refusing access again. His mailbox was moved almost 24hrs ago and completed in just over 2hrs. Unfortunately I removed he local move request shortly after so I don't have much in the way of logs as to how it went, but I know it completed as I saw it was 100% before I removed the request. OWA seems to be flipping between: "Your request couldn't be completed because no server with the correct security settings was found to handle the request. If the problem continues, contact your helpdesk." "Log in failed because the mailbox you tried to access is being moved. The mailbox cannot be accessed until this operation is complete. Please wait and try again later".Allowing access via OWA but never via Outlook.

I've noticed in ADSI Edit on one of my DC's that his homeMDB is on the old server and on the other DC his homeMDB is on the new server. This looks like an AD issue then. I'm worried about what will happen once I reboot the DC and the two start talking again. Any way to minimise/resolve any conflicts?

Hi Is that person starting Outlook on a computer that is running Windows XP? If yes, you can have a view on below KB and try the fixing steps in RESOLUTION http://support.microsoft.com/kb/252304 CheersZi Feng TechNet Community Support

As I said above, this issue was because one DC hadn't replicated the new homeMDB and homeMTA locations to the other. I rebooted the DC and after a few minutes the change was synchronised and the users mailbox was accessible after we created him a new mail profile.