Tag Archive: hyper-v

Tips and tricks to manage Hyper-V server remotely from another computer in a workgroup:

In that example, the server and the client are in a workgroup. As a consequence there is no domain controller and by consequence kerberos is not possible. How to remotely manage hyper-V server from this client computer?

Reference article:


Configuration steps:

Both computers must be in the member of the same WORKGROUP

Both computers must have the same local username/password. And it must be member of local administrators group.

Create a local user to manage the hyperV service and put this account member of hyper-V administrators. On the client computer create also the same account with the same password.

Both computers must have the same time/date ; you can use net time \\server /set /y to synchronize the time

On hyper-V server:

On the server BIOS, enable the Virtualization support (CPU settings):

How to check if hyper-V hypervisor is running: https://technet.microsoft.com/en-us/library/ee941154(v=ws.10).aspx

RAID:  It is recommended to create the RAID using the Storage array directly on the server (at the boot time, by entering the Raid adapter tool). But to manage the hyperV storage remotely from the client (using Computer management “compmgmt.msc”): https://blogs.technet.microsoft.com/wincat/2012/05/02/what-needs-to-be-configured-to-do-remote-disk-management-of-a-server-core-installation-in-windows-server-2012-via-powershell/

Other article: https://www.pandatech.co/2015/04/remote-disk-management-on-windows-server-2012-core/

From a command line on the server start: SCONFIG

a.      Set Computer Name

b.      Joined Domain

c.      Set Network settings

d.      Downloaded updates

e.      Enable Remote Management   ( or from powershell: enable-PSRemoting)

f.      Enable RDP

g.      Enable Ping

h.      Telemetry Settings = security

2.      View Firewall Rules PowerShell

a.      Get-netfirewallrule | format-table name, displaygroup, action, direction, enabled -autosize

3.      Ran powershell: enable-netfirewallrule -DisplayGroup “File and Printer Sharing”

5.      Powershell: enable-netfirewallrule -DisplayGroup “Remote Event Log Management”

6.      Powershell: enable-netfirewallrule -DisplayGroup “Remote Volume Management”

7.      Powershell: enable-netfirewallrule -DisplayGroup “Remote Service Management”

8.      Cmd: netsh advfirewall firewall set rule group = “Windows Firewall Remote Management” new enable=yes

9.      winrm s winrm/config/client “@{TrustedHosts=”client”}”

10.      Set Virtual Disk Service to Auto Start and start it



On client computer (management computer):

1. Test to ping the hyper-V server (and vice versa)

2. Install the HyperV management tools and the management stack

3. On powershell: enable-PSremoting

4. allow Windows remote managenent: winrm s winrm/config/client “@{TrustedHosts=”server”}”

5. netsh advfirewall firewall set rule group=”Remote Volume Management” new enable=yes


6. DCOM configuration on client computer:

Open c:\windows\system32\dcomcnfg.exe, expand My Computer, properties, Security tab and allow ‘anonymous logon’ for local and remote access.







Did you know that you can virtualize your Windows Server 2016 Essentials? Instead of hacking into Windows Server Essentials itself and using that as a Hyper-V host we go ahead and do it the official way and download Microsoft Hyper-V Server 2016 for free. Some administrators don’t like a server without a GUI (server core) but it has a lot of benefits compared to a full blown server with the GUI and roles installed.

  • It requires less resources.
  • It is more secure because the attack surface is smaller.
  • Reduced management.
  • Requires much less updates from Windows Update so less reboots needed.

For managing the Server Core with Hyper-V only we use a normal workstation with Windows 10 + RSAT (Remote Server Administration Tools). OK, admitted it is a little bit more complicated but it outweighs the benefits!

If you want to learn more Hyper-V Server 2016 I suggest What’s new in Hyper-V on Windows Server 2016 at Technet. Probably most important new feature is Windows PowerShell Direct. This allows you to run Windows PowerShell commands in a virtual machine from the host without an actual network connection. More reading here Manage Windows virtual machines with PowerShell Direct

MS technet articles:

Understanding virtual networks: http://blogs.technet.com/b/jhoward/archive/2008/06/17/hyper-v-what-are-the-uses-for-different-types-of-virtual-networks.aspx

LAN teaming and hyperV: http://www.msserverpro.com/configuring-windows-server-2012-nic-teaming-to-a-hyper-v-virtual-machine/

Network recommendations for hyperV cluster in Windows Server 2012: http://technet.microsoft.com/en-us/library/dn550728.aspx#BKMK_NICTeam

Using Hyper-V and Failover Clustering: http://technet.microsoft.com/en-us/library/cc732181%28v=ws.10%29.aspx

Adding and Managing Hyper-V Hosts in VMM: http://technet.microsoft.com/en-us/library/gg610671.aspx

Creating and Modifying Hyper-V Host Clusters in VMM: http://technet.microsoft.com/en-us/library/gg610621.aspx

Study Guide:



Use cases:

http://www.aidanfinn.com/?p=10311 <=== read first !





hyperv R3 et la replication: http://amaugard.wordpress.com/2012/08/30/hyper-v-r3-et-la-replication/