I have recently migrated from Exchange 2003 to 2010 and have suffered several problems with the approval of appointments by delegates to the point that I have decided to abandon the use of delegates who had worked well since 1996. What I like about Exchange 2010 is the shell and I have used it to remove the delegates. For each delegate execute: Set-Mailbox -identity presidente -DeliverToMailboxAndForward $true Set-calendarprocessing -identity presidente -automateprocessing none Set-calendarprocessing -identity presidente -ForwardRequestsToDelegates $false Set-calendarprocessing -identity presidente -ResourceDelegates:$null And finally (to verify) Get-calendarprocessing -Identity presidente | format-list identity,resourcedelegates That result on: Identity : ascer.org/Asociacion/Convocables/Calendarios de cargos/Calendario Presidente ResourceDelegates : {} However, requests for meeting kept arriving to the mailboxes of the delegates, and when the delegates approved the appointment, the reservation of time ending in the calendar of the delegate, not on the calendar of our beloved president. Finally I consulted with Outlook (2010) the list of delegates for mailbox and I found that all the changes that had taken place with the shell had no effect: Delegates were still there!!! Now I have no problems, I deleted the list in Outlook and delegates do not get notifications, they have full access permissions to the mailboxes in question, consult their chiefs inbox daily and approve what is needed. But I think something is not working well in my system or Exchange in general and worth posting on the forum. Orutra

I have recently migrated from Exchange 2003 to 2010 and have suffered several problems with the approval of appointments by delegates to the point that I have decided to abandon the use of delegates who had worked well since 1996. What I like about Exchange 2010 is the shell and I have used it to remove the delegates. For each delegate execute: Set-Mailbox -identity presidente -DeliverToMailboxAndForward $true Set-calendarprocessing -identity presidente -automateprocessing none Set-calendarprocessing -identity presidente -ForwardRequestsToDelegates $false Set-calendarprocessing -identity presidente -ResourceDelegates:$null And finally (to verify) Get-calendarprocessing -Identity presidente | format-list identity,resourcedelegates That result on: Identity : ascer.org/Asociacion/Convocables/Calendarios de cargos/Calendario Presidente ResourceDelegates : {} However, requests for meeting kept arriving to the mailboxes of the delegates, and when the delegates approved the appointment, the reservation of time ending in the calendar of the delegate, not on the calendar of our beloved president. Finally I consulted with Outlook (2010) the list of delegates for mailbox and I found that all the changes that had taken place with the shell had no effect: Delegates were still there!!! Now I have no problems, I deleted the list in Outlook and delegates do not get notifications, they have full access permissions to the mailboxes in question, consult their chiefs inbox daily and approve what is needed. But I think something is not working well in my system or Exchange in general and worth posting on the forum. Orutra After how much time running the PS commands did u verify that thing in outlook? It might take some time due to information Store Service cache or just try to restart the Info Store service on MBX server and then verfiy in outlook. Regards,Laeeq Qazi|Team Lead(Exchange + Sharepoint + BES + DynamicsCRM) www.HostingController.com

Hi Laeeq, Last time, several days from clear on Shell and view on Outlook. But no restart. However during last month and several times I’ve established delegates to null and restarted server due to updates. Now and since your interest I’ll proceed with a lab test. Create user1 and user2. Set user1 delegate user2 (with Outlook). Wait two hours. Restart server. Set to null delegates with Shell. Wait. Restart. See with Outlook. I‘ll tell you. Regards ArturoOrutra

Hi, The default interval for refreshing the cached mailbox information is two hours. How to change the default cache refresh interval http://technet.microsoft.com/en-us/library/bb684892(EXCHG.80).aspx Regards, Xiu

Lab completed. After creating new users, I've set user1 as delegate of user2 in Outlook, then I ran PS command Get-calendarprocessing -Identity user2| f-l identity,resourcedelegates and I saw User1 at the list of delegates. I waited a few minutes and without rebooting I ran Set-calendarprocessing -identity user2 -ResourceDelegates:$null. And now get-calendarprocessing...... return me the emptyList {}. I've left the night passes and I restarted at dawn. Then I've started Outlook, select user2 profile and .... the list of delegates contains User1. At PS remains empty. Mysterious Exchange. Regards Arturo Orutra

