Directly on the ESXi host: esxcfg-info | grep -w “Serial Number” Remotely with PowerCLI: $myCredentialsObject = Get-Credential Connect-VIServer -Server <ServerName> -Credential $myCredentialsObject Get-VMHost | Select @{N=’VMHost’;E={$_.Name}}, @{N=’Serial’;E={($_.ExtensionData.Hardware.SystemInfo.OtherIdentifyingInfo | where {$_.IdentifierType.Key -eq “ServiceTag”}).IdentifierValue}}
If your VMWare vSphere 6.x environment command output of esxtop looks like a bunch of garbled gibberish (it’s actually CSV format), then you need to change the terminal declaration to xterm but don’t ask me why it’s configured like this in the first place. The fix for this problem is: TERM=xterm esxtop Remember that Linux is case-sensitive and therefore this needs to be entered as TERM=xterm and not term=xterm This is what you and everyone else should see: [root@esxi67:/] TERM=xterm esxtop 3:18:40am up 3:09, 647 worlds, 10 VMs, 12 vCPUs; CPU load average: 0.08, 0.10, 0.14 PCPU USED(%):