Trying to set up Hyper-V Server 2016, ripping my hair out
-
Additional info:
On my Windows 10 system, I've enabled ONLY the Hyper-V Management Tools, and not the Hyper-V Platform.
My domain user account I use on this Windows 10 system is not a local admin, just a regular low priveleged user. However, I have tried running the Hyper-V Manager as admin and put in the credentials of the domain user that I also assigned as my Hyper-V server admin. When I go that route, I get the error:
"<< Failed to connect to server "<Computerame>". Make sure the administrative service
Is running on virtual machines and you are authorized to connect to the server.
The Hyper-V administration tools did not allow access to an expected WMI class on computer "<Computerame>".
This may indicate that the Hyper-V platform is not installed on the computer or that is the version of the Hyper-V platform
Hyper-V platform is not compatible with these management tools" -
@dave247 said in Trying to set up Hyper-V Server 2016, ripping my hair out:
Additional info:
On my Windows 10 system, I've enabled ONLY the Hyper-V Management Tools, and not the Hyper-V Platform.
My domain user account I use on this Windows 10 system is not a local admin, just a regular low priveleged user. However, I have tried running the Hyper-V Manager as admin and put in the credentials of the domain user that I also assigned as my Hyper-V server admin. When I go that route, I get the error:
"<< Failed to connect to server "<Computerame>". Make sure the administrative service
Is running on virtual machines and you are authorized to connect to the server.
The Hyper-V administration tools did not allow access to an expected WMI class on computer "<Computerame>".
This may indicate that the Hyper-V platform is not installed on the computer or that is the version of the Hyper-V platform
Hyper-V platform is not compatible with these management tools"Have you confirmed that you can connect with a domain admin account? At least with that you can confirm its an permission issue?
-
@black3dynamite said in Trying to set up Hyper-V Server 2016, ripping my hair out:
@dave247 said in Trying to set up Hyper-V Server 2016, ripping my hair out:
Additional info:
On my Windows 10 system, I've enabled ONLY the Hyper-V Management Tools, and not the Hyper-V Platform.
My domain user account I use on this Windows 10 system is not a local admin, just a regular low priveleged user. However, I have tried running the Hyper-V Manager as admin and put in the credentials of the domain user that I also assigned as my Hyper-V server admin. When I go that route, I get the error:
"<< Failed to connect to server "<Computerame>". Make sure the administrative service
Is running on virtual machines and you are authorized to connect to the server.
The Hyper-V administration tools did not allow access to an expected WMI class on computer "<Computerame>".
This may indicate that the Hyper-V platform is not installed on the computer or that is the version of the Hyper-V platform
Hyper-V platform is not compatible with these management tools"Have you confirmed that you can connect with a domain admin account? At least with that you can confirm its an permission issue?
Yes I've tried with a DA account but no dice.
@black3dynamite said in Trying to set up Hyper-V Server 2016, ripping my hair out:
@dave247 said in Trying to set up Hyper-V Server 2016, ripping my hair out:
Additional info:
On my Windows 10 system, I've enabled ONLY the Hyper-V Management Tools, and not the Hyper-V Platform.
My domain user account I use on this Windows 10 system is not a local admin, just a regular low priveleged user. However, I have tried running the Hyper-V Manager as admin and put in the credentials of the domain user that I also assigned as my Hyper-V server admin. When I go that route, I get the error:
"<< Failed to connect to server "<Computerame>". Make sure the administrative service
Is running on virtual machines and you are authorized to connect to the server.
The Hyper-V administration tools did not allow access to an expected WMI class on computer "<Computerame>".
This may indicate that the Hyper-V platform is not installed on the computer or that is the version of the Hyper-V platform
Hyper-V platform is not compatible with these management tools"Have you confirmed that you can connect with a domain admin account? At least with that you can confirm its an permission issue?
Yes I've tried with a DA account but no dice. I can log in directly to the hyper-v server with the da account but not through the hyper-v manager on my Windows 10 system.
-
What error are you getting?
-
@tim_g said in Trying to set up Hyper-V Server 2016, ripping my hair out:
What error are you getting?
This is the main error I'm getting now: "<< Failed to connect to server "<Computerame>". Make sure the administrative service is running on virtual machines and you are authorized to connect to the server.
The Hyper-V administration tools did not allow access to an expected WMI class on computer "<Computerame>".
This may indicate that the Hyper-V platform is not installed on the computer or that is the version of the Hyper-V platform
Hyper-V platform is not compatible with these management tools"Also, I am getting,
"Enable delegation of user credentials? This computer is not configured to allow delegation of user credentials. Do you want to allow delegation of user credentials to HV01.domain.com?"
I have enabled remote management and added a domain admin as a local administrator to see if I could connect from my Windows 10 management computer. I just can't get in.
Screenshot of my console:
I also tried running these Powershell commands as admin and I still can't connect. I don't really understand the error messages:
Also, I have also attempted to install RSAT on my Windows 10 computer but still no luck.
-
At this point, I'm considering trying out XenServer..
-
I just don’t recall having any issue with connecting to Hyper-V 2016 when both server and workstation is on the same domain.
The issue you are having makes sense if the server is not on a domain.
-
Have you already checked the links that was provided to you?
-
@dave247 said in Trying to set up Hyper-V Server 2016, ripping my hair out:
At this point, I'm considering trying out XenServer..
Look at KVM instead. There was something on here the other day about XenServer lol
-
@black3dynamite said in Trying to set up Hyper-V Server 2016, ripping my hair out:
I just don’t recall having any issue with connecting to Hyper-V 2016 when both server and workstation is on the same domain.
The issue you are having makes sense if the server is not on a domain.
That is something to look for, @dave247 if you go to \servername\c$ and enter the server credentials and open the administrative share. Then now attempt to connect to the server, are you able to.
Also what problems are you having installing RSAT and what Windows 10 version do you have?
-
@dave247 said in Trying to set up Hyper-V Server 2016, ripping my hair out:
At this point, I'm considering trying out XenServer..
Don't, it's a dead project. Try KVM.
-
@black3dynamite said in Trying to set up Hyper-V Server 2016, ripping my hair out:
I just don’t recall having any issue with connecting to Hyper-V 2016 when both server and workstation is on the same domain.
The issue you are having makes sense if the server is not on a domain.
Well they are in fact on the same domain and yes I have looked at all the links and taken all the steps that apply. I have joined HV01 to the domain and I see it listed in AD as a computer and I have dropped it in the "Servers" OU.
-
@dbeato said in Trying to set up Hyper-V Server 2016, ripping my hair out:
@black3dynamite said in Trying to set up Hyper-V Server 2016, ripping my hair out:
I just don’t recall having any issue with connecting to Hyper-V 2016 when both server and workstation is on the same domain.
The issue you are having makes sense if the server is not on a domain.
That is something to look for, @dave247 if you go to \servername\c$ and enter the server credentials and open the administrative share. Then now attempt to connect to the server, are you able to.
Also what problems are you having installing RSAT and what Windows 10 version do you have?
Yes, I am able to get right into the C$ no problem. I still can't connect via Hyper-V Manager in Windows 10.
My Windows 10 info:
- Windows 10 Pro
- Version: 1703
- OS Build: 15063.726
-
That's just so weird, these problems you are having.
If I list a group policy setting, would you be able to apply it to HV01 and your desktop?
-
@tim_g said in Trying to set up Hyper-V Server 2016, ripping my hair out:
That's just so weird, these problems you are having.
If I list a group policy setting, would you be able to apply it to HV01 and your desktop?
Yes, I know, very very frustrating. I actually just got done completely re-installing Hyper-V server 2016 just to go through all the steps again to see if I missed anything. It's now set up and joined to the domain again and I am able to RDP in as the domain user, but still I can not connect to it via the Hyper-V Manager in Windows 10. I get this error when I specify the proper user to connect with:
And I have applied this GPO to my system:
-
@hobbit666 said in Trying to set up Hyper-V Server 2016, ripping my hair out:
@dave247 said in Trying to set up Hyper-V Server 2016, ripping my hair out:
At this point, I'm considering trying out XenServer..
Look at KVM instead. There was something on here the other day about XenServer lol
The discussion was about Amazon moving from Xen (not XenServer) to KVM because of there G5 instances.
-
I don't think the problem is HV01.
If you have just done a fresh install, joined it to the domain, and enabled remote management... you're good on that end.
Now on your Win10 computer, if you are logged in as a Domain Admin, you shouldn't have any trouble accessing it via Hyper-V Managaer.
You can try running
Enable-PSRemotingon your Win10 computer, I think #4 on the Hyper-V host does the same thing, which looks like it's already done. -
@tim_g said in Trying to set up Hyper-V Server 2016, ripping my hair out:
I don't think the problem is HV01.
If you have just done a fresh install, joined it to the domain, and enabled remote management... you're good on that end.
Now on your Win10 computer, if you are logged in as a Domain Admin, you shouldn't have any trouble accessing it via Hyper-V Managaer.
You can try running
Enable-PSRemotingon your Win10 computer, I think #4 on the Hyper-V host does the same thing, which looks like it's already done.I have not logged in as a domain admin on my Windows 10 workstation however I have tried running the hyper-v manager as an administrator and use the domain admin credentials for that. I thought it didn't matter if I was logged into my workstation as a domain admin, and I wouldn't want to be doing that anyways in a normal environment, and running hyper-v as admin seem like the reasonable alternative. I can still give it a try though. EDIT: I tried it and it still doesn't work.
I have already run Enable-PSRemoting on both systems.
-
@dave247 said in Trying to set up Hyper-V Server 2016, ripping my hair out:
@tim_g said in Trying to set up Hyper-V Server 2016, ripping my hair out:
I don't think the problem is HV01.
If you have just done a fresh install, joined it to the domain, and enabled remote management... you're good on that end.
Now on your Win10 computer, if you are logged in as a Domain Admin, you shouldn't have any trouble accessing it via Hyper-V Managaer.
You can try running
Enable-PSRemotingon your Win10 computer, I think #4 on the Hyper-V host does the same thing, which looks like it's already done.I have not logged in as a domain admin on my Windows 10 workstation however I have tried running the hyper-v manager as an administrator and use the domain admin credentials for that. I thought it didn't matter if I was logged into my workstation as a domain admin, and I wouldn't want to be doing that anyways in a normal environment, and running hyper-v as admin seem like the reasonable alternative. I can still give it a try though. EDIT: I tried it and it still doesn't work.
I have already run Enable-PSRemoting on both systems.
Just for some more troubleshooting/visibiity into what's going on..
On your Win10 workstation, open up elevated PowerShell and type the following:
Get-VM -ComputerName HV01.domain.comwith and without the domain.com part. -
Always managed w/out domain in my case so following things could be useless but... Did you enabled winrm both on server and workstation?
