HYPER-V Remote Management Issue

[ITGURU]

I was running Windows 8.1 and was able to successfully connect to my 3 hyper-v host servers running Windows Server 2012 R2 using the hyper-v management console on my workstation.

 

I have now upgraded to Windows 10 and installed the remote admin tools along with the hyper-v management console.

 

For some reason I can now only connect to 1 of the 3 hosts. I was able to connect to the one which was ok without any issues.

 

However, when trying to connect to the other 2 i get, check that the virtual machine management service is running, and that you are authorised to connect to the server.

 

Anyone help me out please? Nothing has changed on the server side and i'm still using my same username to access the hyper-v hosts as when was on windows 8.1

 

A mystery!

[forkies]

Ip changed maybe a acl or firewall issue on hosts?

[ITGURU]

Same IP on servers and clients - Firewall disabled on client!

[Guest MD5T]

You have to change the access in diccomm i have had this issue before

[ITGURU]

You have to change the access in diccomm i have had this issue before

Change What though as was all working before - client is same logged in user, client name and IP as when on Windows 8.1 client. Only change is client is now on Windows 10

[chrisbsc]

Had the same issue yesterday had to run the following command. winrm set winrm/config/client @{TrustedHost="ip address of hyper-v server"}

[ITGURU]

Had the same issue yesterday had to run the following command. winrm set winrm/config/client @{TrustedHost="ip address of hyper-v server"}

 

Running that gave me

WSManFault Message = The client cannot connect to the destination specified in the request. Verify that the service on the destination is running and is accepting requests.

[chrisbsc]

You might need to run winrm quickconfig and y to make changes. Then run previous command

[ITGURU]

You might need to run winrm quickconfig and y to make changes. Then run previous command

 

On the client i'm assuming?Still don't know why i could connect to all hosts in 8.1 but not 10!

[chrisbsc]

Yes you run the commands on the client.

its something to do with windows 10.

after a windows 10 upgrade you need to re-authorize the Hyper-v server again, and you can do this by : running cmd as an admin and type in "winrm quickconfig" and hit enter. After that you get a few prompts and you gotta accept them all when thats done

 

type in: winrm set winrm/config/client @{TrustedHosts="Your Hyper-v Server IP address"} and press enter. after that you should be good to go.

[ITGURU]

No Joy still although searches bring up about HP servers being an issue , there's a one liner supposed fix but shouldnt be used in live environment, which would read right as the one i can connect 2 is a dell server, the other 2 are HP.

The extended error message is:

 

Hyper-v tools could not access an expected WMI class on computer 'servername' may indicate hyperv platform is not installed on the computer or the version of the platform is incompatible with these tools

 

As mentioned before, all working fine from Windows 8.1 client.

[Guest MD5T]

Yeah I had the same issue, I tried this and the issue went away. You might not have the same luck as me, but it is certainly worth a try:

 

Run %windir%System32dcomcnfg.exe as administrator.

Expand “Component Services” and “Computers”

Right-click “My Computer” and choose Properties.

Select the “COM Security” tab.

Under “Access Permissions” click “Edit Limits”

Select “ANONYMOUS LOGON” and check “Allow” for “Remote Access”

Select “ALL APPLICATION PACKAGES” and check “Allow” for “Remote Access”

Click “OK” all the way out, and open Hyper-V Manager again.

This time, you should see your VMs.

[mrwoberts]

@ITGURU

Can you successfully RDP onto the two servers? If you can't then this is not just related to hyper-v management - possibly disable firewall on the servers to test communication. Assuming it is feasible, unplug the lan cable to one of those servers and see if you can ping it - if the IP responds, then there is an IP conflict.

Are these Core edition installations?

Do the error messages say anything about CredSSP??

Are you ticking the box (for the Hyper-V console) 'connect as a different user' so that you supply the hyper-v admin credentials.

 

I have recently setup a 2016 Hyper-V server (Core) and had to issue these commands to be able to connect to it...

