<?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 Wisdom in ESXi Discussions</title>
    <link>https://communities.vmware.com/t5/ESXi-Discussions/Patching-Wisdom/m-p/2670008#M258544</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;I believe the difference in Express vs. patch is one vs multiple bulletins in the patch. I try to stay at the latest patch or update level since it typically fixes an issue I have run into. There is always the risk of a new problem being introduced. Read the release notes.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Tue, 27 Jan 2015 16:40:40 GMT</pubDate>
    <dc:creator>homerzzz</dc:creator>
    <dc:date>2015-01-27T16:40:40Z</dc:date>
    <item>
      <title>Patching Wisdom</title>
      <link>https://communities.vmware.com/t5/ESXi-Discussions/Patching-Wisdom/m-p/2670007#M258543</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;What is the difference between an ESXi patch and an ESXi express patch?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;A href="http://kb.vmware.com/selfservice/microsites/search.do?language=en_US&amp;amp;cmd=displayKC&amp;amp;externalId=1014508" title="http://kb.vmware.com/selfservice/microsites/search.do?language=en_US&amp;amp;cmd=displayKC&amp;amp;externalId=1014508"&gt;VMware KB: Correlating VMware products build numbers to update levels &lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Are there risks involved in installing the latest patch prior to people finding out what things might break by using it or is that not an issue with ESXi?&lt;/P&gt;&lt;P&gt;Do I always want the latest patch?&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 27 Jan 2015 16:07:46 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/ESXi-Discussions/Patching-Wisdom/m-p/2670007#M258543</guid>
      <dc:creator>TheVMinator</dc:creator>
      <dc:date>2015-01-27T16:07:46Z</dc:date>
    </item>
    <item>
      <title>Re: Patching Wisdom</title>
      <link>https://communities.vmware.com/t5/ESXi-Discussions/Patching-Wisdom/m-p/2670008#M258544</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;I believe the difference in Express vs. patch is one vs multiple bulletins in the patch. I try to stay at the latest patch or update level since it typically fixes an issue I have run into. There is always the risk of a new problem being introduced. Read the release notes.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 27 Jan 2015 16:40:40 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/ESXi-Discussions/Patching-Wisdom/m-p/2670008#M258544</guid>
      <dc:creator>homerzzz</dc:creator>
      <dc:date>2015-01-27T16:40:40Z</dc:date>
    </item>
    <item>
      <title>Re: Patching Wisdom</title>
      <link>https://communities.vmware.com/t5/ESXi-Discussions/Patching-Wisdom/m-p/2670009#M258545</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;OK thanks - what is the best policy to balance the risk of a new problem being introduced vs. out of date versions?&amp;nbsp; Is that latest full update such as right now would be "ESXi 5.5 Update 2"? This way there is at least 4 months for any terrible problems to be known on it.&amp;nbsp; Thoughts / opinions?&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 27 Jan 2015 16:45:56 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/ESXi-Discussions/Patching-Wisdom/m-p/2670009#M258545</guid>
      <dc:creator>TheVMinator</dc:creator>
      <dc:date>2015-01-27T16:45:56Z</dc:date>
    </item>
    <item>
      <title>Re: Patching Wisdom</title>
      <link>https://communities.vmware.com/t5/ESXi-Discussions/Patching-Wisdom/m-p/2670010#M258546</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;The best policy patch for me is test the latest patches on non production environment before apply them on production... and of course, read the release notes before plan the upgrade, because some patches apply only for specific problems/configurations that may not apply for you.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 27 Jan 2015 16:50:11 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/ESXi-Discussions/Patching-Wisdom/m-p/2670010#M258546</guid>
      <dc:creator>rcporto</dc:creator>
      <dc:date>2015-01-27T16:50:11Z</dc:date>
    </item>
    <item>
      <title>Re: Patching Wisdom</title>
      <link>https://communities.vmware.com/t5/ESXi-Discussions/Patching-Wisdom/m-p/2670011#M258547</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Thanks - can you be more specific about what you do to test the release in your non-production environment?&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 27 Jan 2015 16:52:17 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/ESXi-Discussions/Patching-Wisdom/m-p/2670011#M258547</guid>
      <dc:creator>TheVMinator</dc:creator>
      <dc:date>2015-01-27T16:52:17Z</dc:date>
    </item>
    <item>
      <title>Re: Patching Wisdom</title>
      <link>https://communities.vmware.com/t5/ESXi-Discussions/Patching-Wisdom/m-p/2670012#M258548</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Regular patches are planned one, ESXi patch usually gets release every 3 (not strict, it changes) months(It will have bug fixes, important, critical, catastrophic, security fixes etc) . Express patch on the other hand is not planned one: It usally gets released when there is issue which is having impact on multiple customers. Also critical security fixes get into the Express patches.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Checking release notes/KBs on particular patch (either regular patch or express) will help you to understand what is being fixed in the patch, based on that you can decide whether you really need to apply the patch right away or you can wait. If fixes does not impact you, then you need not to apply the patch. However, it is recommended that you apply the latest patch. Sometime you can not know when particular issue may pop up in your environment which was fixed in patch.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Testing on non-production environment usually is not must (people do it just to be on safer side), they look into release notes/KBs of the particular patch and test fixed issues in the patch (those matter to them) to make sure whether fixed issues work fine or not. (some time they check whether upgrade workflow works or not ).&amp;nbsp; If it works then they go ahead and apply the patch in production.&amp;nbsp; &lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 27 Jan 2015 17:51:42 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/ESXi-Discussions/Patching-Wisdom/m-p/2670012#M258548</guid>
      <dc:creator>vThinkBeyondVM</dc:creator>
      <dc:date>2015-01-27T17:51:42Z</dc:date>
    </item>
    <item>
      <title>Re: Patching Wisdom</title>
      <link>https://communities.vmware.com/t5/ESXi-Discussions/Patching-Wisdom/m-p/2670013#M258549</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;I will roll out the patches to our non-critical clusters first. Then I normally confirm typical functionality such as vMotion, sVmotion, HA, backups, replication and check hardware status. I also have all logs forwarded to Splunk which really aids in flushing out any errors. I'll usually wait a week before rolling the patch out to the critical clusters.&amp;nbsp; &lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 27 Jan 2015 17:57:26 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/ESXi-Discussions/Patching-Wisdom/m-p/2670013#M258549</guid>
      <dc:creator>homerzzz</dc:creator>
      <dc:date>2015-01-27T17:57:26Z</dc:date>
    </item>
  </channel>
</rss>

