Holds: How to Restore In-Place Hold and Litigation Hold Settings in an Exchange Hybrid Deployment

By Ashwin Venugopal -

 







Process

In an Exchange Hybrid Deployment With or Without On-Premises Microsoft Lync Server 2013

Restore In-Place Hold Settings

In order to restore In-Place Hold settings:

  • Open the Exchange Admin Center via on-premises admin credentials on the Exchange Server.

  • If your organization is enabled for a hybrid deployment with Microsoft Exchange Online in Microsoft 365, click the Enterprise tab in the navigation bar.

  • First select Compliance Management and then in-place eDiscovery & hold.

  • To enter the properties page, double-click the In-Place Hold entry you wish to restore In-Place Hold settings for, or select Edit. 
  • Then select In-Place Hold from the properties page. The user's In-Place Hold settings are shown.

  • Click the Save button after clearing the Place content matching the search query in selected mailboxes on hold check box. 

  • Click the In-Place Hold after reopening the same properties page. You can see that the check box for Place content matching the search query in chosen mailboxes on hold has been cleared.

  • The Place content matching the search query in selected mailboxes on hold check box can be selected by clicking. Additionally, choose Specify number of days to hold things relative to their receipt date, enter the duration, and click Save if you were utilizing a time-based In-Place Hold. By doing this, all In-Place Hold settings that were in place before the problem occurred, are restored. 

  • Repeat steps fourth to eighth for any other In-Place Hold entries that you have.

Restore Litigation Hold Settings

In order to restore Litigation Hold settings:

  • Connect to your on-premises Exchange Server implementation after opening Exchange Management Shell. 

  • To restore a user's Litigation Hold duration setting, run the command-

Set-Mailbox <user> -LitigationHoldDuration <ValueInDays>

  • Repeat the above step for each user whose Litigation Hold duration setting you want to restore. 

In an Exchange Online Deployment with On-Premises Lync Server 2013 that's Running Microsoft Azure Active Directory Sync Tool with Hybrid Enabled

To restore Litigation Hold duration:

  • Remote PowerShell can be used to connect to Exchange Online. 

  • To restore Litigation Hold duration setting, run the command-

Set-Mailbox <user> -LitigationHoldDuration <ValueInDays>

  • For every user whose Litigation Hold duration setting you wish to restore, repeat the above step. The Lync 2013 server will recognize the restored Litigation Hold duration settings following the subsequent directory synchronization operation. 

Conclusion

The In-Place Hold and Litigation Hold settings are restored. 






























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