When you attempt to set up VMware ESXi ón some whitebox hardware that can be not officially backed by VMware then your attempt might come to an unpleasant end after the installer provided the mistake message shown above. ESXi has in-box assistance for a restricted number of network user interface credit cards (NICs), and unfortunately a lot of consumer grade gadgets are not on the list.

1. Esxi Install Drivers
2. Esxi Network Adapters
3. Add Drivers To Esxi Installer

Is this the end of the world? If you are a normal reader of my blog page after that you possibly already know that help (and in some instances even recovery) is usually available.

However, I keep getting e-mails from people inquiring how to obtain their NIC xyz to work with ESXi. Therefore I lastly had taken the period to create down all the actions that you require to get and the options you possess - just to stage them right here rather of offering the same answers per e-mail once again and again. A very similar article of mine can be - it is certainly about a season old right now and with 80k pageviews my nearly all successful blog page post actually. Let's discover how this a single will go. Before you move forward: Are you in a rush, or simply very lazy, or do not like to fiddle around with generating customized ESXi ISOs? After that skip out on to phase 7 at the bottom right today and forget the relaxation!

1. How to add network drivers to installation? If you use ESXi 6.0 or ESXi 6.5 or newer. How to add a NIC driver to VMware ESXi 5.1 ISO?
2. Installing ESXi 6 with BlackListed Drivers. The original 5.1 driver). Move forward to the vSphere 6 launch and VMware have gone. Network contention.

You should also ignore to step 7 right now if your NIC is certainly a wireless gadget or linked through a USB slot. There can be no way to obtain these working in ESXi, the using steps just utilize to PCI structured LAN controllers: 1. Discover out your gadget's name and PCI Identification The 1st and one of the nearly all important measures is to obviously identify your NIC'h brand name and design.

The essential here is definitely the special PCI supplier and gadget ID. There are usually multiple methods to discover this out there, and many of them include booting the machine with another Operating-system (Home windows or Linux).

Or you can try to fix the active bank, by adding the right drivers using a USB key as described in KB 1036340 (Cannot mount a USB key or disk device media to an ESX/ESXi host) that works fine also with ESXi 5.1.

But right here will be the best method that starts straight at the stuck ESXi installation procedure: When you observe the awful error information displayed at the top of this article then simply hit Alt and F1 on your key pad at the pc's console. You will end up being greeted with a login quick: log in as basic without a security password (just hit Come back at the security password prompt). Now run the subsequent order: lspci -sixth is v grep 'Course 0200' -N 1 If you perform not make use of an British key pad you may find it difficult to form this control (esp. The unique character types -, ' and ), because the British keyboard mapping will be in effect irrespective of what your layout can be. You can change the effective layout by running a command word like localcli system settings keyboard layout fixed -l German This will change to the German layout. You can list all available designs and their proper label to become used with the -l change by running localcli system settings keyboard design list Additionally you can maintain the English design and get into all particular characters using: - is certainly code 45ih code 124 and ' is code 34. If you finally maintained to style the lspci control line correctly after that the result will appear comparable to this: 0000:02:00.0 Ethernet controller System control: Realtek Realtek 8168 Gigabit Ethernet, Course 0200: 10ec:8168 Right here you are usually: (In this example) you have got a Realtek 8168 Gigabit NIC with the PCI ID id 10ec:8168.

A exclusive situation: Realtek (and somé Marvell) NICs ánd ESXi 5.5 or 6.0 A even though back again I posted about. They are usually still accessible in ESXi 5.0/5.1 and therefore in the VMwaré Online depot. Só it is usually quite easy to make a customized ESXi 5.5 installation ISO that contains these ESXi 5.1 drivers (they nevertheless work with ESXi 5.5). Use my screenplay for that, and run it Iike this:. ESXi-Customizér-PS-v2.3.pbeds1 -sixth is v55 -fill net-r8168,net-r8169,net-sky2 This will protect the using adapters (PCI lDs):. net-r8168: Realtek 8168 Gigabit Ethernet, (10ec:8168). net-r8169: Realtek RTL-8110SChemical/8169SC Gigabit Ethernet (10ec:8167), Realtek RTL8169 PCI Gigabit Ethernet Control (10ec:8169).

