Can some smarty pants out there help me understand a particular behavior tha
thas me stumped?

We're running Office 2003 SP3 on WinXP SP2.

I have a user, Jane, who has delegate permissions over her boss Bob's
calendar. Jane creates a meeting on Bob's calendar for a Tupperware party
and invites herself and a conference room as a resource. Then she sends the
invitation.

Later, Jane opens the Tupperware party meeting and adds John's name to the
To: list. John is an external customer, not an employee of the company. He
isn't a member of Active Directory. Jane simply enters his email address and
hits the "Send Update" button.

When John receives the invitation, it appears as a forward with a calendar
attachment. The calendar attachment can be opened and viewed, or dragged to
the calendar, but the invitation cannot be Accepted. That means that any
further updates to this appointment would not reach John. Somehow, the magic
link has gotten broken.

To test, I had Jane add me as an attendee by adding my name to the To: list.
When I received the invitation, I could Accept or Decline the meeting
invitation just fine.

I know that when we send calendar invitations to non-AD users, they receive
the most optimum calendar invitation that their system will allow. On more
sophisticated platforms, they are able to either Accept or Decline the
invitation. I know that John's mail handler can support this feature. He has
been invited to, and accepted or declined, more than one meeting invitation
from our company's employees.

What I can't figure out is what's different in this case. The only thing I
can see that's different is that Jane is trying to update the calendar entry
on Bob's behalf. However, when she does so to invite me, it works fine.

Anyone have any bright ideas as to what went wrong?

Thanks,
Jennifer Q

Nothing, huh?

"Jennifer Q" wrote in message
...
Can some smarty pants out there help me understand a particular behavior
tha thas me stumped?

We're running Office 2003 SP3 on WinXP SP2.

I have a user, Jane, who has delegate permissions over her boss Bob's
calendar. Jane creates a meeting on Bob's calendar for a Tupperware party
and invites herself and a conference room as a resource. Then she sends
the invitation.

Later, Jane opens the Tupperware party meeting and adds John's name to the
To: list. John is an external customer, not an employee of the company. He
isn't a member of Active Directory. Jane simply enters his email address
and hits the "Send Update" button.

When John receives the invitation, it appears as a forward with a calendar
attachment. The calendar attachment can be opened and viewed, or dragged
to the calendar, but the invitation cannot be Accepted. That means that
any further updates to this appointment would not reach John. Somehow, the
magic link has gotten broken.

To test, I had Jane add me as an attendee by adding my name to the To:
list. When I received the invitation, I could Accept or Decline the
meeting invitation just fine.

I know that when we send calendar invitations to non-AD users, they
receive the most optimum calendar invitation that their system will allow.
On more sophisticated platforms, they are able to either Accept or Decline
the invitation. I know that John's mail handler can support this feature.
He has been invited to, and accepted or declined, more than one meeting
invitation from our company's employees.

What I can't figure out is what's different in this case. The only thing I
can see that's different is that Jane is trying to update the calendar
entry on Bob's behalf. However, when she does so to invite me, it works
fine.

Anyone have any bright ideas as to what went wrong?

Thanks,
Jennifer Q