On the Server:   Enable-WSManCredSSP -Role server
On the client:   Enable-WSManCredSSP -Role client -DelegateComputer *
(if above client cmdlet didn't work, I also issued the -Role server, on the 10 client

 

EDIT: Also found these pages helpful

LINK 1

LINK 2

Edited April 12, 2017 by mrwoberts

[ITGURU]

@ITGURU

Can you successfully RDP onto the two servers? If you can't then this is not just related to hyper-v management - possibly disable firewall on the servers to test communication. Assuming it is feasible, unplug the lan cable to one of those servers and see if you can ping it - if the IP responds, then there is an IP conflict.

Are these Core edition installations?

Do the error messages say anything about CredSSP??

Are you ticking the box (for the Hyper-V console) 'connect as a different user' so that you supply the hyper-v admin credentials.

 

I have recently setup a 2016 Hyper-V server (Core) and had to issue these commands to be able to connect to it...

On the Server:   Enable-WSManCredSSP -Role server
On the client:   Enable-WSManCredSSP -Role client -DelegateComputer *
(if above client cmdlet didn't work, I also issued the -Role server, on the 10 client

 

EDIT: Also found this page helpful (LINK)

All servers working fine, remote desktop, file access etc

Nothing has changed on the server side.

All Servers are running same version and all up to date of Windows Server 2012 R2, only difference is the one i can connect to is a Dell server, the 2 i cannot are HP Proliant servers.

 

I believe that the connect to using credentials is only for 2016 systems, but yes i did try that to no avail as didn't need to for the 1 server i connected to successfully.

 

Definitely related to windows 10 or HP Servers as everything else is the same on the client, same IP, logged in user , permissions etc.

Edited April 12, 2017 by ITGURU

[mrwoberts]

Updated my post, added a second link.

 

Definitely related to windows 10 or HP Servers as everything else is the same on the client, same IP, logged in user , permissions etc.

Agreed, but there most certainly is something different, or not now in place that we haven't thought of yet.

Did you test disabling the firewall on the affected servers? purely a process of elimination.

Can you identify anything else that has changed during your move from 8.1 to 10. Anything now missing from the new 10 client that the two servers are expecting?

[ITGURU]

Updated my post, added a second link.

 

 

Agreed, but there most certainly is something different, or not now in place that we haven't thought of yet.

Did you test disabling the firewall on the affected servers? purely a process of elimination.

Can you identify anything else that has changed during your move from 8.1 to 10. Anything now missing from the new 10 client that the two servers are expecting?

Firewall disabled on the servers - no change!

Nope, nothing that i'm aware of.

[ITGURU]

https://social.technet.microsoft.com/Forums/windowsserver/en-US/c001cda0-ed0b-4648-8c91-90f8ca638831/manage-server-2012-r2-hyperv-from-win-10-ltsb-2016-client-could-not-access-an-expected-wmi?forum=winserverhyperv

 

Removing the HP WBEM agents now gives me a different error when trying to connect:

 

the WS-Management service cannot process the request, WMI service or provider returned an unknown error

 

Updated the agents from 10.0.0.0 to 10.60.0.0 - back to the old error message about not being compatible.

 

Might be a support call with HP?

[ITGURU]

I have just installed the Hyper-V management console on my home PC (windows 10) to test.

Same error message when trying to connect to the 2 HP Hyper-V hosts

 

However, I could connect to the other Dell Host without any problems but got the error access denied, unable to establish communication which is expected as my pc is not on my network domain, but it added the server to the list, just didn't display the VMs.

[ITGURU]

I have installed Server 2016 onto another HP server identical model to the other 2 i cannot connect to , that are on 2012 r2.

 

It connected straight away Windows 10 to Server 2016 HP Proliant, so appears the issue is with Windows 10 incompatible with a Server 2012 R2 host in some way

[mrwoberts]

This is more intriguing that an episode of Poirot.

So, you established that...

 

Win 8.1 -> 2016 R2 H-V (DELL and HP x 2) works.

Win 10 -> 2016 R2 H-V (DELL) works.

Win 10 -> 2016 R2 H-V (HP x 2) does not work.

Despite the setup of all the Hyper-V hosts being 'identical', and nothing was needed in Windows 10 that you previously had in 8.1.

You found that partially disabling some HP software gave different errors, but still no connection.

 

With all that mind, would it be worth stripping back (uninstalling) some of that HP software, or at least posting the errors you received.

HP support also sounds like a good option, but I don't know how quick they will be to respond.

[ITGURU]

This is more intriguing that an episode of Poirot.

So, you established that...

 

Win 8.1 -> 2016 R2 H-V (DELL and HP x 2) works.

Win 10 -> 2016 R2 H-V (DELL) works.

Win 10 -> 2016 R2 H-V (HP x 2) does not work.

Despite the setup of all the Hyper-V hosts being 'identical', and nothing was needed in Windows 10 that you previously had in 8.1.

You found that partially disabling some HP software gave different errors, but still no connection.

 

With all that mind, would it be worth stripping back (uninstalling) some of that HP software, or at least posting the errors you received.

HP support also sounds like a good option, but I don't know how quick they will be to respond.

 

Not quite:

 

Windows 8.1 > 2012 R2 DELL AND HP Works

Windows 10 > 2012 R2 Dell Works (2 x HP Doesnt work)

Windows 10 > 2016 Server HP Works

Windows 10 > 2012 R2 HP Doesnt Work.

 

as mentioned there isn't a generic issue as access to the 2012 r2 server works fine from windows 7 and 8.1 client pcs' with hyperv manager. Only client experiencing the issue is Windows 10.

 

[mrwoberts]

Apologies, typo of 2016 R2, I meant 2012 R2 :-)

 

I'm thinking though that the way Windows 10 communicates with those HP servers is possibly being disrupted by the HP server software. Can you run cports (nirsoft) to see what ports are being listened to on the working Dell, versus the non-working HP server. I don't see how the 10 client could communicate with one server, but not another, unless there is something different about the two servers.

[ITGURU]

Apologies, typo of 2016 R2, I meant 2012 R2 :-)

 

I'm thinking though that the way Windows 10 communicates with those HP servers is possibly being disrupted by the HP server software. Can you run cports (nirsoft) to see what ports are being listened to on the working Dell, versus the non-working HP server. I don't see how the 10 client could communicate with one server, but not another, unless there is something different about the two servers.

 

Dell Server:

vmms.exe 63575 udp

vmms.exe 2179 tcp

 

hp server

vmms.exe 55871 udp

vmm.exe 2179 tcp

 

any others to check?

[mrwoberts]

I'm not at my console to double check those, but can you spot any suspects or differences between the two lists of cports? How about wmi service related?