Return
-
Title
Briefly describe the article. The summary is used in search results to help users find relevant articles. You can improve the accuracy of search results by including phrases that your customers use to describe this issue or topic.Changes made in the Excha -
Description
When we add a user to a distribution group in the exchange server, the alert does not contain the user we added but rather a random user. -
Resolution
This is a side effect of how the Exchange console adds or removes users to/from groups.
ex. Say you have a group with three members A, B, and C and you want to remove member B. Here is what Exchange will do, in order.
1) Remove member C from the group.
2) Remove member B from the group.
3) Remove member A from the group.
4) Add member C back to the group.
5) Add member A back to the group.
Each of these actions will generate an event in the event logs within the same time. When these events come in as a group to Active Administrator we show the most recent relevant event from the event log to prevent a flood of messages on the same event.
Thus, the notification you will get is the last event. Adding member A back to the group. All of the events will appear in our database however they did not all trigger notifications to prevent an email flood.
An example of where alerting on all changes would be bad would be if a group contained say 50 members. Thus an addition of a member to a group would trigger 101 email notifications, and a removal would trigger 99 email notifications. This would be undesirable. Unfortunately in this case the most recent event, which would normally be the most relevant, is incorrect compared to the desired change leading to the confusion we are seeing here.
Unfortunately due to how the Exchange Console makes group membership changes we have no simple way to tell which of the events is the one you would be interested in as the actual addition or removal could appear anywhere within the list of events from the event log.