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.
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.
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.
ClickOnce has been deprecated by Google but is still supported in current builds... That's why it still works in the old interface, but it is blocked in the new interface.
- Yes, that's what I saw before clicking 'Export' (second screen shot). When I clicked it I got the error box that complains about 'failed to find parameter'. I was in IE when failing to export the results in the new UI. Trying a test export to get you a screen shot is failing now though. Apparently after one export went through others are working just fine in both browsers.
As for chrome not working, the ClickOnce extension still works for me. Is it failing for you? Content search exports are different in the new experience. For one thing, you can no longer use Chrome to export search results because Google has deprecated the feature Microsoft used to download and launch the export app.
But I have certainly been able to export information from a content search.
Export from a content searchLeading to:
Export options
Isn't that what you see in the new experience?
I hate to bring back old threads, but it's always nice to find info in threads that show up high on search results.
As of today (05/10/2018) the export error still exists. However, swapping back to the "old experience" and using the export results link in the right column still works.
OK. Then it's time to log a support call with Microsoft.
I too have some scripts that I use with searches. When I went to test one to investigate this problem, I also found that I had the wrong permissions and the export parameter wasn't available. After I amended permissions and restarted the PowerShell session, all was well...
- It is. We have both been using a script to do this for some time. The error returned is that the export flag does not exist. I have exhaustively tested it.
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.
