Submitted by SomeShinyObject on Mon, 08/04/2014 - 21:33
Today I found that in my haste to set up my Hyper-V virtual machines, I didn't properly account for the XML files it creates to use as configuration files for the VMs. I had haphazardly chosen random places accidentally, not realizing the full extent of what I was doing. Chalk it up to inexperience. I went searching for ways to find my haphazardly placed VM config files. I wasn't getting to far so I figured I'd open up PowerShell and see what I could do with the
Get-VM CmdLet provided in the Hyper-V module.