Log in Register. My Account Log out. Order today PacktPub. NET Advanced Edition. Unable to activate send-on beh May PM thelp. Featured Products. Featured Book Order today PacktPub. All rights reserved. Unable to activate send-on-behalf-of list. You do not have sufficient permission to perform this operation on this object. When you add a delegate, Outlook also tries to grant "send on behalf of" permission to the delegate by default.
This permission is written to the publicDelegates attribute of your user object in Active Directory. The issue that is described in "Symptoms" can occur for either or both of the following reasons. The global catalog GC server to which your Outlook client is connected is not local to your domain.
If your Outlook client is connected to a GC that is not local to your domain, the publicDelegates attribute cannot be written to your user object in Active Directory. Important This section, method, or task contains steps that tell you how to modify the registry. However, serious problems might occur if you modify the registry incorrectly. Therefore, make sure that you follow these steps carefully. For added protection, back up the registry before you modify it. Then, you can restore the registry if a problem occurs.
For more information about how to back up and restore the registry, click the following article number to view the article in the Microsoft Knowledge Base:. Outlook can be configured to enable you to add delegates without requiring you to grant the "send on behalf of" permission.
Start Registry Editor. To do this, use one of the following procedures, as appropriate for your situation. If you are prompted for an administrator password or for confirmation, type the password or click Continue.
Click Start, and then click Run. Locate and then click the following registry subkey:. On the File menu, click Exit to exit Registry Editor. After you add the registry value, you can add a delegate without having write permissions to your own user object on the global catalog server. When you do this, a message that resembles the following message is logged in the Windows Application log to help track the event:.
The "send on behalf of" permission is not needed for meeting-related messages. Microsoft Exchange Server specifically does not require that you have "send on behalf of" permissions to send a meeting request on behalf of another user. Therefore, even without the "send on behalf of" permission, delegates can successfully send meeting requests on behalf of the calendar owner. Ask a question. Quick access. Search related threads.
Remove From My Forums. Answered by:. Archived Forums. Sign in to vote.
0コメント