Hyper-V is a native hypervisor; it can create virtual machines on x86-64 systems and supersedes Windows Virtual PC as the hardware virtualization component of the client editions of Windows NT. A server computer running Hyper-V can be configured to expose individual virtual machines to one or more networks. Hyper-V Server supports remote access via Remote Desktop Connection. Administration and configuration of the host OS and the guest virtual machines is generally done over the network.

Share tech news, updates, or what's on your mind.

Sign up to Post

I have recently purchased the following
Synology DS1817 NAS (not the + version, this version has 2 x built in 10GB NIC's & 2 x 1GB NIC's)
2 x Intel X540-T2 NIC's
1 x DLink DXS-1210-10TS 10GB switch

I installed the 2 x  X540-T2 in our Windows 2012r2 Hyper-V host. Each card has two ports. I have configured
all 4 ports as a team and connected each to the DLink DXS switch. All 4 connections are 10GB as expected - perfect!

Connecting the Synology DS1817 NAS I only get a 1GB connection. Local 2m CAT6 cable.

I raised a support case with Synology. Synology support got me to connect the 2 x 10GB NIC's together with a CAT6 patch lead
and connect the NAS to the DLink switch via one of the 1GB ports. Synology confirmed that the were getting 10GB communications
between the 2 x 10GB and concluded that the issue lay "somewhere else" on the network!

I have used tested 2m CAT6 cables from both 10GB NIC's to the Dlink DXS switch - both connect at 1GB
If I set the switch ports to 10GB I loose communication with the NAS.
All ports on the DXS are 10GB.

Anyone have any idea why, if the Synology DS1817 NAS is working correctly, I am not getting a 10GB connection to the DXS10 switch?
Thanks in advance

On my Windows 10 Pro OS laptop I created a Server 2016 Hyper-V virtual machine.

I shut down this Server 2016 VM within the OS using the shutdown -s -f -t 0 command.

For the last hour, this VM has remained stuck and says "Stopping" within the Hyper-V Manager. This VM already had all of the Windows updates installed.

I don't have the option to stop or shut down this VM and when I open this VM I only get a blank screen.

I have already shut down the Windows 10 Pro host OS but when I have booted Windows 10 back up and opened the Hyper-V Manager the Server 2016 VMis still in its same state.

What command line or PowerShell commands can I use to force the shutdown of this Server 2016 VM?

Or what else can I do to completely shut down this Server 2016 VM?

S2016DC Hyper-V VM stuck
I have server hp ml10 g9 with windows 2016 with Hyper-V and I have a mikrotik 951
I set the server to shutdown everyday @6pm
 I set a mikrotik to wake on lan script on 8am

the problem that is the windows 2016 not support wol on s5 state
its only on s4 and s3
regarding hp:
Press Win + x, select Run and type regedit in the run line.
Select OK to launch the Registry Editor.
Navigate to KEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\NDIS\Parameters.
Right click on Parameters.
Select New DWORD (32-bit) Value.
Add the key AllowWakeFromS5.
Set the value to 1.
Close the Registry Editor.
Restart the computer.
but it's not work too I have last bios update and I enable wake on lan via bios.
any solution for that ?
Hyper-V 2012R2 VM acting as DC with PDC role always comes back to CMOS clock source after reboot.  Takes W32TM /RESYNC command to get clock source back to NTP and external where it will run fine again until the next reboot.

Hyper-V Host is Server 2016 with Time Integration service NOT checked.
Currently ,I have a following infrastructure

One physical server (2012 R2) which is  Configured as a Domain Controller.Also, It contain only a C drive and all file shares running on my  C drive DATA folder.
All files and folders in Shared drives  that are shared with groups and individuals where needed.
All the shared folders  has extensive share permissions definedI bought a new server(server 2016) and planning to creat a Hyper-V host.Then planning to create a DC and file server.
All shared folder mapped to users through GPO's

1)What's the easiest way migrate a physical DC to Hyper-v VM (same Domain Name)?

