Not sure if this is normal or not. I don't think so. Haven't done mailbox moves in a while on Exchange. Using Exchange 2010 SP3 with Update Rollup 1. I had to apply rollup 1 to address a problem with mailbox moves outlined in this article: http://support.microsoft.com/kb/2763065
The update addressed part of the issue but the server still logs event ID 9660 in the Application log which I have never seen before.
The bigger issue is I noticed Outlook goes into a disconnected state while the mailbox is being moved. This is not supposed to happen as far as I can remember. I have been told this is normal at the end of the move when it does it final cleanup but I don't think so.
This means you really can't move a mailbox during the day without affecting the user.
I don't remember any of these issues prior to SP2. Is anyone else experiencing this issue?
Like I said, we are running Exchange 2010 SP3 UR1 on Windows 2008 R2 SP1. Two CAS servers in a CAS array. Two MB servers in a DAG. Just moving a mailbox from one DB to another when both DB's are mounted on the same server produces the problem. During the move, the workstation (XP SP3) can successfully ping the CAS Array so that is not the issue. After the move, the client reconnects and all is well. I was always able to move mailboxes while the user was online and never had any issues.
I have two environments. Test and Prod. It happens in both. Both environments are at the same levels in terms of SP's etc.....I looked at the Log tab on the mailbox in the Move Request folder in EMC and everything looks fine. No issues or errors. UR1 fixed the cleanup issue. It still puts a ton of event ID 9660 warnings in the application log and I think this may have something to do with it. Any help on this would be appreciated.