Logical switch configuration to the host. All seemed to be working until I tried to apply a Some things worked but most reconfigurations via VMM would fail or behave as completed but changes never made. Machine manage running jobs on that particular host. I am thinking maybe a feature that isn't installed? I am going to dig deeper today as to why I can connect to the one, but not the others.īeware if you run “MOFCOMP %SYSTEMROOT%\System32\WindowsVirtualization.V2.mof” it does fix the issue but afterwards you will have issues with System center virtual The one is on older hardware, but the same exact OS build. As I said, I can connect to one, just not the other five. So, people have been able to successfully connect to 2012 servers. In addition to pages like this saying it can be done, I have seen other forums where users mention, "I can connect to my 2012 Hyper-V servers, but why can't I connect to my 2008 R2 Hyper-V servers." The responses to these have been exactly
However, the alternate credential capability is only for Windows 10 instances alternate credentials can't be used with older Hyper-V servers that don't use WS-MAN. Which is possible because of its shift to WS-MAN for configuration. In addition, it provides the ability to use alternate credentials, Q: I'm using Windows 10 Hyper-V Manager with an older Hyper-V server, but using alternate credentials isn't working why not?Ī: The new Hyper-V Manager in Windows 10 has several nice features, including the ability to manage down-level Hyper-V servers such as I am seeing the reference to Windows 10 managing 2012 in many places, but here is the first one I found again just this morning: The key thing is, Windows 10 "should be" compatibleĪnd whilst you may have some success, it is a bit of slog and definitely not pretty. Yes, it could still work, but it is no longer the basis for authorizing actions to users. That was technically deprecated with 2012 R2 when Hyper-V moved away from using Authorization Manager. There are other management consoles that still used dcom, but Hyper-V is not one. Since the Hyper-V Manager is all about using WMI and the virtualization namespace.
I am curious where you got the impression that Windows 10 Hyper-V Manager can manage Windows 8.1 / 2012 R2 Hyper-V.įrom a namespace standpoint it should work, but there will be some features that don't align. Historically the version of the management tools must match the release of the target system being managed. If I understand correctly, you are running Hyper-V from a 2012 R2 Server Datacenter installation and using Windows 10 to do the actual management?īrian Elhert makes an excellent comment, related to Hyper-V Server, but it's quite applicable to Hyper-V on the Windows Server platform (for the time being - this may change when Win 10 is released into the wilds of the marketplace).
MOFCOMP %SYSTEMROOT%\System32\WindowsVirtualization.V2.mof
I would appreciate any help anybody can offer.ĮDIT: Just to have the solution at the top of the thread, thanks to BrianEh below, the WMI namespace became corrupted due to an HP software update. I realize Windows 10 has not officially been released yet, butĪ few of us are testing the waters for compatibility issues. Any ideas why this is not working? Several Google searches have not told me anything so far. I am not trying to use alternate credentials (I read this will NOT work from 10 to 2012 R2). I am reading that Windows 10 should be backward-compatible with managing Hyper-V on 2012, but on connection, it appears a WMI namespace is missing that the Windows 10 tools are trying to connect to. Windows updates maybe? I migrated all the VMs off one of the servers I cannot manage remotely, performed all Windows Updates, I cannot figure out what is different on this one server from the other five. The strange thing is that I CAN connect to one of them. Into an issue connecting to the servers now. I got ahold of Windows 10 build 10240, and I am running I have been managing these from my Windows 8.1 machine with no issues. All six were installed from the same Server 2012 R2 Datacenter ISO.
In this section, a client version of Windows is a version that end-users or OEMs can install on personal computers, including desktop computers, laptops, and workstations.So, we have a total of six Hyper-V servers in our environment.