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.
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?
-
This post is deleted! -
@scottalanmiller 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..
Don't, it's a dead project. Try KVM.
I don't doubt for a second that you know what you're talking about, but if it's a dead project, then why the heck is their site still up and allowing people to download and use their products?
-
@tim_g said in Trying to set up Hyper-V Server 2016, ripping my hair out:
Get-VM -ComputerName HV01
That yields the following:
So it looks like it doesn't like something about my installation of Hyper-V Management tools or something? I don't know.. really strange.
-
What version of Windows 10? Did you mention that already?
-
@coliver said in Trying to set up Hyper-V Server 2016, ripping my hair out:
What version of Windows 10? Did you mention that already?
Already mentioned it above, but here it is:
- Windows 10 Pro
- Version: 1703
- OS Build: 15063.726
And FWIW: My Windows 10 isn't activated yet. I really don't think that matters since everything else works, I just haven't had a chance to purchase another license yet.
-
@matteo-nunziati said in Trying to set up Hyper-V Server 2016, ripping my hair out:
Yes. I did that a while back. Running winrm quickconfig, it tells me this on both Windows 10 pc and Hyper-V server:
"WinRM service is already running on this machine.
WinRM is already set up for remote management on this computer." -
Guys, does anyone here have a 2016 Hyper-V and Windows 10 setup, both joined to the domain? Otherwise, is anyone willing to set it up as a test to see if you get it working? I really want to figure out what my problem is. I think I've literally tried everything at this point and I just can't connect. I even tried adding the Hyper-V Management tools from another Windows 10 system and got the same errors..
-
@dave247 said in Trying to set up Hyper-V Server 2016, ripping my hair out:
Guys, does anyone here have a 2016 Hyper-V and Windows 10 setup, both joined to the domain? Otherwise, is anyone willing to set it up as a test to see if you get it working? I really want to figure out what my problem is. I think I've literally tried everything at this point and I just can't connect. I even tried adding the Hyper-V Management tools from another Windows 10 system and got the same errors..
I've been using it that way since forever.
Hyper-V 2016 and Win10 1703 to manage it.
Any Win10 computer that is joined to the domain can manage the Hyper-V server simply by logging in with the correct credentials, or like you are doing, providing the correct credentials when adding the server to Hyper-V Manager.
-
@tim_g 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:
Guys, does anyone here have a 2016 Hyper-V and Windows 10 setup, both joined to the domain? Otherwise, is anyone willing to set it up as a test to see if you get it working? I really want to figure out what my problem is. I think I've literally tried everything at this point and I just can't connect. I even tried adding the Hyper-V Management tools from another Windows 10 system and got the same errors..
I've been using it that way since forever.
Hyper-V 2016 and Win10 1703 to manage it.
Any Win10 computer that is joined to the domain can manage the Hyper-V server simply by logging in with the correct credentials, or like you are doing, providing the correct credentials when adding the server to Hyper-V Manager.
Geeze.. would it be possible for you to list out the exact steps you took from installing Hyper-V all the way to connecting to the server via the Hyper-V Manager in Windows 10?
I''ve gone through everything twice now and I just can't get it working...
-
@dave247 said in Trying to set up Hyper-V Server 2016, ripping my hair out:
@scottalanmiller 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..
Don't, it's a dead project. Try KVM.
I don't doubt for a second that you know what you're talking about, but if it's a dead project, then why the heck is their site still up and allowing people to download and use their products?
I'm not even sure what you mean to imply by this question. Why would the status of a project affect vendors trying to make money from people buying it or things around it?
-
OpenFiler still has a site up and you can still send money to them. but the project was totally abandoned like 5-6 years ago, and the project that it was based on was shut down and abandoned even before that. But if you want to send them money, they keep the site up just in case you want to.
