Share via


Exchange 2013 - Disabled Mailbox not showing up immediately in the Connect a Mailbox

Question

Monday, September 16, 2013 4:58 AM | 1 vote

I have disable a mailbox  over an hour ago but it doesn’t show in the connect a mailbox section in the ECP Exchange 2013. immediately. The reason why I disable the email as I want to attach it to a new AD user which I have created.

I know you have to wait for replication so it appears in the connect a mailbox but I’m not sure how long and we forced an AD replication to see if that works.

I know with Exchange 2010, to get the disconnected mailbox to show immediately, I used to write a command Clean-MailboxDatabase “DB” to get it to appear in the disconnected mailbox but that doesn’t work with Exchange 2013 anymore.

Anyone have any suggestions?

All replies (17)

Monday, October 7, 2013 5:32 PM

I am also looking for this answer. It seems no one knows.


Tuesday, October 8, 2013 3:43 AM | 1 vote

Yes because of Exchange will waiting the maintance schedule for summary the disconnect mailbox of the day.

So you have to run this command for immediately summary the disconneted mailbox.

Get-MailboxStatistics -Database MDB03 | Where { $_.DisconnectReason -ne $null } | ForEach { Update-StoreMailboxState -Database $_.Database -Identity $_.MailboxGuid -Confirm:$false }

(Change you database name to this command)

http://technet.microsoft.com/en-us/library/jj860462(v=exchg.150).aspx


Friday, December 6, 2013 4:46 AM | 1 vote

I have same issue, I run command you guide, but not result.

Please help me! Thanks.


Thursday, December 12, 2013 1:34 PM | 1 vote

I have same issue. I see just a 53 mailbox as disabled, but there should be more than 200 disabled mailboxes. I've also tried with the command, but for now, no luck. Is there any news about that?

Please help. Thanks


Friday, December 13, 2013 5:01 PM

Hi,

Did you disable mailboxes with emails or were they fresh mailboxes with no email and even mailboxes not being logged in to?

Actually, if you create a new mailbox,  then mailbox object in database is not created until either it recieves\sends some email, or user log into mailbox.

Regards,

Laeeq Qazi|Team Lead(Exchange + Sharepoint + BES + DynamicsCRM) www.HostingController.com


Monday, December 16, 2013 2:09 PM

Noticed this too.

In 2010 the clean-mailboxdatabase always did the trick, but it's not used anymore :-s


Tuesday, December 17, 2013 11:57 AM

Hi,

Update-StoreMailboxState is for same purpose, but works on mailbox, instead of database.

Regards,

Laeeq Qazi|Team Lead(Exchange + Sharepoint + BES + DynamicsCRM) www.HostingController.com


Thursday, December 19, 2013 2:37 AM

Hi Laeeq Qazi,

Mailboxes disable is mailboxes with emails, please help me!

Regards,


Thursday, December 19, 2013 3:17 PM

Hi,

Please tell how did u run 'Update-StoreMailboxState' command. When did u disabled the mailbox? 

Disabled mailboxes are kept in 'Disconnected Mailbox List' for one month by default, and they are then purged automatically when this retention period expires.

Can you try this command, and see if you can see these disabled mailboxes?

Get-MailboxDatabase| Get-MailboxStatistics | Where { $_.DisconnectReason -ne $null } | ForEach { Update-StoreMailboxState -Database $_.Database -Identity $_.MailboxGuid -Confirm:$false }

Regards,

Laeeq Qazi|Team Lead(Exchange + Sharepoint + BES + DynamicsCRM) www.HostingController.com


Wednesday, January 8, 2014 6:40 AM | 1 vote

I'm having a same problem.

I did disable-mailbox to one mailbox over 24 hours ago. The mailbox is lost. Maintenance schedule was last night, but there is no change when i list disconnected mailboxes at the database.

In this environment a new user account is created everytime the cost center of the employee is changed. So i need to do disable mailboxes every day. This is not a first time when the mailboxes have been lost. Many times the mailboxes are seen at the database straight after the disable-mailboxes are done. Some mailboxes are seen at the database after the maintenance schedule. But every now and then, the mailboxes are lost. Because the nature of this environment, this is getting really annoying. I should not use restore of the backup for this...

Right now i'm looking mailbos statistics of the mailbox that got lost (i have started to take statistics to see if the mailbox is empty or not). The mailbox had 864 items and total item size was 33.18 MB.

If the maintenance schedule is not cabable to update the status of the mailbox, then there is no use of using update-storemailboxstate? At least for me this command is doing nothing when i am having this problem.


Wednesday, January 29, 2014 7:17 PM | 1 vote

I found a way to do what you want through Powershell.  I haven't found a command that works like Clean-MailboxDatabase did in Exchange 2010 so you can reconnect through the EAC.

http://www.techieshelp.com/connect-disconnected-mailbox-in-exchange-2013/


Tuesday, March 11, 2014 3:20 AM | 5 votes

There is no more clean-mailboxdatabase persent in Exchange 2013 that is replaced by Update-StoreMailboxState'

Try to run  -

Get-MailboxStatistics -Database MDB02 | ForEach { Update-StoreMailboxState -Database $_.Database -Identity $_.MailboxGuid -Confirm:$false }

http://technet.microsoft.com/en-us/library/jj860462%28v=exchg.150%29.aspx

Exchange Queries


Saturday, April 9, 2016 1:07 PM | 1 vote

I don't know who you are but one of the things you were put on this earth for was to help me with this problem.  This was the fix.  Thank you so much.


Friday, April 29, 2016 9:29 PM

Good news for you however, my Exchange 2013 is not showing the disabled mailbox. I already disabled a mailbox using the GUI admin center. The mailbox was migrated from 2007 exchange to 2013. I need the inbox and calendar from it. I tried the exchange shell command. I waited 24 hours. Why can't exchange 2013 CU9 find the mailbox? I see two 2 other disabled mailboxes that had been deleted 9 days ago. This is a production Exchange 2013 so I don't want to restart services but who knows that might be the only fix. https://technet.microsoft.com/en-us/library/jj860462(v=exchg.150).aspx 


Monday, January 2, 2017 2:47 PM | 2 votes

Thanks! This worked for me too

But I have changed this command a little bit:

Firts I've runned "Get-MailboxStatistics <USER NAME> | FT MailboxGuid" and after I just run 

Update-StoreMailboxState -Database <DB NAME> -Identity <MAILBOXGUID>

Thanks a lot!

-- emnavarro02


Tuesday, April 24, 2018 2:34 AM | 1 vote

Update-StoreMailboxState -Database <DB NAME> -Identity <MAILBOXGUID>

Command worked like Magic for me in Exchange 2013 CU 19

Thanks for the help

I am facing the same error for multiple DBs located on multiple servers but all servers are in single DAG. Backup application is NMM. Can someone suggest in case face such issue.


Monday, January 27, 2020 5:30 PM

Thanks. Problem is that DisconnectReason is null, so this mailboxes doesnt show up. Update-StoreMailboxState -database 'database' is much simpler and also more effective.