I am after the root cause not workarounds.
If you want you can also use the disable-mailbox cmdlet. The disable account option will only delete the user mailbox.
Search for the user account and Right click on the account and select Disable.
I am hoping someone can tell me the cause of this behavior and how to fix it. To remove \ Delete a user mailbox only follow the steps below: Open EMC -> Recipient Configuration -> Mailbox. To find the passive copies: Open Exchange Management Console (EMC). First, we need to remove all passive copies of each database. The service desk users ARE able to delete users and mailboxes using the EMC and using Remove-Mailbox command-let from the EMS, it just doesn't work when running from powershell (either via the script or just running the Remove-Mailbox command-let manually after the exchange 2010 snapin has been loaded). To remove an active database you must first remove all copies from other servers. You would think a simple permissions issue right? It could be, but not one I am aware of. Managemen t.Recipien tTasks.Rem oveMailbox + FullyQualifiedErrorId : 4399785,Microsoft.Exchange. + CategoryInfo : NotSpecified: (0:Int32), ADOperationException AdditionalĪctive directory response: 00000005: SecErr: DSID-03151D12, problem 4003 (INSUFF_ACCESS_RIGHTS), data 0 Remove-Mailbox : Active Directory operation failed on. The problem is, when the service desk run the script they get the following error when the Remove-Mailbox portion of the script is run: Obviously the script loads the Exchange 2010 powershell snapin. In Exchange you can encounter issues when you move mailbox between databases. The script deletes the user and mailbox using the command Remove-Mailbox. Removing Ghost-Mailboxes from Exchange 2010/2013 Written by Super User. What really happens when you disable a mailbox is that the mailbox is disassociated from the related user object in Active Directory by removing the user object’s Exchange attributes. You can modify the quota to suit your requirements.I have a simple powershell script that service desk staff use to delete users. In Exchange 2010 (20 as well) we have the option to remove the mailbox of a mailbox user (remove is quoted, because the action itself is called Disable). By default, discovery mailboxes have a mailbox storage quota of 50Gb.If you remove a discovery mailbox, all search results stored in the mailbox are removed.
Like all mailbox types, a discovery mailbox has an associated Active Directory user account, but it is disabled by default.Email delivery to discovery mailboxes is prohibited by using delivery restrictions. Although visible in exchange address lists, users cannot send email to a discovery mailbox.You can remove a discovery mailbox using the same procedure used to remove other types of mailboxes.A discovery mailbox can’t be converted to another type of mailbox.You can create additional discovery mailboxes as required.Discovery search comes in when your company auditor or HR wants to search for emails across all the mailboxes.įew points to note about discovery mailboxes: This mailbox is a used as the target mailbox for discovery searches in the exchange control panel. You might be wondering what this mailbox does. Exchange 2010 setup creates a special mailbox (discovery mailbox) with a display name “Discovery Search Mailbox” by default.