Firtst, try to remove the VM with the VMM Powershell module:
1 2 |
$vm=Get-SCVirtualMachine -Name "your machine name" Remove-SCVirtualMachine -VM $vm -Force |
If this was not succesvol you can try this:
This is a sweaty hand job, but in most cases succesful..
On your VMM Management server, stop VMM Management service and VMM Agent.
Login to your SQL Management Studio and start a Query against your VirtualManagerDB.
First search for the ID, the Spooky VM have:
1 2 3 4 |
USE [VirtualManagerDB] SELECT *FROM tbl_WLC_VObject WHERE (Name = 'VM001') |
After you get the ID, past this ID in the following 3 sections of code in the GUID section:
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 |
USE [VirtualManagerDB] GO DECLARE @return_value int EXEC @return_value = [dbo].[prc_WLC_RemoveVMInstance] @VMInstanceId = 'GUID' SELECT 'Return Value' = @return_value GO USE [VirtualManagerDB] GO DECLARE @return_value int EXEC @return_value = [dbo].[prc_WLC_RemoveVObject] @ObjectId = 'GUID' SELECT 'Return Value' = @return_value GO USE [VirtualManagerDB] GO DECLARE @return_value int EXEC @return_value = [dbo].[prc_WLC_RemoveHWProfile] @HWProfileId = 'GUID' SELECT 'Return Value' = @return_value GO |