<?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>SupreetK Tracker</title>
    <link>https://communities.vmware.com/wbsdv95928/tracker</link>
    <description>SupreetK Tracker</description>
    <pubDate>Sat, 11 Nov 2023 22:54:43 GMT</pubDate>
    <dc:date>2023-11-11T22:54:43Z</dc:date>
    <item>
      <title>Re: The VMware Authorization Service service terminated with the following service-specific error:  %%6000009</title>
      <link>https://communities.vmware.com/t5/VMware-Workstation-Pro/The-VMware-Authorization-Service-service-terminated-with-the/m-p/522571#M28069</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;More details in the below link -&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;A href="http://www.vbrain.info/2018/01/15/workstation-14-upgrade-authorization-service-error-6000009/" title="http://www.vbrain.info/2018/01/15/workstation-14-upgrade-authorization-service-error-6000009/"&gt;http://www.vbrain.info/2018/01/15/workstation-14-upgrade-authorization-service-error-6000009/&lt;/A&gt; ​&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;-Supreet&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Sun, 17 Nov 2019 11:59:33 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/VMware-Workstation-Pro/The-VMware-Authorization-Service-service-terminated-with-the/m-p/522571#M28069</guid>
      <dc:creator>SupreetK</dc:creator>
      <dc:date>2019-11-17T11:59:33Z</dc:date>
    </item>
    <item>
      <title>Re: Unattended VMtools failing on Windows Enterprise 1909</title>
      <link>https://communities.vmware.com/t5/Virtual-Machine-Guest-OS-and-VM/Unattended-VMtools-failing-on-Windows-Enterprise-1909/m-p/2268963#M40682</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;What errors do you see in the VMware Tools log file?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN data-aura-rendered-by="23:122;a" style="font-family: courier new,courier,monospace;"&gt;* %temp%\vminst.log&lt;BR /&gt;* %temp%\vmmsi.log&lt;BR /&gt;* C:\windows\temp\vminst.log&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;-Supreet&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Sun, 17 Nov 2019 11:56:15 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/Virtual-Machine-Guest-OS-and-VM/Unattended-VMtools-failing-on-Windows-Enterprise-1909/m-p/2268963#M40682</guid>
      <dc:creator>SupreetK</dc:creator>
      <dc:date>2019-11-17T11:56:15Z</dc:date>
    </item>
    <item>
      <title>Re: vCenter Converter Standalone 6.2.0 missing useSudo flag</title>
      <link>https://communities.vmware.com/t5/Converter-Standalone-Discussions/vCenter-Converter-Standalone-6-2-0-missing-useSudo-flag/m-p/1849925#M28707</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hello TT,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;The configuration is present in the converter-worker.xml and is set to auto. Can you just change this and let us know if it works?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; --&amp;gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; &amp;lt;useSudo&amp;gt;auto&amp;lt;/useSudo&amp;gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; &amp;lt;!--&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;-Supreet&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Sun, 17 Nov 2019 11:17:17 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/Converter-Standalone-Discussions/vCenter-Converter-Standalone-6-2-0-missing-useSudo-flag/m-p/1849925#M28707</guid>
      <dc:creator>SupreetK</dc:creator>
      <dc:date>2019-11-17T11:17:17Z</dc:date>
    </item>
    <item>
      <title>Re: Vcenter Migrate problem</title>
      <link>https://communities.vmware.com/t5/VMware-vCenter-Discussions/Vcenter-Migrate-problem/m-p/1849993#M27560</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;As per my understanding, yes you have to. EVC cannot be enabled on a cluster which has VMs in powered on state. Please check step-21 in the below KB -&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;A href="https://kb.vmware.com/s/article/1013111" title="https://kb.vmware.com/s/article/1013111"&gt;VMware Knowledge Base&lt;/A&gt; ​&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;-Supreet&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Sun, 17 Nov 2019 10:42:29 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/VMware-vCenter-Discussions/Vcenter-Migrate-problem/m-p/1849993#M27560</guid>
      <dc:creator>SupreetK</dc:creator>
      <dc:date>2019-11-17T10:42:29Z</dc:date>
    </item>
    <item>
      <title>Re: BSOD xen.sys</title>
      <link>https://communities.vmware.com/t5/Virtual-Machine-Guest-OS-and-VM/BSOD-xen-sys/m-p/2269919#M40693</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hello Dennis,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Don't think this is related to ESXi. Please check the below links -&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;A href="https://support.citrix.com/article/CTX216145" title="https://support.citrix.com/article/CTX216145"&gt;Windows VM BSOD : "BSOD 0x7E xen.sys" After updating Xentools&lt;/A&gt; ​&lt;/P&gt;&lt;P&gt;&lt;A href="https://www.keithit.com/system-thread-exception-not-handled-xensys-bsod_post2018.html" title="https://www.keithit.com/system-thread-exception-not-handled-xensys-bsod_post2018.html"&gt;https://www.keithit.com/system-thread-exception-not-handled-xensys-bsod_post2018.html&lt;/A&gt; ​&lt;/P&gt;&lt;P&gt;&lt;A href="https://www.tediosity.com/windows-2012-r2-system_thread_exception_not_handled-xen-sys/" title="https://www.tediosity.com/windows-2012-r2-system_thread_exception_not_handled-xen-sys/"&gt;SYSTEM_THREAD_EXCEPTION_NOT_HANDLED (xen.sys)&lt;/A&gt; &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;-Supreet&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Sun, 17 Nov 2019 10:37:01 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/Virtual-Machine-Guest-OS-and-VM/BSOD-xen-sys/m-p/2269919#M40693</guid>
      <dc:creator>SupreetK</dc:creator>
      <dc:date>2019-11-17T10:37:01Z</dc:date>
    </item>
    <item>
      <title>Re: Difference between "vmkload_mod xxxxx" and "esxcfg-module xxxxx"</title>
      <link>https://communities.vmware.com/t5/ESXi-Discussions/Difference-between-quot-vmkload-mod-xxxxx-quot-and-quot-esxcfg/m-p/2270634#M221370</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;vmkload_mod is used majorly for getting the module details and unloading it. Whereas with esxcfg-module, we can get/set/enable/disable/query module/module parameters and lot of other things. Moreover, both of these are now deprecated. &amp;lt;esxcli system module&amp;gt; should be used going forward.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;-Supreet&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Sun, 17 Nov 2019 08:42:19 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/ESXi-Discussions/Difference-between-quot-vmkload-mod-xxxxx-quot-and-quot-esxcfg/m-p/2270634#M221370</guid>
      <dc:creator>SupreetK</dc:creator>
      <dc:date>2019-11-17T08:42:19Z</dc:date>
    </item>
    <item>
      <title>Re: Lenovo ST250 ESXi VM Disappearing when host reboots</title>
      <link>https://communities.vmware.com/t5/ESXi-Discussions/Lenovo-ST250-ESXi-VM-Disappearing-when-host-reboots/m-p/522925#M43679</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;By any chance, do you have the SSD controller in pass-thru mode?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;A href="https://serverfault.com/questions/941551/esxi-6-5-unregistering-all-guest-vms-on-reboot" title="https://serverfault.com/questions/941551/esxi-6-5-unregistering-all-guest-vms-on-reboot"&gt;https://serverfault.com/questions/941551/esxi-6-5-unregistering-all-guest-vms-on-reboot&lt;/A&gt; ​&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;-Supreet&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Sun, 17 Nov 2019 08:24:47 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/ESXi-Discussions/Lenovo-ST250-ESXi-VM-Disappearing-when-host-reboots/m-p/522925#M43679</guid>
      <dc:creator>SupreetK</dc:creator>
      <dc:date>2019-11-17T08:24:47Z</dc:date>
    </item>
    <item>
      <title>Re: Vcenter Migrate problem</title>
      <link>https://communities.vmware.com/t5/VMware-vCenter-Discussions/Vcenter-Migrate-problem/m-p/1849990#M27557</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hello Imran,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;EVC cannot be enabled (or the host cannot be admitted into a EVC enabled cluster) on a cluster with VMs being in powered on status.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;A href="https://communities.vmware.com/thread/468999"&gt;EVC Mode - Intel Merom Gen - Xeon E5345 - E5-2690 - The host cannot be admitted the cluster's current EVC mode. Powered-…&lt;/A&gt; &lt;/P&gt;&lt;P&gt;&lt;A href="https://kb.vmware.com/s/article/1013111" title="https://kb.vmware.com/s/article/1013111"&gt;VMware Knowledge Base&lt;/A&gt; ​&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;-Supreet&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Sun, 17 Nov 2019 08:06:51 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/VMware-vCenter-Discussions/Vcenter-Migrate-problem/m-p/1849990#M27557</guid>
      <dc:creator>SupreetK</dc:creator>
      <dc:date>2019-11-17T08:06:51Z</dc:date>
    </item>
    <item>
      <title>Re: Failed to migrate vSphere Standard Switch to Distrbuted Switch</title>
      <link>https://communities.vmware.com/t5/VMware-vCenter-Discussions/Failed-to-migrate-vSphere-Standard-Switch-to-Distrbuted-Switch/m-p/503369#M7828</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Can you check &lt;A href="https://communities.vmware.com/thread/572001"&gt;Cannot migrate VMkernel adapter to distrubiute port group&lt;/A&gt;​?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;- Supreet&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 05 Feb 2019 00:22:29 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/VMware-vCenter-Discussions/Failed-to-migrate-vSphere-Standard-Switch-to-Distrbuted-Switch/m-p/503369#M7828</guid>
      <dc:creator>SupreetK</dc:creator>
      <dc:date>2019-02-05T00:22:29Z</dc:date>
    </item>
    <item>
      <title>Re: Disks showing Healthy (At Risk) after expansion</title>
      <link>https://communities.vmware.com/t5/VMware-vSphere-Discussions/Disks-showing-Healthy-At-Risk-after-expansion/m-p/500748#M6989</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Check if the disk is reporting any errors &lt;A href="https://docs.vmware.com/en/VMware-vSphere/6.5/com.vmware.vsphere.storage.doc/GUID-4460A049-11BF-4924-9B99-3474251261B4.html" title="https://docs.vmware.com/en/VMware-vSphere/6.5/com.vmware.vsphere.storage.doc/GUID-4460A049-11BF-4924-9B99-3474251261B4.html"&gt;Checking and Repairing Virtual Disks&lt;/A&gt;​. For the datastore in which the disk in question is residing, do you see any read/write failures in the vmkernel.log or any other events for that matter? If the above does not help, create a new disk and copy the data or perform a v2v via File level cloning from within the guest operating system.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;- Supreet &lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Sun, 03 Feb 2019 23:23:51 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/VMware-vSphere-Discussions/Disks-showing-Healthy-At-Risk-after-expansion/m-p/500748#M6989</guid>
      <dc:creator>SupreetK</dc:creator>
      <dc:date>2019-02-03T23:23:51Z</dc:date>
    </item>
    <item>
      <title>Re: Host Hardware Health Not Showing Up vCenter 6.7</title>
      <link>https://communities.vmware.com/t5/VMware-vSphere-Discussions/Host-Hardware-Health-Not-Showing-Up-vCenter-6-7/m-p/501716#M7121</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;What is the red alarm on both the hosts? Are they actively connected to the vCenter and in sync?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;- Supreet&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Sun, 03 Feb 2019 23:10:55 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/VMware-vSphere-Discussions/Host-Hardware-Health-Not-Showing-Up-vCenter-6-7/m-p/501716#M7121</guid>
      <dc:creator>SupreetK</dc:creator>
      <dc:date>2019-02-03T23:10:55Z</dc:date>
    </item>
    <item>
      <title>Re: vCenter 6.7U1 file based backups using FileZilla FTPS Server</title>
      <link>https://communities.vmware.com/t5/VMware-vCenter-Discussions/vCenter-6-7U1-file-based-backups-using-FileZilla-FTPS-Server/m-p/493462#M7097</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;When you grep for the word 'address' in the file &amp;lt;/etc/systemd/network/10-eth0.network&amp;gt;, how many rows are seen? Ideally, there should be just one.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;- Supreet&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 30 Jan 2019 23:24:48 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/VMware-vCenter-Discussions/vCenter-6-7U1-file-based-backups-using-FileZilla-FTPS-Server/m-p/493462#M7097</guid>
      <dc:creator>SupreetK</dc:creator>
      <dc:date>2019-01-30T23:24:48Z</dc:date>
    </item>
    <item>
      <title>Re: vCenter 6.7 backup config error "union with a field not required for this case = end_time"</title>
      <link>https://communities.vmware.com/t5/VMware-vCenter-Discussions/vCenter-6-7-backup-config-error-quot-union-with-a-field-not/m-p/491964#M7000</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Have you checked this &lt;A href="https://www.techcrumble.net/2018/06/vcsa-6-7-backup-failed/" title="https://www.techcrumble.net/2018/06/vcsa-6-7-backup-failed/"&gt;https://www.techcrumble.net/2018/06/vcsa-6-7-backup-failed/&lt;/A&gt; already?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;- Supreet&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 30 Jan 2019 00:17:59 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/VMware-vCenter-Discussions/vCenter-6-7-backup-config-error-quot-union-with-a-field-not/m-p/491964#M7000</guid>
      <dc:creator>SupreetK</dc:creator>
      <dc:date>2019-01-30T00:17:59Z</dc:date>
    </item>
    <item>
      <title>Re: Logging onto vCenter 6.5 with Powercli?</title>
      <link>https://communities.vmware.com/t5/VMware-vSphere-Discussions/Logging-onto-vCenter-6-5-with-Powercli/m-p/486228#M5300</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Have you already validated the privilege error that the window is reporting?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;- Supreet&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 28 Jan 2019 05:34:16 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/VMware-vSphere-Discussions/Logging-onto-vCenter-6-5-with-Powercli/m-p/486228#M5300</guid>
      <dc:creator>SupreetK</dc:creator>
      <dc:date>2019-01-28T05:34:16Z</dc:date>
    </item>
    <item>
      <title>Re: (Releasebuild-10302608) panic bora/vmkernel/main/dlmalloc.c c:4924 - Usage error in dlmalloc</title>
      <link>https://communities.vmware.com/t5/VMware-vSphere-Discussions/Releasebuild-10302608-panic-bora-vmkernel-main-dlmalloc-c-c-4924/m-p/481993#M4765</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Relevant KB is &lt;A href="https://kb.vmware.com/s/article/55650" title="https://kb.vmware.com/s/article/55650"&gt;VMware Knowledge Base&lt;/A&gt;​. Issue has been fixed in 6.7 EP-5 (build-10764712).&lt;SPAN style="color: #000000; font-family: MetropolisRegular;"&gt;&lt;BR /&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;- Supreet&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Sun, 27 Jan 2019 23:42:02 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/VMware-vSphere-Discussions/Releasebuild-10302608-panic-bora-vmkernel-main-dlmalloc-c-c-4924/m-p/481993#M4765</guid>
      <dc:creator>SupreetK</dc:creator>
      <dc:date>2019-01-27T23:42:02Z</dc:date>
    </item>
    <item>
      <title>Re: Upgrade of ESXi 5.5  host fails altbootbank error</title>
      <link>https://communities.vmware.com/t5/VMware-vSphere-Discussions/Upgrade-of-ESXi-5-5-host-fails-altbootbank-error/m-p/510718#M8305</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Is the host booting off an SD card? If yes, it might have turned faulty. Try to reseat it once.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Cheers,&lt;/P&gt;&lt;P&gt;Supreet&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 08 Jan 2019 19:19:58 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/VMware-vSphere-Discussions/Upgrade-of-ESXi-5-5-host-fails-altbootbank-error/m-p/510718#M8305</guid>
      <dc:creator>SupreetK</dc:creator>
      <dc:date>2019-01-08T19:19:58Z</dc:date>
    </item>
    <item>
      <title>Re: Upgrade of ESXi 5.5  host fails altbootbank error</title>
      <link>https://communities.vmware.com/t5/VMware-vSphere-Discussions/Upgrade-of-ESXi-5-5-host-fails-altbootbank-error/m-p/510716#M8303</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hate to say this but, a re-installation might be the order of the day :smileyplain:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Cheers,&lt;/P&gt;&lt;P&gt;Supreet&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 08 Jan 2019 19:16:11 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/VMware-vSphere-Discussions/Upgrade-of-ESXi-5-5-host-fails-altbootbank-error/m-p/510716#M8303</guid>
      <dc:creator>SupreetK</dc:creator>
      <dc:date>2019-01-08T19:16:11Z</dc:date>
    </item>
    <item>
      <title>Re: Upgrade of ESXi 5.5  host fails altbootbank error</title>
      <link>https://communities.vmware.com/t5/VMware-vSphere-Discussions/Upgrade-of-ESXi-5-5-host-fails-altbootbank-error/m-p/510714#M8301</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Most likely, there is an issue in reading the blocks. When the file system check fails, what errors do we see in the vmkernel.log?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Cheers,&lt;/P&gt;&lt;P&gt;Supreet&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 08 Jan 2019 16:04:07 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/VMware-vSphere-Discussions/Upgrade-of-ESXi-5-5-host-fails-altbootbank-error/m-p/510714#M8301</guid>
      <dc:creator>SupreetK</dc:creator>
      <dc:date>2019-01-08T16:04:07Z</dc:date>
    </item>
    <item>
      <title>Re: NIC firmware upgradation for esxi hosts</title>
      <link>https://communities.vmware.com/t5/VMware-vSphere-Discussions/NIC-firmware-upgradation-for-esxi-hosts/m-p/487244#M5456</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Depends on what hardware it is. Below are some references -&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;A href="http://h17007.www1.hpe.com/docs/enterprise/servers/icsp/webhelp/content/s_osdbuildplan_how_fw_add.html" title="http://h17007.www1.hpe.com/docs/enterprise/servers/icsp/webhelp/content/s_osdbuildplan_how_fw_add.html"&gt;Upgrade the firmware on my ProLiant server&lt;/A&gt;​ --&amp;gt; HPE&lt;/P&gt;&lt;P&gt;&lt;A href="https://www.dell.com/support/contents/us/en/04/article/product-support/self-support-knowledgebase/enterprise-resource-center/systemsmanagement/firmware-and-drivers" title="https://www.dell.com/support/contents/us/en/04/article/product-support/self-support-knowledgebase/enterprise-resource-center/systemsmanagement/firmware-and-drivers"&gt;Updating Firmware and Drivers on Dell EMC PowerEdge Servers | Dell US&lt;/A&gt; --&amp;gt; Dell&lt;/P&gt;&lt;P&gt;&lt;A href="https://www.cisco.com/c/en/us/td/docs/unified_computing/ucs/c/sw/lomug/2-0-x/3_0/b_huu_3_0_1/b_huu_2_0_13_chapter_011.html" title="https://www.cisco.com/c/en/us/td/docs/unified_computing/ucs/c/sw/lomug/2-0-x/3_0/b_huu_3_0_1/b_huu_2_0_13_chapter_011.html"&gt;Cisco Host Upgrade Utility User Guide - Updating the Firmware on Cisco UCS C-Series Servers [Cisco UCS C-Series Rack Se…&lt;/A&gt; --&amp;gt; Cisco&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Cheers,&lt;/P&gt;&lt;P&gt;Supreet&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Sat, 08 Dec 2018 08:25:47 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/VMware-vSphere-Discussions/NIC-firmware-upgradation-for-esxi-hosts/m-p/487244#M5456</guid>
      <dc:creator>SupreetK</dc:creator>
      <dc:date>2018-12-08T08:25:47Z</dc:date>
    </item>
    <item>
      <title>Re: vSphere Upgrade Failed</title>
      <link>https://communities.vmware.com/t5/VMware-vSphere-Discussions/vSphere-Upgrade-Failed/m-p/1400338#M15302</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Please check the KB - &lt;A href="https://kb.vmware.com/s/article/59157" title="https://kb.vmware.com/s/article/59157"&gt;VMware Knowledge Base&lt;/A&gt;​ &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Cheers,&lt;/P&gt;&lt;P&gt;Supreet&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Sun, 02 Dec 2018 21:51:20 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/VMware-vSphere-Discussions/vSphere-Upgrade-Failed/m-p/1400338#M15302</guid>
      <dc:creator>SupreetK</dc:creator>
      <dc:date>2018-12-02T21:51:20Z</dc:date>
    </item>
  </channel>
</rss>

