Problems with DiscoverySearch

Question

Hello,

Strange problems with both "GUI " and PS-based discovery:

1) Can't export the search to pst - Exchange keeps asking for credentials:

2) This command ...
[PS] C:\Windows\system32>New-MailboxSearch DS1 -StartDate 04/01/2022 -EndDate 05/12/2022 -TargetMailbox 'DiscoverySearchMailbox' -SearchQuery 'FingerPrint' -MessageTypes Email -StatusMailRecipients "entadmin@Company portal .net"

... produces the following error:

The error will be shown for any parameter should I omit the first, the second and etc.
Of course my user account is a member of Discovery Management role group.

???

Answer 1

Hi @Mikhail Firsov

Glad to know that your issue resolved now and thanks for your feedback! Regarding your concern why you need to add this registry key in your environment and for other environment not. That's since The configuration and complexity of each environment is different, such as test environment and production environment. And some configuration in your environmnt may have higher priority which may override the default one, so we need to add the registry key to make it work. It's hard to find the root cause.

I would make a brief summary of this post so that other forum members could easily find useful information here:

[Problems with DiscoverySearch - Summary]

Issue Symptom:
Failed to export the ediscovery PST and keeps asking for credential.

Solution:
Fixed the issue using the PS command New-ItemProperty HKLM:\System\CurentControlSet\Control\Lsa -Name "DisableLoopbackCheck" -Value "1" -PropertyType dword

Reference Links:
On Premises Exchange 2016 eDiscovery PST Export - Discovery Export Credential

You could "Accept Answer" for this summary to close this thread, and your action would be helpful to other users who encounter the same issue and read this thread. Thanks for your understanding!

---

If an Answer is helpful, please click "Accept Answer" and upvote it.

Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.

Answer 2

Hi @Mikhail Firsov

I test the same operation in my environment and it can work properly without prompting for credential.

I noticed in the official document, it said that:

Make sure you didn't configure MFA for your account.

For your second question, the -TargetMailbox "DiscoverySearchMailbox" should be -TargetMailbox "Discovery Search Mailbox"

---

If an Answer is helpful, please click "Accept Answer" and upvote it.

Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.

Answer 3

Hi joyceshen-MSFT,

Regarding Q2: Oh,... rather strange: before running this command I checked what's the name of the discovery mailbox:

Q1: Regarding Q1: of course my accounts is not set for MFA and I've never had any issues with the PST-export on my previous deployments.

Here's the post with the same problem and the only way to resolve the issue was to open a case with MS. By the way, the registry parameter the MS employee had to add to the affected server in those case is missing on my server too:
"He fixed using the PS command New-ItemProperty HKLM:\System\CurentControlSet\Control\Lsa -Name "DisableLoopbackCheck" -Value "1" -PropertyType dwaord" - I'm just not sure is this a real cause of the problem...

Answer 4

Yes, I have:

..but two questions remain:

1) why does it work on your Exchange and on my previous Exchange installations WITHOUT that parameter (and it means this parameter is NOT required!) and

2) why does this information cost 499$ if it seems most likely a bug...

Regards,
Michael

Answer 5

Hi joyceshen-MSFT,

"And some configuration in your environmnt may have higher priority which may override the default one, so we need to add the registry key to make it work. It's hard to find the root cause." - I agree, but when I buy some product I expect that product to be functional in ANY possible configuration - NOT only in the default one - or at least expect a developer would help a customer in a case when their product is not working for some reason and that reason is NOT the customer's mistake, instead of billing him/her for their own bugs!

Regards,
Michael