Select the product you need help with

You cannot use a set of features in Office Communicator 2007 R2 that integrate secure delegation for the local Outlook 2007 calendar

Article ID: 971845 - View products that this article applies to.

SYMPTOMS

In Microsoft Office Communicator 2007 R2, you cannot use a set of features that integrate secure delegation for the local Outlook 2007 calendar if you have enabled Enterprise Voice.

Back to the top | Give Feedback

Previously, only Enterprise Voice enabled users who were configured as delegates were permitted to request a Meeting or Conference focus on behalf of another user.

However, with Office Communicator 2007 R2 (3.5.6907.3) or with later versions, you can use Office Communicator to collect the current delegates of a mailbox owner's calendar, and then process the Session Initiation Protocol (SIP) enabled users as delegates in the Microsoft Office Communications Server (OCS) environment. A correctly configured delegate can manage meeting requests in Outlook calendar and request a Conferencing focus on behalf of the mailbox owner.

Back to the top | Give Feedback

RESOLUTION

To resolve this issue, apply the following updates:

969695
(http://support.microsoft.com/kb/969695/ )
Description of the Communicator 2007 R2 hotfix rollup package: June 2009
969696
(http://support.microsoft.com/kb/969696/ )
Description of the update for Live Meeting Conferencing Add-in for Outlook: July 2009
969821
(http://support.microsoft.com/kb/969821/ )
Description of the update package for Office Communications Server 2007 R2: July, 2009

After you install these updates, you can edit the registry of the Office Communicator 2007 R2 client to include the following registry value:

Click Start , click Run, type regedit in the Open box, and then click OK.
Locate and then click the following registry subkey:
HKEY_CURRENT_USER\Software\Policies\Microsoft\Communicator\
or
HKEY_LOCAL_MACHINE\Software\Policies\Microsoft\Communicator\
On the Edit menu, point to New, and then click DWORD Value.
Type EnableExchangeDelegateSyncUp, and then press ENTER.
Right-click EnableExchangeDelegateSyncUp, and then click Modify.
In the Value data box, type 1, and then click OK.

Note If this value is 1, EnableExchangeDelegateSyncUp is enabled. The default is 0 (disabled).
Exit Registry Editor.

By enabling the EnableExchangeDelegateSyncUp registry value on the Windows client that is hosting the mailbox owner's Outlook 2007 calendar, the Office Communicator 2007 R2 client collects the delegate information from the mailbox owner's calendar.

Note This process is adversely affected by Outlook integration errors and requires a working Outlook delegation scenario between the two users. In this scenario, all users who are configured by using the default Author or Editor permission in the Outlook Delegates configuration can schedule conferences for their delegator.

Back to the top | Give Feedback

MORE INFORMATION

The Outlook 2007 calendar lets you to use a range of permissions that you can apply to the calendar delegate. With these permissions, you can access the delegator's Outlook 2007 calendar for different management tasks. The default permissions that are applied when the delegate is first added to the Outlook 2007 calendar's Access Control List are Author and Editor. The Outlook 2007 calendar gives you a more detailed choice of permissions that you can apply to the calendar delegate by accessing the shared calendar in the Outlook 2007 Graphics User Interface (GUI). If you configure the delegated Outlook 2007 calendar to work with any permissions other than Author or Editor, the delegate cannot schedule a conference for the Outlook 2007 calendar delegator.

The order of precedence for local policy settings, for in-band provisioning, and for the Options dialog box settings is as follows:

HKEY_LOCAL_MACHINE\Software\Policies\Microsoft\Communicator
HKEY_CURRENT_USER\Software\Policies\Microsoft\Communicator
Office Communications Server 2007 in-band provisioning
Communicator 2007 R2 Options dialog box

The current Office Communicator 2007 R2, Communicator.adm Group Policy file does not contain the Group Policy update that is listed earlier. You must apply this local policy update on the local Windows client without using the Active Directory Group Policy.

Back to the top | Give Feedback