2)What's the easiest way to copy all the shared DATA folder to new file server ?
Planning implement new Hyper-V server with 4 vm's.
I bought a 4 bay Server which has 3.5" 600GB 15K SAS 12Gb Hot Swap 512n HDD with raid 5.
Also, this has M.2 CV3 128GB SATA 6Gbps Non-Hot Swap SSD.
Planning to install Host OS (server 2016) on M2 SATA SSD .
I am going to use the 3.5" 600GB 15K SAS 12Gb Hot Swap 512n HDD with raid 5 for VM's storage.
Host server only going to have the hyper-v role.
1) I just wanted to find out whether 128GB is sufficient for HOST OS ?(capacity)
2) 3.5" 600GB 15K SAS 12Gb Hot Swap 512n HDD with raid 5 is ok to store all my VM's ?(performance vise)
2) Performance vise RAM 16GB X4 TruDDR4 2666 MHz (1Rx4 1.2V) RDIMM sufficient to implement Hyper-V hypervisor
I have cisco slm224g switch
I have a windows server 2016 with Hyper-V rule
I have three vlans 2, 3
Hyper-V on port 1
adsl router on port 2
client work station on port 3
on Hyper-V I have a pfsense as vm with two network interface the first one with vlan id =2 and the second one vlan id=3 on the same interface.
I want to assign client ,Hyper-V to vlan 2 and should connect over port 1 to first interface on Hyper-V
I want to assign adsl router to vlan3 and should connect  over port 1 to second interface on Hyper-V
regarding above:
port 1 should be trunk  for vlan id 2,3
port 2 should be access to vlan 3
and port 3 should be access as vlan 2
I tried that but it's not working so what the basic configuration for that ?
HyperV ManagerSnapshotVMs paused-Critical stateHi,Virtual Hard Disk FolderVM stuck during shutdownOptions under Action menu
 I accidently created a snapshot on the VM "FT1" and there are two problems:
(1) Every so many seconds, when I open this VM in Hyper-V manager, it goes to "pause" state showing the screen in shaded color. When I start it, it goes back to shaded/pause  state.
(2) Now I am getting "Out of Disk" message on my Hyper-V server.

I did not intend to create a snapshot at all. I was expecting a snapshot manager screen as I chose "snapshot". But I think it is trying to create a snapshot and the server ran out of space. It seems that the logical thing to do is to cancel "snapshot creation process" because there is no hard drive space for the snapshot to be created in the first place, delete the temporary file "FT1_2481848F-1B1E-4667-A1A2-985A4E532138.avhdx"(18.9GB), and restart the "FT1" VM.

What should I do?

** I forgot to mention that I was trying to shut down the VM, but that is even stuck.
I'm running Hyper-v in a 2012 R2 cluster.  (Note: this is NOT SCVMM)
I'm trying to get a list of all the VMs currently running on the Host I'm logged into and their respective possible owners. i.e. which cluster nodes they could potentially migrate to.  The reason is that I THEN want to set those VMs to only run on that particular host for patching purposes.  Once done I'll want to reverse it so the VMs can once again migrate when needed.  Here is the code and attendant error message.  I'm hoping someone can assist me with achieving my goal or at least point me in the right direction.

$VMs = get-vm
foreach ($vm in $vms)
	get-clusterresource -vmid "$VM.vmid" | get-clusterownernode

Open in new window

The error I am getting is:

