All of Microsoft’s server stuff is designed to work within an already existing Active Directory environment. Most home users don’t have an Active Directory server, unless you are running SAMBA 4 or higher (Linux product, advanced users only). So additional configuration is needed to get server products running and talking to eachother in a Workgroup environment.
Three main steps here
A) Setup Hyper-V Server 2012 R2 to accept connections
B) Setup Remote Server Management on desktop machine
C) Setup Hyper-V Management on desktop machine
- Add Local Administrator whose name and password match your user account on your desktop
- Configure Domain/Workgroup to match that of your home Workgroup (default is probably fine)
- Change computer name to something recognizable (like “hypervserv”)
- Configure/enable remote management
- Enable all clients Remote Desktop
- Disable firewall* using this command line (works in cmd.exe or powershell) netsh advfirewall set allprofiles state off
- Download and install Windows 8 Remote Server Management (not yet avalible for Windows 8.1 but it should be by October 18th)
- Edit your desktop hosts file AS ADMINISTRATOR in notepad. Add your hyperv server to %windir%\System32\drivers\etc\hosts file via notepad. It should look something like
For whatever reason microsoft server products will NOT connect via IP, you MUST use server names. Make sure you save it as “all files” “hosts” file and not as a “hosts.txt” file.
9. Open powershell AS ADMINISTRATOR and enter this command. If you don’t you will get an error like “WinRM Negotiate authentication error”
Set-Item wsman:\localhost\Client\TrustedHosts hypervserv -Concatenate -Force
10. To setup Hyper-V manager with workgroups, Run
-Right click My computer under Component Services\Computers
-Select COM Security, Edit Limits under Access Permissions
-Check “allow” for “Remote Access” on both ANONYMOUS LOGON and ALL APPLICATION PACKAGES
11. Restart Hyper-V manager
And you should be good now. If anything doesn’t work, make sure you are running powershell/notepad/etc as administrator and not as local user.
*Yes, really! If this is a production environment, don’t do this, but this is for a home user on a workgroup who doesn’t have Active Directory setup. Once everything is working you can turn it back on