Connect EXO - no longer working, cannot do compliance bulk delete option 18

[jaredparkerRS]

I think the script to connect to exchange online needs to be updated. When I try to run any of the modules that use EXO. It fails with the following error:
"Script Encountered an un-handled exception! This will export in folder: c:\users\username\desktop\powershelloutputs"

The script will then eat up all harddrive space in that folder until the script crashes with:
Export-Clixml : There is not enough space on the disk.
At C:\Program Files\WindowsPowerShell\Modules\O365Troubleshooters\2.0.0.26\O365Troubleshooters.psm1:1859 char:18

• ... $_ | Export-Clixml -Depth 100 -Path "$([Environment]::GetFolde ...

•             ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
  

  • CategoryInfo : NotSpecified: (:) [Export-Clixml], IOException
  • FullyQualifiedErrorId : System.IO.IOException,Microsoft.PowerShell.Commands.ExportClixmlCommand

[divadiow]

same here. did you solve?

[jaredparkerRS]

No luck yet getting it to work. I tried downgrading to exchangeonlineservices v2.5 from 3.0 but it still will not work. If you import exchangeonlineservices and run the Connect-IPPSSession command. You can then manually run the start-ComplianceSearchBulkDelete.ps1 script after editing a few commands. You need to change the Get-ccComplianceSearch's by removing the cc before compliance search as the command is different. The script will run but will not be able to create a log. IIt was working for us but the next day we started having issues with our tenant and when we run any compliance purge job, it completes but the emails are never deleted. We have a ticket in with Microsoft about that issue now. It would be nice to have this tool working like it used to in the past.