Consider the following scenario:
You specify some delegates in a resource mailbox in a Microsoft Exchange Server 2010 environment.
You configure the following settings in Exchange Management Console:
On the Resource General tab in the Properties dialog box of the resource mailbox, you select the Enable the Resource Booking Attendant check box.
On the Resource In-Policy Requests tab in the Properties dialog box of the resource mailbox, you select the Selected recipients option button for the Specify users who are allowed to submit in-policy meeting requests that will be automatically approved option.
On the Resource In-Policy Requests tab in the Properties dialog box of the resource mailbox, you select the All users option button for the Specify who can submit in-policy meeting requests that are subject to approval by a resource mailbox delegate option.
You disable a mailbox that belongs to one of the delegates.
You send a meeting request to the resource mailbox.
In this scenario, the resource mailbox does not forward themeeting to the remaining delegates. For example, you create a room mailbox that has two delegates (delegate A and delegate B), you configure the settings, and then you disable the mailbox that belongs to delegate A. In this example, delegate B does not receive the meeting request.
Note If you check the Resource Policy tab in Properties dialog box of the resource mailbox, you see that the disabled mailbox is still displayed together with a red cross in the delegate list. Additionally, the Organizational Unit field is displayed as Object not found."
This issue occurs because the ResourceBookingProcessing function tries to query the Exchange distinguished name attribute for the disabled delegate. However, the attribute no longer exists. Therefore, an "Object Not Found" exception is thrown and the meeting request is not forwarded to the remaining delegates.
To resolve this issue, install the following update rollup:
2661854 Description of Update Rollup 2 for Exchange Server 2010 Service Pack 2
To work around this issue, remove the disabled delegate from the delegate list.
Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.
For more information about how to add delegates to a resource mailbox, visit the following Microsoft website:
How to add delegates to a resource mailboxFor more information about resource mailboxes, visit the following Microsoft website: