<?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>Digory34 Tracker</title>
    <link>https://communities.vmware.com/wbsdv95928/tracker</link>
    <description>Digory34 Tracker</description>
    <pubDate>Fri, 24 Nov 2023 07:02:46 GMT</pubDate>
    <dc:date>2023-11-24T07:02:46Z</dc:date>
    <item>
      <title>Re: App Volumes not loading when assigned to user group</title>
      <link>https://communities.vmware.com/t5/App-Volumes/App-Volumes-not-loading-when-assigned-to-user-group/m-p/2932357#M9033</link>
      <description>&lt;P&gt;Hi&amp;nbsp;&lt;a href="https://communities.vmware.com/t5/user/viewprofilepage/user-id/393112"&gt;@Chris_Nodak&lt;/a&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;As troubleshooting, you can check the log from the App volume Manager and what is the error during the login with the group.&lt;/P&gt;&lt;P&gt;What you can do is typing&amp;nbsp;&lt;SPAN&gt;http://&lt;/SPAN&gt;&lt;I&gt;AppVolumes ManagerFQDN:port number/log + &lt;/I&gt;reproduce the issue, then refresh the log webpage and check with the group user name.&lt;/P&gt;&lt;P&gt;It could be related&amp;nbsp;to your active directory and group management as this is working with user directly.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Fri, 07 Oct 2022 06:32:11 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/App-Volumes/App-Volumes-not-loading-when-assigned-to-user-group/m-p/2932357#M9033</guid>
      <dc:creator>Digory34</dc:creator>
      <dc:date>2022-10-07T06:32:11Z</dc:date>
    </item>
    <item>
      <title>Re: ESXi 7.0 - VMXNET3 RX Ring Buffer Exhaustion and Packet Loss</title>
      <link>https://communities.vmware.com/t5/ESXi-Discussions/ESXi-7-0-VMXNET3-RX-Ring-Buffer-Exhaustion-and-Packet-Loss/m-p/2932352#M284031</link>
      <description>&lt;P&gt;Hi&amp;nbsp;&lt;a href="https://communities.vmware.com/t5/user/viewprofilepage/user-id/245712"&gt;@gopinathan&lt;/a&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;What is your nic card here?&amp;nbsp; and what is your issue?&lt;/P&gt;&lt;P&gt;The setting is changed following your driver normally, some cards have different value, but you can change the current value, the preset is set by vendor normally and cannot be changed, if i'm not wrong.&lt;/P&gt;&lt;P&gt;&lt;A href="https://kb.vmware.com/s/article/50121760" target="_blank" rel="noopener"&gt;Troubleshooting network receive traffic faults and other NIC errors in ESXi (50121760) (vmware.com)&lt;/A&gt;&lt;/P&gt;&lt;P&gt;Following the network card, you may find the best practice to set on your card.&lt;/P&gt;&lt;P&gt;Depending on your issue, missed error from Nic statistic,&amp;nbsp;for example, it could be related to other issue relating to the netqueue from your driver.&lt;/P&gt;&lt;P&gt;Quick example KB:&lt;/P&gt;&lt;P&gt;&lt;A href="https://kb.vmware.com/s/article/56457" target="_blank" rel="noopener"&gt;&amp;nbsp;ESXi hosts using QLogic QL411XX Nics randomly experience Network interuptions (56457) (vmware.com)&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Fri, 07 Oct 2022 06:25:42 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/ESXi-Discussions/ESXi-7-0-VMXNET3-RX-Ring-Buffer-Exhaustion-and-Packet-Loss/m-p/2932352#M284031</guid>
      <dc:creator>Digory34</dc:creator>
      <dc:date>2022-10-07T06:25:42Z</dc:date>
    </item>
    <item>
      <title>Re: Datastore access problem after ESX 7.0 upgrade</title>
      <link>https://communities.vmware.com/t5/vSphere-Upgrade-Install/Datastore-access-problem-after-ESX-7-0-upgrade/m-p/2932351#M34171</link>
      <description>&lt;P&gt;Also, i think that i got this issue before and from DSM i could see an issue on port SAS, the FW Version from the Array was not compatible with Esxi 7.0 and need to be updated.&lt;/P&gt;&lt;P&gt;You may check with the storage vendor or the Compellent HCL.&lt;/P&gt;</description>
      <pubDate>Fri, 07 Oct 2022 06:16:20 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/vSphere-Upgrade-Install/Datastore-access-problem-after-ESX-7-0-upgrade/m-p/2932351#M34171</guid>
      <dc:creator>Digory34</dc:creator>
      <dc:date>2022-10-07T06:16:20Z</dc:date>
    </item>
    <item>
      <title>Re: Datastore access problem after ESX 7.0 upgrade</title>
      <link>https://communities.vmware.com/t5/vSphere-Upgrade-Install/Datastore-access-problem-after-ESX-7-0-upgrade/m-p/2932350#M34170</link>
      <description>&lt;P&gt;Hi Tcrosasso,&lt;/P&gt;&lt;P&gt;Could you check if you NMP is always set to SATP_ALUA with PSP Round Robin?&lt;/P&gt;&lt;P&gt;in Version 7.0, i know that HPP was introduce and can cause some error.&lt;/P&gt;&lt;P&gt;&lt;A href="https://docs.vmware.com/en/VMware-vSphere/7.0/com.vmware.vsphere.storage.doc/GUID-F7B60A5A-D077-4E37-8CA7-8CB912173D24.html" target="_blank"&gt;VMware High Performance Plug-In and Path Selection Schemes&lt;/A&gt;&lt;/P&gt;&lt;P&gt;What is your driver / FW also?&lt;/P&gt;</description>
      <pubDate>Fri, 07 Oct 2022 06:11:32 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/vSphere-Upgrade-Install/Datastore-access-problem-after-ESX-7-0-upgrade/m-p/2932350#M34170</guid>
      <dc:creator>Digory34</dc:creator>
      <dc:date>2022-10-07T06:11:32Z</dc:date>
    </item>
    <item>
      <title>Re: On "VMware Compatibility Guide / IO device": “VMware Inbox” and “native” definition</title>
      <link>https://communities.vmware.com/t5/ESXi-Discussions/On-quot-VMware-Compatibility-Guide-IO-device-quot-VMware-Inbox/m-p/2932348#M284030</link>
      <description>&lt;P&gt;Driver native can be find downloading VIP offline bundle zip on VMware HCL website or installed using custom ISO from Partner - Dell&amp;nbsp; / HPE etc / during an update or upgrade.&lt;/P&gt;&lt;P&gt;So you can follow the HCL to update your NIC device driver for example, but you can also download the ISO from custom ISO.&lt;/P&gt;&lt;P&gt;If you use normal ISO, you need to check the build release but most the time they are included.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Fri, 07 Oct 2022 06:06:36 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/ESXi-Discussions/On-quot-VMware-Compatibility-Guide-IO-device-quot-VMware-Inbox/m-p/2932348#M284030</guid>
      <dc:creator>Digory34</dc:creator>
      <dc:date>2022-10-07T06:06:36Z</dc:date>
    </item>
    <item>
      <title>Re: On "VMware Compatibility Guide / IO device": “VMware Inbox” and “native” definition</title>
      <link>https://communities.vmware.com/t5/ESXi-Discussions/On-quot-VMware-Compatibility-Guide-IO-device-quot-VMware-Inbox/m-p/2931916#M283986</link>
      <description>&lt;P&gt;Inbox driver :&amp;nbsp;&lt;A href="https://communities.vmware.com/t5/Legacy-User-Blogs/Difference-between-ASYNC-and-INBOX-drivers-by-VMware/ta-p/2764488" target="_blank"&gt;Difference between ASYNC and INBOX drivers by VMwa... - VMware Technology Network VMTN&lt;/A&gt;&lt;/P&gt;&lt;P&gt;Native driver :&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;A href="https://kb.vmware.com/s/article/2147565" target="_blank"&gt;Article Detail (vmware.com)&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;A href="https://kb.vmware.com/s/article/2044993" target="_blank"&gt;Troubleshooting native drivers in ESXi 5.5 or later (2044993) (vmware.com)&lt;/A&gt;&lt;/P&gt;&lt;P&gt;Hope that it will answer your questions.&lt;/P&gt;</description>
      <pubDate>Tue, 04 Oct 2022 14:59:19 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/ESXi-Discussions/On-quot-VMware-Compatibility-Guide-IO-device-quot-VMware-Inbox/m-p/2931916#M283986</guid>
      <dc:creator>Digory34</dc:creator>
      <dc:date>2022-10-04T14:59:19Z</dc:date>
    </item>
    <item>
      <title>Re: Moving Esxi to HA Cluster without maintaince mode</title>
      <link>https://communities.vmware.com/t5/VMware-vCenter-Discussions/Moving-Esxi-to-HA-Cluster-without-maintaince-mode/m-p/2931915#M46446</link>
      <description>&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;Any reason to reinstall the host instead of upgrade from 6.7 to 7.?&lt;/P&gt;&lt;P&gt;If you have two ESXi working on same cluster you can just disabled the HA /EVC/ DRS and migrate all VM from one host to other (if you resource allow this), put first host in maintenance mode and upgrade it to 7.0, then migrate back VM from second host&amp;nbsp; to the first host (now in 7.0 and) and update the second node.&amp;nbsp;&lt;/P&gt;&lt;P&gt;You Vcenter must be in 7.0 but it's okay according to your post.&lt;/P&gt;&lt;P&gt;The process should be the same if you have to reinstall, you can just remove the host from cluster and reinstall it and reconfigure it (vswitch or dvs / storage).&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Tue, 04 Oct 2022 14:55:06 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/VMware-vCenter-Discussions/Moving-Esxi-to-HA-Cluster-without-maintaince-mode/m-p/2931915#M46446</guid>
      <dc:creator>Digory34</dc:creator>
      <dc:date>2022-10-04T14:55:06Z</dc:date>
    </item>
    <item>
      <title>Re: Need Help with Inaccessible VMs</title>
      <link>https://communities.vmware.com/t5/Horizon-Desktops-and-Apps/Need-Help-with-Inaccessible-VMs/m-p/2931913#M97856</link>
      <description>&lt;P&gt;The error could be host related.&lt;/P&gt;&lt;P&gt;are all your host connected and up and running on your vcenter? if not, can you try to reconnect or try to ping them.&lt;/P&gt;&lt;P&gt;If this is a datastore issue, you should see from VCENTER if you have a Datastore disconnected or inacessible.&lt;/P&gt;</description>
      <pubDate>Tue, 04 Oct 2022 14:45:32 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/Horizon-Desktops-and-Apps/Need-Help-with-Inaccessible-VMs/m-p/2931913#M97856</guid>
      <dc:creator>Digory34</dc:creator>
      <dc:date>2022-10-04T14:45:32Z</dc:date>
    </item>
    <item>
      <title>Re: Upgrading ESXi 7.0U2 to 7.0U3</title>
      <link>https://communities.vmware.com/t5/vSphere-Upgrade-Install/Upgrading-ESXi-7-0U2-to-7-0U3/m-p/2931911#M34164</link>
      <description>&lt;P&gt;Hi Sweehan,&lt;/P&gt;&lt;P&gt;Seems to be a corrupted Zip. Did you check the md5 ?&lt;/P&gt;&lt;P&gt;What's kind of method are you using to upgrade? Are you using Oneclick upgrade?&lt;/P&gt;&lt;P&gt;You should check the HCL from Nutanix portal to see if 7.0U3 is supported with your HPE server and use one click upgrade if you can (official method supported if i'm not wrong). You should find the json file on the hypervisor list in nutanix website&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Tue, 04 Oct 2022 14:37:41 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/vSphere-Upgrade-Install/Upgrading-ESXi-7-0U2-to-7-0U3/m-p/2931911#M34164</guid>
      <dc:creator>Digory34</dc:creator>
      <dc:date>2022-10-04T14:37:41Z</dc:date>
    </item>
    <item>
      <title>Re: Vcenter launch not working</title>
      <link>https://communities.vmware.com/t5/VMware-vCenter-Discussions/Vcenter-launch-not-working/m-p/2931904#M46445</link>
      <description>&lt;P&gt;It can be a DNS issue / Certificate issue /&amp;nbsp;&lt;/P&gt;&lt;P&gt;Did you use a hostname or only a IP during the deployment?&lt;/P&gt;&lt;P&gt;can you check if the entries is correctly set on your DNS (including reverse forest) ?&lt;/P&gt;&lt;P&gt;ping fqdn should work and nslookup also.&lt;/P&gt;&lt;P&gt;is the vami console is working using the IP:5480?&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Tue, 04 Oct 2022 13:43:15 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/VMware-vCenter-Discussions/Vcenter-launch-not-working/m-p/2931904#M46445</guid>
      <dc:creator>Digory34</dc:creator>
      <dc:date>2022-10-04T13:43:15Z</dc:date>
    </item>
    <item>
      <title>Re: Error upgrade ESX 6.7 to 7.0.3</title>
      <link>https://communities.vmware.com/t5/ESXi-Discussions/Error-upgrade-ESX-6-7-to-7-0-3/m-p/2931903#M283985</link>
      <description>&lt;P&gt;Hi Marco,&lt;/P&gt;&lt;P&gt;Could you extract or do a screenshot of the content inside your offline bundle?&lt;/P&gt;&lt;P&gt;Just want to be sure that you are using the correct zip.&lt;/P&gt;&lt;P&gt;as workaround, you can attach the ISO file (from IDRAC /ILO or any virtual console) and boot to it to upgrade from 6.7 to 7.0.3.&lt;/P&gt;&lt;P&gt;Custom Iso are available from VMware website support.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Tue, 04 Oct 2022 13:41:19 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/ESXi-Discussions/Error-upgrade-ESX-6-7-to-7-0-3/m-p/2931903#M283985</guid>
      <dc:creator>Digory34</dc:creator>
      <dc:date>2022-10-04T13:41:19Z</dc:date>
    </item>
    <item>
      <title>Re: Datastore access problem after ESX 7.0 upgrade</title>
      <link>https://communities.vmware.com/t5/vSphere-Upgrade-Install/Datastore-access-problem-after-ESX-7-0-upgrade/m-p/2931897#M34163</link>
      <description>&lt;P&gt;Hi Tcrosasso,&lt;/P&gt;&lt;P&gt;Did you try this KB ?&lt;/P&gt;&lt;P&gt;&lt;A href="https://www.dell.com/support/kbdoc/en-us/000118040/preparing-vmware-esxi-hosts-to-attach-to-scv20x0-scv30x0-sc4020-sc5020-sas-arrays" target="_blank"&gt;Dell Storage: Preparing VMware ESXi Hosts To Attach to SCv20x0, SCv30x0, SC4020, SC5020 SAS Arrays | Dell US&lt;/A&gt;&lt;/P&gt;&lt;P&gt;Please check after the upgrade if the driver lsi_msgpt3 is used. on 6.7 mpt3sas could be use but not in Esxi 7.0.&lt;/P&gt;&lt;P&gt;Also you have to enable :&amp;nbsp;&lt;SPAN&gt;issue_scsi_cmd_to_bringup_drive to 1.&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;so in the nutshell, check the driver use after the upgrade (disable mpt3sas and enable lsi_msgpt3) and enabled the feature&amp;nbsp;issue_scsi_cmd_to_bringup_drive.&lt;/SPAN&gt;&lt;/P&gt;</description>
      <pubDate>Tue, 04 Oct 2022 13:25:34 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/vSphere-Upgrade-Install/Datastore-access-problem-after-ESX-7-0-upgrade/m-p/2931897#M34163</guid>
      <dc:creator>Digory34</dc:creator>
      <dc:date>2022-10-04T13:25:34Z</dc:date>
    </item>
    <item>
      <title>Re: issue when creating vsphere pod</title>
      <link>https://communities.vmware.com/t5/VMware-vSphere-Discussions/issue-when-creating-vsphere-pod/m-p/2927472#M43333</link>
      <description>&lt;P&gt;What is your command used to create your POD?&lt;/P&gt;</description>
      <pubDate>Tue, 06 Sep 2022 09:48:53 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/VMware-vSphere-Discussions/issue-when-creating-vsphere-pod/m-p/2927472#M43333</guid>
      <dc:creator>Digory34</dc:creator>
      <dc:date>2022-09-06T09:48:53Z</dc:date>
    </item>
    <item>
      <title>Re: How do you check or enable Quick Boot in vSphere 7 Update 3?</title>
      <link>https://communities.vmware.com/t5/VMware-vSphere-Discussions/How-do-you-check-or-enable-Quick-Boot-in-vSphere-7-Update-3/m-p/2927471#M43332</link>
      <description>&lt;P&gt;&lt;A href="https://docs.vmware.com/en/VMware-vSphere/7.0/com.vmware.vsphere-lifecycle-manager.doc/GUID-5AF3C64F-1178-4F1E-B5EC-2882957C6045.html" target="_blank"&gt;https://docs.vmware.com/en/VMware-vSphere/7.0/com.vmware.vsphere-lifecycle-manager.doc/GUID-5AF3C64F-1178-4F1E-B5EC-2882957C6045.html&lt;/A&gt;&lt;/P&gt;&lt;P&gt;Normally, the feature should be enabled on the&amp;nbsp;&lt;SPAN&gt;Remediation Settings from LCM. you have to tick the options.&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;&lt;IMG src="https://live.staticflickr.com/65535/51039264862_da9159963b_z.jpg" border="0" /&gt;&lt;/SPAN&gt;&lt;/P&gt;</description>
      <pubDate>Tue, 06 Sep 2022 09:44:57 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/VMware-vSphere-Discussions/How-do-you-check-or-enable-Quick-Boot-in-vSphere-7-Update-3/m-p/2927471#M43332</guid>
      <dc:creator>Digory34</dc:creator>
      <dc:date>2022-09-06T09:44:57Z</dc:date>
    </item>
    <item>
      <title>Re: Unable to remove standalone host from domain</title>
      <link>https://communities.vmware.com/t5/VMware-vSphere-Discussions/Unable-to-remove-standalone-host-from-domain/m-p/2927469#M43331</link>
      <description>&lt;P&gt;My appologie, looking to this kb&amp;nbsp;&lt;A href="https://kb.vmware.com/s/article/50112055" target="_blank"&gt;https://kb.vmware.com/s/article/50112055&lt;/A&gt;&amp;nbsp;and it's appear that the command is for VCSA.&lt;/P&gt;&lt;P&gt;They are another KB that you can try but I'm not sure about the resolution on 6x and 7x.&lt;/P&gt;&lt;P&gt;&lt;A href="https://kb.vmware.com/s/article/2035634" target="_blank"&gt;https://kb.vmware.com/s/article/2035634&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Tue, 06 Sep 2022 09:21:55 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/VMware-vSphere-Discussions/Unable-to-remove-standalone-host-from-domain/m-p/2927469#M43331</guid>
      <dc:creator>Digory34</dc:creator>
      <dc:date>2022-09-06T09:21:55Z</dc:date>
    </item>
    <item>
      <title>Re: Regarding the vsphere lisencing</title>
      <link>https://communities.vmware.com/t5/VMware-vSphere-Discussions/Regarding-the-vsphere-lisencing/m-p/2927334#M43326</link>
      <description>&lt;P&gt;&lt;SPAN&gt;SRM&amp;nbsp;should have its own&amp;nbsp;&lt;SPAN class=""&gt;Site Recovery Manager&lt;/SPAN&gt;&amp;nbsp;license key.&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;Based of this matrix here for SRM 8.1 :&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;&lt;A href="https://docs.vmware.com/en/Site-Recovery-Manager/8.1/rn/srm-compat-matrix-8-1.html" target="_blank" rel="noopener"&gt;https://docs.vmware.com/en/Site-Recovery-Manager/8.1/rn/srm-compat-matrix-8-1.html&lt;/A&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;Downgrading from vSphere&amp;nbsp;Enterprise to Standard should work (but not for advanced).&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;The only things that you need to check is the inter-ops matrix between your SRM version and your Esxi 6.x version.&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;&lt;A href="https://interopmatrix.vmware.com/Interoperability" target="_blank" rel="noopener"&gt;https://interopmatrix.vmware.com/Interoperability&lt;/A&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;And also, if check if this is the same for your SRM version if you are lower than 8.1&lt;/SPAN&gt;&lt;/P&gt;</description>
      <pubDate>Mon, 05 Sep 2022 10:08:02 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/VMware-vSphere-Discussions/Regarding-the-vsphere-lisencing/m-p/2927334#M43326</guid>
      <dc:creator>Digory34</dc:creator>
      <dc:date>2022-09-05T10:08:02Z</dc:date>
    </item>
    <item>
      <title>Re: How to update vSphere7 with vSphere-FT?</title>
      <link>https://communities.vmware.com/t5/vSphere-Upgrade-Install/How-to-update-vSphere7-with-vSphere-FT/m-p/2927328#M34132</link>
      <description>&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;Normally here the process to update Esxi with FT VM :&lt;/P&gt;&lt;P&gt;&lt;A href="https://docs.vmware.com/en/VMware-vSphere/7.0/com.vmware.vsphere.avail.doc/GUID-104ED4FA-6FF7-4C6C-B5ED-AF5A0B0B94C5.html" target="_blank" rel="noopener"&gt;https://docs.vmware.com/en/VMware-vSphere/7.0/com.vmware.vsphere.avail.doc/GUID-104ED4FA-6FF7-4C6C-B5ED-AF5A0B0B94C5.html&lt;/A&gt;&lt;/P&gt;&lt;P&gt;following this link, you should be able to do this without any downtime.&lt;/P&gt;</description>
      <pubDate>Mon, 05 Sep 2022 09:52:49 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/vSphere-Upgrade-Install/How-to-update-vSphere7-with-vSphere-FT/m-p/2927328#M34132</guid>
      <dc:creator>Digory34</dc:creator>
      <dc:date>2022-09-05T09:52:49Z</dc:date>
    </item>
    <item>
      <title>Re: Host disconnection in vcenter</title>
      <link>https://communities.vmware.com/t5/VMware-vSphere-Discussions/Host-disconnection-in-vcenter/m-p/2927326#M43324</link>
      <description>&lt;P&gt;This is correct, there is no vpxa.cfg on 7.0.U3.&lt;/P&gt;&lt;P&gt;Here the KB to explain you why and how to modify it using json file :&lt;/P&gt;&lt;P&gt;&lt;A href="https://kb.vmware.com/s/article/87438" target="_blank"&gt;https://kb.vmware.com/s/article/87438&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Mon, 05 Sep 2022 09:46:26 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/VMware-vSphere-Discussions/Host-disconnection-in-vcenter/m-p/2927326#M43324</guid>
      <dc:creator>Digory34</dc:creator>
      <dc:date>2022-09-05T09:46:26Z</dc:date>
    </item>
    <item>
      <title>Re: Unable to remove standalone host from domain</title>
      <link>https://communities.vmware.com/t5/VMware-vSphere-Discussions/Unable-to-remove-standalone-host-from-domain/m-p/2927325#M43323</link>
      <description>&lt;P&gt;you can try to update your VMware server user (currently EDS\VMware-admins) with another ldap user (you can use your ldap if you have the admin right).&lt;/P&gt;&lt;P&gt;If someone or your active directory have disable your vmware service account for policy security or just deleted, it will not work.&lt;/P&gt;&lt;P&gt;The error show that this account can not be used at this moment to leave the current active directory.&lt;/P&gt;&lt;P&gt;If need, you can try to use command line to leave the domain :&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;/opt/likewise/bin/domainjoin-cli leave&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;then reboot.&lt;/SPAN&gt;&lt;/P&gt;</description>
      <pubDate>Mon, 05 Sep 2022 09:43:03 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/VMware-vSphere-Discussions/Unable-to-remove-standalone-host-from-domain/m-p/2927325#M43323</guid>
      <dc:creator>Digory34</dc:creator>
      <dc:date>2022-09-05T09:43:03Z</dc:date>
    </item>
    <item>
      <title>Re: Instant clone desktop pool failed</title>
      <link>https://communities.vmware.com/t5/Horizon-Desktops-and-Apps/Instant-clone-desktop-pool-failed/m-p/2927323#M97665</link>
      <description>&lt;P&gt;Sorry for my first question i read linked clone instead of lnstant clone.&lt;/P&gt;&lt;P&gt;I assume that you install this feature during the agent deployment on your gold image, right?&lt;/P&gt;&lt;P&gt;Are you selecting the correct snapshot during the deskpool deployment? Did you use sysprep or script for custom OS (like double nic in VM or something else)?&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Mon, 05 Sep 2022 09:36:33 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/Horizon-Desktops-and-Apps/Instant-clone-desktop-pool-failed/m-p/2927323#M97665</guid>
      <dc:creator>Digory34</dc:creator>
      <dc:date>2022-09-05T09:36:33Z</dc:date>
    </item>
  </channel>
</rss>

