We have an Exchange 2003 server with the latest SP, etc. Some of our
employees are using Outlook 2003 and some are using Outlook 2007; all of the
employees have the current service packs installed.

Until now, we have been able to send a meeting invitation to the address of
a public folder. The public folder itself is not a calendar type; it can
accept posts, email messages, calendar invitations, etc. Employees with
Outlook 2003 can open the invitation in the public folder and accept it and
the appointment gets added to their personal calendar. When employees with
Outloook 2007 attempt to do the same thing, they receive a message that
states, "As the meeting organizer, you don't need to respond to the meeting."
and they can't accpet it and it doesn't get added to their calendar.

We have used this method for years without any problem until we started to
roll out Outlook 2007.

I am not the only Microsoft customer having this problem. There were posts
to this forum on 9/25/2007 and 10/11/2007 from others describing exactly the
same problem but they did not receive a response to their inquiry. I am
hoping that I will be the lucky one to get an answer.

--
Jeff Anderson

Is there a workaround to this issue?

What happens when you try? "Can't" is a rather vague problem description.

--
Milly Staples [MVP - Outlook]

Post all replies to the group to keep the discussion intact.
How to ask a question: http://support.microsoft.com/KB/555375


After furious head scratching, parul shah asked:

| Is there a workaround to this issue?

Is the public folder a resource? if so, see
http://www.slipstick.com/calendar/skedresource.asp

--
Diane Poremsky [MVP - Outlook]
Need Help with Common Tasks? http://www.outlook-tips.net/beginner/
Outlook 2007: http://www.slipstick.com/outlook/ol2007/

Outlook Tips by email:


Exchange Messaging Outlook newsletter:


Outlook Tips: http://www.outlook-tips.net/
Outlook & Exchange Solutions Center: http://www.slipstick.com

Access this newsgroup directly by visiting
http://www.microsoft.com/office/comm...s/default.mspx


"parul shah" wrote in message ...
Is there a workaround to this issue?