Hello again Xiu, I've verified HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\MSExchangeIS\ParametersSystem. Does not contain a key for Mailbox Cache Age Limit, so I guess it comes to default values: two hours as you say. But in my lab test (see up) I've wait more than 12 hours. Regards, ArturoOrutra

Hi, Sometimes, we have delegate rules configured on the mailbox, we can delete the rule via the following steps. 1. Start MFCMAPI by double clicking it. 2. Click OK on the about screen & get to the main UI window. 3. From the main UI window,go to the "Session" menu option and select "Logon and Display Store Table". This will open the mailbox. 4. In the Mailbox window you'll see the Mailbox & Public Folders instances. Double click the Mailbox. This will open the mailbox in a seperate window. 5. Click the "+" next to the Root-Mailbox object. Here you will see the various objects within the Mailbox (like the IPM_SUBTREE, CommonViews, Shortcuts, etc. This is for a mailbox on an Exchange 2003 Server configured with an Outlook 2003 MAPI Profile and using Search Folders. For other environments, you might see something different. I have not tested this. 6. Click the "+" next to "IPM_SUBTREE". You will now see the folders that are a part of the mailbox (like the Inbox, Outbox, Sent Items, etc). 7. Highlight the Inbox folder, right click and choose "Display Rules Table". This will open a new windows (titled Rules Table) and will display the rules configured on this mailbox. The rules will be listed in the top half of this window. 8. In the top window of the Rules table, scroll all the way to the right till you see a column titled "PR_RULE_PROVIDER::0X6681001E:PT_STRING8". This column lists the TYPE of rule configured. A regular rule created via the Rules Wizard in Outlook will have the RuleProvider listed as "RuleOrganizer". When a delegate is configured on a mailbox, the RuleProvider entry will read "Schedule+ EMS Interface". This is the delegate rule that is added to the mailbox. 9. The RuleName for this new Delegate Rule will be listed as <NULL String>. You can see this in the second column of the top half of the Rules Table (the column called Rule Name). 9. Right click the Delegate Rule mentioned above ("Schedule=EMS Interface") and then chose Delete. This will delete the rule from the mailbox. If that is not the issue, then I think we need to check the settings on outlook side, especially to check if you have ticked “Delegate receives copies of meeting-related messages sent to me” from Tools->Delegates->…->Delegates permission. Note: These users appear on the Delegates tab(Outlook) because they have Send-on-behalf permissions to the resource mailbox. Regards, Xiu

A wonderful walk through MFCMAPI. This tool has always intrigued me and has been a pleasure to follow your instructions to learn its secrets. But the focus of my proposal for discussion are not the messages forwarded to delegates, but it refers to the existence of the delegates themselves. It seems that there are two representations of the lists of delegates stored on server, one that is managed by the tools on the server (PS) and one that is managed by MAPI clients. Changes made on the client are moved to both lists but changes made on PS did not appear in the client list. Interestingly OWA 2010 avoids the problem by not offering management of delegate list. Also, I suspect that this dual representation of the list affects the response to events such as meeting requests. A little history: I seem to remember that the delegates appeared in MS Schedule prior to the acquisition of Exchange. Therefore should have a MAPIclient-oriented implementation (Direct Booking) which was supplemented with a server-side store event sink (Auto Accept Agent). With the introduction of Exchange 2007, the server team introduced two changes that may be significant: a) New alternatives for resource management: http://msexchangeteam.com/archive/2007/05/14/438944.aspx b) The Messaging API (MAPI) client libraries was not provided as a part of the base product installation I think we're in a transition phase incomplete and I have installed Outlook 2010 (MSDN RTM Edition) to see if there was better integration with Exchange 2010. In some ways yes, but in this no. Well, I wanted to draw attention to this inconsistency in delegates to see if it resolves in the next SP1.Orutra