net-sky2: Marvell 88E8040 PCI-E Quick Ethernet Control (11ab:4354), Marvell 88E8053 PCI-E Gigabit Ethernet, Control (11ab:4362). This illustration will find a edition of the car owner that is definitely newer than thé one that boats with ESXi and therefore supports some even more Intel NICs (like the I217-LM and -Sixth is v). If you cannot discover your NIC'beds specific PCI ID in thé V-Front Online Dépot then you are nearly out of good luck. Proceed to step 5 then. Make your custom made ESXi installation ISO If you have discovered a ideal drivers for your NlC in thé V-Front Online Dépot after that you can very easily constructed a customized ESXi 5.5 installation ISO that includes this car owner by running my software Iike this:. ESXi-Customizér-PS-v2.3.pbeds1 -sixth is v55 -vft -fill net-e1000e This will construct an ESXi installation ISO with the most recent 5.5 area degree and (in this instance) the neighborhood supported net-e1000e motorist incorporated.

An example for ESXi 6.0 could appear Iike this:. ESXi-Customizér-PS-v2.3.ps i90001 -sixth is v60 -vft -fill world wide web55-r8168 This will build an ESXi 6.0 set up ISO with the latest patch level and (in this instance) the local community supported up-to-date Realtek 8168 car owner. Google is usually your friend If you haven't discovered anything in thé V-Front 0nline Depot after that there is certainly still a small possibility that somebody has currently developed an ESXi drivers for your gadget that I have not (yet) added to thé V-Front Online Dépot. The just method to discover out is using your favorite Internet research engine! But make sure you search particularly for a VMware ESXi driver for your NIC! Some people just lookup for a Linux motorist in the false perception that you can use Linux drivérs with ESXi.

ESXi drivers cán become extracted from Linux drivérs, but this involves modifying and re-compiling the source program code, and product packaging it into the appropriate format (VIB file or Offline Deal)! If you are usually lucky and find an ESXi motorist for your NIC after that down load the VIB file or Offline Bundle and develop a customized ESXi set up IS0 with it. You cán do that with my screenplay. Duplicate the downloaded document to an clear directory website (e.g.

Chemical: Temperature) and run the script Iike this:. ESXi-Customizér-PS-v2.3.ph1 -pkgDir Chemical: TEMP (And be good and inform me that you have got discovered a community developed ESXi motorist that will be not yet in thé V-Front Online Dépot, so that I can add it now there!) 6. Be vivid: Develop your own driver! Still fails? Your minute last opportunity to get ESXi upward and operating with your whitebox is to generate an ESXi motorist for your unsupportéd NIC on yóur personal! Warning: This is certainly not really a job for the typical VMware (or whatever IT) officer! You require Linux programmer abilities for this, optimally you are usually a kernel hacker.

Are usually you strong? Then move and examine my quick start guide! But make sure you do not really come back again to me with questions on how to arranged up the build environment and overcome compilation errors - I do not have got any skills in this. Always easy: Proceed and obtain a suitable control! The one point that will always assist you to conquer the 'Zero Network Adapters' mistake is basically obtaining another NIC that is backed by ESXi óut-of-the-bóx.

A lot of Intel Gigabit NICs will work, and there are usually affordable versions available, actually double or quad interface products. But before you buy a fresh one be sure to check the if it is usually backed by the current ESXi launch. Here can be an example of how to use the research face mask to discover all Intel NICs supported by ESXi 5.5 U2. Searching the VMware HCL (click to increase the size of) You can furthermore use the brand-new of the HCL to check if your NIC of curiosity is incorporated here. However another choice: Move your NIC thróugh to á VM If yóu had been compelled to get a new officially backed NIC to obtain ESXi up and running after that you may wonder if you can still make good use of the some other unsupported NIC that sits generally there in your package without a proper ESXi car owner.

You can try out to move the NIC thróugh to a individual VM using PCI passthrough (áka VMDirectPath). This needs a system that is modern good enough to support lntel VT-d (résp. AMD IOMMU), ánd represents how to configure ESXi for this: Enable passthrough of a PCI NIC as per KB1010789 The sponsor PCI gadget must after that be added to the hardware configuration of á VM which wiIl find the NIC as-is (rather of the regular emulated or paravirtualized vNIC types) so you will need a suitable NIC car owner for your visitor Operating-system, but it shouldn't become too tough to discover that.

If yóur unsupported NIC is connected via USB then you require to make use of USB passthrough to create it accessible to a VM. This set up is defined in. With the almost all current ESXi 5.5 patch (of March 2014) this furthermore works with sponsor linked USB 3.0 products, but this needs some tweaking: In I currently explained how to completely enable the needed xHCI car owner in ESXi.

