Hello I'm having ongoing grief with using the disconnect / reconnect mailbox feature. My issues are 1. Disconnected mailboxes usually take many hours to show up in the disconnected mailboxes section of EMC 2. Re-connected mailboxes remain innacessible for at least a day, or until I run the "clean-mailboxdatabase" commandlet. As well as being inaccessible, I also get the following error when trying to access the properties for a mailbox that has been re-connected Am I right in thinking this was meant to be fixed in Rollup 3 for SP2? I have applied this update and it made no difference. http://support.microsoft.com/kb/2682047  We installed this a while ago and we are currently on RU4. It's getting quite annoying now as we are a 24/7 operation and we have no downtime / free periods. I'm continually having to run "Clean-Mailboxdatabase" to hurry things along. Am I doing something wrong? Any advise much appreciated. We are running Exchange 2010 SP2 RU4 / Outlook 2010 clients.

I dont think you are doing anything wrong. All I can find is people running into the same issue and asking if this is fixed is RU4, which you prove that it isn't. As a workaround, why dont you script the "Get-Mailboxdatabase | Clean-Mailboxdatabase" command, and than set it up as a scheduled task to run every say 30 mins or an hour?

Hi first what is your schedule time for mailboxdatabase maintenance ? If you disconnect (disable) mailbox, then it will appear in disconnected mailboxes when: mailbox database maintenance agent will check database or you can manually run get-MailboxDatabase | Clean-MailboxDatabase Problem with connecting mailboxes back to user can be caused by domain controllers replication. Check how often this replication beetween domain controllers occur. We work with Exchange 2010 SP2 Rollup 3 and 5 domain controllers and we don't have any problem with reconnecting mailboxes. Remigiusz ExchangeBlog

I dont think you are doing anything wrong. All I can find is people running into the same issue and asking if this is fixed is RU4, which you prove that it isn't. As a workaround, why dont you script the "Get-Mailboxdatabase | Clean-Mailboxdatabase" command, and than set it up as a scheduled task to run every say 30 mins or an hour? Same here, I can't find anyone with answers, just the same complaints that it just doesn't work. I'll probably put in a scheduled task every hour to clean mailbox databases, but the issue remains that in my opinion, I shouldn't HAVE to! My issue is we have another team that looks after user account creations / moves / user name changes etc. When a mailbox is detached and reconnected that should be their work done. They have to keep coming to me to get the "clean-mailboxdatabase" command run. I can't find a way to allow them to run this without giving them a high level of access in Exchange. Is anyone from Microsoft reading who could give a definate answer? I won't hold my breath! :) Problem with connecting mailboxes back to user can be caused by domain controllers replication. Check how often this replication beetween domain controllers occur. I don't think replication is the cause. We have no issues whatsoever with any other tasks, only this one. If there was a replication issue, I'd expect to see it more often.

I didn't say it doesn't work. It works perfectly just like we configured this. If we disable mailbox we will find it next day morning because we have scheduled maintenance for databases to make at night. When we reconnect mailbox it's reconnected in 15 minutes - DC replication time, this time is set by us. Remigiusz

Hello, I also seen other customer said, he has this issue after apply Exchange 2010 SP2 rollup4. One workaround for this issue now is to run the clean-mailboxdatabase. Thanks, Evan Liu TechNet Subscriber Support in forum If you have any feedback on our support, please contact tnmff@microsoft.com Evan Liu TechNet Community Support