Hyper-V Remote Management Configuration Utility (HVRemote)

HVRemote reduces the manual configuration steps needed for Hyper-V Remote Management down to a few simple commands, and can diagnose common configuration errors.

4.7 Star
Add to favorites
E-mail Twitter del.icio.us Digg Facebook
  • Unable to connect to root\cimv2 WMI namespace
    6 Posts | Last post May 01, 2013
    • When running HVRemote /show /target:servername I am getting an error that it is unable to connect to the root\cimv2 WMI namespace.  I have verified that name resolution works in both directions.  I followed the steps for the Domain client/Workgroup Server instructions on Windows 8/Server 2012.  Firewall rules look good, perms look good.  I did notice though that when running wbemtest from the client it will only work if I enter my credentials.  I also have re-booted the Windows 8 laptop and Hyper-V 2012 server several times.  Only thing I can think of at this point is that IPsec is getting in the way on my Windows 8 laptop, but if that was the case then I am wondering why the wbemtest works when I specify credentials.  Thank you for any help you can provide! 
    • Providing the output of the above command from both machines would be the first point of call. IPsec will generally be configured to block calls back from the server to the client in your scenario (as IPsec through GP won't be applied to a workgroup machine). So I would expect wbemtest to work as it is connecting to the server, and you should need creds to connect. You could also temporarily stop IPsec to see if makes a differences by running net stop bfe on the client machine. It will however interrupt other network communication to non-boundary servers while the service is stopped.
    • John, thank you for responding.  I shut down the base filtering engine which also stopped the firewall and IKE and AuthIP IPsec Keying Modules services.  I then tried Hyper-V Manager again and I am still getting the operation failed error.  I am also still getting the same Cannot connect to root\cimv2 on server warning in HVRemote.  Is there any way I can provide the output of HVRemote /show using a private channel like email?
    • Yes - there's a link on my blog to contact me. Link to blog is on the description page.
    • John, I submitted the info via the blog site.
    • John, thank you for your help!  The fix was to remove the FQDN from my client's HOST file and make it just the server name.  After that I was able to connect to root\cimv2 on the Hyper-V server.
41 - 41 of 41 Items