P.s., just noticed that there is an inconsistency in the instructions. So, unless I made a mistake somewhere, I suggest following most of the instructions above, apart from MOVING the config files, COPY them instead The first one is to directly call the function and provide the parameter which accepts the VM name. I could then Import the VM with the files that I had previously moved. Then I could delete the VM (and associated, but now redundant) config files. To get this to work, I had to copy (not move!) the machine files back to their previous locations. ![]() after moving the VM config files - the VM config options in Hyper-V manager were missing. I don't know whether I did something wrong, but when following these instructions using Hyper-V manager under Windows 10 and referencing a Hyper-V server running Hyper-V 2016, I could not delete the VM.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |