Just installed most recent VBO 365, ran into same issue
Apparantly the Cmdlets will only run under Windows PowerShell.
Throwing errors when ran from PowerShell.
Import-Module has a parameter, -UseWindowsPowerShell, which runs a seperate Windows PowerShell session in the background and imports the module there.
But everything gets deserialized, this is not convenient to say the least.
Only working bypass seems to be;
Code: Select all
$result = Invoke-Command -Session $session -ScriptBlock {
Import-Module Veeam.Backup.Powershell -UseWindowsPowerShell ; Get-VBRBackup | fl *
}
return $result
But since this returns deserialized data, it cannot be used as objects for any further actions.
When can we expect to see no more (legacy) Windows Powershell dependancy?