eDiscovery: Can't Run In-Place eDiscovery Search For Exchange Online Mailbox in Exchange Server 2019 or 2016 By Using EAC

By Ashwin Venugopal -

 






Symptoms

Depending on the situation, you may encounter the following error message when attempting to use Exchange Admin Center (EAC) on the on-premises server to conduct In-Place eDiscovery searches in Microsoft Exchange Server 2019 or 2016 for cloud-based mailboxes in a Microsoft Exchange hybrid deployment environment:

Scenario 1

You are trying to search a remote mailbox that doesn't have an online archive enabled. In this scenario, an error message resembling the following will appear-

Export failed with error type: 'FailedToSearchMailboxes'. Details: The underlying connection was closed: An unexpected error occurred on a receive. Endpoint: https://mail.contoso.com:444/EWS/Exchange.asmx

Scenario 2

You are trying to search a remote mailbox that has an online archive enabled. The estimate of search results succeeds. However, when you try to copy the results to a discovery mailbox, the attempt fails and returns an error message resembling the following-

Failed Search or Export, Mailbox: UserOne@Contoso.com: :Item: : :DocumentId: : :ItemId: with error: [FailedToGetRootFolders] Export failed with error type: 'FailedToGetRootFolders'. Message: ErrorNonExistentMailbox : No mailbox with such guid. Endpoint: https://mail.contoso.com:444/EWS/Exchange.asmx

Workarounds

It's a known issue in Exchange Server 2019 and 2016. To work around this issue, use any of the following methods:

Method 1

Use the Office 365 Security & Compliance Center to run the In-Place eDiscovery search for the Exchange Online mailboxes.

Method 2

If you still have a server that is running Microsoft Exchange Server 2013 that is installed in your on-premises organization, move the discovery mailbox to the Exchange Server 2013 server, and then try the search again. 

Conclusion

The symptoms of eDiscovery issues are cured with the help of above methods.








































Comments

Post a Comment

Popular posts from this blog

Deployment (Part 3)

By Ashwin Venugopal -
Image
  To read part 1, please click  here To read part 2, please click  here Microsoft Monitoring Agent (MMA) MMA is used across multiple Microsoft solutions and has undergone a few name changes as its features and functionality have evolved. If it is being considered to be used, then following areas should be covered during a Microsoft Sentinel deployment project: Consider the timelines and the strategy for a migration to AMA (Azure Monitor Agent) before the MMA end-of-life.  Consider the central deployment and management methodology for MMA. Determine which endpoints are in scope for deployment as these affect the log ingestion volume significantly.  Azure Monitor Agent (AMA) Organizations with MMA as the main Microsoft Sentinel agent should start planning the migration to AMA as soon as possible to avoid a rushed migration. One of the main advantages of AMA is the ability to control the log collection policy centrally and apply different policies against different...
Read more

Deployment (Part 1)

By Ashwin Venugopal -
Image
  To read part 2, please click  here To read part 3, please click  here Azure Resources Microsoft Sentinel needs following resources to be created: Subscription (if a dedicated subscription(s) will be used) Resource group(s) Log Analytics workspace(s) Automation rules/playbook Alert rules Workbooks Microsoft Sentinel offers hundreds of alert rules, workbooks, and automation playbook templates along with hunting scripts. The templates can be used to activate/deploy schedule alerts, create customized dashboards, create automation playbooks and perform threat-hunting activities. Generally, once deployed, the resources created have to be adjusted to match the existing environment, configure local credentials, etc. Methods of deployment: Manual- Administrator can manually configures the Microsoft Sentinel resources with the help of Azure portal. Any manual process has the inherent risks of human operator error, lack of compliance with potential change control procedures, and u...
Read more

Design Planning (Part 3)

By Ashwin Venugopal -
Image
  To read part 1, please click  here To read part 2, please click  here Complex Organizational Structures SIEM can be an expensive security control, hence, it is common multiple businesses to contribute to the overall expense. Various organizational units may require a level of access to specific dashboards or sets of data. Microsoft Sentinel offers the ability to assign table-level permissions and limit the level of access to the minimum required to perform requisite job functions.  Role-based Access Control (RBAC) Requirements Microsoft Sentinel offers an extensive list of Azure built-in roles that can be used to provide granular access according to the job requirements and permitted level of access. Some of them are various Microsoft Sentinel dedicated roles: Microsoft Sentinel Contributor- Can perform all engineering-related configuration, such as creating alert rules, configuring data connectors, and additional similar tasks.  Microsoft Sentinel Reader- Can...
Read more