If you find that WinPE 2.1 doesn’t work on VMWare, then please refer to this Juice article as it tells you how to get your VM to work with WinPE. http://juice.altiris.com/tip/2919/tweaking-vmware-work-winpe-2x-and-microsoft-vista#comment-6050
Didn't work for me. Anyone got any suggestions? I am trying to create a DS 6.9 Boot disk for my ESX 3.5 guests to connect to the DS. The NIC never works. I tried the VMWare drivers and even tried the e1000 hack (Shouldn't have to do that IMHO). I just want my guests to conenct so I can throw down an image on them (Win2K3 Server) Quote from HP site (they use DS) ---- By default, WinPE 2.1 x86/x64 supports the VMware NIC model e1000. When possible, use this NIC model with your virtual machines. However, a virtual machine created for Windows 2003 x86 Standard Edition can only use the VMware Flexible NIC which is not supported by default. ---- Need the VMWare driver for WINPE2.1 it looks like.
Right so WinPE 2.1 does not include the ol' skool AMD PC NET driver ... 1.6 did. So if you want to add that support, you can reference this article. How To Add VMware Flexible NIC Driver For WinPE 2.1 x86/x64 Automation HTH
I honestly think that the HP article is incorrect. I do not think the win2k directory has the correct driver although I could be wrong. Win PE2.1 is Vista / 2008 based so I think you use those drivers which are on ESX update 3 minimum. The previous ESX versions did not work for me.
Nice catch Bill Versioning maybe a bit off, but the 2.1 WinPE drivers are certainly on our 3.5 Update 2 hosts. CDROM:\program files\VMware\VMware Tools\Drivers\vmxnet\win2008
Has this process worked for anyone using the VMware Tools that are provided with ESX 3.5 Update 4? I am at a new client site that only has Update 4 and am not able to add any of the 2008 drivers to the Hardware Device Drivers.
My problem is now resolved. The issue was the drivers were not importing correctly through the GUI. Deleted sub folders in Server|Express|Bootwiz|platforms|Winpe2|x86|Drivers|CUSTOM|Drivers Manually copied the 2008 vmware scsi / network folders to the the network location above. Re-ran the gui and picked the vmware drivers.
