We have 2 users who are trying to send meeting invites to Outlook 2007 users. When these 2 users send a meeting invite, the accept reject buttons are not visible and the message “as the meeting organizer, you do not need to respond to the meeting” is displayed in the invite, even though the recipient of the invitation is not the organizer. I can also reproduce this with a test user. However, one other person on our end is able to send a meeting invite that the same Outlook user and the accept/reject button are visible. The difference is that for this user the ICS file appears to already be processed by the time the Outlook user receives the invite in his inbox. For the 2 problem users (and another test user) the Outlook invite has an .ICS file attached to the invitation. For the 1 non-problem user there is no ICS file so it seems that Exchange knows something about the user and does some auto processing of the invite and delivers it already converted in Outlook format. Does anyone know of any settings in Exchange or the Outlook client that would cause the invites to arrive differently for different senders? On our end, all 3 users are configured with the same client version and settings. Location doc is set to “MIME Format”. I know someone suggested to change this to Notes Rich Text but all 3 of my users have it set to MIME so if it works for 1 it should work the same for all. I’ve compared notes.ini of all 3 users as well and don’t see any compelling differences.
When I manually view the ICS files with WordPad I can see the Product ID for invitations that work look like this: PRODID:-//Lotus Development Corporation//NONSGML Notes 6.0//EN
and for invitations that don’t work it looks like this: PRODID:Microsoft CDO for Microsoft Exchange
So it appears that Exchange is possibly creating or processing the ICS files for the problem users and converting the info wrong. I’ve already googled “as the meeting organizer, you do not need to respond to the meeting” and read EVERY posting and none applied here. Also checked Microsoft’s public KB and nothing turned up there either.