I'm trying to remotely manage Hyper V server 2012 from a windows 8 pc, both client and server are on a workgroup.
I've spent about 3-4 hours trying to get this working with no luck so far trying the following:
Creating a new administrator on the server with the same details as the client ie. username / password.
Add an entry into my hosts file to point to the remote ip by server name.
Tried using HVRemote.
Disabled both firewalls.
The error that I'm getting is RPC Service Unavailable.
How can I accomplish what I'm trying to do?
Update
Some of the operations on the Hyper-V Manager work. IE. Virtual Switch Works. I can open the New VM Wizard. I run into an error when creating a new Virtual Hard Disk tho. I've tried creating a VM without a hard disk, which works. Using the new hard disk wizard does not work either.
I still can not see any Virtual Machines. RPC server unavailable. Unable to establish communication between 'ServerName' and 'ClientName'
Update 2
Here's a screen shoot of my error.
Allow MMC & WMI through the Windows Firewall, on both
netsh advfirewall firewall add rule name="Microsoft Management Console" dir=in action=allow program="%windir%\system32\mmc.exe" enable=yes profile=private
netsh advfirewall firewall set rule group="Windows Management Instrumentation (WMI)" new enable=yes
Allow Annoymous DCOM Access, on the client
Directions from: http://publicjotting.blogspot.com/2012/06/hyper-v-server-2012-and-remote-hyper-v.html & http://technet.microsoft.com/en-us/library/jj647788.aspx
It's an UAC issue. In a workgroup environment you must use the built-in Administrator account on the hyper-v host since WMI can't elevate a regular Administrator account.
There are only three way to run a WMI script elevated.
Running it from a elevated cmd/powershell prompt. Scheduling it to run in a administrator account context (any administrator account). Use the built-in Administrator account (which always run elevated).
Ie, creating a matching user on the server and putting it in the Administrators group is not enough since you can't elevate your account WMI will regard it as a regular user account and fail your request.
I wrote a pretty extensive blog post on how and why.
http://blog.plausibledeniability.se/post/33464344054/hyper-v-remote-administration
My preferred solution (TLDR)
You still need to open up the firewall for incoming WMI management on the Hyper-V host and add the ANONYMOUS LOGON group to the “Distributed COM Users” group or update the CINOM registry setting to allow anonymous callbacks, on the client.