VMware Cloud Community
mcsnott
Contributor
Contributor
Jump to solution

How do Install intel network driver on windows 2003 VM

Have been told I can setup vlan via guest VM if I have a intel e1000 driver installed.

I have added the following line in my vmx file-

ethernet0.virtualDev = "e1000"

But the device manager is still saying "AMD PCNet"

I know this config is not supported by VMware but I dont appear to be able to get other configs to work.

Thanks

Reply
0 Kudos
1 Solution

Accepted Solutions
oreeh
Immortal
Immortal
Jump to solution

You don't need to delete any files.

To reregister the VM you can either use "vmware-cmd -s register pathtovmx" in the console or in the VI client open the datastore browser and right click the VM and select register.

View solution in original post

Reply
0 Kudos
8 Replies
oreeh
Immortal
Immortal
Jump to solution

Did you unregister the VM before changing this and reregister it afterwards?

sbeaver
Leadership
Leadership
Jump to solution

Ditto!! Do not know why but seems you have to do that to get it to stick

Steve Beaver
VMware Communities User Moderator
VMware vExpert 2009 - 2020
VMware NSX vExpert - 2019 - 2020
====
Co-Author of "VMware ESX Essentials in the Virtual Data Center"
(ISBN:1420070274) from Auerbach
Come check out my blog: [www.virtualizationpractice.com/blog|http://www.virtualizationpractice.com/blog/]
Come follow me on twitter http://www.twitter.com/sbeaver

**The Cloud is a journey, not a project.**
Reply
0 Kudos
oreeh
Immortal
Immortal
Jump to solution

Don't know the reason too, but I assume VC uses the DB and only flushes / updates the DB (and the VMX) after an unregister / register.

Reply
0 Kudos
sbeaver
Leadership
Leadership
Jump to solution

Maybe but it is "supposed" to read the vmx file everytime the VM is powered on

Steve Beaver
VMware Communities User Moderator
VMware vExpert 2009 - 2020
VMware NSX vExpert - 2019 - 2020
====
Co-Author of "VMware ESX Essentials in the Virtual Data Center"
(ISBN:1420070274) from Auerbach
Come check out my blog: [www.virtualizationpractice.com/blog|http://www.virtualizationpractice.com/blog/]
Come follow me on twitter http://www.twitter.com/sbeaver

**The Cloud is a journey, not a project.**
Reply
0 Kudos
oreeh
Immortal
Immortal
Jump to solution

We could try and file a SR / bug report Smiley Wink

Reply
0 Kudos
mcsnott
Contributor
Contributor
Jump to solution

Thanks, stupid question but how do you re-register the vm.

I have switched it off, removed from inventory, deleted log and ram files and added the vm again. But this didn't work??

Reply
0 Kudos
oreeh
Immortal
Immortal
Jump to solution

You don't need to delete any files.

To reregister the VM you can either use "vmware-cmd -s register pathtovmx" in the console or in the VI client open the datastore browser and right click the VM and select register.

Reply
0 Kudos
mcsnott
Contributor
Contributor
Jump to solution

OK thats strange did the same again. Only no need to delete ram or logs files as there were none. Andf the drivers have change. Stange just needed two attempts by looks of it. See if I can get this vlan stuff working now.

Ta ALL

Reply
0 Kudos