Skip to main content

How to completely remove a VM from Hyper-V

By
When a VM has done its job and it is time to say “c’est la vie” to it, getting rid of it completely may not be as cut and dry as you think.

First off, delete it from your Hyper-V Manager.  To do this, open Hyper-V Manager

Right click the VM you want to remove and click Delete.

Click Delete once more.

The Status column for that VM will show you Hyper-V Manager’s progress.

image

This only removed the VM from that Hyper-V Manager.  It did not delete the VMs files.  This could be both a good, and a bad thing.  The good thing is that you an always port this VM to another Hyper-V host or back into the original one.  The bad news is that it is still consuming your hard drive space.  If you truly want to get rid of this VM, browse to the location where it was stored and delete the parent folder.
Labels:

Comments

Anonymous said…
Thanks for the post, I couldn't find this information on Microsoft site at all. However, how about more information on the 5 types of files and how to determine their locations.
August 29, 2013 at 12:38 PM
Jason Yoder, MCT said…
If you are on Windows Server 2012 or Windows 8, Open PowerShell as an Administrator. Execute this command:

PS C:\Windows\system32> Get-VM -Name Test | Select-Object -Property *

You will be able to see where the files of the VM are stored.


VMName : test
VMId : 7e7629cd-2f64-4e29-8dc7-093ed8d75f5d
Id : 7e7629cd-2f64-4e29-8dc7-093ed8d75f5d
Name : test
State : Off
OperationalStatus : {Ok}
PrimaryOperationalStatus : Ok
SecondaryOperationalStatus :
StatusDescriptions : {Operating normally}
PrimaryStatusDescription : Operating normally
SecondaryStatusDescription :
Status : Operating normally
Heartbeat :
ReplicationState : Disabled
ReplicationHealth : NotApplicable
ReplicationMode : None
CPUUsage : 0
MemoryAssigned : 0
MemoryDemand : 0
MemoryStatus :
SmartPagingFileInUse : False
Uptime : 00:00:00
IntegrationServicesVersion :
ResourceMeteringEnabled : False
ConfigurationLocation : d:\VM\Test\Test1\test
SnapshotFileLocation : d:\VM\Test\Test1\test
AutomaticStartAction : StartIfRunning
AutomaticStopAction : Save
AutomaticStartDelay : 0
SmartPagingFilePath : d:\VM\Test\Test1\test
NumaAligned :
NumaNodesCount : 1
NumaSocketCount : 1
IsDeleted : False
ComputerName : JASONPC2
Notes :
Path : d:\VM\Test\Test1\test
CreationTime : 8/29/2013 12:59:08 PM
IsClustered : False
SizeOfSystemFiles : 27930
ParentSnapshotId :
ParentSnapshotName :
MemoryStartup : 1073741824
DynamicMemoryEnabled : False
MemoryMinimum : 536870912
MemoryMaximum : 1099511627776
ProcessorCount : 1
RemoteFxAdapter :
NetworkAdapters : {Network Adapter}
FibreChannelHostBusAdapters : {}
ComPort1 : Microsoft.HyperV.PowerShell.VMComPort
ComPort2 : Microsoft.HyperV.PowerShell.VMComPort
FloppyDrive : Microsoft.HyperV.PowerShell.VMFloppyDiskDrive
DVDDrives : {DVD Drive on IDE controller number 1 at location 0}
HardDrives : {Hard Drive on IDE controller number 0 at location 0}
VMIntegrationService : {Time Synchronization, Heartbeat, Key-Value Pair Exchange,
Shutdown...}
August 29, 2013 at 1:01 PM
Post a Comment

Popular posts from this blog

How to run GPResult on a remote client with PowerShell

By
In the past, to run the GPResult command, you would need to either physically visit this client, have the user do it, or use and RDP connection.  In all cases, this will disrupt the user.  First, you need PowerShell remoting enabled on the target machine.  You can do this via Group Policy . Open PowerShell and type this command. Invoke-Command –ScriptBlock {GPResult /r} –ComputerName <ComputerName> Replace <ComputerName> with the name of the target.  Remember, the target needs to be online and accessible to you.
Post a Comment
Read more

Set up your Environment to utilize Invoke-GPUpdate

By
I’m sitting in O’Hare enjoying my 3 hour layover as I get ready to teach a Windows 10 class in Fort Wayne.  I’m actually prepping for my class in Fort Wayne in a few weeks, 10982 Supporting and Troubleshooting Windows 10.  This class is very much like the Windows 7 version that I used to teach so I decided to up the detail quite a bit.  In the GPO troubleshootin chapter, I’m including a demonstration on how to use PowerShell’s Invoke-GPUpdate.  I needed to make sure the environment is set up for me to be able to utilize this cmdlet.  If you read the Notes section on Invoke-GPUpdate’s help file, you will see there are three firwall rules that need to be in place:          Remote Scheduled Tasks Management (RPC)          Remote Scheduled Tasks Management (RPC-ERMAP)          Windows Management Instrumentation (WMI-IN) I decided to create a little PowerShell script to crea...
Post a Comment
Read more

Where did a User’s Account Get Locked Out?

By
Updated: May 15, 2015 When this article was originally published, two extra carriage returns were add causing the code to malfunction.  The code below is correct.   My client for this week’s PowerShell class had a really interesting question. They needed to know where an account is being locked out at. OK, interesting. Apparently users hop around clients and forget to log off, leading to eventual lock out of their accounts. The accounts can be unlocked, but are then relocked after Active Directory replication. This problem is solved in two parts. The first one is to modify the event auditing on the network. The second part is resolved with PowerShell. The first part involves creating a group policy that will encompass your Domain Controllers. In this GPO, make these changes. Expand Computer Configuration \ Policies \ Windows Settings \ Security Settings \ Advanced Audit Policy Configuration \ Audit Policies \ Account Management Double click User Account Management C...
18 comments
Read more