Booting Kace Boot Environment (KBE) inside Hyper-V VM is hit or miss.
When PXE booting our standard KBE (that works flawlessly on actual machines) inside of Hyper-V VMs, it works OK about twice out of 15 tries. When it does work, it works prefectly, just like it does on actual machines. But when it fails, it throws 8004100c errors when running certain WMI queries (such as the one inside kprintmac.vbs, for example) and nothing works from there. I'm at whits end as to what I could do to remedy the issue, especially since there are not many hits when Googling the above error code.
Does anyone have any suggestions? I've already added the Hyper-V integration drivers to the KBE, that did not make a difference.
Thanks,
Jonas
-
This worked for me on Server 2012 R2, although I had to use a generation 1 machine. You can always convert to a gen 2 or steal a gen 2's VHDX after creation. - shortman1400 10 years ago
Answers (1)
I may have found a solution, so I'll post here for anyone else's benefit: I had the VM set to use 2 CPUs, but moving it down to just 1 CPU allowed the KBE to boot properly each time. Not sure if it's an issue with the Hyper-V Server Beta, or the KBE, but as long as it works, I don't care :)
Comments:
-
That solved my issue, i was not able to capture an image of my Hyper-V VM via Kace KBE. i was using 2 processors and dynamic RAM. after changing down to One CPU, static RAM and Allow CPU migration to any machine option worked for me - skrishi 10 years ago
-
Sweet, thanks for confirming that this works! - SwissJay 10 years ago
-
I'd been struggling with this in Hyper-V for Windows 8.1. Your solution of using a single processor and not using dynamic RAM worked for me too. I wouldn't have thought of the single processor fix, because I'm using a 64bit KBE. Great post thanks! - bbaldrid 9 years ago