Re: VMware and HP ProLiant DL380 G5 DavetheWave Jan 16, 2018 9:52 PM ( in response to DH4774 ) HPE versions of ESXi will detect everything under the hood of your ProLiant, smart array controllers, fan and temp sensors, even iLO logs.

There is NO Teaming in VMware, that uses HP teaming software. So this does not apply.if you are using the vSphere Client to connect to the ESX Server,Select the Host, Configuration, Network Adaptors, ALL the Physical NIC MAC Addresses are there.These are the physical MAC Addresses, but you have also go several virtual mac addresses, e.g.

For VMKernel Portgroup, and also ALL your VMs. These MAC Addresses carry storage traffic.VMware Mac Address The MAC address range is 00:50:56:00:00:00-00:50:56:3F:FF:FF.you can use the following PowerCLI script to retreive ALL your VM Mac Addresses.

Hiyou can try updating driver manually extract.exe and using device manager search for the inf file and update if that does not work and I see the actual driver is way to old 2.8.13try at least 2 previous previous version before installing the latest oneyou right now are trying to install versionVersion: 4.6.17.0 (C) (4 Feb 2009)so I can recommend you try1. Version: 3.4.10.0 (13 Jul 2007)2. Version: 4.1.5.0 (25 Feb 2008)3.

And latest the one you are trying to installall versions herebye. BrendanM,Sorry for the confusion.I got the same error as you got but the OS i used was Windows 2008 Standard Server x32 and x64.Anyway, here are my steps that i took to install the latest nic driver (post psp8.15b) on these servers;As I could not install the latest NIC driver directly, which gave me the same error as you had, I installed the nic driver coming with psp8.15b.This driver installed without error so now I got the 'HP virtual bus' driver thing in device manager.Now I extracted the latest NIC package (extracting means executing the package and choose extract the files to a location). What is the best webcam for mac. This extraction got me the plain drivers which I could now use to manually update the virtual bus driver.After manually updating, only the virtual bus driver, I executed the install package again and now I could install without error.To me there is a problem with the latest nic package - 4.6.17.0 (C) 4 Feb 2009 for x32 and x64 Windows 2008.As far as I tested on 3 fresh Windows installs the driver would not install without error.