Forum Discussion
Export to PST via Powershell
No way to do it without going to the SCC and initializing the download via the click-one app, sorry. Perhaps you can automate it via AzCopy or some other tool that takes container/token as input - you can get those via the Result property of Get-ComplianceSearchAction.
As for the cmdlet, make sure you also use the -Format parameter!
The Format parameter specifies the format of the search results when you use the Export switch. Valid values are:
FxStream Export to PST files. This is the only option that's available when you export search results from the Security & Compliance Center.
Mime Export to .eml messsage files. This the default value when you use cmdlets to export the search results.It's most likely what causes the issue in your case.
Are there eDiscovery PowerShell commands to do the export? We want to export the content search results from eDiscovery content searches to a shared drive for investigators to access.
I have searched a lot but I don't think there is a way to download it through PS
Actually, even the export no longer works. I have currently opened a ticket with Office 365 to find out why. There is:
New-ComplianceSearchAction -SearchName $SearchName -Export
A parameter cannot be found that matches parameter name 'Export'.
The updated help still shows the parameter, and the TechNet page has not been updated. However, search for it in the Command modules help in ISE, the check box for Export has now disappeared in the last week as well as the ArchiveFormat parameter. Can't find anything about it.
The compliance search functionality is being rewritten at present. This might have had the side-effect of removing the parameter. I have pinged the development team to ask.
- Thank you!
Do you know if it Will je possible to download results through powershell?
Hi Brad
I was having the exact same issue.
I tried it on thuesday and it failed to find the parameter
Tried it on wednesday and it found the parameter
I think they are activly working on the cmdlet. I wouldn't use it in the meanwhile.
Check that the account you use to log into PowerShell is a member of the Compliance Center eDiscovery Manager role group... The account needs to have this right to expose the Export function.
