<?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: Patching ESXi custom images (HPE) with Update Manager - can I use the default repository? in VMware vSphere™ Discussions</title>
    <link>https://communities.vmware.com/t5/VMware-vSphere-Discussions/Patching-ESXi-custom-images-HPE-with-Update-Manager-can-I-use/m-p/1404223#M15550</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Yes you can. The VMware repository for ESXi specific updates/patches and the HPE repository for HP specific driver and management agents updates.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Fri, 28 Sep 2018 14:16:54 GMT</pubDate>
    <dc:creator>homerzzz</dc:creator>
    <dc:date>2018-09-28T14:16:54Z</dc:date>
    <item>
      <title>Patching ESXi custom images (HPE) with Update Manager - can I use the default repository?</title>
      <link>https://communities.vmware.com/t5/VMware-vSphere-Discussions/Patching-ESXi-custom-images-HPE-with-Update-Manager-can-I-use/m-p/1404222#M15549</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi all,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;we are using ESXi 6.5 on HPE ProLiant DL380 Gen8/Gen9 servers and installed them with the corresponding ESXi custom images from HPE. Regarding patching: Can we use the VMware default repository in VMware Update Manager or do we have to use a different repository (i.e. from HPE) in order to install regular ESXi patches?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;In the past we did the following:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;- For clean installations and upgrades (i.e. from 5.5 to 6.0) we used the custom images&lt;/P&gt;&lt;P&gt;- For normal patches within the same major version we used the VMware repository&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;However, since it's been a while that we patched ESXi I'm not sure this is still the right procedure. I would appreciate if someone could clarify this.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks&lt;BR /&gt;Michael&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 28 Sep 2018 14:00:32 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/VMware-vSphere-Discussions/Patching-ESXi-custom-images-HPE-with-Update-Manager-can-I-use/m-p/1404222#M15549</guid>
      <dc:creator>Support_MDM</dc:creator>
      <dc:date>2018-09-28T14:00:32Z</dc:date>
    </item>
    <item>
      <title>Re: Patching ESXi custom images (HPE) with Update Manager - can I use the default repository?</title>
      <link>https://communities.vmware.com/t5/VMware-vSphere-Discussions/Patching-ESXi-custom-images-HPE-with-Update-Manager-can-I-use/m-p/1404223#M15550</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Yes you can. The VMware repository for ESXi specific updates/patches and the HPE repository for HP specific driver and management agents updates.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 28 Sep 2018 14:16:54 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/VMware-vSphere-Discussions/Patching-ESXi-custom-images-HPE-with-Update-Manager-can-I-use/m-p/1404223#M15550</guid>
      <dc:creator>homerzzz</dc:creator>
      <dc:date>2018-09-28T14:16:54Z</dc:date>
    </item>
    <item>
      <title>Re: Patching ESXi custom images (HPE) with Update Manager - can I use the default repository?</title>
      <link>https://communities.vmware.com/t5/VMware-vSphere-Discussions/Patching-ESXi-custom-images-HPE-with-Update-Manager-can-I-use/m-p/1404224#M15551</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;thanks for your reply. I've also asked VMware support about this and they told me that I should use custom images for updating hosts that were installed with custom images. They said this is because if we update using the VMware standard repository it is possible that custom drivers are replaced by default ones.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;However, I'm not sure whether this is correct. The document &lt;STRONG&gt;Deploying and updating VMware vSphere on HPE ProLiant servers &lt;/STRONG&gt;from HP states the following:&lt;/P&gt;&lt;P&gt;&lt;span class="lia-inline-image-display-wrapper" image-alt="pastedImage_1.png"&gt;&lt;img src="https://communities.vmware.com/t5/image/serverpage/image-id/4896iDB6EBF62F03C1C12/image-size/large?v=v2&amp;amp;px=999" role="button" title="pastedImage_1.png" alt="pastedImage_1.png" /&gt;&lt;/span&gt;&lt;/P&gt;&lt;P&gt;&lt;A href="https://h20195.www2.hpe.com/V2/GetPDF.aspx/4AA4-7994ENW.pdf" title="https://h20195.www2.hpe.com/V2/GetPDF.aspx/4AA4-7994ENW.pdf"&gt;https://h20195.www2.hpe.com/V2/GetPDF.aspx/4AA4-7994ENW.pdf&lt;/A&gt; &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;In addition to that, the &lt;STRONG style="mso-fareast-font-family: Calibri; mso-ansi-language: DE; mso-fareast-theme-font: minor-latin; mso-fareast-language: EN-US; font-size: 11pt; font-family: 'Calibri',sans-serif; mso-bidi-language: AR-SA;"&gt;HPE VMware ESXi and vSphere 5.x, 6.x and Updates Getting Started Guide&lt;/STRONG&gt;&lt;SPAN style="font-family: 'Calibri',sans-serif; font-size: 11pt; mso-fareast-font-family: Calibri; mso-fareast-theme-font: minor-latin; mso-ansi-language: DE; mso-fareast-language: EN-US; mso-bidi-language: AR-SA;"&gt; also states that patches to VMware are provided by VMware and patches for HP components are provided by HP:&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="font-family: 'Calibri',sans-serif; font-size: 11pt; mso-fareast-font-family: Calibri; mso-fareast-theme-font: minor-latin; mso-ansi-language: DE; mso-fareast-language: EN-US; mso-bidi-language: AR-SA;"&gt;&lt;span class="lia-inline-image-display-wrapper" image-alt="pastedImage_2.png"&gt;&lt;img src="https://communities.vmware.com/t5/image/serverpage/image-id/4897iD0236C49D58F9C1F/image-size/large?v=v2&amp;amp;px=999" role="button" title="pastedImage_2.png" alt="pastedImage_2.png" /&gt;&lt;/span&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;A href="https://support.hpe.com/hpsc/doc/public/display?docId=c05063275" title="https://support.hpe.com/hpsc/doc/public/display?docId=c05063275"&gt;https://support.hpe.com/hpsc/doc/public/display?docId=c05063275&lt;/A&gt; &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I usually would say:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;1. Within a major version, we update ESXi with ESXi patches from the VMware repository and HP patches from the HP repository&lt;/P&gt;&lt;P&gt;2. For major upgrades, i.e. 6.0 to 6.5, we use custom images&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;But now I'm not sure about what VMware support has stated about driver replacements. Has anyone experienced this yet?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks&lt;BR /&gt;Michael&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 01 Oct 2018 11:51:39 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/VMware-vSphere-Discussions/Patching-ESXi-custom-images-HPE-with-Update-Manager-can-I-use/m-p/1404224#M15551</guid>
      <dc:creator>Support_MDM</dc:creator>
      <dc:date>2018-10-01T11:51:39Z</dc:date>
    </item>
    <item>
      <title>Re: Patching ESXi custom images (HPE) with Update Manager - can I use the default repository?</title>
      <link>https://communities.vmware.com/t5/VMware-vSphere-Discussions/Patching-ESXi-custom-images-HPE-with-Update-Manager-can-I-use/m-p/1404225#M15552</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Did you ever get anymore clarification on this issue?&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 29 Mar 2019 18:18:10 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/VMware-vSphere-Discussions/Patching-ESXi-custom-images-HPE-with-Update-Manager-can-I-use/m-p/1404225#M15552</guid>
      <dc:creator>kieron85</dc:creator>
      <dc:date>2019-03-29T18:18:10Z</dc:date>
    </item>
  </channel>
</rss>

