- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
As documented in KB2008957, a unregister/register of the VM might help.
Try with this
$vm = Get-VM -Name MyVM
$pathVMX = $vm.ExtensionData.Config.Files.VmPathName
$esx = $vm.Host
$rp = $vm.ResourcePool
Remove-Inventory -Item $vm -Confirm:$false
New-VM -VMFilePath $pathVMX -VMHost $esx -ResourcePool $rp -Confirm:$false
Blog: lucd.info Twitter: @LucD22 Co-author PowerCLI Reference