While reading on Milestone #4, I was planning to use an external hard drive to boot up Windows Server 2016 and complete the necessary tests. However, no matter what I could possibly do, during the installation of Windows Server 2016 would not allow me to install the OS on the external hard drive, giving me the error that USB installations are not supported. I had attempted to use the software "WinToUSB" to proceed with the installation, but the free version does not support Windows Server 2016. Eventually, I had just partitioned the internal hard drive on this laptop and ran the installation. The download was successful and was given the option to choose which OS to boot from. However, several services were disabled by default, such as the WiFi. In the PowerShell, I had to "Get" the wireless windows feature and install it, then start the service WlanSvc as well as install the network adapter drivers from the laptop manufacturer's website.
I was then able to enable the Hyper-V function in server roles, access the virtual switch manager, set up the network adapter, and finally create the virtual machine. I ran the BC Backup utility and went through the options to back up the Hyper-V specifically. The backup succeeded with no errors, but upon restoration, the files that were "extracted" had a different extension name and the file type of the restored contents changed to FASTNEURON with several arbitrary letters and numbers ahead of it. I am unsure if this is intentional but I was unable to access the restored VM. I manually changed the name of the restored file to end with VHDX in hopes the Hyper-V would recognize the file. But unfortunately the file was not recognized. I believe I could have overlooked a step on my part, but I was under the impression that the restoration option would complete all necessary steps and extract a usable file without any additional steps.
