I have a fully migrated (from Ex 2010 to) Exchange 2013 environment; all users are running on 2013, Outlook 2010.  Simple environment...one site has two all-in-one machines, the other site has one all-in-one machine. 

About a month ago we had a fairly serious internal communication failure that disconnected an entire site of users from Exchange. I had to exercise one of my free TechNet support tickets to get it fixed.  Somewhere along the way during the repair, the migration of mailboxes got muddied up, which I go into detail below.  I did contact back to the support tech (who was fantastic btw), and he said that nothing he did would have affected the situation, and moved on.

Situation:

If we create a NEW user (new meaning after the failure repair) and place the mailbox in site 1, then realize it would be better served from the server in site 2, we can open the ECP, choose the user, choose the new mailbox dbase and migrate them over, no problems at all. 

If we choose a user that was in existence PRIOR to the failure repair, open the ECP, choose that user, choose the new mailbox dbase and start the migration, the job ends in less than 5 minutes.  The email generated looks like what's below and the user is never moved.  Nothing ever shows up in the logs...

_____________________________________________

Migration batch XXX to XXX has completed successfully.               

________________________________

Synced:                None   

Total mailboxes:               None                  

Please don't reply to this e-mail. It was sent from an unmonitored account.        

______________________________________________

We CAN move mailboxes using the Exchange Command Shell no matter when it was created; and while it's cool at and all, the boss that doesn't want to use PowerShell. She would prefer using the ECP (as do I).

I'm grasping at straws on this one trying to figure out what's wrong and how to fix it, other than it appears that the ECP is struggling to communicate to the subsystem on these 'older' accounts. 

It's not the 'bad item' count either...I set it at 10,000 on a box that had nothing in it... same results.

Appreciate any insight or assistance...

Chris R

• Edited by Have Fun Thursday, April 30, 2015 5:29 PM