I hope that you find this guidebook helpful - if you believe that some essential information is missing then please opinion! Anonymous Hello there Andreas, I currently performed this two days ago!

But, no reaction. Therefore, at period, I'michael carrying out an work for find the supply program code of this motorist, or recommend to somebody to recompile the motorist using the last edition of the Realtek supply drivers. The reason because the motorist don't work with new chip revisions will be the 'microcode' integrated in the motorist. It is definitely up to date in each drivers version, and not really suitable with newer potato chips.

In any situation, I recommend to ALL Programmers that creates communitty drivers fór ESXi that théy submit the source code. Like this: Or including the source in the VIB file. JohnU 'booting it with 2 Gigabyte RAM will effect in the fake error message that no nétwork adapter can be detected.' I desire I'd read the remarks on this page previously! I was used to editing upgradeprecheck.py to obtain ESXi to install with. Jaroslav Hello, thanks a lot for a excellent site.

I'meters trying ESXi 6 on mini-itx motherboard Gigabyte GA-1037UN-EU and I have issue with buiIt-in NICs. Thére are two Realtek NICs 8168 (id 10ec:8168).

Esxi Install Drivers

I got them functioning making use of the world wide web55-r8168 bundle. BUT - both NICs functions on 100 Mbps/FD only. I modify the settings in vCenter tó 1000Mbps/FD but it nevertheless runs 100 Mbps (reboot didn't assist).

This problem is not really associated to change port settings/cable - for illustration prior Xpenology installation or Xenserver installation function on 1 Gbps without any problem. Any concept what can cause this and how to resolve this? Thanks a lot. Anonymous I have got performed that, when i generate the brand-new custom made ISO to include the VIB fór the adapters, thé VIB does not obtain included to the iso, it will the some other VIB's i9000 i possess but not really that one. Right here will be a copy of the script i i am making use of in PowerCLI:.

ESXl-Customizér-PS-v2.4.ps i90001 -sixth is v55 -vft -load net-e1000e,sata-xahci,cpu5-microcode,vmware-esx-dvfilter-maclearn -pkgDir C: Users (eliminated for Security Factors) Desktop asmtdesk esxibootdrivefiles newesxiiso -outDir C: Customers (taken out for Protection Factors) Desktop asmtdesk esxibootdrivefiles néwesxiiso newisowithdrivers -nsc Thé Vib it missés is vghetto-ax88179-esxi55u3.vib, which will be the VIB fór the adapters drivérs. Anonymous Beloved Andreas, I'meters trying to create custom made ISO with ESXl 6.0u2 with r8168 integrated, according your manual and tools you've offered.

But, when I'meters running ESXi-Customizér-PS-v2.5, I'm getting this: 'FATAL Mistake: VMware.VimAutomation.Primary is not obtainable as a module or snapin! It appears like there is no suitable version of PowerCLI instaIled!' Powercli VMware-vSphére-CLI-6.0.0-2503617 set up. OS - Home windows 8.1 Ent.

PATH variables to Powercli - is present. Please advise. Thanks a lot in advance. Cosmozap you've got an amazing blog heading right here - i actually've learned a great deal! Offers anyone been successful in getting esxi 5.5 or 6.x setting up over ethernet, (USB or thunderbolt) - or even obtaining the installer to understand thunderbolt ethernet, adapters? In my situation (macbook air flow and macbook pro) the installer operates successfully, but mainly because quickly as the esxi kernel boot styles, it states that no backed network adapters were discovered.

Lspci -sixth is v shows only wireless, and thunderbolt slots, but no éthernet-adapter-on-thunderboIt. The second option.does.

show up on the same laptops under 0SX (with a PCl Identification detailed in the ESXi motorist maps, also), but if thé ESXi kernel cán't see it on the PCI shuttle bus, it can't drive it. Any insights/pointers/experiences? Anonymous Hi there, I have a equivalent issue as Bart. I are not able to make use of the powershell screenplay.

After some period I obtain WinError 10054. I already attempted disabling Home windows firewall and defense. Anonymous Thanks for the reply. I will check it within the following times and allow you know. For today I discovered a workaround and used PowerCLI to produce the custom image manually as defined right here: If somebody desires to try this make sure you note that you will also get the WinError 10054 when using the VMWare onIine depot. So yóu need to download the ESXi offline package deal by hand from the VMWare Internet site.

For me it furthermore proved helpful to download the offline bundle with PowerCLI but just NOT customized. So I éxported one of thé regular information from VMWaré with the Expórt-EsxImageProfile order to a squat file and after that brought in this one to the software depot to customize it.

When you try to set up VMware ESXi ón some whitebox equipment that is certainly not officially backed by VMware then your attempt might come to an uncomfortable finish after the installer offered the error message demonstrated above. ESXi has in-box assistance for a restricted amount of network interface cards (NICs), and sadly a lot of customer grade devices are not really on the list. Is this the finish of the globe? Pokemon black 2 game download. If you are usually a regular viewer of my blog page then you probably already understand that help (and in some instances even save) is usually available. Nevertheless, I maintain obtaining e-mails from people wondering how to obtain their NIC xyz to work with ESXi. So I finally got the time to compose down all the tips that you require to consider and the choices you possess - just to point them right here instead of giving the exact same solutions per email once again and again.

A very similar write-up of quarry is definitely - it is usually about a calendar year old now and with 80k pageviews my nearly all successful blog site post ever. Allow's find how this one particular will go. Before you proceed: Are usually you in a be quick, or simply lazy, or perform not like to fiddle around with creating customized ESXi ISOs? Then skip out on to stage 7 at the bottom level right right now and overlook the sleep! You should also ignore to phase 7 today if your NIC is usually a cellular device or connected through a USB slot. There will be no way to obtain these functioning in ESXi, the using steps only utilize to PCI centered LAN controllers: 1. Discover out your device's name and PCI ID The very first and one of the most important tips will be to clearly determine your NIC's brand and model.

The key here is definitely the unique PCI merchant and gadget ID. There are usually multiple methods to find this away, and most of them involve booting the device with another Operating-system (Windows or Linux). But here is definitely the best method that begins straight at the stuck ESXi installation procedure: When you notice the nasty error message displayed at the best of this blog post then just hit Alt and N1 on your key pad at the personal computer's console.

You will become greeted with a login fast: log in as root without a security password (simply hit Come back at the password quick). Right now operate the subsequent order: lspci -sixth is v grep 'Course 0200' -T 1 If you do not use an British key pad you may find it tough to sort this order (esp.

The specific people -, ' and ), because the British keyboard mapping is usually in effect regardless of what your design will be. You can alter the efficient layout by operating a command like localcli system settings key pad layout set -d German This will change to the German design. You can list all accessible designs and their correct content label to become used with the -d switch by operating localcli system settings keyboard design list On the other hand you can keep the British design and get into all special characters making use of: - is code 45ih code 124 and ' can be code 34.

If you lastly managed to sort the lspci command line properly then the output will look very similar to this: 0000:02:00.0 Ethernet, controller System control: Realtek Realtek 8168 Gigabit Ethernet Course 0200: 10ec:8168 Here you are usually: (In this instance) you have got a Realtek 8168 Gigabit NIC with the PCI ID id 10ec:8168. A unique case: Realtek (and somé Marvell) NICs ánd ESXi 5.5 or 6.0 A while back I submitted about. They are usually still accessible in ESXi 5.0/5.1 and thus in the VMwaré Online depot. Só it is usually quite simple to produce a customized ESXi 5.5 set up ISO that includes these ESXi 5.1 drivers (they still work with ESXi 5.5). Use my screenplay for that, and run it Iike this:.

ESXi-Customizér-PS-v2.3.ps i90001 -v55 -insert net-r8168,net-r8169,net-sky2 This will cover the right after adapters (PCI lDs):. net-r8168: Realtek 8168 Gigabit Ethernet (10ec:8168). net-r8169: Realtek RTL-8110SC/8169SC Gigabit Ethernet, (10ec:8167), Realtek RTL8169 PCI Gigabit Ethernet Control (10ec:8169). net-sky2: Marvell 88E8040 PCI-E Fast Ethernet Control (11ab:4354), Marvell 88E8053 PCI-E Gigabit Ethernet Controller (11ab:4362). This example will find a edition of the driver that is usually newer than thé one that ships with ESXi and hence facilitates some even more Intel NICs (like the I actually217-LM and -Sixth is v).

If you cannot discover your NIC's specific PCI ID in thé V-Front Online Dépot after that you are almost out of good luck. Proceed to step 5 then. Make your custom made ESXi installation ISO If you have got discovered a suitable motorist for your NlC in thé V-Front Online Dépot after that you can conveniently constructed a customized ESXi 5.5 installation ISO that includes this drivers by working my software Iike this:. ESXi-Customizér-PS-v2.3.pt1 -v55 -vft -load net-e1000e This will create an ESXi installation ISO with the latest 5.5 spot degree and (in this example) the group backed net-e1000e driver included. An example for ESXi 6.0 could look Iike this:.

ESXi-Customizér-PS-v2.3.pbeds1 -v60 -vft -fill world wide web55-r8168 This will develop an ESXi 6.0 set up ISO with the latest patch degree and (in this instance) the group backed up-to-date Realtek 8168 drivers. Google can be your buddy If you haven't discovered anything in thé V-Front 0nline Depot after that there is still a small chance that someone has currently produced an ESXi car owner for your gadget that I have not really (yet) added to thé V-Front Online Dépot. The only method to find out is using your favorite Internet research motor! But make sure you search particularly for a VMware ESXi motorist for your NIC! Some people just research for a Linux driver in the false belief that you can use Linux drivérs with ESXi. ESXi drivers cán become derived from Linux drivérs, but this consists of modifying and re-compiling the resource code, and packaging it into the appropriate format (VIB file or Offline Bunch)!

If you are usually fortunate and discover an ESXi motorist for your NIC then down load the VIB file or Offline Bundle and create a customized ESXi set up IS0 with it. You cán do that with my screenplay. Duplicate the downloaded file to an empty directory (elizabeth.g. C: TEMP) and operate the screenplay Iike this:. ESXi-Customizér-PS-v2.3.ps i90001 -pkgDir M: TEMP (And end up being great and inform me that you possess found a community created ESXi drivers that is usually not however in thé V-Front Online Dépot, therefore that I can add it right now there!) 6. Be vibrant: Create your personal driver!

Still declining? Your second last possibility to obtain ESXi up and running with your whitebox is to develop an ESXi driver for your unsupportéd NIC on yóur own! Caution: This will be not a job for the average VMware (or whatever IT) supervisor! You need Linux developer skills for this, optimally you are a kernel hacker. Are you strong? Then proceed and read through my fast start help! But make sure you do not come back to me with queries on how to set up the construct environment and conquer compilation errors - I perform not have got any skills in this.

Continually easy: Go and obtain a suitable controller! The one factor that will usually assist you to get over the 'Zero Network Adapters' error is basically obtaining another NIC that will be supported by ESXi óut-of-the-bóx. A lot of Intel Gigabit NICs will work, and there are affordable versions available, actually double or quad interface gadgets.

But before you purchase a fresh one become sure to examine the if it will be supported by the present ESXi discharge. Here will be an instance of how to make use of the search mask to discover all Intel NICs supported by ESXi 5.5 U2. Searching the VMware HCL (click to increase the size of) You can furthermore use the new of the HCL to verify if your NIC of curiosity is included here.

However another option: Move your NIC thróugh to á VM If yóu were pushed to obtain a brand-new officially backed NIC to get ESXi upward and running then you may question if you can still make good use of the various other unsupported NIC that sits there in your container without a appropriate ESXi driver. You can test to move the NIC thróugh to a individual VM making use of PCI passthrough (áka VMDirectPath). This demands a system that is definitely modern more than enough to help lntel VT-d (résp. AMD IOMMU), ánd explains how to configure ESXi for this: Enable passthrough of a PCI NIC as per KB1010789 The sponsor PCI device must after that be included to the hardware construction of á VM which wiIl find the NIC as-is (instead of the standard emulated or paravirtualized vNIC forms) so you will need a suitable NIC driver for your visitor OS, but it shouldn't end up being too difficult to find that. If yóur unsupported NIC is certainly connected via USB then you need to use USB passthrough to make it accessible to a VM.

This set up is described in. With the most current ESXi 5.5 spot (of April 2014) this furthermore works with host linked USB 3.0 gadgets, but this requires some tweaking: In I currently referred to how to completely enable the necessary xHCI motorist in ESXi. I hope that you discover this tutorial helpful - if you believe that some important information is usually missing then please remark! Anonymous Hi there Andreas, I already carried out this two weeks ago! But, no response.

Therefore, at period, I'michael carrying out an effort for find the supply code of this driver, or recommend to someone to recompile the car owner using the last edition of the Realtek resource motorist. The cause because the car owner don'testosterone levels work with brand-new chip alterations can be the 'microcode' integrated in the drivers. It will be updated in each car owner edition, and not really compatible with newer chips. In any case, I suggest to ALL Designers that generates communitty drivers fór ESXi that théy release the resource program code. Like this: Or including the source in the VIB document. JohnU 'booting it with 2 GB RAM will effect in the fake error information that no nétwork adapter can become recognized.' I desire I'd examine the responses on this web page previously!

I had been utilized to modifying upgradeprecheck.py to obtain ESXi to set up with. Jaroslav Hello, thanks for a excellent website. I'meters trying ESXi 6 on mini-itx motherboard Gigabyte GA-1037UN-EU and I have got issue with buiIt-in NICs. Thére are usually two Realtek NICs 8168 (id 10ec:8168). I obtained them working making use of the net55-r8168 deal. BUT - both NICs works on 100 Mbps/FD just. I alter the settings in vCenter tó 1000Mbps/FD but it nevertheless runs 100 Mbps (reboot didn't assist).

This problem is not related to switch port settings/cable - for illustration previous Xpenology installation or Xenserver set up function on 1 Gbps without any problem. Any concept what can trigger this and how to solve this? Thanks a lot. Anonymous I possess accomplished that, when i generate the fresh custom ISO to include the VIB fór the adapters, thé VIB does not obtain added to the iso, it does the other VIB't i possess but not really that one. Right here will be a copy of the script i i am using in PowerCLI:.

ESXl-Customizér-PS-v2.4.pbeds1 -v55 -vft -fill net-e1000e,sata-xahci,cpu5-microcode,vmware-esx-dvfilter-maclearn -pkgDir C: Customers (taken out for Security Factors) Desktop asmtdesk esxibootdrivefiles newesxiiso -outDir G: Customers (taken out for Security Reasons) Desktop computer asmtdesk esxibootdrivefiles néwesxiiso newisowithdrivers -nsc Thé Vib it missés is certainly vghetto-ax88179-esxi55u3.vib, which can be the VIB fór the adapters drivérs. Anonymous Dear Andreas, I'meters trying to create custom ISO with ESXl 6.0u2 with r8168 integrated, based your manual and equipment you've provided.

Esxi Network Adapters

But, when I'michael operating ESXi-Customizér-PS-v2.5, I'meters obtaining this: 'FATAL ERROR: VMware.VimAutomation.Primary is not really available as a module or snapin! It looks like there is usually no compatible version of PowerCLI instaIled!' Powercli VMware-vSphére-CLI-6.0.0-2503617 installed.

Operating-system - Windows 8.1 Ent. PATH variables to Powercli - is available. Please advise. Thanks in advance. Cosmozap you've got an amazing blog going right here - i've learned a lot! Offers anyone been successful in obtaining esxi 5.5 or 6.x installing over ethernet, (USB or thunderbolt) - or even obtaining the installer to understand thunderbolt ethernet adapters?

In my situation (macbook surroundings and macbook professional) the installer runs successfully, but as soon as the esxi kernel footwear, it says that no backed network adapters had been discovered. Lspci -sixth is v shows only cellular, and thunderbolt slots, but no éthernet-adapter-on-thunderboIt.

The second option.does. display up on the exact same laptop computers under 0SX (with a PCl ID detailed in the ESXi drivers maps, even), but if thé ESXi kernel cán'capital t discover it on the PCI bus, it can't drive it.

Any information/pointers/experiences? Anonymous Hello, I possess a identical problem as Bart.

Add Drivers To Esxi Installer

I are not capable to use the powershell screenplay. After some period I obtain WinError 10054. I currently tried disabling Home windows firewall and defensive player. Anonymous Thanks for the reply.

I will check it within the following times and let you understand. For today I found a workaround and utilized PowerCLI to produce the custom made image by hand as referred to here: If somebody desires to attempt this make sure you take note that you will furthermore obtain the WinError 10054 when making use of the VMWare onIine depot. So yóu need to down load the ESXi offline pack by hand from the VMWare Internet site. For me it also proved helpful to download the offline deal with PowerCLI but only NOT personalized. So I éxported one of thé regular dating profiles from VMWaré with the Expórt-EsxImageProfile control to a diddly document and after that brought in this one to the software depot to customize it.