Moved from VMWare; new VB VM won't forget VMWare NIC! Help!

[RnRF]

Hello!
I just installed VB and am happy so far with it. I used VMWare Server before but just could NOT get it to work on Windows 2008 so, goodbye!

I created an Acronis backup of the VMWare servers and used Acronis Universal Restore to restore the image to the new VB VM. [Universal Restore strips the HAL layer so that an Acronis image can be moved to a new set of hardware.]

I finally got the new VM, which is a Windows 2003 server, to boot up. Yay! But no network connectivity. Boo!

When I look at the VM's Device Manager, it still see the "VMWare Accelerated AMD" Adapapter. Even if I uninstall it, it comes back.
I installed the drivers for the physical host's network card, but the VM still doesn't recognize any other NIC.

Any help would be GREATLY appreciated.
I need to run in Bridged mode because this VM will need a static address. That's how I have it set now. I've tried all, but none work.
How do I get my new VB VM to recognize its new host's network card?
Thanks!

[Sasquatch]

That device is created and installed because you still have the VMWare Tools installed. That is the root cause of the problem. Uninstall them and it should go a lot better. It's best to remove them while the VM is still running as a VMWare image, so good luck in removing it from VB. You may have to redo the transfer all over again.
If the uninstall of the tools fail and you don't want to redo the transfer, then change the NIC type to one of the Intels. The 1000T-Server should be the one that is supported by 2003, else just download the driver on the Host, put it on a shared folder or USB stick and transfer it to the Guest.


Now, you may have to sign up to this forum again due to the OSSO migration that you can read about in Using VirtualBox section. I won't be doing that, so this may very well be my last post here.

[RnRF]

I'm honored that your last post (of many!) will help me so much. Thank you!
I wasn't aware of the migration; I'll read about it.