We found the issue was that the VM was already being vmotioned, but the vsphere console wasn't showing the task. Had to use Get-Task to see it. Pity, the old fat vpshere client never had these issues.
↧
We found the issue was that the VM was already being vmotioned, but the vsphere console wasn't showing the task. Had to use Get-Task to see it. Pity, the old fat vpshere client never had these issues.