<?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>IT_pilot Tracker</title>
    <link>https://communities.vmware.com/wbsdv95928/tracker</link>
    <description>IT_pilot Tracker</description>
    <pubDate>Tue, 21 Nov 2023 13:07:04 GMT</pubDate>
    <dc:date>2023-11-21T13:07:04Z</dc:date>
    <item>
      <title>Re: Invoke-VMScript returning 500 (Internal Server Error) , on VM which is attached to domain</title>
      <link>https://communities.vmware.com/t5/VMware-PowerCLI-Discussions/Invoke-VMScript-returning-500-Internal-Server-Error-on-VM-which/m-p/2856351#M102243</link>
      <description>&lt;P&gt;And when you go under this Account, the folder does not say that you need to have administrator rights?&lt;/P&gt;</description>
      <pubDate>Thu, 08 Jul 2021 11:33:44 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/VMware-PowerCLI-Discussions/Invoke-VMScript-returning-500-Internal-Server-Error-on-VM-which/m-p/2856351#M102243</guid>
      <dc:creator>IT_pilot</dc:creator>
      <dc:date>2021-07-08T11:33:44Z</dc:date>
    </item>
    <item>
      <title>Re: Expansion of the system disk of the Windows cluster led to errors and migration of the role to the second node.</title>
      <link>https://communities.vmware.com/t5/VMware-vSphere-Discussions/Expansion-of-the-system-disk-of-the-Windows-cluster-led-to/m-p/447237#M384</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;I changed the system disk&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 05 Jun 2019 11:11:21 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/VMware-vSphere-Discussions/Expansion-of-the-system-disk-of-the-Windows-cluster-led-to/m-p/447237#M384</guid>
      <dc:creator>IT_pilot</dc:creator>
      <dc:date>2019-06-05T11:11:21Z</dc:date>
    </item>
    <item>
      <title>Expansion of the system disk of the Windows cluster led to errors and migration of the role to the second node.</title>
      <link>https://communities.vmware.com/t5/VMware-vSphere-Discussions/Expansion-of-the-system-disk-of-the-Windows-cluster-led-to/m-p/447235#M382</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;VMware ESXi, 6.5.0&lt;/P&gt;&lt;P&gt;Microsoft Windows Server 2008 R2&lt;/P&gt;&lt;P&gt;LSI Logic SAS&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN class="tlid-translation translation" lang="en"&gt;&lt;SPAN title=""&gt;A few seconds after the expansion of the system disk (via ESXi) such errors occurred&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN class="tlid-translation translation" lang="en"&gt;&lt;SPAN title=""&gt;Physical Disk: PNP: Failed to get volume info for disk resource Disk I, status 3 &lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN class="tlid-translation translation" lang="en"&gt;&lt;SPAN title=""&gt;Physical Disk: PNP: Failed to get volume info for disk resource Disk H, status 3 &lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN class="tlid-translation translation" lang="en"&gt;&lt;SPAN title=""&gt;Physical Disk: PNP: Failed to get volume info for disk resource Disk D, status 3 &lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN class="tlid-translation translation" lang="en"&gt;&lt;SPAN title=""&gt;Physical Disk: PNP: HardDiskpSetPnpUpdateTimePropertyWorker: status 0,&amp;nbsp; &lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN class="tlid-translation translation" lang="en"&gt;&lt;SPAN title=""&gt;IsAlive sanity check failed!, pending IO completed with status 1235.&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Microsoft-Windows-FailoverClustering&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; 1038&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; (18)&lt;/P&gt;&lt;P&gt;This event is logged when Ownership of cluster disk has been unexpectedly lost by this node&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN class="tlid-translation translation" lang="en"&gt;&lt;SPAN title=""&gt;The system disk was expanded first in the first node and 40 seconds later in the second.&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN title=""&gt;Six minutes after changing the disk size, the cluster role moved to the second node.&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN title=""&gt;Is this normal cluster behavior?&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;SPAN class="tlid-translation-gender-indicator translation-gender-indicator"&gt;&lt;/SPAN&gt;&lt;SPAN class="tlid-trans-verified-button trans-verified-button"&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 05 Jun 2019 09:38:54 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/VMware-vSphere-Discussions/Expansion-of-the-system-disk-of-the-Windows-cluster-led-to/m-p/447235#M382</guid>
      <dc:creator>IT_pilot</dc:creator>
      <dc:date>2019-06-05T09:38:54Z</dc:date>
    </item>
    <item>
      <title>Re: Cannot delete files in datastore?</title>
      <link>https://communities.vmware.com/t5/VMware-vSphere-Discussions/Cannot-delete-files-in-datastore/m-p/2267897#M28254</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Have you deleted this VM (menu: delete from disk)?&lt;/P&gt;&lt;P&gt;How exactly the files are damaged. For what reason?&lt;/P&gt;&lt;P&gt;You can connect to the host through WinSCP.&lt;/P&gt;&lt;P&gt;If everything is very bad, you may need to migrate other VMs from the datastore and recreate it.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 11 Apr 2019 09:05:36 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/VMware-vSphere-Discussions/Cannot-delete-files-in-datastore/m-p/2267897#M28254</guid>
      <dc:creator>IT_pilot</dc:creator>
      <dc:date>2019-04-11T09:05:36Z</dc:date>
    </item>
    <item>
      <title>Re: Cannot delete files in datastore?</title>
      <link>https://communities.vmware.com/t5/VMware-vSphere-Discussions/Cannot-delete-files-in-datastore/m-p/2267894#M28251</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;It's not entirely clear why you want to delete a folder. Have you completed storage vMotion, but you still have a folder named VM? Keep in mind that if you renamed a VM, the folder with its files does not change the name before migrating to another storage using storage vMotion and maybe you are trying to delete files of another VM.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 09 Apr 2019 06:35:39 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/VMware-vSphere-Discussions/Cannot-delete-files-in-datastore/m-p/2267894#M28251</guid>
      <dc:creator>IT_pilot</dc:creator>
      <dc:date>2019-04-09T06:35:39Z</dc:date>
    </item>
    <item>
      <title>Re: My ESXI is down.</title>
      <link>https://communities.vmware.com/t5/VMware-vSphere-Discussions/My-ESXI-is-down/m-p/2267088#M28179</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Perhaps it will be faster to connect another USB drive and try installing ESXi on it (different versions 6.5, 6.7). If the installation of all versions is not successful, then the problem is in the hardware. If any version is installed, then it is possible to HCL (Hardware Compatibility List). Sometimes reinstalling ESXi and setting it up is faster than looking for an error.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 09 Apr 2019 06:24:20 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/VMware-vSphere-Discussions/My-ESXI-is-down/m-p/2267088#M28179</guid>
      <dc:creator>IT_pilot</dc:creator>
      <dc:date>2019-04-09T06:24:20Z</dc:date>
    </item>
    <item>
      <title>Re: Unable to vMotion between 2 vCenter servers in different SSO domains</title>
      <link>https://communities.vmware.com/t5/VMware-PowerCLI-Discussions/Unable-to-vMotion-between-2-vCenter-servers-in-different-SSO/m-p/512396#M16808</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Maybe you are migrating VM between Distributed Switch and Standard Switch?&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 25 Jul 2018 10:02:11 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/VMware-PowerCLI-Discussions/Unable-to-vMotion-between-2-vCenter-servers-in-different-SSO/m-p/512396#M16808</guid>
      <dc:creator>IT_pilot</dc:creator>
      <dc:date>2018-07-25T10:02:11Z</dc:date>
    </item>
    <item>
      <title>Re: Unable to vMotion between 2 vCenter servers in different SSO domains</title>
      <link>https://communities.vmware.com/t5/VMware-PowerCLI-Discussions/Unable-to-vMotion-between-2-vCenter-servers-in-different-SSO/m-p/512389#M16801</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Try it in "manual mode" using the utility &lt;A href="https://labs.vmware.com/flings/cross-vcenter-workload-migration-utility#changelog" title="https://labs.vmware.com/flings/cross-vcenter-workload-migration-utility#changelog"&gt;Cross vCenter Workload Migration Utility&lt;/A&gt; &lt;/P&gt;&lt;P&gt;Maybe the problem is not in the script.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 25 Jul 2018 09:16:06 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/VMware-PowerCLI-Discussions/Unable-to-vMotion-between-2-vCenter-servers-in-different-SSO/m-p/512389#M16801</guid>
      <dc:creator>IT_pilot</dc:creator>
      <dc:date>2018-07-25T09:16:06Z</dc:date>
    </item>
    <item>
      <title>Re: Possible to deploy vSAN on one Node?</title>
      <link>https://communities.vmware.com/t5/VMware-vSAN-Discussions/Possible-to-deploy-vSAN-on-one-Node/m-p/1845518#M7328</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;vSAN data-at-rest encryption, is a VM encryption, adapted for use in a vSAN cluster. Therefore, this is not the same thing. And therefore it is used not because it is super encryption, but because it is required by vSAN technology.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 24 Jul 2018 09:48:40 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/VMware-vSAN-Discussions/Possible-to-deploy-vSAN-on-one-Node/m-p/1845518#M7328</guid>
      <dc:creator>IT_pilot</dc:creator>
      <dc:date>2018-07-24T09:48:40Z</dc:date>
    </item>
    <item>
      <title>Re: Swap Object Thin Provisioning in vSAN 6.7</title>
      <link>https://communities.vmware.com/t5/VMware-vSAN-Discussions/Swap-Object-Thin-Provisioning-in-vSAN-6-7/m-p/1845239#M7321</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;This is all logical, I do not argue. I myself think this way. But somewhere it's all fixed officially?&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 24 Jul 2018 08:45:50 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/VMware-vSAN-Discussions/Swap-Object-Thin-Provisioning-in-vSAN-6-7/m-p/1845239#M7321</guid>
      <dc:creator>IT_pilot</dc:creator>
      <dc:date>2018-07-24T08:45:50Z</dc:date>
    </item>
    <item>
      <title>Re: Possible to deploy vSAN on one Node?</title>
      <link>https://communities.vmware.com/t5/VMware-vSAN-Discussions/Possible-to-deploy-vSAN-on-one-Node/m-p/1845516#M7326</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;vSAN on one host just for encryption?&lt;/P&gt;&lt;P&gt;It does not make sense. Encryption works without vSAN.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 24 Jul 2018 08:43:34 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/VMware-vSAN-Discussions/Possible-to-deploy-vSAN-on-one-Node/m-p/1845516#M7326</guid>
      <dc:creator>IT_pilot</dc:creator>
      <dc:date>2018-07-24T08:43:34Z</dc:date>
    </item>
    <item>
      <title>Re: Swap Object Thin Provisioning in vSAN 6.7</title>
      <link>https://communities.vmware.com/t5/VMware-vSAN-Discussions/Swap-Object-Thin-Provisioning-in-vSAN-6-7/m-p/1845237#M7319</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Of course, I'm using the latest ESXi update: U2&amp;nbsp; and the build is 8294253&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 23 Jul 2018 14:14:27 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/VMware-vSAN-Discussions/Swap-Object-Thin-Provisioning-in-vSAN-6-7/m-p/1845237#M7319</guid>
      <dc:creator>IT_pilot</dc:creator>
      <dc:date>2018-07-23T14:14:27Z</dc:date>
    </item>
    <item>
      <title>Swap Object Thin Provisioning in vSAN 6.7</title>
      <link>https://communities.vmware.com/t5/VMware-vSAN-Discussions/Swap-Object-Thin-Provisioning-in-vSAN-6-7/m-p/1845235#M7317</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;SPAN&gt;In the article &lt;/SPAN&gt;&lt;A class="jive-link-external-small" href="https://blogs.vmware.com/virtualblocks/2018/07/18/swap-object-thin-provisioning-in-vsan-6-7/" rel="nofollow"&gt;https://blogs.vmware.com/virtualblocks/2018/07/18/swap-object-thin-provisioning-in-vsan-6-7/&lt;/A&gt;&lt;SPAN&gt; write that "As of vSAN 6.7 the default behavior of the vSAN swap object is set to thin provisioned ". I have version 6.6.1, and VSAN.SwapThickProvisionDisabled = 1 (default). My comment is not published. I'm wondering who has what values of this parameter.&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;Learn the meaning via PowerCLI: Get-AdvancedSetting -Entity My-ESXi -Name "VSAN.SwapThickProvisionDisabled"&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 23 Jul 2018 11:58:17 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/VMware-vSAN-Discussions/Swap-Object-Thin-Provisioning-in-vSAN-6-7/m-p/1845235#M7317</guid>
      <dc:creator>IT_pilot</dc:creator>
      <dc:date>2018-07-23T11:58:17Z</dc:date>
    </item>
    <item>
      <title>Re: Should this work?</title>
      <link>https://communities.vmware.com/t5/VMware-vSAN-Discussions/Should-this-work/m-p/1422645#M5643</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;&lt;SPAN&gt;I did not find the AMD SB710 SATA Controller in the vSAN compatibility list. And in the compatibility list ESXi only version 5.1. &lt;/SPAN&gt;&lt;A class="jive-link-external-small" href="https://www.vmware.com/resources/compatibility/pdf/vi_vsan_guide.pdf" rel="nofollow"&gt;https://www.vmware.com/resources/compatibility/pdf/vi_vsan_guide.pdf&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp; You have correctly indicated the name. Most likely this is the case.&lt;/P&gt;&lt;P&gt;Did you make the installation according to the instructions? The vSAN traffic in the interface properties included?&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 18 Jul 2018 19:07:16 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/VMware-vSAN-Discussions/Should-this-work/m-p/1422645#M5643</guid>
      <dc:creator>IT_pilot</dc:creator>
      <dc:date>2018-07-18T19:07:16Z</dc:date>
    </item>
    <item>
      <title>Re: vm orphaned</title>
      <link>https://communities.vmware.com/t5/VMware-vSphere-Discussions/vm-orphaned/m-p/1421881#M16824</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;1. Create a folder, move the VM there, and delete the folder. The VM must be removed.&lt;/P&gt;&lt;P&gt;2. &lt;A href="https://www.virtualizationhowto.com/2017/01/remove-orphaned-vm-in-vmware-vcenter-web-client/" title="https://www.virtualizationhowto.com/2017/01/remove-orphaned-vm-in-vmware-vcenter-web-client/"&gt;https://www.virtualizationhowto.com/2017/01/remove-orphaned-vm-in-vmware-vcenter-web-client/&lt;/A&gt; &lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 18 Jul 2018 08:09:30 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/VMware-vSphere-Discussions/vm-orphaned/m-p/1421881#M16824</guid>
      <dc:creator>IT_pilot</dc:creator>
      <dc:date>2018-07-18T08:09:30Z</dc:date>
    </item>
    <item>
      <title>Re: Deploying to OVF Fails - VCSA 6.5</title>
      <link>https://communities.vmware.com/t5/VMware-vCenter-Discussions/Deploying-to-OVF-Fails-VCSA-6-5/m-p/1844182#M27346</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;If this is an isolated case you can use &lt;A href="http://www.doublecloud.org/2017/05/free-java-gui-to-deploy-vms-onto-vsphere-of-all-versions-a-solid-and-fast-alternative-to-vsphere-web-client-and-ovftool/" title="http://www.doublecloud.org/2017/05/free-java-gui-to-deploy-vms-onto-vsphere-of-all-versions-a-solid-and-fast-alternative-to-vsphere-web-client-and-ovftool/"&gt;Free Java GUI to Deploy VMs onto vSphere of All Versions – A Solid and Fast Alternative to vSphere Web Client and ovftoo…&lt;/A&gt; &lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 16 Jul 2018 20:08:26 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/VMware-vCenter-Discussions/Deploying-to-OVF-Fails-VCSA-6-5/m-p/1844182#M27346</guid>
      <dc:creator>IT_pilot</dc:creator>
      <dc:date>2018-07-16T20:08:26Z</dc:date>
    </item>
    <item>
      <title>Re: vSAN statDB object Out of Date compliance</title>
      <link>https://communities.vmware.com/t5/VMware-vSAN-Discussions/vSAN-statDB-object-Out-of-Date-compliance/m-p/1844667#M7304</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;&lt;A href="https://greatwhitetec.com/2017/02/17/vsan-stats-object-out-of-date/" title="https://greatwhitetec.com/2017/02/17/vsan-stats-object-out-of-date/"&gt;https://greatwhitetec.com/2017/02/17/vsan-stats-object-out-of-date/&lt;/A&gt; &lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 16 Jul 2018 20:01:55 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/VMware-vSAN-Discussions/vSAN-statDB-object-Out-of-Date-compliance/m-p/1844667#M7304</guid>
      <dc:creator>IT_pilot</dc:creator>
      <dc:date>2018-07-16T20:01:55Z</dc:date>
    </item>
    <item>
      <title>Re: vmtools 10.3 update</title>
      <link>https://communities.vmware.com/t5/VMware-vSphere-Discussions/vmtools-10-3-update/m-p/508337#M7940</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;You can download VMware Tools Offline VIB Bundle in Update Manager in the manual mode &lt;A href="https://my.vmware.com/web/vmware/details?downloadGroup=VMTOOLS1030&amp;amp;productId=491" title="https://my.vmware.com/web/vmware/details?downloadGroup=VMTOOLS1030&amp;amp;productId=491"&gt;Download VMware vSphere&lt;/A&gt; &lt;/P&gt;&lt;P&gt;&lt;A href="http://it-pilot.ru/2018/01/17/vmware-tools-vum-update-manager/" title="http://it-pilot.ru/2018/01/17/vmware-tools-vum-update-manager/"&gt;Обновление VMware Tools с использованием VUM (Update Manager) | IT-пилот&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;You can also resolve the vulnerability by using the isolation.tools.hgfs.disable parameter.&lt;/P&gt;&lt;P&gt;&lt;A href="http://it-pilot.ru/2018/07/16/vulnerability-vmware-tools-hgfs-cve-2018-6969/" title="http://it-pilot.ru/2018/07/16/vulnerability-vmware-tools-hgfs-cve-2018-6969/"&gt;Уязвимость/vulnerability VMware Tools HGFS. Установка isolation.tools.hgfs.disable с PowerCLI. | IT-пилот&lt;/A&gt; &lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 16 Jul 2018 19:50:11 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/VMware-vSphere-Discussions/vmtools-10-3-update/m-p/508337#M7940</guid>
      <dc:creator>IT_pilot</dc:creator>
      <dc:date>2018-07-16T19:50:11Z</dc:date>
    </item>
    <item>
      <title>Re: vSAN on vSphere essential plus ESXi hosts</title>
      <link>https://communities.vmware.com/t5/VMware-vSAN-Discussions/vSAN-on-vSphere-essential-plus-ESXi-hosts/m-p/496082#M1572</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi, &lt;B&gt;TheBobkin&lt;/B&gt;​&lt;/P&gt;&lt;P&gt;Yes, the limit is three hosts. BUT! On three PHYSICAL hosts. witness host when it is appliance does not consume vCenter Essentials license.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="font-weight: bolder; color: #212529; font-family: Metropolis, 'Avenir Next', 'Helvetica Neue', Arial, sans-serif; background-color: #fafafa;"&gt;Licensing Issues&lt;/SPAN&gt;&lt;/P&gt;&lt;UL&gt;&lt;LI&gt;&lt;SPAN style="font-weight: bolder;"&gt;Cannot add witness virtual machine to vCenter Server with Essentials license&lt;/SPAN&gt;&lt;/LI&gt;&lt;/UL&gt;&lt;P&gt;&lt;SPAN style="margin-top: 1rem; margin-bottom: 1rem;"&gt;When the witness host for a stretched cluster is an appliance that resides in a virtual machine, it incorrectly consumes a host license. This problem occurs because the vCenter Server considers the witness appliance to be a physical host. If your license does not cover an additional host, you cannot add the witness appliance to vCenter Server.&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="margin-top: 1rem; margin-bottom: 1rem; color: #e23d39;"&gt;Workaround: Add the witness appliance VM to vCenter Server before you add the physical hosts.&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="margin-top: 1rem; margin-bottom: 1rem;"&gt;&lt;A href="https://docs.vmware.com/en/VMware-vSphere/6.5/rn/vsphere-vcenter-server-65u2-release-notes.html" title="https://docs.vmware.com/en/VMware-vSphere/6.5/rn/vsphere-vcenter-server-65u2-release-notes.html"&gt;VMware vCenter Server 6.5 Update 2 Release Notes&lt;/A&gt; &lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="margin-top: 1rem; margin-bottom: 1rem;"&gt;And that's great news!&lt;/SPAN&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 11 Jul 2018 08:52:18 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/VMware-vSAN-Discussions/vSAN-on-vSphere-essential-plus-ESXi-hosts/m-p/496082#M1572</guid>
      <dc:creator>IT_pilot</dc:creator>
      <dc:date>2018-07-11T08:52:18Z</dc:date>
    </item>
    <item>
      <title>Re: vSAN on vSphere essential plus ESXi hosts</title>
      <link>https://communities.vmware.com/t5/VMware-vSAN-Discussions/vSAN-on-vSphere-essential-plus-ESXi-hosts/m-p/496080#M1570</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;&lt;SPAN style="background-color: #f0fade; color: #666666; font-weight: inherit; font-size: inherit !important; font-family: proxima-nova, Arial, sans-serif; font-style: inherit;"&gt; &lt;/SPAN&gt;&lt;A _jive_internal="true" data-containerid="-1" data-containertype="-1" data-objectid="1000445" data-objecttype="3" href="https://communities.vmware.com/people/suhag79" name="&amp;amp;amp;lpos=apps_scodevmw : 83" style="font-family: proxima-nova, Arial, sans-serif; color: #3399cc; background-color: #f0fade;"&gt;&lt;SPAN style="font-weight: inherit; font-size: inherit !important; font-style: inherit;"&gt;suhag79&lt;/SPAN&gt;&lt;/A&gt; &lt;/P&gt;&lt;P&gt;You can add an additional host to a limited license for vCenter Foundation and vSphere Essentials.&lt;/P&gt;&lt;P&gt;&lt;A href="http://www.yellow-bricks.com/2018/07/06/adding-a-fifth-virtual-esxi-host-to-vcenter-foundation/" title="http://www.yellow-bricks.com/2018/07/06/adding-a-fifth-virtual-esxi-host-to-vcenter-foundation/"&gt;Adding a fifth (virtual) ESXi host to vCenter Foundation - Yellow Bricks&lt;/A&gt; &lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 11 Jul 2018 08:29:08 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/VMware-vSAN-Discussions/vSAN-on-vSphere-essential-plus-ESXi-hosts/m-p/496080#M1570</guid>
      <dc:creator>IT_pilot</dc:creator>
      <dc:date>2018-07-11T08:29:08Z</dc:date>
    </item>
  </channel>
</rss>

