<?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>Kinnison Tracker</title>
    <link>https://communities.vmware.com/wbsdv95928/tracker</link>
    <description>Kinnison Tracker</description>
    <pubDate>Fri, 10 Nov 2023 23:57:56 GMT</pubDate>
    <dc:date>2023-11-10T23:57:56Z</dc:date>
    <item>
      <title>Re: What is ops TCP/IP stack. This was pre-built with v8</title>
      <link>https://communities.vmware.com/t5/VMware-vSphere-Discussions/What-is-ops-TCP-IP-stack-This-was-pre-built-with-v8/m-p/2995159#M46394</link>
      <description>&lt;P&gt;&lt;STRONG&gt;Hello,&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;&lt;BR /&gt;Sorry, in ESXi 7.x there are three types of TCP/IP stack, the "default" one, the "vMotion" one and the "Provisioning" one, nothing else.&lt;/P&gt;&lt;P&gt;&lt;BR /&gt;&lt;STRONG&gt;Regards,&lt;/STRONG&gt;&lt;BR /&gt;&lt;STRONG&gt;Ferdinando&lt;/STRONG&gt;&lt;/P&gt;</description>
      <pubDate>Fri, 10 Nov 2023 17:22:42 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/VMware-vSphere-Discussions/What-is-ops-TCP-IP-stack-This-was-pre-built-with-v8/m-p/2995159#M46394</guid>
      <dc:creator>Kinnison</dc:creator>
      <dc:date>2023-11-10T17:22:42Z</dc:date>
    </item>
    <item>
      <title>Re: What is ops TCP/IP stack. This was pre-built with v8</title>
      <link>https://communities.vmware.com/t5/VMware-vSphere-Discussions/What-is-ops-TCP-IP-stack-This-was-pre-built-with-v8/m-p/2995153#M46392</link>
      <description>&lt;P&gt;&lt;STRONG&gt;Hello jicooper,&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;&lt;BR /&gt;No, I don't think it's so, the "OPS" TCP/IP stack was absent till the first build of ESXi 8.0, I can tell you that ESXi 7.0U3n it does not feature any "OPS" TCP/IP stack, the same way as previous versions of which I still have memory.&lt;/P&gt;&lt;P&gt;&lt;BR /&gt;&lt;STRONG&gt;Regards,&lt;/STRONG&gt;&lt;BR /&gt;&lt;STRONG&gt;Ferdinando&lt;/STRONG&gt;&lt;/P&gt;</description>
      <pubDate>Fri, 10 Nov 2023 16:22:15 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/VMware-vSphere-Discussions/What-is-ops-TCP-IP-stack-This-was-pre-built-with-v8/m-p/2995153#M46392</guid>
      <dc:creator>Kinnison</dc:creator>
      <dc:date>2023-11-10T16:22:15Z</dc:date>
    </item>
    <item>
      <title>Re: Workstation 17.5.0: (enhanced?) keyboard driver problem</title>
      <link>https://communities.vmware.com/t5/VMware-Workstation-Pro/Workstation-17-5-0-enhanced-keyboard-driver-problem/m-p/2995114#M183677</link>
      <description>&lt;P&gt;&lt;STRONG&gt;Hello,&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;&lt;BR /&gt;You're right, mine was just a curiosity at the time.&lt;/P&gt;&lt;P&gt;&lt;BR /&gt;Then, if we want to see it in slightly more practical terms, reading the various comments expressed, I doubt you will find an effective remedy to the problem exposed here, other than trying to go back to the immediately previous version.&lt;/P&gt;&lt;P&gt;&lt;BR /&gt;&lt;STRONG&gt;Regards,&lt;/STRONG&gt;&lt;BR /&gt;&lt;STRONG&gt;Ferdinando&lt;/STRONG&gt;&lt;/P&gt;</description>
      <pubDate>Fri, 10 Nov 2023 12:28:52 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/VMware-Workstation-Pro/Workstation-17-5-0-enhanced-keyboard-driver-problem/m-p/2995114#M183677</guid>
      <dc:creator>Kinnison</dc:creator>
      <dc:date>2023-11-10T12:28:52Z</dc:date>
    </item>
    <item>
      <title>Re: Workstation 17.5.0: (enhanced?) keyboard driver problem</title>
      <link>https://communities.vmware.com/t5/VMware-Workstation-Pro/Workstation-17-5-0-enhanced-keyboard-driver-problem/m-p/2995098#M183672</link>
      <description>&lt;P&gt;&lt;STRONG&gt;Hello,&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;&lt;BR /&gt;Curious, yesterday this thread spread over four "pages", today they have become three.&lt;/P&gt;&lt;P&gt;&lt;BR /&gt;&lt;STRONG&gt;Regards,&lt;/STRONG&gt;&lt;BR /&gt;&lt;STRONG&gt;Ferdinando&lt;/STRONG&gt;&lt;/P&gt;</description>
      <pubDate>Fri, 10 Nov 2023 10:35:40 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/VMware-Workstation-Pro/Workstation-17-5-0-enhanced-keyboard-driver-problem/m-p/2995098#M183672</guid>
      <dc:creator>Kinnison</dc:creator>
      <dc:date>2023-11-10T10:35:40Z</dc:date>
    </item>
    <item>
      <title>Re: How to open fsl from vmware workstation</title>
      <link>https://communities.vmware.com/t5/VMware-Workstation-Player/How-to-open-fsl-from-vmware-workstation/m-p/2995097#M41090</link>
      <description>&lt;P&gt;&lt;STRONG&gt;Hello,&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;&lt;BR /&gt;So the solution at least as far as VMware technologies are concerned is all in all simple, deploy a suitably sized virtual machine with the GUEST operating system that you deem appropriate and then load those libraries.&lt;/P&gt;&lt;P&gt;&lt;BR /&gt;&lt;STRONG&gt;Regards,&lt;/STRONG&gt;&lt;BR /&gt;&lt;STRONG&gt;Ferdinando&lt;/STRONG&gt;&lt;/P&gt;</description>
      <pubDate>Fri, 10 Nov 2023 10:28:56 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/VMware-Workstation-Player/How-to-open-fsl-from-vmware-workstation/m-p/2995097#M41090</guid>
      <dc:creator>Kinnison</dc:creator>
      <dc:date>2023-11-10T10:28:56Z</dc:date>
    </item>
    <item>
      <title>Re: windows image backup restore on ESXi 8.02</title>
      <link>https://communities.vmware.com/t5/ESXi-Discussions/windows-image-backup-restore-on-ESXi-8-02/m-p/2994869#M291036</link>
      <description>&lt;P&gt;&lt;STRONG&gt;Hello,&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;&lt;BR /&gt;It's difficult to say, a generic "Windows Backup Image" doesn't say much about its concrete possibility of making some use of it in an operating context different from the one, not better specified, from which it was obtained (and how).&lt;/P&gt;&lt;P&gt;&lt;BR /&gt;&lt;STRONG&gt;Regards,&lt;/STRONG&gt;&lt;BR /&gt;&lt;STRONG&gt;Ferdinando&lt;/STRONG&gt;&lt;/P&gt;</description>
      <pubDate>Thu, 09 Nov 2023 06:28:17 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/ESXi-Discussions/windows-image-backup-restore-on-ESXi-8-02/m-p/2994869#M291036</guid>
      <dc:creator>Kinnison</dc:creator>
      <dc:date>2023-11-09T06:28:17Z</dc:date>
    </item>
    <item>
      <title>Re: windows server 2022 slow on vmware esxi 6.7</title>
      <link>https://communities.vmware.com/t5/ESXi-Discussions/windows-server-2022-slow-on-vmware-esxi-6-7/m-p/2994868#M291035</link>
      <description>&lt;P&gt;&lt;STRONG&gt;Hello,&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;&lt;BR /&gt;In a time of hardship which is not unusual in the micro-business sector it can be a problem but, in my opinion, you should consider getting a more modern system, otherwise having licenses for the most recent versions of the ESXi product isn't of much use if for a reason you may not be able to use them due to lack of support / incompatible hardware.&lt;/P&gt;&lt;P&gt;&lt;BR /&gt;&lt;STRONG&gt;Regards,&lt;/STRONG&gt;&lt;BR /&gt;&lt;STRONG&gt;Ferdinando&lt;/STRONG&gt;&lt;/P&gt;</description>
      <pubDate>Thu, 09 Nov 2023 06:16:58 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/ESXi-Discussions/windows-server-2022-slow-on-vmware-esxi-6-7/m-p/2994868#M291035</guid>
      <dc:creator>Kinnison</dc:creator>
      <dc:date>2023-11-09T06:16:58Z</dc:date>
    </item>
    <item>
      <title>Re: windows server 2022 slow on vmware esxi 6.7</title>
      <link>https://communities.vmware.com/t5/ESXi-Discussions/windows-server-2022-slow-on-vmware-esxi-6-7/m-p/2994732#M291021</link>
      <description>&lt;P&gt;&lt;STRONG&gt;Hello,&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;&lt;BR /&gt;I understand, from a RAID 6 array made up of mechanical ones, perhaps of an old generation, the expectation of adequate performance, especially in writing, in conditions of high IOPS is objectively unrealistic, perhaps the possible cache of the disk controller, assuming in "write back" mode (in case check the battery status) it does something but as they say where I come from, "you can't get blood from turnips".&lt;/P&gt;&lt;P&gt;&lt;BR /&gt;&lt;STRONG&gt;Regards,&lt;/STRONG&gt;&lt;BR /&gt;&lt;STRONG&gt;Ferdinando&lt;/STRONG&gt;&lt;/P&gt;</description>
      <pubDate>Wed, 08 Nov 2023 16:27:06 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/ESXi-Discussions/windows-server-2022-slow-on-vmware-esxi-6-7/m-p/2994732#M291021</guid>
      <dc:creator>Kinnison</dc:creator>
      <dc:date>2023-11-08T16:27:06Z</dc:date>
    </item>
    <item>
      <title>Re: windows server 2022 slow on vmware esxi 6.7</title>
      <link>https://communities.vmware.com/t5/ESXi-Discussions/windows-server-2022-slow-on-vmware-esxi-6-7/m-p/2994722#M291018</link>
      <description>&lt;P&gt;&lt;STRONG&gt;Hello,&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;&lt;BR /&gt;Now it's a little clearer, so your E5-2609 (V1/V2) has 4 physical cores without hyperthreading and limited to DDR3 memory modules with 800/1066 Mhz speeds, so you have to be careful about how you configure your virtual machines, because depending on your workloads, if you have too unfavorable a ratio between physical cores and virtual cores, performance suffers, with the understanding that you can't expect much anyway.&lt;BR /&gt;Your storage is made up of 8 disk drives in a RAID 6 array but it is not clear whether mechanical or solid state and what type, this also affects the final result to a more or less significant extent.&lt;/P&gt;&lt;P&gt;&lt;BR /&gt;So, to try to narrow down the causes of your problems, in my opinion I would start by consulting the contents of this KB article:&lt;BR /&gt;&lt;A href="https://kb.vmware.com/s/article/2001003" target="_blank"&gt;https://kb.vmware.com/s/article/2001003&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;BR /&gt;Forget the experience of the OP, each case is a story in itself as is the concept of performance if there is no objectively reproducible and/or measurable feedback.&lt;/P&gt;&lt;P&gt;&lt;BR /&gt;&lt;STRONG&gt;Regards,&lt;/STRONG&gt;&lt;BR /&gt;&lt;STRONG&gt;Ferdinando&lt;/STRONG&gt;&lt;/P&gt;</description>
      <pubDate>Wed, 08 Nov 2023 15:30:05 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/ESXi-Discussions/windows-server-2022-slow-on-vmware-esxi-6-7/m-p/2994722#M291018</guid>
      <dc:creator>Kinnison</dc:creator>
      <dc:date>2023-11-08T15:30:05Z</dc:date>
    </item>
    <item>
      <title>Re: windows server 2022 slow on vmware esxi 6.7</title>
      <link>https://communities.vmware.com/t5/ESXi-Discussions/windows-server-2022-slow-on-vmware-esxi-6-7/m-p/2994668#M291011</link>
      <description>&lt;P&gt;&lt;STRONG&gt;Hello,&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;&lt;BR /&gt;One moment please, I use some systems from another manufacturer but of the same generation as yours but I haven't even thought about installing the 3 Terabytes of RAM nominally supported on paper not even when they were brand new. So you see that "maxed out" on RAM can mean many things. So explain for a moment how you achieved the result, for example you won't be using a configuration called 3DPC or just part of the four available memory controllers of your CPU. The issue of ESXi licenses is also a topic of relative value if you don't specify for a moment what license level you refer to.&lt;/P&gt;&lt;P&gt;&lt;BR /&gt;If we want to talk about this and that, you plan to procure new licenses related to the "Microsoft Windows Server 2022" product because perhaps you use versions that are no longer supported but then as a basis you plan to use an equally unsupported version of ESXi and not without vulnerability, don't you find it a sort of contradiction in terms?&lt;/P&gt;&lt;P&gt;&lt;BR /&gt;In short, IMHO, if you want some less far-fetched advice, in my opinion you should provide some details, going a little more specifically into how your system is actually configured.&lt;/P&gt;&lt;P&gt;&lt;BR /&gt;&lt;STRONG&gt;Regards,&lt;/STRONG&gt;&lt;BR /&gt;&lt;STRONG&gt;Ferdinando&lt;/STRONG&gt;&lt;/P&gt;</description>
      <pubDate>Wed, 08 Nov 2023 12:40:39 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/ESXi-Discussions/windows-server-2022-slow-on-vmware-esxi-6-7/m-p/2994668#M291011</guid>
      <dc:creator>Kinnison</dc:creator>
      <dc:date>2023-11-08T12:40:39Z</dc:date>
    </item>
    <item>
      <title>Re: windows server 2022 slow on vmware esxi 6.7</title>
      <link>https://communities.vmware.com/t5/ESXi-Discussions/windows-server-2022-slow-on-vmware-esxi-6-7/m-p/2994662#M291008</link>
      <description>&lt;P&gt;&lt;STRONG&gt;Hello NickDaGeekUK,&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;&lt;BR /&gt;I mean, we can discuss many things but objectively ESXi 6.5 (to which you are referring) as well as being a product that is no longer supported, does not benefit from those substantial improvements, large and small, introduced with subsequent versions, which your system, at least on paper (i.e. for HCL), should support up to the latest build of the 7.0U3 line. The system firmware released by the manufacturer has an equally important role in the iteration and usually when a more recent version is released it is because more or less substantial corrections have been applied to various types of inconveniences.&lt;/P&gt;&lt;P&gt;&lt;BR /&gt;It's not clear to me what you mean by "maxed out" on RAM and STORAGE but not in CPU count, because in itself it doesn't say much.&lt;BR /&gt;And moreover, it is not entirely negligible how the hardware of your virtual machine and/or the operating system itself is set.&lt;/P&gt;&lt;P&gt;&lt;BR /&gt;The point of my speech is that based on what I have read you can only formulate hypotheses but not go much further.&lt;/P&gt;&lt;P&gt;&lt;BR /&gt;&lt;STRONG&gt;Regards,&lt;/STRONG&gt;&lt;BR /&gt;&lt;STRONG&gt;Ferdinando&lt;/STRONG&gt;&lt;/P&gt;</description>
      <pubDate>Wed, 08 Nov 2023 11:11:10 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/ESXi-Discussions/windows-server-2022-slow-on-vmware-esxi-6-7/m-p/2994662#M291008</guid>
      <dc:creator>Kinnison</dc:creator>
      <dc:date>2023-11-08T11:11:10Z</dc:date>
    </item>
    <item>
      <title>Re: How can I recover the Win11 product key in VM?</title>
      <link>https://communities.vmware.com/t5/VMware-Workstation-Pro/How-can-I-recover-the-Win11-product-key-in-VM/m-p/2994626#M183616</link>
      <description>&lt;P&gt;&lt;STRONG&gt;Hello,&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;&lt;BR /&gt;I apologized in general for intruding on a question that I would have been better off not answering in the first place.&lt;/P&gt;&lt;P&gt;&lt;BR /&gt;&lt;STRONG&gt;Regards,&lt;/STRONG&gt;&lt;BR /&gt;&lt;STRONG&gt;Ferdinando&lt;/STRONG&gt;&lt;/P&gt;</description>
      <pubDate>Wed, 08 Nov 2023 05:44:26 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/VMware-Workstation-Pro/How-can-I-recover-the-Win11-product-key-in-VM/m-p/2994626#M183616</guid>
      <dc:creator>Kinnison</dc:creator>
      <dc:date>2023-11-08T05:44:26Z</dc:date>
    </item>
    <item>
      <title>Re: How can I recover the Win11 product key in VM?</title>
      <link>https://communities.vmware.com/t5/VMware-Workstation-Pro/How-can-I-recover-the-Win11-product-key-in-VM/m-p/2994580#M183602</link>
      <description>&lt;P&gt;&lt;STRONG&gt;Hello,&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;&lt;BR /&gt;Of course the virtual maybe it could be recoverable "as is", but the question was a little more specific, that is, where to recover the "product key" and that is another matter. Sorry if I intruded.&lt;/P&gt;&lt;P&gt;&lt;BR /&gt;&lt;STRONG&gt;Regards,&lt;/STRONG&gt;&lt;BR /&gt;&lt;STRONG&gt;Ferdinando&lt;/STRONG&gt;&lt;/P&gt;</description>
      <pubDate>Tue, 07 Nov 2023 20:05:56 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/VMware-Workstation-Pro/How-can-I-recover-the-Win11-product-key-in-VM/m-p/2994580#M183602</guid>
      <dc:creator>Kinnison</dc:creator>
      <dc:date>2023-11-07T20:05:56Z</dc:date>
    </item>
    <item>
      <title>Re: How can I recover the Win11 product key in VM?</title>
      <link>https://communities.vmware.com/t5/VMware-Workstation-Pro/How-can-I-recover-the-Win11-product-key-in-VM/m-p/2994573#M183599</link>
      <description>&lt;P&gt;&lt;STRONG&gt;Hello,&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;&lt;BR /&gt;Rather difficult, to say unlikely at least from a non-functional machine, it is supposed that the "product key" used to activate the product it was obtained somehow and stored somewhere. Perhaps by asking in more specific forums about Microsoft products you might find a better answer to your question, whether it is a physical or virtual machine your problem does not change.&lt;/P&gt;&lt;P&gt;&lt;BR /&gt;If you had a working copy, not necessarily recent, of that same virtual machine, solving your "problem" could be much simpler. You can find several possible methods on the internet.&lt;/P&gt;&lt;P&gt;&lt;BR /&gt;&lt;STRONG&gt;Regards,&lt;/STRONG&gt;&lt;BR /&gt;&lt;STRONG&gt;Ferdinando&lt;/STRONG&gt;&lt;/P&gt;</description>
      <pubDate>Tue, 07 Nov 2023 19:32:48 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/VMware-Workstation-Pro/How-can-I-recover-the-Win11-product-key-in-VM/m-p/2994573#M183599</guid>
      <dc:creator>Kinnison</dc:creator>
      <dc:date>2023-11-07T19:32:48Z</dc:date>
    </item>
    <item>
      <title>Re: windows server 2022 slow on vmware esxi 6.7</title>
      <link>https://communities.vmware.com/t5/ESXi-Discussions/windows-server-2022-slow-on-vmware-esxi-6-7/m-p/2994570#M290995</link>
      <description>&lt;P&gt;&lt;STRONG&gt;Hello,&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;&lt;BR /&gt;If I may interject, my experience with Microsoft Windows Server 2022 in the context of my small vSphere infrastructure is completely different, personally I find it much more responsive than previous versions. However, I must also tell you that the improvements, also in terms of "performance", made in subsequent product versions compared to the one you use have been substantial, then it also depends on how your virtual machines are configured, in relation to the intended workload.&lt;/P&gt;&lt;P&gt;&lt;BR /&gt;In the end, IMHO, the efficiency / effectiveness of a system is the sum of a whole set of multiple interrelated factors, often small things that we sometimes risk putting off until another time and perhaps ending up forgetting.&lt;/P&gt;&lt;P&gt;&lt;BR /&gt;&lt;STRONG&gt;Regards,&lt;/STRONG&gt;&lt;BR /&gt;&lt;STRONG&gt;Ferdinando&lt;/STRONG&gt;&lt;/P&gt;</description>
      <pubDate>Tue, 07 Nov 2023 18:51:55 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/ESXi-Discussions/windows-server-2022-slow-on-vmware-esxi-6-7/m-p/2994570#M290995</guid>
      <dc:creator>Kinnison</dc:creator>
      <dc:date>2023-11-07T18:51:55Z</dc:date>
    </item>
    <item>
      <title>Re: Installing vcenter 7 on esxi 6.7 host without Internet, domain or dns.  Is this possible?</title>
      <link>https://communities.vmware.com/t5/VMware-vCenter-Discussions/Installing-vcenter-7-on-esxi-6-7-host-without-Internet-domain-or/m-p/2994564#M49731</link>
      <description>&lt;P&gt;&lt;STRONG&gt;Hello,&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;&lt;BR /&gt;I'm sorry but I don't agree, there is no real need to bother with an infrastructure centered around the "Active Directory" services to provide DNS, DHCP and NTP services, this can be achieved by using a LINUX distribution set up for that one and only purpose and/or the capabilities of many barely decent network devices.&lt;/P&gt;&lt;P&gt;&lt;BR /&gt;This is without prejudice to the fact that, as others have pointed out, moreover explained in a BLOG, it is possible to deploy a vCenter object in a context where DNS and NTP services are unavailable.&lt;/P&gt;&lt;P&gt;&lt;BR /&gt;&lt;STRONG&gt;Regards,&lt;/STRONG&gt;&lt;BR /&gt;&lt;STRONG&gt;Ferdinando&lt;/STRONG&gt;&lt;/P&gt;</description>
      <pubDate>Tue, 07 Nov 2023 17:46:45 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/VMware-vCenter-Discussions/Installing-vcenter-7-on-esxi-6-7-host-without-Internet-domain-or/m-p/2994564#M49731</guid>
      <dc:creator>Kinnison</dc:creator>
      <dc:date>2023-11-07T17:46:45Z</dc:date>
    </item>
    <item>
      <title>Re: How to evaluate VCSA 8 in current environment?</title>
      <link>https://communities.vmware.com/t5/vCenter-Server-Discussions/How-to-evaluate-VCSA-8-in-current-environment/m-p/2994558#M95141</link>
      <description>&lt;P&gt;&lt;STRONG&gt;Hello,&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;&lt;BR /&gt;The issue is a little more complex than simply evaluating how a version 8.x vCenter object behaves because you have to consider the relationships/iterations that exist with other products from both VMware and any third parties. Before embarking on the undertaking it is always advisable to consult the available compatibility matrices first, it can help you avoid many potential problems from the start.&lt;/P&gt;&lt;P&gt;&lt;BR /&gt;From my very personal point of view, if you have adequate time and means, the only way to gain confidence in such a case is to try to build an IT laboratory which, albeit within certain limits, reproduces the specifics of your vSphere infrastructure as faithfully as possible.&lt;/P&gt;&lt;P&gt;&lt;BR /&gt;&lt;STRONG&gt;Regards,&lt;/STRONG&gt;&lt;BR /&gt;&lt;STRONG&gt;Ferdinando&lt;/STRONG&gt;&lt;/P&gt;</description>
      <pubDate>Tue, 07 Nov 2023 17:16:17 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/vCenter-Server-Discussions/How-to-evaluate-VCSA-8-in-current-environment/m-p/2994558#M95141</guid>
      <dc:creator>Kinnison</dc:creator>
      <dc:date>2023-11-07T17:16:17Z</dc:date>
    </item>
    <item>
      <title>Re: ESXi installation drive and IBM RAID card</title>
      <link>https://communities.vmware.com/t5/ESXi-Discussions/ESXi-installation-drive-and-IBM-RAID-card/m-p/2994283#M290965</link>
      <description>&lt;P&gt;&lt;STRONG&gt;Hello,&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;&lt;BR /&gt;You have to make sure, consult the HCL list, that your system is supported for the version of ESXi you intend to install and it is generally advisable to use the "custom" builds released by the manufacturer of the same which include more specific drivers for the underlying hardware.&lt;/P&gt;&lt;P&gt;&lt;BR /&gt;&lt;STRONG&gt;Regards,&lt;/STRONG&gt;&lt;BR /&gt;&lt;STRONG&gt;Ferdinando&lt;/STRONG&gt;&lt;/P&gt;</description>
      <pubDate>Sun, 05 Nov 2023 18:48:54 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/ESXi-Discussions/ESXi-installation-drive-and-IBM-RAID-card/m-p/2994283#M290965</guid>
      <dc:creator>Kinnison</dc:creator>
      <dc:date>2023-11-05T18:48:54Z</dc:date>
    </item>
    <item>
      <title>Re: Installing vmware esxi 6.0 on pcie M.2 SSD</title>
      <link>https://communities.vmware.com/t5/ESXi-Discussions/Installing-vmware-esxi-6-0-on-pcie-M-2-SSD/m-p/2994279#M290964</link>
      <description>&lt;P&gt;&lt;STRONG&gt;Hello,&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;&lt;BR /&gt;No, some NVME SSD had a built-in "Option ROM" to make them usable as "legacy boot devices" in (some) systems that did not have native support for them but they are now uncommon, some adapters allowed the same to be achieved. Your system was not designed to boot from a pure NVME drive so its "bios" lacks the necessary code and it's so dated that no one (reasonable) thought to implement it at a later time.&lt;/P&gt;&lt;P&gt;&lt;BR /&gt;In rather general terms, hardware aimed at the enterprise market is designed for use in those specific contexts, where anything that can compromise its reliability or complicate its supportability always translates into potentially economically significant damage.&lt;/P&gt;&lt;P&gt;&lt;BR /&gt;&lt;STRONG&gt;Regards,&lt;/STRONG&gt;&lt;BR /&gt;&lt;STRONG&gt;Ferdinando&lt;/STRONG&gt;&lt;/P&gt;</description>
      <pubDate>Sun, 05 Nov 2023 18:17:34 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/ESXi-Discussions/Installing-vmware-esxi-6-0-on-pcie-M-2-SSD/m-p/2994279#M290964</guid>
      <dc:creator>Kinnison</dc:creator>
      <dc:date>2023-11-05T18:17:34Z</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/2994250#M95138</link>
      <description>&lt;P&gt;&lt;STRONG&gt;&lt;a href="https://communities.vmware.com/t5/user/viewprofilepage/user-id/5551087"&gt;@pmichelli&lt;/a&gt;, hello,&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;&lt;BR /&gt;Personally I think that a lot depends on the specific operating context, which is different for each of us, but limiting myself to my specific case, this new build, like the one immediately before it, did not impress me and I would not derive any practical benefits as a result of the new features introduced. Of course I updated my vCenter object to version 8.0U1d to fix a discovered critical vulnerability and that was that.&lt;/P&gt;&lt;P&gt;&lt;BR /&gt;&lt;STRONG&gt;Regards,&lt;/STRONG&gt;&lt;BR /&gt;&lt;STRONG&gt;Ferdinando&lt;/STRONG&gt;&lt;/P&gt;</description>
      <pubDate>Sun, 05 Nov 2023 08:08:59 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/vCenter-Server-Discussions/vCenter-8-02-U2a-is-out-Change-notes/m-p/2994250#M95138</guid>
      <dc:creator>Kinnison</dc:creator>
      <dc:date>2023-11-05T08:08:59Z</dc:date>
    </item>
  </channel>
</rss>

