However, if you make yourself a local admin on the hyper-v server, it'll connect fine.with the new issue being a normal user account now has complete access to hyper-v cluster.Ĭlarify: I can log into it and manage via Failover Cluster Manager, its only the hyper-v manager that has issues. So if you try to connect to a server using alternate credentials or open hyper-v as a differen user - you can't connect. Windows 10 uses WS-MAN to pass credentials which 2012R2 isn't apparently using. We only just upgraded the IT dep from w8.1 to w10 and only just noticed we couldn't connect. This may indicate that the hyper-v platform is not installed on the computer or that the version of the Hyper-v platform is incompatible with these management tools. Click OK and the Hyper-V Manager snap-in will load. When the run box appears type: Virtmgmt.msc. To launch Hyper-V Manager using the run window in Windows 8, Server 2012 and Server 2012 R2, simply right click in the lower left corner and select run. The hyper-v management tools could not access an expected WMI class on computer 'ServerName'. Windows 8, Windows 8.1, Server 2012 or Server 2012 R2 from the Run Window. Check that the virtual machine management service is running and that you are authorized to connect to the server. Has anyone seen this issue with W10 on 1709 not being able to connect via Hyper-V manager of a windows 2012 R2 server?Īn error occured while attempting to connect to server "ServerName".
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |