<?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>srwsol Tracker</title>
    <link>https://communities.vmware.com/wbsdv95928/tracker</link>
    <description>srwsol Tracker</description>
    <pubDate>Tue, 21 Nov 2023 06:09:23 GMT</pubDate>
    <dc:date>2023-11-21T06:09:23Z</dc:date>
    <item>
      <title>Re: vCenter 8.02 U2a is out - Change notes</title>
      <link>https://communities.vmware.com/t5/vCenter-Server-Discussions/vCenter-8-02-U2a-is-out-Change-notes/m-p/2994242#M95137</link>
      <description>&lt;P&gt;I backed out ESXi 8.0U2, regressed to 7.02 and ESXi successfully connected to version 8.02a of vCenter Server.&amp;nbsp; &amp;nbsp;I'm beginning to think this might be an issue with ESXi 8.0U2 rather than vCenter Server 8.02a.&lt;/P&gt;</description>
      <pubDate>Sun, 05 Nov 2023 04:01:36 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/vCenter-Server-Discussions/vCenter-8-02-U2a-is-out-Change-notes/m-p/2994242#M95137</guid>
      <dc:creator>srwsol</dc:creator>
      <dc:date>2023-11-05T04:01:36Z</dc:date>
    </item>
    <item>
      <title>Re: ESXi 8.0U2 Can't connect to vCenter Server</title>
      <link>https://communities.vmware.com/t5/ESXi-Discussions/ESXi-8-0U2-Can-t-connect-to-vCenter-Server/m-p/2994241#M290958</link>
      <description>&lt;P&gt;I backed out ESXi 8.0U2, regressed to 7.02, and then ESXi successfully connected to version 8.02a of vCenter Server.&amp;nbsp; &amp;nbsp;Therefore either there is some incompatibility between ESXi 8.0U2 and vCenter Server 8.02a, or something went wrong with the upgrade process on ESXi.&amp;nbsp; &amp;nbsp;&lt;/P&gt;&lt;P&gt;I'm going to stay on 7.02 on this copy of ESXi until I get some answers about what happened.&amp;nbsp; &amp;nbsp;For the record I upgraded via the ISO image rather than using the offline upgrade bundle.&amp;nbsp; &amp;nbsp; &amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Sun, 05 Nov 2023 03:57:50 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/ESXi-Discussions/ESXi-8-0U2-Can-t-connect-to-vCenter-Server/m-p/2994241#M290958</guid>
      <dc:creator>srwsol</dc:creator>
      <dc:date>2023-11-05T03:57:50Z</dc:date>
    </item>
    <item>
      <title>Re: Unable to access Esxi Host which already registered to vCenter</title>
      <link>https://communities.vmware.com/t5/ESXi-Discussions/Unable-to-access-Esxi-Host-which-already-registered-to-vCenter/m-p/2993614#M290882</link>
      <description>&lt;P&gt;If you can get in through the console, then as&amp;nbsp;&lt;SPAN&gt;lukaszzasko indicated, the issue is probably that the host was configured to go into lockdown mode when first connected to vcenter.&amp;nbsp; &amp;nbsp;&lt;/SPAN&gt;&lt;/P&gt;</description>
      <pubDate>Tue, 31 Oct 2023 20:21:22 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/ESXi-Discussions/Unable-to-access-Esxi-Host-which-already-registered-to-vCenter/m-p/2993614#M290882</guid>
      <dc:creator>srwsol</dc:creator>
      <dc:date>2023-10-31T20:21:22Z</dc:date>
    </item>
    <item>
      <title>Re: Unable to access Esxi Host which already registered to vCenter</title>
      <link>https://communities.vmware.com/t5/ESXi-Discussions/Unable-to-access-Esxi-Host-which-already-registered-to-vCenter/m-p/2993549#M290873</link>
      <description>&lt;P&gt;Have you tried accessing the host directly through the console rather than via SSH?&lt;/P&gt;</description>
      <pubDate>Tue, 31 Oct 2023 15:12:41 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/ESXi-Discussions/Unable-to-access-Esxi-Host-which-already-registered-to-vCenter/m-p/2993549#M290873</guid>
      <dc:creator>srwsol</dc:creator>
      <dc:date>2023-10-31T15:12:41Z</dc:date>
    </item>
    <item>
      <title>ESXi 8.0U2 Can't connect to vCenter Server</title>
      <link>https://communities.vmware.com/t5/ESXi-Discussions/ESXi-8-0U2-Can-t-connect-to-vCenter-Server/m-p/2993261#M290860</link>
      <description>&lt;P&gt;Hi folks:&lt;/P&gt;&lt;P&gt;I just upgraded a copy of ESXi 7 to ESXi 8.0U2 and after the upgrade I'm unable to connect it to vCenter Server (I have the essentials package).&amp;nbsp; &amp;nbsp;At first I thought the problem may have been vCenter Server as prior to upgrading the host I upgraded vCenter Server to 8.02a, and I thought perhaps the issue was with the vCenter Server database, so I installed a brand new copy of vCenter Server 8.02a and the problem still happens.&amp;nbsp; &amp;nbsp;&lt;/P&gt;&lt;P&gt;When I add the host to vCenter Server all goes well at first and the host for a brief moment appears in the inventory, then the host disconnects after vCenter Server puts out a task message saying "&lt;SPAN&gt;Generate a certificate signing request using the specified Distinguished Name".&amp;nbsp; &amp;nbsp;That shows it completes, but immediately after that the host disconnects and won't connect again.&amp;nbsp; I have to remove the host from vCenter, stop service vpxa, and remove user vpxuser, at which point I can try again, but the same thing happens.&amp;nbsp; &amp;nbsp;&lt;/SPAN&gt;&lt;SPAN&gt;&amp;nbsp;&amp;nbsp;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;The vpaxa log file shows a number of errors while this process is going on, some specifically about fields not being defined properly, and at timestamp 00:45:26.492Z there is a panic error 1089, whatever that means.&amp;nbsp; &amp;nbsp;I'm attaching the log file here, if it will fit.&amp;nbsp; All these messages were from a single attempt to connect the host to vcenter server.&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;I've had no luck searching on this panic error, so I'm not sure what it's about.&amp;nbsp; &amp;nbsp;I was also discussing this in a thread in the vcenter server section, but after the problem recurrs on a freshly installed copy of vcenter server, I'm beginning to think the problem may be in the host.&amp;nbsp; &amp;nbsp;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;/P&gt;</description>
      <pubDate>Mon, 30 Oct 2023 01:11:40 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/ESXi-Discussions/ESXi-8-0U2-Can-t-connect-to-vCenter-Server/m-p/2993261#M290860</guid>
      <dc:creator>srwsol</dc:creator>
      <dc:date>2023-10-30T01:11:40Z</dc:date>
    </item>
    <item>
      <title>Re: vCenter 8.02 U2a is out - Change notes</title>
      <link>https://communities.vmware.com/t5/vCenter-Server-Discussions/vCenter-8-02-U2a-is-out-Change-notes/m-p/2993248#M95094</link>
      <description>&lt;P&gt;I created a new vCenter server appliance from scratch and I had the exact same problem.&amp;nbsp; The host disconnected after the certificate exchange and couldn't be connected again, so the problem wasn't involved with the upgrade of my previous vcenter server to 8.02a, or any stale data on its database.&amp;nbsp; &amp;nbsp;I may try replacing the default certificate on the host, even though it looks good, as I'm not sure what else I can do at this point.&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Sun, 29 Oct 2023 21:32:45 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/vCenter-Server-Discussions/vCenter-8-02-U2a-is-out-Change-notes/m-p/2993248#M95094</guid>
      <dc:creator>srwsol</dc:creator>
      <dc:date>2023-10-29T21:32:45Z</dc:date>
    </item>
    <item>
      <title>Re: vCenter 8.02 U2a is out - Change notes</title>
      <link>https://communities.vmware.com/t5/vCenter-Server-Discussions/vCenter-8-02-U2a-is-out-Change-notes/m-p/2993219#M95092</link>
      <description>&lt;P&gt;I believe I have a similar problem.&amp;nbsp; I have just the essentials package and am running two hosts on vcenter server.&amp;nbsp; &amp;nbsp;I was trying to upgrade one of the hosts from version 7 to version 8.02 this weekend, and so I upgraded vcenter server to 8.02a first and then upgraded the host.&amp;nbsp; &amp;nbsp;Now I can't connect the host to vcenter server.&amp;nbsp; &amp;nbsp;The process starts, and for a moment it shows in the inventory, then it disconnects.&amp;nbsp; The last thing in the tasks before it disconnects is "&lt;SPAN&gt;Generate a certificate signing request using the specified Distinguished Name", which says it completes normally, but an instant after that the host disconnects, followed by an event indicating that the host is no longer responding.&amp;nbsp; &amp;nbsp;It continues saying that until I delete the host from vcenter, delete user vpxuser from the host, and stop the service vpxa on the host.&amp;nbsp; At that point I can try to re-add the host, but the same sequence just starts again.&amp;nbsp; &amp;nbsp;There is only one certificate on the host, and it looks like the default certificate, which isn't expired.&amp;nbsp; &amp;nbsp; The second host is 8.00 and it appears to be able to connect normally.&amp;nbsp; &amp;nbsp;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;Not quite sure where to go from here, other than perhaps try to create a whole new vcenter server appliance from scratch and see if that works under the theory that it's database got somehow corrupted during either the vcenter upgrade or the upgrade of the host, which required me to delete the version 7 host from vcenter before I could add it back as version 8.&amp;nbsp; &amp;nbsp;&lt;/SPAN&gt;&lt;/P&gt;</description>
      <pubDate>Sun, 29 Oct 2023 06:29:09 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/vCenter-Server-Discussions/vCenter-8-02-U2a-is-out-Change-notes/m-p/2993219#M95092</guid>
      <dc:creator>srwsol</dc:creator>
      <dc:date>2023-10-29T06:29:09Z</dc:date>
    </item>
    <item>
      <title>Re: ESXi 7.02 reboots instead of powering off when Shutdown command issued</title>
      <link>https://communities.vmware.com/t5/ESXi-Discussions/ESXi-7-02-reboots-instead-of-powering-off-when-Shutdown-command/m-p/2973312#M288637</link>
      <description>&lt;P&gt;Upgraded NUC to BIOS 0073 to solve some AMT problems and the reboot problem still occurs&amp;nbsp;&lt;img class="lia-deferred-image lia-image-emoji" src="https://communities.vmware.com/html/@D5E6B168D16C1011E835DECBE0488360/emoticons/2639.png" alt=":frowning_face:" title=":frowning_face:" /&gt;&lt;/P&gt;</description>
      <pubDate>Thu, 15 Jun 2023 20:22:09 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/ESXi-Discussions/ESXi-7-02-reboots-instead-of-powering-off-when-Shutdown-command/m-p/2973312#M288637</guid>
      <dc:creator>srwsol</dc:creator>
      <dc:date>2023-06-15T20:22:09Z</dc:date>
    </item>
    <item>
      <title>Re: ESXi 7.02 reboots instead of powering off when Shutdown command issued</title>
      <link>https://communities.vmware.com/t5/ESXi-Discussions/ESXi-7-02-reboots-instead-of-powering-off-when-Shutdown-command/m-p/2957822#M287029</link>
      <description>&lt;P&gt;Bad news continues.&amp;nbsp; &amp;nbsp;I just upgraded my NUC 11 to ESXi 8.0b, and the BIOS to&amp;nbsp;&lt;SPAN&gt;TNTGLV57.0070.2022.1028.1324, and the reboot problem on shutdown still occurs.&amp;nbsp; I haven't tried upgrading S2600 system yet.&amp;nbsp; &amp;nbsp;&amp;nbsp;&lt;img class="lia-deferred-image lia-image-emoji" src="https://communities.vmware.com/html/@D5E6B168D16C1011E835DECBE0488360/emoticons/2639.png" alt=":frowning_face:" title=":frowning_face:" /&gt;&lt;/SPAN&gt;&lt;/P&gt;</description>
      <pubDate>Sun, 05 Mar 2023 04:03:30 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/ESXi-Discussions/ESXi-7-02-reboots-instead-of-powering-off-when-Shutdown-command/m-p/2957822#M287029</guid>
      <dc:creator>srwsol</dc:creator>
      <dc:date>2023-03-05T04:03:30Z</dc:date>
    </item>
    <item>
      <title>Re: ESXi 7.02 reboots instead of powering off when Shutdown command issued</title>
      <link>https://communities.vmware.com/t5/ESXi-Discussions/ESXi-7-02-reboots-instead-of-powering-off-when-Shutdown-command/m-p/2946200#M285661</link>
      <description>&lt;P&gt;Bad news&amp;nbsp;&lt;img class="lia-deferred-image lia-image-emoji" src="https://communities.vmware.com/html/@1C6E75E7C785988F2EA295D9769CEF91/emoticons/1f625.png" alt=":sad_but_relieved_face:" title=":sad_but_relieved_face:" /&gt;.&amp;nbsp; &amp;nbsp; I upgraded my nuc 11 to ESXi 8.00 and it still reboots when you try to shut it down.&amp;nbsp; &amp;nbsp; The screen about the system being halted and that you can now power it off appears briefly at the end of the shutdown sequence, and then it reboots.&amp;nbsp; &amp;nbsp;&lt;img class="lia-deferred-image lia-image-emoji" src="https://communities.vmware.com/html/@C2A029D8F56497C0B9F536A9C279C6DF/emoticons/1f644.png" alt=":face_with_rolling_eyes:" title=":face_with_rolling_eyes:" /&gt;&lt;/P&gt;</description>
      <pubDate>Sun, 01 Jan 2023 19:57:32 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/ESXi-Discussions/ESXi-7-02-reboots-instead-of-powering-off-when-Shutdown-command/m-p/2946200#M285661</guid>
      <dc:creator>srwsol</dc:creator>
      <dc:date>2023-01-01T19:57:32Z</dc:date>
    </item>
    <item>
      <title>Re: ESXi 7.02 reboots instead of powering off when Shutdown command issued</title>
      <link>https://communities.vmware.com/t5/ESXi-Discussions/ESXi-7-02-reboots-instead-of-powering-off-when-Shutdown-command/m-p/2944025#M285347</link>
      <description>&lt;P&gt;The only temporary solution is to shutdown all the VMs and then let the power drop.&amp;nbsp; ESXi itself doesn't appear to have a problem being powered off while running.&amp;nbsp; &amp;nbsp;That's what I'm doing.&amp;nbsp; &amp;nbsp;I've set my shutdown script to only shutdown the VMs and not attempt to shutdown the hypervisor.&amp;nbsp; &amp;nbsp;&lt;/P&gt;&lt;P&gt;ESXi 8 is out now and next month I'll get the chance to install it on the NUC and see if this problem is fixed in the new version.&amp;nbsp;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Wed, 14 Dec 2022 23:28:40 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/ESXi-Discussions/ESXi-7-02-reboots-instead-of-powering-off-when-Shutdown-command/m-p/2944025#M285347</guid>
      <dc:creator>srwsol</dc:creator>
      <dc:date>2022-12-14T23:28:40Z</dc:date>
    </item>
    <item>
      <title>Re: ESXi 7.02 reboots instead of powering off when Shutdown command issued</title>
      <link>https://communities.vmware.com/t5/ESXi-Discussions/ESXi-7-02-reboots-instead-of-powering-off-when-Shutdown-command/m-p/2930104#M283834</link>
      <description>&lt;P&gt;Now that's a very interesting observation!&amp;nbsp; &amp;nbsp; Both of the computers I'm having the issue with also have two nics.&amp;nbsp; &amp;nbsp;As the nics are part of the motherboards I'm not able to remove one, but perhaps I can disable one in the bios and see what happens.&amp;nbsp; &amp;nbsp;It might be a few weeks before I get an opportunity to take one down long enough to conduct the test though.&lt;/P&gt;</description>
      <pubDate>Thu, 22 Sep 2022 15:23:48 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/ESXi-Discussions/ESXi-7-02-reboots-instead-of-powering-off-when-Shutdown-command/m-p/2930104#M283834</guid>
      <dc:creator>srwsol</dc:creator>
      <dc:date>2022-09-22T15:23:48Z</dc:date>
    </item>
    <item>
      <title>Re: ESXi 7.02 reboots instead of powering off when Shutdown command issued</title>
      <link>https://communities.vmware.com/t5/ESXi-Discussions/ESXi-7-02-reboots-instead-of-powering-off-when-Shutdown-command/m-p/2926537#M283563</link>
      <description>&lt;P&gt;I just upgraded ESXi on the NUC to 7.03f and the same thing still happens:&amp;nbsp; &amp;nbsp;shutdown = reboot rather than poweroff.&amp;nbsp; &amp;nbsp;&lt;img class="lia-deferred-image lia-image-emoji" src="https://communities.vmware.com/html/@D5E6B168D16C1011E835DECBE0488360/emoticons/2639.png" alt=":frowning_face:" title=":frowning_face:" /&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Haven't upgraded the S2600 motherboard system yet.&amp;nbsp; &amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Tue, 30 Aug 2022 20:58:09 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/ESXi-Discussions/ESXi-7-02-reboots-instead-of-powering-off-when-Shutdown-command/m-p/2926537#M283563</guid>
      <dc:creator>srwsol</dc:creator>
      <dc:date>2022-08-30T20:58:09Z</dc:date>
    </item>
    <item>
      <title>ESXi 7.02 reboots instead of powering off when Shutdown command issued</title>
      <link>https://communities.vmware.com/t5/ESXi-Discussions/ESXi-7-02-reboots-instead-of-powering-off-when-Shutdown-command/m-p/2922668#M283141</link>
      <description>&lt;P&gt;Has anyone had an issue with ESXi 7.02 rebooting instead of powering off when given the shutdown command?&amp;nbsp; &amp;nbsp;I've had this happen on two different machines now, with two different patch levels of ESXi 7.02.&amp;nbsp; &amp;nbsp;The first time it happened on an Intel NUC, and I just disregarded it because the NUC isn't a supported platform.&amp;nbsp; &amp;nbsp;However, it just happened on an Intel s2600 motherboard that is supported, as I was testing a UPS shutdown script.&amp;nbsp; The script issued a powershell "Stop-VMhost -Force" command and rather than power off it rebooted, which is about the worst thing that can happen when the battery backup power is almost gone.&amp;nbsp; &amp;nbsp;The Stop-VMhost doesn't have any options concerning restart versus power off, but I was assuming it means power off.&amp;nbsp; &amp;nbsp; I can get around this by simply having the script not issue a Stop-VMhost command after the VMs have received their own shutdown commands and just let the computer go off when the power fails as it doesn't seem that ESXi itself has issues if the power is cut rather than being shutdown, but as this has happened on two different platforms now I'm wondering if there was a bug introduced somewhere in ESXi 7.02.&amp;nbsp; &amp;nbsp;&lt;/P&gt;&lt;P&gt;The bios in both computers is set to automatically boot upon power being applied, which is what you want for a computer in a location that isn't attended 24x7, but up to now that hasn't caused a reboot when ESXi was shutdown.&amp;nbsp; &amp;nbsp;&lt;/P&gt;&lt;P&gt;If anyone with a home lab would like to try setting their bios to automatically start when power is applied and then try to shutdown ESXi to see if it powers off or reboots I'd appreciate the feedback.&amp;nbsp; I don't know at this point if it's something particular to how I have ESXi configured (on both machines), or if this is a bug.&amp;nbsp; &amp;nbsp;I know it didn't used to reboot upon shutdown on the s2600 motherboard, but I don't remember the last patch level that I actually tried it and verified that it worked.&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Thu, 15 Jun 2023 20:29:06 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/ESXi-Discussions/ESXi-7-02-reboots-instead-of-powering-off-when-Shutdown-command/m-p/2922668#M283141</guid>
      <dc:creator>srwsol</dc:creator>
      <dc:date>2023-06-15T20:29:06Z</dc:date>
    </item>
    <item>
      <title>Powershell Stop-VMHost Question</title>
      <link>https://communities.vmware.com/t5/ESXi-Discussions/Powershell-Stop-VMHost-Question/m-p/2922622#M283134</link>
      <description>&lt;P&gt;I have a question about the functionality of the Powershell Stop-VMHost command.&amp;nbsp; &amp;nbsp; I am writing a UPS shutdown script that will run on a Linux VM on the host to be shutdown.&amp;nbsp; The script will be triggered by a snmp trap from the Tripplite UPS when the battery gets down to 7 minutes remaining.&amp;nbsp; &amp;nbsp;I'm able to shutdown all the VMs, except the one the script is running on, or at least issue a shutdown command to all of them (no point in waiting on completion as the power will fail shortly whether they finish in time or not).&amp;nbsp; &amp;nbsp;The final two commands in the script are to shutdown the host and shutdown the VM the script is running on.&amp;nbsp; I'm going to issue the host shutdown first in case issuing the shutdown to the VM running the script first causes it to shutdown before the command to shutdown the host could be issued.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;My question concerns what the -Force option really does.&amp;nbsp; &amp;nbsp;I've read conflicting things, and maybe it does both.&amp;nbsp; &amp;nbsp;I've read that it allows the shutdown to be done without the host going into maintenance mode, which is what I want as I want the VMs to come back up automatically after the power comes back on, which they won't if the host is in maintenance mode; but I've also read that it just terminates (i.e. powers off) any running VMs rather than waiting for a graceful shutdown, which I don't really want.&amp;nbsp; Also I've read that if you don't use -Force and the host isn't in maintenance mode a prompt message comes out like it would if you did a shutdown from the console not in maintenance mode, which of course I absolutely don't want in a UPS shutdown scenario when nobody will be there to answer.&amp;nbsp; &amp;nbsp;The documentation isn't clear on how -Confirm, -Force, and maintenance mode interact with each other.&amp;nbsp; &amp;nbsp; &amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;What I'd like to have happen is to give the VMs all the time remaining if necessary before the power goes off for them to gracefully shutdown, rather than arbitrarily killing them if there is still power available.&amp;nbsp; From what I've seen it doesn't seem that ESXi itself has a problem with being hard powered off (i.e. it doesn't seem to have data structures of its own in memory that need to be flushed or risk having it not startup correctly the next time if it shuts down hard).&amp;nbsp; &amp;nbsp;If that's actually the case I could simply not issue the host shutdown command at all and just leave it running until the battery dies, which would also have the effect of giving any VMs still in shutdown the maximum amount of time to actually shutdown and only give up on them when the battery dies.&amp;nbsp; &amp;nbsp;On the other hand, if I could tell ESXi to shutdown only after the last VM has gracefully shutdown, not hard power them off, and not prompt if not in maintenance mode, I think that would be the best possible situation, assuming that there aren't issues with ESXi itself going down hard if the battery runs out first.&amp;nbsp; &amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Sun, 07 Aug 2022 02:36:58 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/ESXi-Discussions/Powershell-Stop-VMHost-Question/m-p/2922622#M283134</guid>
      <dc:creator>srwsol</dc:creator>
      <dc:date>2022-08-07T02:36:58Z</dc:date>
    </item>
    <item>
      <title>ESXi 7 / Intel NUC / Laptop Docks</title>
      <link>https://communities.vmware.com/t5/ESXi-Discussions/ESXi-7-Intel-NUC-Laptop-Docks/m-p/2911394#M281942</link>
      <description>&lt;P&gt;Hi folks:&lt;/P&gt;&lt;P&gt;I'm just putting this out here as an FYI for those of you who might be using Intel NUCs with ESXi for a home lab or something.&amp;nbsp; &amp;nbsp;I recently got an Intel NUC11TNHv7 that I'm going to put in a remote location, running ESXi 7, and just for the heck of it during my testing I tried hooking up my Lenovo Thinkpad laptop dock to the thunderbolt port on the NUC to see what happened.&amp;nbsp;&lt;/P&gt;&lt;P&gt;I was pleasantly surprised to find out that ESXi recognizes the dock and allows the devices attached to the dock to be assigned to VMs as USB devices.&amp;nbsp; &amp;nbsp;It appears that any actual USB devices show up as individual devices to ESXi just as if you had plugged them in to a regular USB port.&amp;nbsp; &amp;nbsp;There is one other device that you can connect to a VM as a Host USB Device which is identified as the dock itself.&amp;nbsp; &amp;nbsp;It appears that this USB device contains all the other devices on the dock other than actual USB devices.&amp;nbsp; &amp;nbsp;In my case when I assigned the dock itself to a VM, it gained access to the ethernet adapter on the dock.&amp;nbsp; I think it also gained access to the hdmi and display ports, but I don't think they would be usable in a VM unless it had an actual graphics card assigned to it as well.&amp;nbsp; &amp;nbsp;As the NUC only has one graphics adapter I was reluctant to enable it as a PCI passthru device out of fear that ESXi wouldn't boot without a graphics card and I'd be hard pressed to undo that change if that happened.&amp;nbsp; &amp;nbsp;&lt;/P&gt;&lt;P&gt;Anyway, I just thought I'd post this as something interesting for folks thinking of using a NUC for their home labs or in some capacity where it was OK to have a technically non-supported device running ESXi.&amp;nbsp; &amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Thu, 26 May 2022 21:34:39 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/ESXi-Discussions/ESXi-7-Intel-NUC-Laptop-Docks/m-p/2911394#M281942</guid>
      <dc:creator>srwsol</dc:creator>
      <dc:date>2022-05-26T21:34:39Z</dc:date>
    </item>
    <item>
      <title>Re: NUC 11 Hardware Sensors</title>
      <link>https://communities.vmware.com/t5/ESXi-Discussions/NUC-11-Hardware-Sensors/m-p/2909766#M281714</link>
      <description>&lt;P&gt;OK, thanks for the replies.&amp;nbsp; &amp;nbsp;It's not a show stopper, but the NUC will end up in a remote location where it's kind of warm, so it would have been nice to have the sensor data available to see if it's getting anywhere close to the limits.&amp;nbsp; &amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Wed, 18 May 2022 15:06:02 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/ESXi-Discussions/NUC-11-Hardware-Sensors/m-p/2909766#M281714</guid>
      <dc:creator>srwsol</dc:creator>
      <dc:date>2022-05-18T15:06:02Z</dc:date>
    </item>
    <item>
      <title>NUC 11 Hardware Sensors</title>
      <link>https://communities.vmware.com/t5/ESXi-Discussions/NUC-11-Hardware-Sensors/m-p/2909274#M281647</link>
      <description>&lt;P&gt;Hi folks:&lt;/P&gt;&lt;P&gt;I just got my hands on an Intel NUC11TNHv7 and have installed the latest version of ESXi on it after creating a custom install ISO with the drivers for the 2.5gbs network adapters in it.&amp;nbsp; &amp;nbsp;It seems to work just fine with the exception of not seeing the hardware health sensors.&amp;nbsp; &amp;nbsp;Does anyone know if there are any flings or other drivers available for those?&amp;nbsp; &amp;nbsp;Also if drivers aren't available, is there any way to make those hardware sensors available to a VM, as the more recent versions of the Linux kernel do support those sensors as I saw the temperature data when booting a live version of Debian 11 off of a thumb drive.&amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Mon, 16 May 2022 16:29:25 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/ESXi-Discussions/NUC-11-Hardware-Sensors/m-p/2909274#M281647</guid>
      <dc:creator>srwsol</dc:creator>
      <dc:date>2022-05-16T16:29:25Z</dc:date>
    </item>
    <item>
      <title>ESXi 7 Update 3c Install Issue</title>
      <link>https://communities.vmware.com/t5/vSphere-Upgrade-Install/ESXi-7-Update-3c-Install-Issue/m-p/2901167#M33912</link>
      <description>&lt;P&gt;Hi folks:&lt;/P&gt;&lt;P&gt;I'm having an issue upgrading an ESXi 7.0 update 2 (&lt;SPAN&gt;&amp;nbsp;ESXi-7.0U2a-17867351-standard) to update 3c via the iso file.&amp;nbsp; When the computer boots into the iso image it fails right after loading tools.t00 with error 10, out of resources.&amp;nbsp; &amp;nbsp; Now I will preface this with the fact that I'm running ESXi on an old whitebox that's not listed as compatible hardware, but it's quite generic and has worked for the past ten years (it's an Intel DQ77KB motherboard with a 3770S CPU and 16 gb of memory).&amp;nbsp; &amp;nbsp;I use this in my second home to run a few Linux VMs that serve as the backup site for my one person consulting business, so I really don't need anything more powerful than this.&amp;nbsp; &amp;nbsp;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;I've read several things about this error occurring with other versions of ESXi when installing from the ISO and they seem to center around either incompatible hardware, too many adapters, bios settings, or not booting with UEFI.&amp;nbsp; &amp;nbsp; I had an old pcie wifi card and an extra usb adapter on the motherboard, so I removed them with no effect.&amp;nbsp; &amp;nbsp;The bios doesn't have much in the way of settings for how memory is used, so the only setting I could change was to reduce the video memory from 128M to 32M, which didn't fix the problem.&amp;nbsp; &amp;nbsp; &lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;I am legacy booting, although the bios does support UEFI.&amp;nbsp; &amp;nbsp;I didn't try setting it to UEFI because I was concerned that if it worked, what would happen when the upgrade ran against an ESXi installation that wasn't UEFI and perhaps I'd end up with an unbootable system.&amp;nbsp; &amp;nbsp;Am interested if anyone knows if the upgrade would change the boot records to UEFI if I did that.&amp;nbsp; &amp;nbsp;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;Also, I know I could run the upgrade from the offline bundle and I suspect that the upgrade would finish, but I was concerned that the system might hang at exactly this same spot upon reboot, as I'm under the impression that the boot sequence for the iso is the same as what the system on disk would use after an upgrade.&amp;nbsp; &amp;nbsp;If that's not the case, then I could try that.&amp;nbsp; &amp;nbsp;I guess I could also try using the offline bundle without the tools, if the problem is actually related to loading tools.t00.&amp;nbsp; &amp;nbsp; &lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;&amp;nbsp;Suggestions welcome.&amp;nbsp;&amp;nbsp;&lt;/SPAN&gt;&lt;/P&gt;</description>
      <pubDate>Tue, 29 Mar 2022 20:33:58 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/vSphere-Upgrade-Install/ESXi-7-Update-3c-Install-Issue/m-p/2901167#M33912</guid>
      <dc:creator>srwsol</dc:creator>
      <dc:date>2022-03-29T20:33:58Z</dc:date>
    </item>
    <item>
      <title>Upgrading 6.7 to 7 with clean install to another disk?</title>
      <link>https://communities.vmware.com/t5/vSphere-Upgrade-Install/Upgrading-6-7-to-7-with-clean-install-to-another-disk/m-p/2809910#M32707</link>
      <description>&lt;P&gt;Hi folks:&lt;/P&gt;&lt;P&gt;I'm getting ready to upgrade ESXi 6.7 to 7 and I'm trying to figure out the best and safest way to go about it.&amp;nbsp; Right now 6.7, which has been upgraded over the years from originally version 4, is installed on a 4TB Raid 10 array along with the datastore.&amp;nbsp; &amp;nbsp;After reading about the partition changes that will happen with version 7, thus preventing any kind of roll back if there are problems, short of having a full 4tb sector by sector disk image of the whole array, I was wondering if it might be better to buy a half terabyte ssd drive and install ESXi 7 on that drive along with whatever minimal datastore it requires for the installation, and then simply mount the existing big datastore on the Raid array to ESXi 7, thus preserving the 6.7 installation and the partition layout just in case I have to back out.&amp;nbsp; &amp;nbsp;&lt;/P&gt;&lt;P&gt;The two potential issues that I see with this approach are first if ESXi 7 makes any changes to the datastore itself that would render it unusable by 6.7, and second I didn't think that one could backup the configuration from a prior release of ESXi and restore it to a freshly installed later version although I'm not 100% sure of that.&amp;nbsp; &amp;nbsp;I've been wanting for several years to divorce the datastore from the same physical drive as ESXi itself was on, as that might lend additional flexibility to take a full sector by sector image backup of the datastore partition while running copies of just a couple of the critical VMs that can't be down for a weekend (e.g. the email server) on another temporary datastore, which would be very difficult the way things are setup now, and so that would be another good reason to do this if I can make it work.&lt;/P&gt;&lt;P&gt;Thoughts and suggestions welcome.&amp;nbsp; &amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Tue, 17 Nov 2020 03:03:59 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/vSphere-Upgrade-Install/Upgrading-6-7-to-7-with-clean-install-to-another-disk/m-p/2809910#M32707</guid>
      <dc:creator>srwsol</dc:creator>
      <dc:date>2020-11-17T03:03:59Z</dc:date>
    </item>
  </channel>
</rss>

