This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
Hello,
I had the problem with eDiscovery according to this article:
In the optional step 5 MS says:
"Add a discovery mailbox as a member of the distribution group used to create the custom management scope"
I was suprised to see this because after adding the discovery mailbox to the distribution group used to create the custom scope, the eDiscovery search would be run against the group that will contain the discovery mailbox and this mailbox will be used for coping search results later on.
Furthermore, I thought there could be one more issue with that configuration because adding the discovery mailbox to the "target" group should lead to this discovery mailbox to be searched too.
Anyway, MS says
"Create an eDiscovery search, and select the distribution group that was used to create the custom management scope as the source of mailboxes to be searched. All mailboxes should be successfully searched."
After following all the steps in the article I've bumped exactly in two issues I'd expected:
1) the discovery mailbox can not be searched:
2) you can't copy the search results to the mailbox that is a member of the group being searched:
So I don't quite understand what have I done wrong... I was just following the steps in the article... ???
Thank you in advance,
Michael
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(25.6, 67%, 12%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EJS%3C/text%3E%3C/svg%3E)
Hi @Mikhail Firsov , don't remember to accept the helpful reply below as answer which resolved your initial question. Thanks for your understanding!
Would anyone please check whether this works in your environment:
Thank you in advance!
Hi @Mikhail Firsov , I tried in my environment, it works with below command:
Get-Recipient -Filter "MemberOfGroup -eq 'CN=group1,CN=Users,DC=contoso,DC=com'"
Hi joyceshen-MSFT,
Thank you for your test!
Am I getting it right that the command with the "name" parameter did not succeed (... eq 'Group1'")?
Seems neither the RecipientRestrictionFilter in the -NewManagementScope nor the Filter in the Get-Reipient does not "understand" the "name" parameter.
Thank you all for help!
Regards,
Michael
Hi @Mikhail Firsov , can the search work properly after changing the group name like 'CN=XXX,CN=XXX,DC=domain,DC=com'?
In my test, it seems work. I use Exchange 2016, for example user imap is not a member in group1, it will got error
and for users in group1 the search can be created successfully 
...recreated from scratch: now I even can't create the search as discovery manager for the newly-created scope - seems the -RecipientRestrictionFilter does not "understand" the DS names properly:
I even tried to feed the New-ManagementScope the non-existent path and it did succeed - I think that's the answer to my question "does anybody know why MS recommends to use the "double-step method" - 1) $DG=... 2) $DG.DistinguishedName".
...will post later how it works with the MS's method.
...exactly the same error: ~ "the source DS_Test is outside the scope .../Test/DS_Test ..." - no comments.
Anyway, the initial question was about the copying of the search results and it was clarified - thank you all for your help!
Regards,
Michael
Hi, I test, the same behavior as yours.
In addition, you could accept the helpful reply above as answer which resolved your initial question. Your action would be helpful to other users who encounter the same issue and read this thread, thanks for your understanding!