Get-ClusterResource : Cannot bind parameter 'VMId'. Cannot convert value "Microsoft.HyperV.PowerShell.VirtualMachine.vmid" to type "System.Guid". Error: "Guid should contain 32 digits with 4 dashes (xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx)."
At line:1 char:50
+ foreach ($vm in $vms) {get-clusterresource -vmid "$vm.vmid" | get-clusterownerno ...
+                                                  ~~~~~~~~~~
    + CategoryInfo          : InvalidArgument: (:) [Get-ClusterResource], ParameterBindingException
    + FullyQualifiedErrorId : CannotConvertArgumentNoMessage,Microsoft.FailoverClusters.PowerShell.GetResourceCommand
Hello I've got a Virtual Machine which will not shutdown.  I've tried from Hyper-V Manager (Right Click, Shut Down).   It will not shutdown every-time get the following error:
"An error occurred while attempting to shutdown the virtual machine."
"Failed to stop"

Info is as follows:
Host = Dell Precision 7710, running Windows 10
Guest in question running Red Enterprise Edition

Not sure what to try.
Quick Backup of windows 2016 hyper-v server.

Can I just shut down hyper-v server . Then to copy vhdx file to a usb?
Hey all,

I have just taken over a site and one of the critical servers (VM1) is running out of disk space on the C:Drive. Host is running Hyper-V with plenty of space for allocating extra stroage to VM1. The weird thing is that when I look the Disk management within the VM, it shows that there is space that hasn't been allocated. It also has a replica of free unallocated space on the D:Drive which is very odd.

I would ideally  like to just expand the C:Drive - is this safe to do so knowing I have good backups also?
 I have a test Hyper-V Server 2016 and installed Windows 2012 Server for in-place upgrade testing purposes.
 So I opened the virtual machine settings for Win2012 and performed the following:
1. changed the ISO file to Win2012R2.iso.
2. Start the VM and pressed [F8] key and got to Windows 2012R2 setup menu.
3. Clicked "Install" and I tried both "Upgrade" and "Custom" option.
    - "Upgrade" option did not do anything except I saw the message saying that I have to restart the computer.
    - "Custom" option said it was going to put old stuff in "Windows.old" folder. After customer upgrade, a brand new OS was created with Windows 2012R2. It was not an upgrade from Windows 2012.

 Having said that, this was not what I expected.
 How can I perform in-place upgrade to a newer server OS while keeping programs, files, computer name, IP information ... etc?
I have a Hyper-V Server 2016 setup (the free one).  I experienced a system failure and have to rebuild.  How do I create a system image backup for disaster recovery that I can use when I boot up to the server setup and choose system recovery image?  All the information I can find expects a full Windows server install with GUI.
I have a Single physical DC (2012R2) and need to convert this to Hyper-v VM.
Since the server is 2 years old and planning to use the same server as Hyper-v host.
I just wanted to find out the best practice to convert physical DC to VM.
I am trying to verify some AWS prerequisites for Server Migration.  Could someone help me with the following 3 prerequisites listed below.   specifically:

a) verify if the following prerequisite connections are allowed
b) if they are blocked, how to open the requested ports in the fortigate

