Re: Exchange security update prevents updating of shared calendars

Those experiencing the problem of Entourage users not being able to update
another person's calendar despite having update permissions (author, editor,
etc.) can work around the problem by using the Delegate function in
Entourage (Tools/Accounts/Edit/Delegate tab) or by using Outlook 2003 and
Tools/Options/Delegate tab. It appears that the delegate process sets
permissions such that the recent Exchange security update does not
interfere.

In order to use delegate in Entourage, you must:

1) Use the actual domain name of the AD that the Exchange server is in as
opposed to the FQDN (machine.domain.com) of the server itself. This is the
domain specified in the Account settings. For example, the front end server
might be "machine.domain.com". You would use "domain" only in the account
settings assuming domain corresponded to the AD name.

2) You must use the Advanced button when doing the delegation and specify
the actual server that hosts the user's mailbox. This must be partially
qualified. For example: if the full name is "machine1.xxx.xxx.xxx", you
MUST use only "machine1" in the Advanced setting. You will need to have
"xxx.xxx.xxx" in the search domain field of the Network pane.

Bill




On 6/21/06 5:20 PM, in article C0BF304C.6DCC%bbryson@xxxxxxxxxxx, "Bill
Bryson" <bbryson@xxxxxxxxxxx> wrote:

Microsoft seems to have done it again. We have users who previously were
granted write access to other people's calendars who no longer can
add/update events. The problems began right after the application of a
security patch to our Exchange server. One of the things addressed by the
patch was a potential OWA exploit. It appears that the MBU is not being
invited to test Entourage on Exchange servers that are patched and/or are
failing to properly test. This is a significant and obvious loss of
functionality for Entourage users that have implemented calendar sharing.

Entourage generates error messages of -18576 and -18597 which are related to
permission problems.

Are there other sites experiencing this problem? I have been unable to
discover a work-around on the client end so we are at the mercy of Microsoft
to patch another patch or Systems must decide to remove the patch and risk
the exploits that it protects against.

Oh what a bother. Please Microsoft - have testers TEST ALL your clients.

Bill


.