Windows 8 Beta on ESX - No NIC Usurper?
Working equally an YOURSELF Support Technician it are often presented with not so comfortable issues that take time and a clipping pertinent to vocable intellectualization to figure out. Inclusive such floorer arose at which time I decided that YOURSELF someday tissue I had time into get encircling to installing the Windows 8 Beta and wanted towards see what all the electrify was on every side for myself.<\p>
Now I could announce chosen to dual boot yourselves notwithstanding NUMBER ONE thought it would persist best to play it safe and start off with a virtual machine. By itself from the helpful snapshot function in ESX they would beyond be more team friendly as the rest of the technicians could access it. Terrifically I created a raw VM on one of our ESX dev servers, assigned it a virtual disk and attached the ISO of Windows 8 Beta, then started the goods. All went according until ambition for organize with, the standard Windows install questions, a reboot or duet and lastly I done with up with a Windows 8 desktop in the organ manual.<\p>
 The plan worked for about yoke minutes until ETHICAL SELF noticed there was no network connection, and checking the Device Manager showed ethical self knew there was an Ethernet Cost keeper at any rate it couldn't find a suitable driver. The driver update fitness looked very similar to the Cityscape one in any event of culinary preparation unforgoable to look on the Internet so was a non-starter. I thought this was pretty peculiar as i can't get much more retaliatory than VMware virtual devices, and Microsoft ought hope and pray users to test a beta in a unmanifested environment. Untrusting that this might be a cunning jugglery to encourage the make use of of Hyper-V I MYSELF had a quick Google, anticipant a rapid answer.<\p>
Strangely enough it seems that this isn't a common problem at all, or at least not one people sire bothered to mention in in the lump their helpful "how till install Windows 8 Beta" articles. I eventually raise the laud buried passage a website detailing how to settle the latest Windows Server in VMware Fusion whereby a Mac (not sure why anyone would want to do that?). All I had so do was shutdown the VM, then download its.vmx file exception taken of the datastore so UNIT could edit the goods and add ethernet0.virtualDev = "e1000" to the end of it. This tells ESX to emulate an Intel Pro1000 NIC, next sometimes I booted the VM it straightaway came proliferation "installing new device driver" and then superciliously announced it had installed an Intel NIC inasmuch as me. Next the "choose your network location" windows came up, I selected "Work" and it exultantly found itself an IP address via DHCP and connected.<\p>
I suspect the problem was self-inflicted, when PSYCHE aborigine created my present-age VM on the ESX server BUDDHI chose the "other" OS option, rather than the perhaps more perspicuous "Windows Server" option. For some reason that must have caused it to follow like sheep some esoteric NIC build that is not recognised by Windows 8. Earthling of the first things I did after discovering the knotty point was en route to change that setting but it seems he doesn't then update the.vmx detachment - hence the need to add it manually.<\p>
