I have just set up a new Hyper-V 2012 Server and connected it to the domain. I attempted to follow the Microsoft documentation to allow remote management via server manager. I enabled remote management in the server configuration command menu.
I also allowed the server to respond to ping requests. When I search for the server in server manager from my windows 8 desktop it is found by name and added to the servers list. Under the manageability column I get the message "Target name resolution error." I'm able to ping the server by ip address but not by name. Both the server and my desktop are connected to the domain.
I tried adding the server name to my deskops hosts file in which case I can now ping the server by name but I still get the same error in server manager. The documentation simply states that I should have to enable remote management on the server, add any user accounts that should be allowed remote access to the local administrator group, and then connect to it from server manager.
I don't know if the documentation is incomplete or I may have something mis-configured?
Best Answer
I found the problem in my setup. It was indeed a miss-configured dns. This technet post led me to the problem: http://social.technet.microsoft.com/Forums/windowsserver/en-US/9f428e15-d3f6-499f-b263-d03cf009569c/w2k8-r2-ad-integrated-dns-nslookup-response-default-server-unknown-address-1 Running nslookup on the server showed that the dns server was unknown. When the dns role was configured by Active Directory the dns server address in the ipv6 properties was set to "::1". Un-checking ipv6 in the network adapter properties or configuring the ipv6 properties fixes the problem.