为什么 Exchange 自定义保留策略会改回以前的策略

为什么 Exchange 自定义保留策略会改回以前的策略

我设置了自定义保留策略,但大约一小时后,保留策略又变回了之前的策略。知道为什么会发生这种情况吗?我通过 Powershell 设置了几次保留策略,但它总是恢复原样。

  • 我应该补充一点,邮箱目前已满,这就是我应用新策略来腾出空间的原因。邮箱目前无法使用。

风俗:

Name                 RetentionPolicyTagLinks
----                 -----------------------
15 Month Delete      {15 Month Delete - All, Junk Email - 7 Day, Deleted Items - 30 Day}

恢复至:

Name                 RetentionPolicyTagLinks
----                 -----------------------
Company MRM Policy   {1 Year Delete}

尝试手动强制将策略应用于邮箱

Powershell>Start-ManagedFolderAssistant -Identity "[email protected]"
Powershell>
Powershell>
Powershell>
Powershell>Get-MailboxFolderStatistics "[email protected]" -FolderScope Inbox | Format-Table Name,FolderPath,ItemsInFolder,FolderAndSubfolderSize

Name                 FolderPath            ItemsInFolder FolderAndSubfolderSize
----                 ----------            ------------- ----------------------
Inbox                /Inbox                       177017 84.44 GB (90,667,087,358 bytes)
....

还尝试使用合规性搜索 + 操作

Powershell>New-ComplianceSearch -Name "Remove older than 15 month messages" -ExchangeLocation "[email protected]" -ContentMatchQuery "(Received <= $((get-date).AddMonths(-15).ToString("MM/dd/yyy")))"

Powershell>New-ComplianceSearchAction -SearchName "Remove older than 15 month messages" -Purge -PurgeType SoftDelete

Confirm
Are you sure you want to perform this action?
This operation will make message items meeting the criteria of the compliance search "Remove older than 15 month messages" completely inaccessible to users.
 is no automatic method to undo the removal of these message items.
[Y] Yes  [A] Yes to All  [N] No  [L] No to All  [?] Help (default is "Y"): A

Name                                      SearchName                          Action RunBy       JobEndTime Status
----                                      ----------                          ------ -----       ---------- ------
Remove older than 15 month messages_Purge Remove older than 15 month messages Purge  adminuser              Starting


答案1

您可以尝试在 EAC 中分配保留策略并检查此问题是否继续存在?

将保留策略分配给用户后,运行 Start-ManagedFolderAssistant。然后确认问题是否仍然存在。

另外,这个问题是所有用户都会出现还是只针对某一个特定的用户?

相关内容