vCenter@ipaddress instead of vCenter@hostname

[Ronald Lucas]

Why are vCenter CIs named vCenter@ipaddress when vCenter is discovered on an appliance?   We would rather these CIs be named vCenter@hostname.  

[Ronald Lucas]

The hostname of the appliance is visible in the vCenter Server Appliance application under Summary.   So maybe it's possible to retrieve that value so the CI can be named vCenter@hostname?   I don't need the host of the appliance discovered.   I simply want the vCenter CI named vCenter@hostname instead of vCenter@ipaddress.  

[Ronald Lucas]

Couldn't ServiceNow enhance vCenter discovery by creating an appliance CI?  ESXi server CIs are created using information gathered from vCenter.  SSH is not used to discover ESXi servers.  Why not do the same thing for the appliance since basic information about the appliance is exposed in vCenter?

[jcanjura]

Did you figure out how to get the vCenter@hostname?

Our users are asking the same.

[adilrathore]

The hostname part of the vCenter comes from the discovery of the server hosting the Vcenter. So for vCenter hosted on Windows you will need to have the Windows Server Credentials as well as the vCenter Credentials. For vCenter on a Linux server the name will be vCenter@ip_address as OOB ServiceNow would not be able to discover the Linux host for vCenter. Below is the KB for reference purpose:

Some vCenter name is vCenter@hostname and some are vCenter@ip_address

[Corey MacDonald]

@doug.schulze 

Customers are confused with the naming standard of the vCenter CIs. Some are vCenter@hostname & vCenter@ipaddress. I have explained to them the ones with the IP Address are the vCenter servers running on the linux appliances and the others are vCenter servers running on Windows. Is there a way to change the scripts to set the name of the vCenter servers running on linux to use the dns name instead of the IP?

Thanks,

Corey