Share via

eDiscovery .PST export

Anonymous
2020-01-31T17:32:16+00:00

I'm receiving the eDiscovery credentials box when attempting to export the emails to a .pst file. After repeated login attempts with admin accounts and accounts i've added to discovery permissions, nothing has worked. keep getting the popup for credentials

what i've done:

-logged in as an administrator and have Discovery permissions, verified over and over again

-cleared credential manager of cached creds

-tried various browsers, ie11 is the only browser that ill allow the to get that far. others just crash fail immediately and dont attempt to launch the ediscovery tool

-tried inprivate mode in ie11

-checked and verified permissions of the folder to save the .pst file to

Microsoft 365 and Office | Subscription, account, billing | For home | Windows

Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.

0 comments No comments

6 answers

Sort by: Most helpful
  1. Anonymous
    2020-02-04T14:35:26+00:00

    Shyamal,

    I have tried checking and unchecking the boxes

    I can preview the search results, and have specified beginning and end dates along with specifying everything (which is what I really need)

    I have an on-premisis environment. I have gotten around that localhost\ews error by using the external mail connection mail.mydomain.com\ecp

    I still get the credentials prompt but no matter what, not matter how many accounts I create or machines I test from, same results. Credentials prompt continues to pop up and nothing gets done.

    Thanks

    Was this answer helpful?

    0 comments No comments
  2. Anonymous
    2020-02-04T14:23:32+00:00

    Hi Erv121,

    Thanks for the update. May I know whether you have Include unsearchable items checkbox? If so, un-checkbox to check this issue.

    Are you able to preview the search results without any issue?

    Have you tried to perform the eDiscovery search without specifying start and end dates, and then export to a PST file to check this issue?

    Since error indicate that locahost/ews, I would like to know which kind of environment you have set up. Is it purely Exchange Online or Hybrid Deployment?

    However, I have tested on my side using Edge browser can export without any issue, my environment is purely Exchange Online.

    Moreover, you may also use the eDiscovery search and hold features in the Microsoft 365 Compliance Center. See Manage eDiscovery cases in the Security & Compliance Center

    Your time and understanding will be highly appreciated.

    Best regards,

    Shyamal

    Was this answer helpful?

    0 comments No comments
  3. Anonymous
    2020-02-03T14:11:14+00:00

    now i'm getting this error without the credentials box popping up anymore

    Was this answer helpful?

    0 comments No comments
  4. Anonymous
    2020-02-03T14:07:09+00:00

    Shyamal,

    i've installed the clickonce extension

    no multifactor authentication

    used 3 diff global admin accounts, same issue

    tried on multiple PC's

    added the sites you posted above to the trusted sites intranet zone.

    The only difference is now i cannot get the popup to even show. not sure if there was an update over the weekend that caused this, but i'm worse off than Friday at this point.

    thanks

    Was this answer helpful?

    0 comments No comments
  5. Anonymous
    2020-01-31T20:26:37+00:00

    Hi Erv121,

    Thank you for posting your issue on Microsoft Community. Make sure local intranet zone settings set up correctly in Internet Explorer, *.outlook.com, *.office365.com, *.sharepoint.com and *.onmicrosoft.com are added to the Local intranet zone trusted sites. See Export eDiscovery search results to a PST file

    If you try use other browsers such as Chrome, be sure you install the ClickOnce extension/add-in.

    Do you have set up multi-factor authentication (MFA) for your account? If so, please create app password to check this issue.

    Have you tried to check this issue via using different Global admin account to determine whether it can be reproduce?

    Moreover, please try to troubleshoot this issue via using different PC (e.g. any colleague’s user’s PC) to see whether it is specific client side issue.

    Best regards,

    Shyamal

    Was this answer helpful?

    0 comments No comments