<?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 Re: How to edit/remove oem.xml in ESXi Discussions</title>
    <link>https://communities.vmware.com/t5/ESXi-Discussions/How-to-edit-remove-oem-xml/m-p/2909874#M281739</link>
    <description>&lt;P&gt;Thanks...I'll take a look.&amp;nbsp; As I said, it's just a cosmetic/UI issue that doesn't affect functionality whatsoever.&amp;nbsp; I just don't login to the console very often (no need to), and I always do a double-take seeing the warning and double-check to make sure that yes, I'm on 7.x.&lt;/P&gt;</description>
    <pubDate>Wed, 18 May 2022 21:24:35 GMT</pubDate>
    <dc:creator>petersonmd</dc:creator>
    <dc:date>2022-05-18T21:24:35Z</dc:date>
    <item>
      <title>How to edit/remove oem.xml</title>
      <link>https://communities.vmware.com/t5/ESXi-Discussions/How-to-edit-remove-oem-xml/m-p/2908594#M281538</link>
      <description>&lt;P&gt;This is a basic UI problem that I can't figure out how to fix.&amp;nbsp; It doesn't affect anything except my OCD.&amp;nbsp; &amp;nbsp;We are running&amp;nbsp; ESXi 7.0U3 - but for some reason, during the upgrade, the file that contains the text that we're running a customized Dell image was not deleted.&amp;nbsp; Every time I login to the web console, ESXi informs me that we're running 6.0.0U2 A02, even though we're obviously not.&amp;nbsp; The text is contained in /etc/vmware/oem.xml, but ESXi 7 won't let me chmod / rm the file.&amp;nbsp; Any ideas on how to get around this?&amp;nbsp; It's really just an annoyance...but one I'd like to fix.&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;span class="lia-inline-image-display-wrapper lia-image-align-inline" image-alt="Screenshot.png" style="width: 762px;"&gt;&lt;img src="https://communities.vmware.com/t5/image/serverpage/image-id/95231i60204F386F519155/image-size/large/is-moderation-mode/true?v=v2&amp;amp;px=999" role="button" title="Screenshot.png" alt="Screenshot.png" /&gt;&lt;/span&gt;&lt;/P&gt;</description>
      <pubDate>Wed, 11 May 2022 20:13:12 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/ESXi-Discussions/How-to-edit-remove-oem-xml/m-p/2908594#M281538</guid>
      <dc:creator>petersonmd</dc:creator>
      <dc:date>2022-05-11T20:13:12Z</dc:date>
    </item>
    <item>
      <title>Re: How to edit/remove oem.xml</title>
      <link>https://communities.vmware.com/t5/ESXi-Discussions/How-to-edit-remove-oem-xml/m-p/2909567#M281689</link>
      <description>&lt;P&gt;I wouldn't think about this. Also 6.0 is not supported anymore &lt;img class="lia-deferred-image lia-image-emoji" src="https://communities.vmware.com/html/@DCF4E2F7991292CEECF250394DB2C2BC/emoticons/1f642.png" alt=":slightly_smiling_face:" title=":slightly_smiling_face:" /&gt;&lt;/P&gt;</description>
      <pubDate>Tue, 17 May 2022 21:03:43 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/ESXi-Discussions/How-to-edit-remove-oem-xml/m-p/2909567#M281689</guid>
      <dc:creator>aakalan</dc:creator>
      <dc:date>2022-05-17T21:03:43Z</dc:date>
    </item>
    <item>
      <title>Re: How to edit/remove oem.xml</title>
      <link>https://communities.vmware.com/t5/ESXi-Discussions/How-to-edit-remove-oem-xml/m-p/2909577#M281692</link>
      <description>&lt;P&gt;&lt;a href="https://communities.vmware.com/t5/user/viewprofilepage/user-id/1006701"&gt;@aakalan&lt;/a&gt;&amp;nbsp;&lt;BR /&gt;Why do you suggest not to edit files just because you would not do it ?&lt;BR /&gt;The scenario here looks like a very good reason to edit this file - and your argument that 6.0 is not supported anymore is completely irrelevant in this case.&lt;BR /&gt;&lt;BR /&gt;Ulli&lt;/P&gt;</description>
      <pubDate>Tue, 17 May 2022 22:28:40 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/ESXi-Discussions/How-to-edit-remove-oem-xml/m-p/2909577#M281692</guid>
      <dc:creator>continuum</dc:creator>
      <dc:date>2022-05-17T22:28:40Z</dc:date>
    </item>
    <item>
      <title>Re: How to edit/remove oem.xml</title>
      <link>https://communities.vmware.com/t5/ESXi-Discussions/How-to-edit-remove-oem-xml/m-p/2909578#M281693</link>
      <description>&lt;P&gt;When you cant edit or delete a file in /etc try this approach.&lt;BR /&gt;&lt;A href="https://kb.vmware.com/s/article/2043564" target="_blank"&gt;https://kb.vmware.com/s/article/2043564&lt;/A&gt;&lt;BR /&gt;Maybe you can get access at boot-time.&lt;BR /&gt;Is your state.tgz encrypted ? - if not you could eventually remove the file or replace it with a fixed one by repackaging the state.tgz&lt;/P&gt;&lt;P&gt;Ulli&lt;/P&gt;</description>
      <pubDate>Tue, 17 May 2022 22:44:37 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/ESXi-Discussions/How-to-edit-remove-oem-xml/m-p/2909578#M281693</guid>
      <dc:creator>continuum</dc:creator>
      <dc:date>2022-05-17T22:44:37Z</dc:date>
    </item>
    <item>
      <title>Re: How to edit/remove oem.xml</title>
      <link>https://communities.vmware.com/t5/ESXi-Discussions/How-to-edit-remove-oem-xml/m-p/2909874#M281739</link>
      <description>&lt;P&gt;Thanks...I'll take a look.&amp;nbsp; As I said, it's just a cosmetic/UI issue that doesn't affect functionality whatsoever.&amp;nbsp; I just don't login to the console very often (no need to), and I always do a double-take seeing the warning and double-check to make sure that yes, I'm on 7.x.&lt;/P&gt;</description>
      <pubDate>Wed, 18 May 2022 21:24:35 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/ESXi-Discussions/How-to-edit-remove-oem-xml/m-p/2909874#M281739</guid>
      <dc:creator>petersonmd</dc:creator>
      <dc:date>2022-05-18T21:24:35Z</dc:date>
    </item>
  </channel>
</rss>

