Today the Exchange administrator of my customer got the request to disable “Meeting Forward Notifications” for a specific person. What does that mean? When I send you an invite to a meeting and you forward that invite, I will get a message stating that you’ve forwarded my invite…
Depending on the role of a person, let’s say a secretary for example, the number of such messages can be enormous!
As with more and more specific features, this was not possible through the GUI but only through PowerShell.
Configuring this on a global level is pretty easy:
Set-RemoteDomain -MeetingForwardNotificationEnabled $false
So, on a single user you would expect the same property name (MeetingForwardNotificationEnabled), right? As I found out, this was not the case!
On a user, the property is named ”RemoveForwardMeetingNotification” and can be configured with the following line:
Set-CalendarProcessing -Identity “Jeff.Wouters@methos-it.com” -RemoveForwardMeetingNotification $True
“Darn it! Is PowerShell really that inconsistent?” was the question I got within moments from my colleague…
Well, this time PowerShell is not to blame. When you look at the properties of the global object RemoteDomain on Echange level and compare them to the properties of a user object (also still in Exchange) you will notice that the names differ inside Exchange and therefor also in PowerShell 
