Archiving with Hyper-V on Windows 10 Pro
This is not meant to be a professional guide, just the steps I took to get it running
- Install the prerequisites
- You will also need 7-zip. You can use this in Linux or Windows. I used the GUI on Windows.
- Download the appliance
- Open the appliance file with 7-Zip and extract the files to your Download folder (or you can move it somewhere else, just don't lose it).
- You will need the tool qemu-img located in the package qemu-utils, I used Ubuntu to run the tool, using the Windows Subsystem for Linux. You can download Ubuntu on the Microsoft Store after installing the Windows Subsystem for Linux. In the Microsoft Store, hit "Launch" and it will download Ubuntu
- Type Bash in a run window (Win+R or open Task Manager and go to File>Run)
- Update your repositories sudo apt update
- Install qemu-utils with sudo apt install qemu-utils
- Bash will start you in the home directory for your Linux user. Most likely, this is not where you downloaded the appliance. Your current directory will be ~ or /home/<yourname>. To get to your Windows drives, we need to change directories. cd /mnt will move you to the folder with all of your partitions. Most of the time your download folder will be on your C: drive. Mine is on L:. From here you can cd c/Users/<yourname>/Downloads. In my case it was cd l/Downloads.
- The command I used to convert the .vmdk to a .vhdx was qemu-img convert archiveteam-warrior-v3-20171013-disk001.vmdk -O vhdx -o subformat=dynamic archiveteam-warrior-v3-20171013.vhdx
- Now we have archiveteam-warrior-v3-20171013.vhdx which we can use in Hyper-V!
Now we need to create our VM
- Using the Hyper-V Manager we can create and manage our VM. First we'll need internet access for the VM otherwise the Warrior is useless. You can search for this tool in your Start menu.
- In the Actions sidebar click Virtual Switch Manager. Click New virtual network switch, make sure External is highlighted, then click Create Virtual Switch
- You can name your switch whatever you want to help identify it, this name will be used to identify our new network adapter. Make sure you change your connection type as needed. If it's set to the wrong network adapter the VM won't have internet access! When you're done simply hit OK
- Now we're ready to create the VM. In the actions sidebar, click New then click Virtual Machine when the context menu pops up.
- Click Next
- Name your Virtual Machine. In this case, I'll use ArchiveTeam Warrior v3 #2. You can also change where the VM will be stored if you like. When you're done hit Next
- Make sure you select Generation 1. This is VERY IMPORTANT. The Warrior did not run for me with UEFI enabled. YMMV, Gen1 works. Click Next to continue.
- Adjust your Startup memory as needed then click Next. You can leave it as default if you have enough RAM.
- On the Configure Networking screen we are going to select the adapter we created earlier. Choose your network adapter then click Next
- Now we need to select our Storage. We already have a .vhdx, so select Use an existing virtual hard disk and click Browse.... Find your archiveteam-warrior-v3-20171013.vhdx and click Open then click Next
- If everything looks good and you're ready to start, hit Finish. Hyper-V will now create your VM and if everything goes well you'll see it under "Virtual Machines" and it's state will be Off by default.
- Click your VM in the list, then on the right side under your VM's name, click Settings.... Here you can adjust important aspects of your VM as needed, such as Memory, Processor, Network Adapter, Automatic Start Action (If you want your Warrior to boot automatically with your PC), and Automatic Stop Action (How Hyper-V handles shutting down the VM when you shut down your PC.) I recommend Shut down the guest operating system but it's up to you.
- Click OK to save any changes, or Cancel to forget them.
- You can start your VM in Headless mode by clicking Start on the right, and if you hit Connect... you can get a Remote Desktop Connection started to the VM. You can close the RDC window at any time, your VM will keep running in the background. It is managed by the Hyper-V service now. If you need to manually manage it, you can do so in the right Actions sidebar.
No Internet Connection
When creating these VMs, I was running into a problem where the VMs weren't being assigned IPs via DHCP. I didn't spend a lot of time digging into it, but what did help was just resetting the VM until it got an IP, then it downloads the Warrior and continues normally. This may help if you run into the same problem. You can do this from Action>Reset... or hit CTRL+R