1)  DNS—Allow the connector ( to initiate connections to port 53 for name resolution.

 2)  HTTPS on WinRM port 5986 on your SCVMM or standalone Hyper-V host

 3)  Inbound HTTPS on port 443 of the connector ( —Allow the connector to receive secure web connections on port 443 from Hyper-V hosts containing the VMs you intend to migrate.
I am trying to reset Disk identifier on one of my hyper-v virtual disks.  AWS support tells me that there is no identifier, and this is preventing me from migrating the virtual disk to the AWS cloud.

I am using the following PS:
 Set-VHD -Path "M:\VMs\Virtual Hard Disks\NC-LBL.vhdx" -ResetDiskIdentifier[1]

I get the following error:

A positional parameter cannot be found that matches parameter name 'ResetDiskIdentifier'

CategoryInfo : InvalidArgument: (:) [Set-VHD], ParameterBindingException
FullyQualifiedErrorID : NamedParameterNotFound, Microsoft.vhd.powershell.setvhdcommand

Could someone assist me with the error?
Hi All,

I have a dilemma and wanted to get some feedback.

We have some Hyper-V server hosts that are lease is up and management is sending them back to Dell and a new Hyper-V server is being built as we speak.

The issue I am most concerned about is that the FSMO role holder virtual is on the Hyper V host that is going back.
This VM is currently backed up daily with VEEAM.

Here are the options for moving and or removing this server off of our host that is going back and not taking down our whole Active Directory.

1. Move FSMO roles to Physical 2016 DC, and move DC to new server and import into new host.
2. Restore Virtual to new host with VEEAM. ( I am concerned with different versions of Hyper V backing up and restoring too)
3. Demote the DC all together after transferring FSMO roles and rebuild new DC on new host.

The reason we use a virtual is because of back up.  I back up the physical DC but only C drive and system state.  VEEAM backs up the whole DC.

Any thoughts or new suggestions are appreciated.

Thank you,

I have a server 2012 running hyper-v with guests.  It has two nics.  I also have two networks with 2 routers each with static IPs.

I want to use one nic for the guests and the other nic for the host OS.  I don't want the networks to see each other. Reason being, one network (hyper-v guests) will be public facing (website and game servers) while the other network (host) will be used for personal purposes in my home network.  

How can I do this?

Note: I know how to assign a guest to a specific nic but my concern is the host server being on both networks.  I know that the OS will default to the first nic it loads, but since the second nic still gets an IP, my worry is security from that second network, even if it is not activly using it.
Windows Server 2016 Fail over Cluster Manager

Cluster Event Log:
Cluster resources " Virtual Machine APP01 of type Virtual Machine in Clustered Role "APP01" failed.

Based on the failure policies for the resources and role, the cluster service may try to bring the resource online on this node or move the group to another node of the cluster and then restart it. Check the resources and group state using Failover Cluster Manager or the Get-Cluster-Resources Windows PowerShell cmdlet.

Event ID : 1069

Any idea usually what causing this ?  it kind a generic for me
Hi Guys,

We have 2 Server 2016 Hyper-V hosts in our environment, when we try to checkpoint the VM's on the hosts we get the error "The operation cannot be performed while the object is in use" and the following from the logs. "SERVER**' background disk merge failed to complete: The process cannot access the file because it is being used by another process. (0x80070020). (Virtual machine ID E33D1EB8-D888-4CE8-9100-891EA98C566C)

The checkpoints work when the host is restarted but it just fails again, obviouslt this is also affecting the backups.

Anyone else come accross this?

I have a small 2 host HyperV cluster with about 4 VMs on each host.    When we go in to do our monthly updates, we dont want the machines to move.   We do them very hands-on.   We patch all 8 VMs.   Then we shut down or suspend the VMs and do the hosts.     No matter what we try including shutting all VMs down, HyperV moves the VMs to the host that is up.   How can we temporarily suspend the automated movement of these VMs?  

Have 6 2016 host servers for Hyper-V HA Cluster configuration. 2 hosts will run 2 DC, 2 RDS Brokers, 2 APP servers. The other 4 hosts will be running 3 to 4 VM RDS Session Hosts VMs per device.
I envisioned these physical servers as 2 clusters. One for the 2 hosts for the DC,RDS Broker, APP servers and the second for the 4 VM RDS Session hosts.

Probably more of an opinion - anyone note pros and cons of having two separate clusters or one cluster for all. Data/Shares and VM images will be on a NAS.

I've always used Oracle VM Virtual Box for my VM needs to keep copies of Windows operating systems (from 98SE up) available to me, as well as a couple of Linux distros. But I often see questions (and articles) on Experts Exchange that deal with Microsoft Hyper-V and it's got me to wondering if I'm doing myself a dis-service somehow by not using it, rather than the Oracle VM solution.

Are there any experts who have experience with both that can identify the pros and cons of using the Microsoft solution as opposed to Oracle VM or vice versa? I have Windows 10 Pro so Hyper-V is available to me.

I've looked at a number of Microsoft articles about Hyper-V to try and work out the difference, but they've been of little help to satisfy my curiosity.

Your opinions about both solutions would be appreciated.

Regards, Andrew
Very long story short: I am trying to manually migrate a hyper-v server to AWS ec-2 without using SMS.

I am copying the vhdx virtual disk as I type.  I plan to use the CLI to import the image into an new instance.  My question is, can I also somehow integrate the xml file from hyper-v manager to copy the config of the vm?  Or should I re-define the vm instance in E2 with a fresh start?  If I do the latter, will it affect any of the windows drivers?(maybe dumb question)


Hyper-V is a native hypervisor; it can create virtual machines on x86-64 systems and supersedes Windows Virtual PC as the hardware virtualization component of the client editions of Windows NT. A server computer running Hyper-V can be configured to expose individual virtual machines to one or more networks. Hyper-V Server supports remote access via Remote Desktop Connection. Administration and configuration of the host OS and the guest virtual machines is generally done over the network.