Hi - I would concentrate on getting WinRM working rather than DCOM/WMI, its more reliable. Information about what you need to get either one working can be found here -    [URL]   Look at the section 'Configuring Collection Methods' - to get WinRM working its pretty much the winrm commands you mentioned above, the DCOM/WMI requires a bunch of registry permission changes.   So concentrating on WinRM - assuming you've checked all the normal network/firewall connect issues between the Foglight server and the Hyper-V hosts, check out this Knowledge base article with some troubleshooting steps in it;    [URL]   Also to give you more information on what's actually going on with the connection - in the console goto Adminstration/Agent Status - click on one of the Hyper-V agents and click 'Get Log' at the bottom of the screen. These log files contain lots of information, and can be difficult to read. Sometimes I find it easier to delete the agent, re-create it and then retrieve this log file after a minute or so, you will see entries for it creating and starting the agent and then connecting to the host, it will give more information - you can search the KB at support.quest.com with these error messages (use 'Foglight' as the product).   If you still don't have joy on getting it working, you are entitled to full support under your trial period. You can log a call here -[URL] - A support person will contact you and work through the problem with you – with these types of issues, it can be a number of different things and can be hard to fix in this type of forum.   If you get it fixed - please let us know what the root cause problem was - hopefully it will help other people... thanks Danny 
Over the weekend, I installed Foglight on one of our test servers. The software install was fairly straightforward, and I was able to get logged in via HTTPS. I then continued the setup for Hyper-V monitoring using the "Add Hyper-V" function, but I haven't been able to get any data from my Hyper-V 2012 hosts.  I tried adding the host servers with both the WinRM and DCOM connection types, and the DCOM type seems to be working for our Server 2008 R2 Hyper-V hosts (3 total). However, it isn't working on our Hyper-V 2012 hosts (6 hosts, one cluster) or our Hyper-V 2012 R2 hosts (2 hosts, non-clustered).  I think there are some additional configuration steps that will be needed for either option (DCOM or WinRM), but those steps are not entirely clear. I think DCOM requires the Remote Registry service to be running and set to Automatic.  I also think there are some separate configuration steps for WinRM, but I haven't been able to get it working as of yet.  I would prefer to use WinRM if possible, but it looks like DCOM might be easier to set up. Any ideas what I'm missing?  I set up a new AD user account for Foglight to use when connecting to these hosts and that account has Domain Admin privileges.  To attempt resolution of this on my own, I've tried configuring Windows Remote Management by executing the below commands on one of my Hyper-V 2012 hosts:  winrm quickconfigwinrm set winrm/config/service @{AllowUnencrypted="true"}winrm set winrm/config/service/auth @{Basic="true"}  Following that, I restarted the Windows Remote Management service and re-added the host in Foglight using WinRM and my previously created Domain Admin account (with kerberos authentication). No luck. The error I get is:  The Agent is having difficulty logging on to the remote host  I've also tried using a local admin account with basic authentication on one of my 2012 R2 Hyper-V hosts but that doesn't seem to be getting me anywhere either. The error I get on that one is:  Internal error, for more information please check the logs  Any news on what configuration steps I need to take to pull data from these 2012 and 2012 R2 hosts?
Foglight 7.0 Configuration - Hyper-V 2012