Trying to set up Hyper-V Server 2016, ripping my hair out
-
I'm trying out Microsoft's Hyper-V 2016 server -- not the OS role, I'm talking about the actual Hypervisor without the "Desktop Experience" GUI. I got that installed and joined to our domain and then added an administrator and then I installed the Hyper-V management tools on my Windows 10 workstation and then I tried to connect to the server as that user. However I can't seem to get connected. It's constant errors.
Right now I'm stuck on "Enable delegation" as I get an error that says "Delegation of credentials to the server could not be enabled. CredSSP authentication is currently disabled.
I keep trying to google things but 90% of the stuff I find seems to be about setting up the Hyper-V role, not the straight Hypervisor. Then anything more explicit than that, such as with the CredSSP stuff, I just find about of stuff regarding PowerShell scripts.
I'm now trying to run Enable-WSManCredSSP commands according to this guide but it's not working...
I've been slowly doing this for hours now and I'm just ripping my hair out at this point. Is there a more straight-forward way to set up and manage Hyper-V without having to do a bunch of obscure steps? I just want to get to where I can install some VMs. See I've gotten used to the user friendliness of WMware where I can just connect to the hosts or vCenter via web browser and go from there.
Now I'm not crying about this because it's hard -- I enjoy learning challenges.. but right now I'm just drained and need some guidance. Otherwise I was considering installing some other free Hypervisor in hopes that it's easier to setup.
-
-
-
Is your Windows 10 workstation joined to the same domain your hyper-V host is? It sounds a lot like it's not. If that's the case, it's a real pain to get them to connect.
-
@mike-davis said in Trying to set up Hyper-V Server 2016, ripping my hair out:
Is your Windows 10 workstation joined to the same domain your hyper-V host is? It sounds a lot like it's not. If that's the case, it's a real pain to get them to connect.
Yeah I'm having this problem got a HyperV server in another office that's on a different Domain.
-
@mike-davis said in Trying to set up Hyper-V Server 2016, ripping my hair out:
Is your Windows 10 workstation joined to the same domain your hyper-V host is? It sounds a lot like it's not. If that's the case, it's a real pain to get them to connect.
Yes, my Windows 10 workstation is joined to the domain, same one that the Hyper-V server is joined to. I haven't gotten back to this yet since it's the holidays but I plan to do a little more in the next day, then I'll report back.
Thanks for the help
-
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?
