https://community.hpe.com/t5/server-management-systems/trouble-identifying-a-vm-esx-4-1/m-p/4713987#M42487 I can discover this system, but it appears as unknown<BR />I can ping the VM host<BR />I can Putty into the host<BR />I can use vsphere<BR />All this is done from the CMS<BR />HP agents are installed I have the root credentials for WBEM<BR />When I try to identify the system I get<BR /><BR />Critical: The managed system is not reachable.<BR /> * Running system Manage Communication diagnosis...<BR /> * System identification finished on system. <BR /><BR />Any help would be very appreciated Tue, 16 Nov 2010 13:41:44 GMT Mathew Kohnen 2010-11-16T13:41:44Z https://community.hpe.com/t5/server-management-systems/trouble-identifying-a-vm-esx-4-1/m-p/4713987#M42487 I can discover this system, but it appears as unknown<BR />I can ping the VM host<BR />I can Putty into the host<BR />I can use vsphere<BR />All this is done from the CMS<BR />HP agents are installed I have the root credentials for WBEM<BR />When I try to identify the system I get<BR /><BR />Critical: The managed system is not reachable.<BR /> * Running system Manage Communication diagnosis...<BR /> * System identification finished on system. <BR /><BR />Any help would be very appreciated Tue, 16 Nov 2010 13:41:44 GMT https://community.hpe.com/t5/server-management-systems/trouble-identifying-a-vm-esx-4-1/m-p/4713987#M42487 Mathew Kohnen 2010-11-16T13:41:44Z https://community.hpe.com/t5/server-management-systems/trouble-identifying-a-vm-esx-4-1/m-p/4713988#M42488 I ended up solving this myself.<BR />It was the name given to the server in the SIM.<BR />The name contained illegal characters according to the SIm naming guildlines Tue, 16 Nov 2010 14:42:30 GMT https://community.hpe.com/t5/server-management-systems/trouble-identifying-a-vm-esx-4-1/m-p/4713988#M42488 Mathew Kohnen 2010-11-16T14:42:30Z