none
Hyper-V Manager cannot connect after upgrading to Windows 10 RRS feed

  • Question

  • I had a Windows 8.1 Pro workstation computer that I used to manage virtual machines hosted on Windows Server 2012 R2 Hyper-V servers.  After upgrading to Windows 10 Pro, I cannot connect to any of the Hyper-V hosts.  The Hyper-V hosts are on a workgroup and my workstation is on a workgroup.  The workgroups and the domain that the virutal machines reside are all on the same subnet.  This all still works fine on another Windows 8.1 workgroup laptop.


    If I add user credentials to the 'Connect to Server' (credentials that succeed when using RDP to hyper-v host) I get the dialog telling me 'you do not have the required permission to complete this task'

                

    I've tried the winrm config commands,  cmdkey commands for authentication.  When I run HVRemote, I get no errors.  I have no idea what else to do.

    C:\temp>cscript hvremote.wsf /show /target:VRTX-DCSQL /override
    Microsoft (R) Windows Script Host Version 5.812
    Copyright (C) Microsoft Corporation. All rights reserved.


    Hyper-V Remote Management Configuration & Checkup Utility
    John Howard, Hyper-V Team, Microsoft Corporation.
    http://blogs.technet.com/jhoward
    Version 1.08 9th Sept 2013

    INFO: Computername is pavilion
    INFO: Computer is in workgroup PCAINC
    INFO: Current user is PAVILION\Norm
    INFO: OS is 10.0.10240 64-bit Microsoft Windows 10 Pro
    INFO: Assuming /mode:client as the Hyper-V role is not installed
    WARN: User override to assume Windows 8.1/Windows Server 2012 R2 behaviour
    INFO: Hyper-V Tools are enabled

    -------------------------------------------------------------------------------
    DACL for COM Security Access Permissions
    -------------------------------------------------------------------------------

    \Everyone    (S-1-1-0)
         Allow: LocalLaunch RemoteLaunch (7)

    NT AUTHORITY\ANONYMOUS LOGON    (S-1-5-7)
         Allow: LocalLaunch RemoteLaunch (7)

    BUILTIN\Distributed COM Users    (S-1-5-32-562)
         Allow: LocalLaunch RemoteLaunch (7)

    BUILTIN\Performance Log Users    (S-1-5-32-559)
         Allow: LocalLaunch RemoteLaunch (7)

    APPLICATION PACKAGE AUTHORITY\ALL APPLICATION PACKAGES    (S-1-15-2-1)
         Allow: LocalLaunch (3)

    -------------------------------------------------------------------------------
    ANONYMOUS LOGON Machine DCOM Access
    -------------------------------------------------------------------------------

    ANONYMOUS LOGON has remote access

    -------------------------------------------------------------------------------
    Firewall Settings for Hyper-V Management Clients
    -------------------------------------------------------------------------------

    Private Firewall Profile is active

       Enabled:  Hyper-V Management Clients - WMI (Async-In)
       Enabled:  Hyper-V Management Clients - WMI (TCP-Out)
       Enabled:  Hyper-V Management Clients - WMI (TCP-In)
       Enabled:  Hyper-V Management Clients - WMI (DCOM-In)

    -------------------------------------------------------------------------------
    IP Configuration
    -------------------------------------------------------------------------------


    Windows IP Configuration

       Host Name . . . . . . . . . . . . : Pavilion
       Primary Dns Suffix  . . . . . . . :
       Node Type . . . . . . . . . . . . : Hybrid
       IP Routing Enabled. . . . . . . . : No
       WINS Proxy Enabled. . . . . . . . : No

    Wireless LAN adapter Wi-Fi:

       Media State . . . . . . . . . . . : Media disconnected
       Connection-specific DNS Suffix  . :
       Description . . . . . . . . . . . : Intel(R) WiFi Link 5100 AGN
       Physical Address. . . . . . . . . : 00-16-EA-7A-6E-94
       DHCP Enabled. . . . . . . . . . . : Yes
       Autoconfiguration Enabled . . . . : Yes

    Ethernet adapter Ethernet:

       Connection-specific DNS Suffix  . :
       Description . . . . . . . . . . . : Realtek PCIe FE Family Controller
       Physical Address. . . . . . . . . : 00-1E-EC-82-5E-3C
       DHCP Enabled. . . . . . . . . . . : No
       Autoconfiguration Enabled . . . . : Yes
       IPv4 Address. . . . . . . . . . . : 10.1.1.17(Preferred)
       Subnet Mask . . . . . . . . . . . : 255.255.255.0
       Default Gateway . . . . . . . . . : 10.1.1.253
       DNS Servers . . . . . . . . . . . : 10.1.1.56
       NetBIOS over Tcpip. . . . . . . . : Enabled

    Tunnel adapter Teredo Tunneling Pseudo-Interface:

       Connection-specific DNS Suffix  . :
       Description . . . . . . . . . . . : Teredo Tunneling Pseudo-Interface
       Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
       DHCP Enabled. . . . . . . . . . . : No
       Autoconfiguration Enabled . . . . : Yes
       IPv6 Address. . . . . . . . . . . : 2001:0:9d38:6ab8:1424:9f96:bd23:9796(Preferred)
       Link-local IPv6 Address . . . . . : fe80::1424:9f96:bd23:9796%5(Preferred)
       Default Gateway . . . . . . . . . : ::
       DHCPv6 IAID . . . . . . . . . . . : 218103808
       DHCPv6 Client DUID. . . . . . . . : 00-01-00-01-1A-C2-11-D3-00-1E-EC-82-5E-3C
       NetBIOS over Tcpip. . . . . . . . : Disabled

    Tunnel adapter isatap.{F98D62F4-9C85-44D2-BFB6-9A00DB1BF98A}:

       Media State . . . . . . . . . . . : Media disconnected
       Connection-specific DNS Suffix  . :
       Description . . . . . . . . . . . : Microsoft ISATAP Adapter #2
       Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
       DHCP Enabled. . . . . . . . . . . : No
       Autoconfiguration Enabled . . . . : Yes


    -------------------------------------------------------------------------------
    Stored Credentials
    -------------------------------------------------------------------------------


    Currently stored credentials:

        Target: Domain:target=TERMSRV/10.1.1.7
        Type: Domain Password
        User: satbend\norm
        Local machine persistence

        Target: Domain:target=TERMSRV/10.1.1.9
        Type: Domain Password
        User: satbend\norm
        Local machine persistence

        Target: Domain:target=webmail.phoseon.net
        Type: Domain Password
        User: phoseon\norio
        Local machine persistence

        Target: Domain:target=TERMSRV/PTI-WS09
        Type: Domain Password
        User: PHOSEONTECH\NOrio
        Local machine persistence

        Target: Domain:target=TERMSRV/216.228.186.49
        Type: Domain Password
        User: PAVILION\norm
        Local machine persistence

        Target: Domain:target=TERMSRV/10.1.1.3
        Type: Domain Password
        User: satbend\norm
        Local machine persistence

        Target: Domain:target=TERMSRV/satdc8
        Type: Domain Password
        User: satbend\norm
        Local machine persistence

        Target: Domain:target=TERMSRV/10.1.1.8
        Type: Domain Password
        User: satbend\norm
        Local machine persistence

        Target: WindowsLive:target=virtualapp/didlogical
        Type: Generic
        User: 02kavhthhyjc
        Local machine persistence

        Target: Domain:target=TERMSRV/satsql8
        Type: Domain Password
        User: satbend\administrator
        Local machine persistence

        Target: Domain:target=B-SATNAS1
        Type: Domain Password
        User: satbend\norm

        Target: Domain:target=VRTX-DCSQL
        Type: Domain Password
        User: administrator

        Target: Domain:target=ts8-3
        Type: Domain Password
        User: satbend\norm



    -------------------------------------------------------------------------------
    Testing connectivity to server:VRTX-DCSQL
    -------------------------------------------------------------------------------

    1: - Remote computer network configuration
         PASS - Found one or more network adapters

         Network adapter 1 of 1
           - Broadcom NetXtreme Gigabit Ethernet
           - Host Name:VRTX-DCSQL
           - IP Addresses: 10.1.1.11 fe80::40cc:fd96:67:c54
           - IP Subnets: 255.255.255.0 64

    2: - Remote computer general information
         PASS - Queries succeeded

         - Name: vrtx-dcsql
         - Workgroup: SatHostWGroup
         - OS: 6.3.9600 64-bit Microsoft Hyper-V Server 2012 R2
         - OS Type: Server

    3: - Ping and resolve name of remote computer
         PASS - Server found
              - Protocol Address:             10.1.1.11
              - Protocol Address resolved:    10.1.1.11

         The name could not be resolved using WMI. A regular ping will be done
         to see if name resolution is working. This is not a sign of an issue.

    4: - Ping VRTX-DCSQL using IPv4

         A timeout is OK, but if you get an error that VRTX-DCSQL
         could not be found, you need to fix DNS or edit
         \windows\system32\drivers\etc\hosts.

         >
         > Pinging VRTX-DCSQL [10.1.1.11] with 32 bytes of data:
         > Reply from 10.1.1.11: bytes=32 time<1ms TTL=128
         >
         > Ping statistics for 10.1.1.11:
         >     Packets: Sent = 1, Received = 1, Lost = 0 (0% loss),
         > Approximate round trip times in milli-seconds:
         >     Minimum = 0ms, Maximum = 0ms, Average = 0ms
         >


    5: - Ping VRTX-DCSQL using IPv6

         A timeout is OK, but if you get an error that VRTX-DCSQL
         could not be found, you need to fix DNS or edit
         \windows\system32\drivers\etc\hosts.

         > Ping request could not find host VRTX-DCSQL. Please check the name and try again.
         >


    6: - Connect to root\cimv2 WMI namespace
         PASS - Connection established

    7: - Connect to root\virtualization\v2 WMI namespace
         PASS - Connection established

    8: - Simple query to root\cimv2 WMI namespace
         PASS - Simple query succeeded

    9: - Simple query to root\virtualization\v2 WMI namespace
         PASS - Simple query succeeded
              - 4 computer system(s) located

    10: - Async notification query to root\virtualization\v2 WMI namespace
         PASS - Async notification to root\virtualization\v2 query succeeded

    INFO: Are running the latest version

    -------------------------------------------------------------------------------
    1 warning or error was found in the configuration. Review the
    detailed output above to determine whether you need to take further action.
    Summary is below.

    1: Running on a later OS than tested on. User override given

    -------------------------------------------------------------------------------
    INFO: HVRemote complete


    Friday, October 16, 2015 5:18 PM

All replies

  • Any update? I have this same issue. Hyper-v manager will connect from 8.1 or 2012 R2 servers but not windows 10 to 2012 R2 hosts. It will connect in my case to 2012 hosts.
    Monday, November 30, 2015 5:03 PM
  • There are some known issues that are being worked on in regards to this.

    I am not sure on the timeline for management patches, since Server 2016 is not fully baked / released.


    Brian Ehlert
    http://ITProctology.blogspot.com
    Learn. Apply. Repeat.

    Friday, December 4, 2015 6:08 PM
    Moderator