<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Data populated for PowerCli / VIM in Operating System - VMware</title>
    <link>https://community.hpe.com/t5/operating-system-vmware/data-populated-for-powercli-vim/m-p/4501767#M22</link>
    <description>Can someone in HP tell me why certain fields are not populated in the same way as Dell and IBM ...&lt;BR /&gt;&lt;BR /&gt;For example a lot of emphasis is being placed on using the PowerCli (VMware Cmdlets for Powershell) to query and effect config changes in vmware.&lt;BR /&gt;&lt;BR /&gt;One of the areas you should be able to query in PowerCli/VMware is Hardware.SystemInfo  where things such as Serial Number, Asset Number, BIOS revision are populated and are easily reportable.&lt;BR /&gt;&lt;BR /&gt;Most users seem able to pull back information for Dell and IBM but not HP ...&lt;BR /&gt;&lt;BR /&gt;See this link to a vmware forum on the subject - &lt;A href="http://communities.vmware.com/message/1371149" target="_blank"&gt;http://communities.vmware.com/message/1371149&lt;/A&gt;&lt;BR /&gt;&lt;BR /&gt;As you can see HP are populating the serial number somewhere in the Linux console as it can be retrieved using esxcfg-info. &lt;BR /&gt;&lt;BR /&gt;It would be really good to get this standard across all vendors for scripts to be useable across the board.&lt;BR /&gt;&lt;BR /&gt;Thanks in advance.&lt;BR /&gt;&lt;BR /&gt;Matt Roblin</description>
    <pubDate>Tue, 22 Sep 2009 20:39:24 GMT</pubDate>
    <dc:creator>omtsg</dc:creator>
    <dc:date>2009-09-22T20:39:24Z</dc:date>
    <item>
      <title>Data populated for PowerCli / VIM</title>
      <link>https://community.hpe.com/t5/operating-system-vmware/data-populated-for-powercli-vim/m-p/4501767#M22</link>
      <description>Can someone in HP tell me why certain fields are not populated in the same way as Dell and IBM ...&lt;BR /&gt;&lt;BR /&gt;For example a lot of emphasis is being placed on using the PowerCli (VMware Cmdlets for Powershell) to query and effect config changes in vmware.&lt;BR /&gt;&lt;BR /&gt;One of the areas you should be able to query in PowerCli/VMware is Hardware.SystemInfo  where things such as Serial Number, Asset Number, BIOS revision are populated and are easily reportable.&lt;BR /&gt;&lt;BR /&gt;Most users seem able to pull back information for Dell and IBM but not HP ...&lt;BR /&gt;&lt;BR /&gt;See this link to a vmware forum on the subject - &lt;A href="http://communities.vmware.com/message/1371149" target="_blank"&gt;http://communities.vmware.com/message/1371149&lt;/A&gt;&lt;BR /&gt;&lt;BR /&gt;As you can see HP are populating the serial number somewhere in the Linux console as it can be retrieved using esxcfg-info. &lt;BR /&gt;&lt;BR /&gt;It would be really good to get this standard across all vendors for scripts to be useable across the board.&lt;BR /&gt;&lt;BR /&gt;Thanks in advance.&lt;BR /&gt;&lt;BR /&gt;Matt Roblin</description>
      <pubDate>Tue, 22 Sep 2009 20:39:24 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-vmware/data-populated-for-powercli-vim/m-p/4501767#M22</guid>
      <dc:creator>omtsg</dc:creator>
      <dc:date>2009-09-22T20:39:24Z</dc:date>
    </item>
  </channel>
</rss>

