[Solved] Unable to view VM Guest (Hyper-V)

Hmmm....anything special about the network?  Solid LAN?  Variable WAN?  

I wonder if you can just try WMI without SNMP to see if there is a difference.

This whitepaper (www.delltechcenter.com/ome) may have a bit of info on hyperv.

en.community.dell.com/.../20281547.aspx

Thanks,

Rob

Hi than's to reply :emotion-1:,

All network than I manage are not local, they are remote (by VPN).

The only things different is the Forest (and domain) name is composed (a.b.c) and other forest (and domain)  name are in (d.e).

All domains that I manage are in independent forest (AD).

Discover without SNMP, not found Vm name's, we lose few informations (battery status, etc...)

I I had already looked the white paper posting...

Any other Idea ?

Best Regards.

Hmmm...I can't think of any other ideas at the moment.  Perhaps the support team can direct you in the right direction.  You can open a ticket by calling 800-945-3355.

Best regards,

Rob

I just found!!

All my servers are in French, and the search criteria for VM are in English, modifying the criteria it works.

Info for the changes I made:
Line 9835 of \Dell\SysMgt\Essentials\configuration\DataFormatterFiles\Insrtuctions\FormatInstructions.xml
change :

 
 
 
 
 

  
  
  
  
  


   
    (contains (KEY(31f854cd-8ec8-45c5-91a7-197a5be99948),"Virtual"))
   

 
 
 
 
 

   
    (contains (KEY(31f854cd-8ec8-45c5-91a7-197a5be99948),"Virtual") || contains (KEY(31f854cd-8ec8-45c5-91a7-197a5be99948),"virtuel"))
   

and
Line 9856 (same file)
change : 

  
 
 
 
 

   
  
  
  
  


    
     (contains (KEY(31f854cd-8ec8-45c5-91a7-197a5be99948),"Host"))
    

  
 
 
 
 
to :

   
  
  
  
  

    
   
   
   
   


     
      (contains (KEY(31f854cd-8ec8-45c5-91a7-197a5be99948),"Host") || contains (KEY(31f854cd-8ec8-45c5-91a7-197a5be99948),"informatique"))
     

   
  
  
  
  

It works for me.

If you can tell the issue to software developper to fix in futur version, that will help...

Thank you for everything.

Very interesting update :-)

I will be sure to raise this with the dev team.

Regards,

Rob

Hi,

Very interesting indeed. Just a few things i wanted to understand,

• Is your OME machine also in FRENCH?
• What is different between the 2 HyperV Hosts which are not showing up the VMs and the other Hyper V Hosts ?

As you have mentioned, that all your Machines are in French, we would expect this issue for all the Hyper V Hosts. But it is not. It is happening only with two of them. This will help us in narrowing down the issue. 

Your help is appreciated.

Hi,

• the OME machine is also in FRENCH.
• This info is wrong, I thinked other machine can retrieve information but that was cached information...

Thanks for the information. It was a lot of help.

It should help us in making sure we do not land up in such issues again.

Hi from germany,

we have the same problem with our Hyper-V Virtual Machines. None of them is detected as Hyper-V VM, all are "not classified".

SNMP and WMI is working on the Hyper-V Hosts and on the guests. All of our servers are installed with german language as default.

I tried to make the changes in the FormatInstructions.xml, but I have problems finding the right string in germany language. Can anybody help me?

OME 2.2 was installed today, did not fix the problem.

Thanks, Daniel

The problem is: How to modify the formatinstructions.xml that my "german" servers are recognized correctly??

OME 2.3 does not address this problem yet.

You will have to use the workaround mentioned in this thread.

Hello again,

Problem not solved with OME 2.3

Can anybody help?

Thanks

I would request you to reach out to Dell Support. They can take a closer look and assist on the problem.

This problem is addressed with OpenManage Essentials v2.4 which is now available for downloads.

Hi,

today I updated to 2.5, the problem still persists unfortunately. Could updating from former versions be the problem? As Shivendra wrote, the problem was adressed with 2.4. But we still had the problem with 2.4, and now with 2.5. We updated OME since 2.1

Could an complete OME reinstallation from scratch solve the problem?

Thanks