Hi there, I came across a nasty issue with the Recipient Administrator the other day and was wondering if anyone has run into this also. When assigning a user Recipient Administrator permissions, but NO account operator rights, and the user tries to disable a mailbox on a Exchange 2007 server it will execute, but with the following warning: Failed to commit the change on object "<GUID>" because access is denied. At this point all Exchange attributes are removed from the AD object, but somehow the mailbox is NOT marked as deleted and cannot be found in the Disconnected Mailboxes. I cannot reattach and the mailbox is still in the Exchange database given the Get-MailboxStatistics cmdlet. Cheers, Mark

Yes, we are having the same issue. Did you find a fix for it? Thanks.

Yes, we are having the same issue. Did you find a fix?

I have the same issue. Anyone found a solution for this? /Jakob

I have found this in the Split permission reference (http://technet.microsoft.com/en-us/library/bb430782(EXCHG.80).aspx): Mailbox-Disabling User Objects To run the Disable-Mailbox cmdlet against a user or inetOrgPerson object, the Exchange administrator must have the appropriate rights in the configuration partition. For more information about how to delegate the role, see How to Delegate Server Administration. You must be a local administrator and have the following role on the Exchange server where the mailbox resides: If the Exchange server is running Exchange2007, the account does not require any role; you only need to have the permissions defined below. However, when executing Disable-Mailbox, you will receive a warning, "Failed to commit the change on object "<Mailbox GUID>" because access is denied". This warning means that an attempt was made to immediately disable the mailbox but the action failed for some reason. Therefore, you have to wait until online maintenance does this in batch for the store in which the mailbox resides. Does this mean that we have to make the administrators admin on the server also, or that it can be ignored since the maintenance will do this for us? /Jakob

I have worked with PSS on this and this is a bug in Exchange 2007. The workaround to remove the error is to give the user ms-Exch-Store-Admin rights on the organisation. You do this with command: Add-ADPermission -Identity "CN=ContosoOrg,CN=Microsoft Exchange,CN=Services,CN=Configuration,DC=Contoso,DC=com" -User "company\Admin" -ExtendedRights ms-Exch-Store-Admin -InheritanceType All The warning can saftly be ignore since the error is MAPI call to the store to flush the cache that is failing.

We are having exactly the same issue. Any update regarding this issue? Boudewijn

Boudewijn,You have to options. Either Add the Store-Admin rights as in my previous post, or just let the delegated admins know that this can safetly be ignored. We have chosen the last option.According to PSS, this error will not be resolved until Exchange 14, or if some major Exchange customer demands it, since it's just a "cosmetic" error.Jakob

Thank you for your responce.If you ask me, I think this is not fair from Microsoft. In my opinion this IS an issue. We have about 9000 mail(box) enabled users with a lot of administrators, you can imagine this kind of problem will pop-up many times.They should either disable the disable-mailbox feature for Exchange Recipient Administrators, or they should solve it.Boudewijn

I agree with you. Unfortunately they are claiming that it won't be fixed with this release of Exchange. They don't care that we have 40 000 mailboxes... :)Grzegorz

Hello, Does anyone received any article from Microsoft for above issue as we need to convey it to customer. With workaround mentioned above it solves the issue.