#windowsproblems

1) Certain ASUS motherboards don’t allow you to use configure the boot order to use multiple “HDDs” (you can’t choose a USB stick as a separate boot option as it shows up as a hard drive) it is a single option of HDD, Removable Devices and Optical Drive.  This presents an issue for installing Hyper-V Server-the installer will flat out refuse to do anything to the drive beyond letting you delete or add partitions-it will not install the OS because it says it cannot make changes to the drive.  Solution: Tap the F8 key during POST to get the boot device options dialog and choose your USB device this way instead to get past this hurdle.

2) Hyper-V Server 2016 requires SLAT support to even run the HyperVisor.  The Core 2 Quad I’m trying to use obviously does not have that feature *sadface*  Hyper-V Server 2012 R2 however does not require SLAT unless you are running a client OS.  I do not plan on it.  Awesome possum.

3) To connect a non-domain joined Windows client to a non-domain joined Hyper-V server, you must do the following: 

A) Ensure you’ve turned the firewall off on your Hyper-V server (this is a test lab, right?) you can do this from the Hyper-V Server using the command prompt and entering the following command: NetSh Advfirewall set allprofiles state off 

B) On the client, enter the following command at an elevated PowerShell prompt: winrm s winrm/config/client '@{TrustedHosts="RemoteComputerName"}' 

C) Install RSAT on your client 

D) From the Server Manager, add the Hyper-V Server (you will have to specify different credentials to talk to it! 

E) Add the Hyper-V Manager to Windows via the Add or Remove Windows Features panel

F) Download hvremote and save it on your client stations somewhere you can conveniently open it from a command prompt.

G) Open the command prompt as an administrator, navigate to where you saved hvremote and execute the following command:

 Windows 7 - 8.1: hvremote /anondcom:grant

Windows 10: cscript hvremote.wsf /anondcom:grant /override

F) FINALLY!  Open the Server Manager, right click on the Hyper-V server and choose Hyper-V Manager and then connect to the server-do NOT specify credentials.  BAM!  Done

Now I only need to wait on the updates to install before I can reboot and hope that fixes the problem with the RPC error the Hyper-V Manager is giving me on my client :P

Once this is all working, I’ll be building a closer to reality VM network based on AMD64 compatible Ubuntu VMs to run Docker and Docker Swarm.  My poor little Pis don’t have Docker 1.8 yet and ETCD doesn’t even run on 32-bit hardware without some more under the hood diving that I just don’t have the patience for right now.