MicrosoftWhile I understand the desire to control access to Content Searches similarly to how permissions are managed in eDiscovery, this new model (of just putting Content Searches into a single eDiscovery-like case) causes problems.
Content Searches and eDiscovery have two very different purposes, and by lumping in Content Search as eDiscovery, we are now prevented from deleting old content searches and their associated review sets.
For instance, I have 100 "new" content searches created for various unrelated matters. For 5 of them, the content has been found (the purpose of Content Search) and the topic is considered resolved. How do I now delete just those 5 resolved content searches and review sets?
Untested in the "new world," but something like this may work for the new Content Searches as well:
$searchid = Get-ComplianceSearch |?{$_.runby -like "*theDude*" -AND $_.jobendtime -le ((Get-Date).AddDays(-90))}|select -ExpandProperty identity
then
foreach ($s in $searchid){Remove-ComplianceSearch -Identity $s}
Stefanie_Bier The new export process is one of the worst export experiences I have ever had with a microsoft product.
Yes, that is the biggest issue I'm seeing. Exports for a small set of results are now taking several hours and this is without the friendly naming, etc. options selected. I used to be able to run a search on targeted mailboxes, review sample (easily modify) and export a search in under 30 minutes.
