Hyper -V encountered an error while configuring the network on XP Virtual Machine.
Hyper-V encountered an error while trying to access an object on computer xxxxxxxx because the object was not found............1 vote
I am running into the issue of Windows 10 having Config 8.2 and my Server 2016 Config 8.0. Running Windows Updates so far has not yielded the needed 8.2
I often create my VMs on Windows 10, export and bring them up on Server. This is only going to get worst. Let's fix it right away.
An option could be offered also to export to specific version, of course a warning that capabilities will be lost. Only makes sense.1 vote
I run CentOS 7 and RHEL 7 virtual machines on a Hyper-V Server 2016.
Virtual TPMs in the VMs somehow worked, at least as entropy sources, before June 2017 Patch Tuesday. After I've applied the latest cumulative patch every TPM got broken on the next VM restart.
The bug is a regression between 14393.1230 and 14393.1358.
(I've downgraded and everything seems fine now.)2 votes
Hi You have a mistake on the bottom of the "Resume-VMReplication" website(japan version). The last example for resuming replication for all the VMs are wrong. It should be "resume-VMreplication *" instead of "Resume-Replication *"1 vote
How about we can manage remote Hyper-V host running on Server 2012 R2. All I get is error:
"The class Msvm_RegisteredProfile does not exist in the root/interop namespace"
Issue described here:
Please finally allow physical com port redirection to a virtual machine. I know this would limit high availability of the virtual machine but sadly some applications/hardware still require com port communications.10 votes
- Don't see your idea?