http://support.microsoft.com/kb/2593557
One of my customers came to me with the following issue and asked if
there were “better” solutions available than they found using their own
Internet research. They use a mix of Outlook 2007 and Outlook 2010
clients and a lot of shared mailboxes. The access to these mailboxes is
granted through group memberships, which have “full mailbox access” and
“send-as” permissions granted. Outlook is configured to use a second
profile for the Shared Mailbox access.
The Symptom:
In
the phase of testing their mailbox migration to Exchange 2010 Sp1 RU6
they encountered the following issue trying to delegate Calendar
permissions using the “Outlook delegation wizard” on their shared
mailboxes:
“The
Delegates settings were not saved correctly. Cannot activate
send-on-behalf-of-list. You do not have sufficient permission to perform
this operation on this object”
Troubleshooting steps:
If
you do an Internet research there appear to lots of people complaining
about this exact behaviour. The two most popular described solutions are
the following:
1. Using the “IgnoreSOBError” – “SendOnBehalf”
Registry key to silently drop the error message and proceed with
permission assignment. With the usage of this key the described error
message is just dropped by Outlook and the selected permissions out of
the delegation wizard are applied (without setting the SendOnBehalfof
permission).
The SendOnBehalf Permission is not needed to act as
calendar delegate. If the delegate has to use the “send on behalf of”
permission for writing email “in behalf of” this has to be done by an
administrator using the Exchange Management Shell or Exchange Management
Console.
Outlook 2007 Registry key:
HKCU\Software\Microsoft\Office\12.0\Outlook\Preferences or
HKCU\Software\Policies\Microsoft\Office\12.0\Outlook\Preferences
Dword: IgnoreSOBError value = 1
Outlook 2010 Registry key:
HKCU\Software\Microsoft\Office\14.0\Outlook\Preferences or
HKCU\Software\Policies\Microsoft\Office\14.0\Outlook\Preferences
Dword: IgnoreSOBError value = 1
2. Create a new
RBAC
role and strip all parameters for “GrantSendOnBehalf plus Identity” and
add the user who should be able to do their delegation without an
error. In this case the Outlook Wizard will finish successfully and the
delegate will be added to the list of “publicDelegates”.
The
downside of this solution about using this “Organization wide” RBAC role
is that the user is now able (using remote PowerShell) to
“GrantSendOnBehalf” in every mailbox, not only his delegated mailboxes.
http://blogs.technet.com/b/mspfe/archive/2012/06/26/solving_2d00_the_2d00_delegates_2d00_settings_2d00_were_2d00_not_2d00_saved_2d00_correctly_2d00_error_2d00_on_2d00_exchange_2d00_2010.aspx