Hyper-V Manager connection issues on Windows 10 1709
-
@black3dynamite said in Hyper-V Manager connection issues:
@fuznutz04 said in Hyper-V Manager connection issues:
@black3dynamite said in Hyper-V Manager connection issues:
@fuznutz04 said in Hyper-V Manager connection issues:
I started having issues since upgrading to Windows 10 1709. Have you tried turning off the firewall to see if you can connect?
That is the same version of Windows I am on as well. I disabled the firewall, but no change.
Do you have your server listed in TrustedHosts?
Get-Item WSMan:\localhost\Client\TrustedHostsYep, it is listed in there.
-
@fuznutz04 said in Hyper-V Manager connection issues:
I thought I saw a step by step procedure on here once that outlined the needed steps for HV management in a workgroup environment, but I cannot find it. Anyone else ever run into this issue?
There was... Not sure where it is.
Can you remote PowerShell to it?
-
@tim_g said in Hyper-V Manager connection issues:
@fuznutz04 said in Hyper-V Manager connection issues:
I thought I saw a step by step procedure on here once that outlined the needed steps for HV management in a workgroup environment, but I cannot find it. Anyone else ever run into this issue?
There was... Not sure where it is.
Can you remote PowerShell to it?
Yes, I can remote PowerShell into it.
-
@fuznutz04 said in Hyper-V Manager connection issues:
@tim_g said in Hyper-V Manager connection issues:
@fuznutz04 said in Hyper-V Manager connection issues:
I thought I saw a step by step procedure on here once that outlined the needed steps for HV management in a workgroup environment, but I cannot find it. Anyone else ever run into this issue?
There was... Not sure where it is.
Can you remote PowerShell to it?
Yes, I can remote PowerShell into it.
Oh, well what more do you need?
Try a:
Get-VM | FT -AutoSize...and this will be your friend:
Get-Command -Noun *vm* -
@tim_g said in Hyper-V Manager connection issues:
Get-VM | FT -AutoSize
Well, that will work for now.
-
Tag this thread Windows 1709 and also update the subject line.
This is clearly yet another 1709 issue.
-
@fuznutz04 said in Hyper-V Manager connection issues:
I also checked that DCOM permissions are set correctly.
Yeah, I read that 1709 completely changes the network stack. It's what supposedly causing my mis-reporting info for my AV and firewall.
-
@dashrender said in Hyper-V Manager connection issues:
@fuznutz04 said in Hyper-V Manager connection issues:
I also checked that DCOM permissions are set correctly.
Yeah, I read that 1709 completely changes the network stack. It's what supposedly causing my mis-reporting info for my AV and firewall.
My firewall had to be reconfigured so I can reconnect Hyper-V Manager to Hyper-V 2012 R2. I had no issue connecting to Hyper-V 2016.
-
@jaredbusch said in Hyper-V Manager connection issues:
Tag this thread Windows 1709 and also update the subject line.
This is clearly yet another 1709 issue.
Done
-
@black3dynamite said in Hyper-V Manager connection issues on Windows 10 1709:
@dashrender said in Hyper-V Manager connection issues:
@fuznutz04 said in Hyper-V Manager connection issues:
I also checked that DCOM permissions are set correctly.
Yeah, I read that 1709 completely changes the network stack. It's what supposedly causing my mis-reporting info for my AV and firewall.
My firewall had to be reconfigured so I can reconnect Hyper-V Manager to Hyper-V 2012 R2. I had no issue connecting to Hyper-V 2016.
Do you remember what settings you changed (and where) so you can connect to HyperV 2012R2 again?
