Issue:
When user creates a schedule appointment in Outlook and then updates it at a later time (maybe an attachment was added or some other information such as the meeting time), the calendar update emails are going straight into the attendees deleted items folder. So, the users are not seeing the updates.
However, if the user that created the meeting updates the calendar invite and makes a change to the “location” field, the calendar update email goes into the attendee’s inbox like it should.
Important:
Is this issue with multiple users or a single.
Resolution:
Checked and found that for one user user1@domain.com it was working and for other users it wasn't
Checked the output of the below command:
Get-CalendarProcessing -Identity user1@domain.com | Fl
Get-CalendarProcessing -Identity user2@domain.com | Fl
Found that AutomateProcessing was set to: AutoUpdate for the user user1@domain.com and AutomateProcessing was set to: None for user2@domain.com
We ran the command Set-CalendarProcessing -Identity user2@parkwayproducts.com -AutomateProcessing Autoupdate to change the AutomateProcessing value to set it from None to Autoupdate
Further, from Get-OrganizationConfig |Fl output we could see VisibleMeetingUpdateProperties value was set to: Location:15
We changed the VisibleMeetingUpdateProperties value to: Allproperties by executing the below command:
Set-OrganizationConfig -VisibleMeetingUpdateProperties AllProperties
Moreover, As per article: https://docs.microsoft.com/en-us/powershell/module/exchange/organization/set-organizationconfig?view=exchange-ps
-VisibleMeetingUpdateProperties
This parameter is available only in the cloud-based service.
The VisibleMeetingUpdateProperties parameter specifies whether meeting message updates will be auto-processed on behalf of attendees. Auto-processed updates are applied to the attendee's calendar item, and then the meeting message is moved to the deleted items. The attendee never sees the update in their inbox, but their calendar is updated.
This parameter uses the syntax: MeetingProperty1:MeetingStartTimeWithinXMinutes1,MeetingProperty2:MeetingStartTimeWithinXMinutes2,...MeetingPropertyN:MeetingStartTimeWithinXMinutesN.
The valid meeting properties to monitor for updates are:
Location: The meeting location field.
Subject: The meeting subject or title.
Sensitivity: The sensitivity (privacy) of the event.
Body: The meeting body or description.
OnlineMeetingLinks: The meeting join URL.
AllowForwarding: The option to allow or prevent forwarding of meetings.
RequestResponses: The option on whether responses are requested.
AllowNewTimeProposals: The option to allow or prevent new time proposals.
ShowAs: The free/busy state of the meeting: Free, Tentative, Busy, Working elsewhere, or Away/Out of office.
Reminder: The reminder time.
AllProperties: Any meeting change.
If you don't specify a MeetingStartTimeWithinXMinutes value for the meeting property, any change to the meeting property will result in visible meeting update messages (regardless of how soon or how far away the meeting is). For updates to recurring meetings, the meeting start time is the start time of the next occurrence in the series.
The default value is Location,AllProperties:15: changes to the meeting location at any time, or changes to other meeting properties within 15 minutes of the meeting start time results in visible meeting update messages.
There are three scenarios where meeting update messages are not auto-processed regardless of the values specified in this parameter (in these scenarios, attendees will always see meeting update messages in their Inbox):
The update contains a change to the meeting date, time, or recurrence pattern.
The meeting message is received for a delegated shared calendar.
The receiving attendee is @ mentioned in the meeting body.
The attendee has not yet responded to the meeting.
Resolution:
Comments
0 comments
Please sign in to leave a comment.