VMware

This Question is Possibly Answered

1 "correct" answer available (10 pts) 2 "helpful" answers available (6 pts)
3 Replies Last post: Mar 16, 2009 2:48 PM by taits  

HP BL460c NIC problem after p2v conversion posted: Mar 15, 2009 6:20 PM

Click to view Monolithic's profile Novice 6 posts since
Mar 4, 2009

Hello all,

Over this weekend I did a p2v of an HP BL460c (g1) server running Windows 2003 64bit. The physical box has the HP insight and management agents and according software. After the P2V it still had the NC373i multifunction drivers hidden. I ran the devmgt hidden =1 command but they did now show up hidden in the device manager. I then downloaded the devcon tool and they are there displayed when i run the list all command. When i run the command to have devcon remove them it says failed. I do not want these drivers on there and these drivers retain my old ip address info on there, so when i change the virtual nic address, it says they are still being used by another device driver. Ideally i want to remove these as i want to make sure that this won't cause an issue down the road.

I didn't put that VM into production as there was other hp software on there and i ran out of time, i had to get the physcial box back into production. This coming weekend i'm planning on putting a new p2v vm into production of this server. I was going to remove the drivers ahead of time before the conversion but if i remove the NIC drivers how can i get the vm to my esx hosts? the simpliest solution would be to just remove the drivers after the p2v.

has anyone run into this problem with these drivers? they are 64 bit? any help at all or direction would be greatly appreciated! thanks in advanced!

Re: HP BL460c NIC problem after p2v conversion

1. Mar 15, 2009 10:31 PM in response to: Monolithic
Click to view taits's profile Hot Shot 81 posts since
Nov 6, 2007
Had a similiar issue with Intel Pro1000 nics. After converting a physical Win 2003 machine to a VM that had the Intel Pro1000 nics the VM was assigned a generic Network Driver (AMD) and configured them with a DHCP address. The original Intel adapters were hidden. When I tried to assign an actual IP address to the Network adapter I got a message that said "the IP address is assigned to another adapter which is hidden. In order to allocate the actual IP address of the server to the network adapter/s you'll need to remove the hidden adapters." Did this:


Converter your server, then

From a cmd window within your converted Windows server, type:
set devmgr_show_nonpresent_devices=1
devmgmt.msc

Then select View > Show Hidden Devices and locate and remove the old NIC adapter.

Hope this helps, tait

Re: HP BL460c NIC problem after p2v conversion

3. Mar 16, 2009 2:50 PM in response to: Monolithic
Click to view taits's profile Hot Shot 81 posts since
Nov 6, 2007
after running the command - 'set devmgr_show_nonpresent_devices=1'
did you then run 'devmgmt.msc' from the command line? i found that if I ran the devmgr_show_nonpresent_devices and then closed the command window and started Device Manager from the start menu I couldn't see the Nics.

From memory I had teaming software installed in the physical server. I think the order of removal was teaming software, then Nics. Also when doing the conversion make sure to assign the same number of vNics to the VM as the physical server has.

t

VMware Beta Programs

Want to be Considered for Future Beta Programs?

Learn More

VMware Developer

Download SDKs, APIs, videos,
training, and more in the Developer community.

Learn More

Developer
Sample Code

Increase your developer productivity with VMware API sample code.

Learn More

VMworld
Sessions & Labs

Online access to the latest VMworld Sessions & Labs and online services.

Learn more

Purchase PSO Credits Online

Purchase credits to redeem training and consulting services online.

Buy Now

Community Hardware Software

View reported configurations or report your own.

Learn More

Only VMware ... Delivers Nexus 1000V

Ensure consistent, policy-based network capabilities to virtual machines across your data center.

Learn More

Communities