I'm stymied on troubleshooting the alleged dupes due to politics. I don't know WHO is getting them or from WHOM the message originates. I'm of the opinion there are no dupes (it would mean the categorizer is seriously borked).
From: [email protected] To: [email protected] Subject: RE: [Exchange] embedded DG's Date: Wed, 17 Jun 2015 16:34:13 +0000 I would do some message tracking on the supposed duplicate. Make sure that it wasn’t sent externally and that both the group and individual weren’t copied. Also, depending on Outlook configuration, I have seen Inbox rules and corruption of PST files cause duplicates to appear. Need all nested group members? Use Active Directory Module for Windows Powershell: Get-ADGroupMember -Recursive -Identity “samAccountName of the group” If you want the email addresses of those users you can pipe it to Get-ADUser: Get-ADGroupMember -Recursive -Identity “samAccountName of the group” | Get-ADUser -properties mail From: [email protected] [mailto:[email protected]] On Behalf Of Daniel Chenault Sent: Wednesday, June 17, 2015 11:07 AM To: [email protected] Subject: [Exchange] embedded DG's I recall back in the first couple versions (4.0, 5.x) that if UserA was in a DG and that DG was a child of another DG of which UserA was a member that user would get two copies of the message. I also recall this was fixed in Ex2000. I just got a ticket from a user claiming this is happening. Said user is a high-level manager (actually Director level) and he says this is from the company owner. I've tried to get some troubleshooting going but it seems politics is getting in the way (there are no technical solutions for behavioral issues). Now the problem description has changed from "duped mails" to "want to see all members of a DG without having to dig." In other words I've been told to unravel a BUNCH of DG's with a lot of embedded DGs. I can script this (sorta; having some issues) but was wondering if someone else had already encountered this and had a better solution than me hammering out a PS script.
