See also more Hyper-V pages

If managing a server that is not joined to your domain, connect to Hyper-V servers from a workstation using a login with the same admin username and password as the server.

DNS must be in place so that the server and remote management PC can connect to each other via host name and IP address. Do this with your current DNS system or using host files.

On a Windows 8 Pro or higher PC, add the Hyper-V Manager feature in Programs and Features under Hyper-V → Hyper-V Management Tools.

http://technet.microsoft.com/en-us/library/ddb147c1-621c-4b89-9003-81c93ba050d7#BKMK_1_4

On the Hyper-V server command menu:

Configure items 1, 2, 4, 7, 8 and 9.

To allow all MMC snap-ins to connect, at the command prompt on the Hyper-V server run:

netsh advfirewall firewall set rule group="Windows Firewall Remote Management" new enable=yes

If you get the “Group cannot be specified with other identification conditions” error, delete the double quotes and replace on the console. This error occurs if you copy and paste from the Technet website.

To allow only specific MMC snap-ins to connect run this PowerShell command:

Enable-NetFirewallRule -DisplayGroup "<rulegroup>"

Where rulegroup is one of the values from the table below, depending on which snap-in you want to connect.

All MMC Snap-ins work except for “Computer Manager” that is needed to manage disks. For that to work, you can disable the firewall with netsh advfirewall set allprofiles state off at the console command line. Enable with netsh advfirewall set allprofiles state on.

http://www.techrepublic.com/blog/datacenter/configure-the-iscsi-initiator-in-windows-server-core-or-hyper-v-server/3945

If you have a separate NIC for Storage, perhaps 10GbE, you need to configure it separately.

On the Hyper-V server console, access the menu with sconfig.cmd:

1. Choose Network Settings
   1. Select the Index Number of the NIC to configure
      1. Choose (1) Set Network Adapter Address
         1. (S) Static
            1. Enter Static IP address
            2. Enter Subnet Mask
            3. Enter Gateway
      2. Choose (2) Set DNS Servers
         1. Enter primary and secondary servers

On the Hyper-V server console command prompt, type iscsicpl.exe.

If the iSCSI Initiator service is not running click yes to start and make automatic at start up.

In the iSCSI Initiator type the “Target Name” or IP address of the iSCSI share and click connect.

Remember to use the storage network NIC IP of storage server if applicable.

Once you have connected the iSCSI share, you may need to reboot both Hyper-V server and the management PC to see the volume in Computer Manager.

If you have trouble initializing the disk do this at the Hyper-V server console.

Type diskpart at the command line:

DISKPART> LIST DISK 
   Note the disk number of the ISCSI disk.
DISKPART> SELECT DISK n
DISKPART> ATTRIBUTES DISK CLEAR READONLY
DISKPART> ONLINE DISK
DISKPART> CONVERT GPT

It may take a reboot of the Hyper-V server to see the drive in Computer Management on your remote management PC.

http://technet.microsoft.com/en-us/library/ddb147c1-621c-4b89-9003-81c93ba050d7#BKMK_1_4

1. On the Windows 8 computer, start an MMC snap-in, such as Computer Management. (right-click Computer → Manage)
2. In the left pane, right-click the top of the tree and click Connect to another computer.
3. Type the computer name of the server that is in Server Core mode and click OK. You can now use the MMC snap-in to manage the Server Core server as you would any other computer running a Windows Server operating system.
4. On Windows 8 PC from Start just type hyper-v and choose Hyper-V Manager.
5. In the left pane right click on Hyper-V Manager and select “Connect to Server”.
6. Enter the Hostname or IP of server.
7. Right click the Hyper-V server name and select New, Virtual machine.