Host Windows Server 2016 standard OEM, 2 VM’s with 2016 standard OEM – cannot activate? 0xC004FD03

Can someone please explain the correct activation and rules for the VM’s.  With the standard edition you can not use AVMA, supposedly you use the same OEM key you activated on the host. When I try to use the key I got the 0xC004FD03 error. I used telephone
activation for the 1st VM. When I activated the Host I answered 1 computer, apparently you answer 0 for the first activation, 1 for the second (VM1) and 2 for the third (VM3). When I use 2 I get the error. BTW I did try the AVMA keys first before I tried the
OEM key. My OEM is useless and keeps telling me to use AVMA but I do not have  the datacenter version of windows server 2016 to use as the virtulization server. It seems that this problem is very common and Microsoft should clarify how to fix it! I have
seen some vage info that the OEM should supply keys or authorize guests but I have not been able to get this done. 

Thanks in advance for any help. 

Read full post . . . .

VM with disk on SMB3 share has good read but bad write speed

Hi All,

I’ve got a Hyper-V Node connected to a Windows FileServer (all Server 2016) via 2x10Gb on the node and 4x10Gb on the FileServer. 

During testing I’ve removed all NIC teaming with no effect but bot machines are doing multichannel as expected.

But when I now run CrystalDiskMark on the VM it shows up to 1800MB/S _read_ but only 150MB/R _write_.

This can be also watched on the network side as the FileServer NICs are not show much traffic during write.

Any Idea how I can track that down? Measured already Read/Write on the fileserver but this is good (RAID100 SSD with 6K MB read and 1k MB write).

If I just manually copy some files to the fileshare the transfer runs around 600MB/S.



Read full post . . . .

Hyper V- connecting to host drives

Hi all,

Just set up a windows 7 vm on windows 10 host. I am wondering since enhanced session mode is not available for my VM, what are my options to connect to host drives so I can access host usb-ports and printers?

Read full post . . . .

Cannot reconnect to VM once initial connection is closed

I have a windows 10 enterprise x64 (10.0.15063) hyper-v host and a windows 10 pro x64 (10.0.18362) hyper-v guest. Both run windows defender and no other anti-virus. All has been working
fine until today, I see this behaviour:

 - The guest starts up in the hyper-v console and I can connect using RDP or the built in window from the management console. All is good.

 - I can minimize the session and re-store, all is good.

 - If I close the remote desktop session then the vm is in a strange state. I cannot reconnect to it or shut it down, my only choice is to turn off the VM (!) then restart it and again and only then is it ok again. (I see this exact same behaviour when
connecting directly from the hyper-v console).

The only thing that I am aware of that’s changed is that a windows update ran on the guest (to get me to the version listed above).

Please let me know if this is a known issue or what I can check on the vm that could cause this?

Read full post . . . .

hyperv replica

Hi guys,

can someone please advise on how to configure hyper-v for replication between a cluster 2 nodes in mainsite and a standalone hyper-v in the DR site.


Read full post . . . .

Virtual Machines not utilizing NUMA Node


I have a dell R720 configured as a VDI virtualization host, hosting approximately 30 Windows 10 VMs. Specs are as follows:

Intel Xeon CPU E5-2650 v2 @ 2.60Ghz

2 sockets

16 cores

32 logocial processors

192GB Ram

The problem I’m facing is when assigning 32 vCPU to some of the virtual machines, the VM is not detecting the second NUMA Node and socket, and just uses the one, resulting in performance issues with startup times and CPU usage. 

When a VM has 32 logical processors assigned and is using 1 NUMA nodes and socket, I receive event ID 3056:

‘VM_NAME’ is configured to have a different non-uniform memory architecture (NUMA) topology to that of the physical machine. Some virtual processors are accessing memory on a remote NUMA node. This configuration is not recommended because it will reduce

There are some virtual machines that are able to use all numa nodes and doesn’t seem to generate the error, which is strange as the vms are using the same master image.

How can I set these vms to use all numa nodes and sockets when assigning 32 logical processors? I normally configure all vms with maximum virtual processors then adjust restriction in the VM settings.

Read full post . . . .

SSD RAID 6 Endurance


I’m planning to use Hyper-v cluster with SSD drives. However, I have some problems to get information what RAID level which I should set. The storage will be used for virtualization with some Database, Exchange and other servers (around 50). I was planning
to set RAID 6 but I worry about endurance as some people say it will wear twice faster than RAID 10. Other say RAID 6 is absolutely fine. Can somebody advise me if should I use RAID 6 or not?

Read full post . . . .

Tesla V100 – Hyper-V 2019 – device cannot find enough resources (code12) – MMIO config ?

I have a server HPE Proliant DL380 Gen10, 512GB RAM, with inside a Tesla V100-PCIE-32GB.
Windows Server 2019 is installed.
We have configured the Hyper-V role and installed a VM with 320GB RAM.

What we have done on the host is :
- Disabled the Tesla on the host.
- Set-VM -Name $VMName -AutomaticStopAction TurnOff
- Set-VM -LowMemoryMappedIoSpace 3Gb -VMName $VMName
- Set-VM -HighMemoryMappedIoSpace 33000Mb -VMName $VMName
- $locationPath = "PCIROOT(36)#PCI(0000)#PCI(0000)"
- Dismount-VMHostAssignableDevice -force -LocationPath $locationPath
- Add-VMAssignableDevice -LocationPath $locationPath -VMName $VMName

Unfortunately, each time the VM starts I have this error message in the device manager :
This device cannot find enough free resources that it can use. (Code 12)
If you want to use this device, you will need to disable one of the other devices on this system.

I have tried to change the MMIO to
3GB / 33000MB
2GB / 4GB (found on a blog but for Grid cards)
176Mb / 560Mb -> because the MS script listed the card as :
Express Endpoint — more secure.
And its interrupts are message-based, assignment can work.
And it requires at least: 48 MB of MMIO gap space
So I added 48 to the 128Mb / 512Mb from the default configuration.

When changing the MMIO config, do I need to remove the card from the VM, change the config and reconnect the card to the VM or can I just change the config without doing anything to the VM ?

No MMIO configuration solve the problem.
Can someone please help me ?

Thanks in advance for your help.


Read full post . . . .

Do not save Hyper-v data

Guys, I would like not to save data on the virtual machine, but whenever I turn it off, it saves everything, how not to save?

Read full post . . . .

Windows Server Backup with Hyper-V

I’m trying to use Windows Server Backup on a Windows Server 2019 Standard with Hyper-V, but it gives me errors.

This is the message from Windows Server Backup:
"Backup succeeded but some components backed up were inconsistent in the snapshot. The application this component belongs to might not function properly after this backup is used for recovery."

And this is the message I get in Event Viewer for each VM that is online during the backup:
"VSS writers inside virtual machine ‘*****’ failed to perform BackupComplete to its shadow copy (VSS snapshot) set: A function call was made when the object was in an incorrect state for that function (0x80042301)."

Any suggestion on how to use Windows Server Backup for our Hyper-V VMs?

Read full post . . . .

Go Que Newsroom Categories

Fatal error: Allowed memory size of 67108864 bytes exhausted (tried to allocate 36 bytes) in /home/content/36/8658336/html/goquecom/wp-includes/taxonomy.php on line 3361