NIC error after P2V conversion

My company recently purchased VMware Infrastructure 3.x and are in the *testing* phase. Today we have performed a few Physical-to-Virtual migrations, and for the most part they have been really fast and very simple. One of the issues we keep encountering when we perform one of these P2V migrations, is that once the server has been virtualized it loses its static TCP/IP settings and reverts to DHCP. If I attempt to put the static settings back I receive the following message:

[CODE]
The IP address XXX.XXX.XXX.XXX you have entered for this network adapter is already assigned to another adapter Name of adapter. Name of adapter is hidden from the network and Dial-up Connections folder because it is not physically in the computer or is a legacy adapter that is not working. If the same address is assigned to both adapters and they become active, only one of them will use this address. This may result in incorrect system configuration. Do you want to enter a different IP address for this adapter in the list of IP addresses in the advanced dialog box?
[/CODE]

I found an MS KB article on how to remove this information from the registry, however is this a normal error when doing P2V migrations? Is there anyway to have the settings come over during the conversion process?

NIC-Error.JPG
Marc_JohnsonAsked:
Who is Participating?

[Product update] Infrastructure Analysis Tool is now available with Business Accounts.Learn More

x
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

Marc_JohnsonAuthor Commented:
Also here is the KB article from MS I found, however I would rather the settings come over during the migration ;)

 http://support.microsoft.com/kb/269155
0
65tdRetiredCommented:
This probably caused by the nic driver changing from Intel to VMWare driver once the VM tools are installed.

found this short article:
http://www.rtfm-ed.co.uk/?cat=4
0

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
Marc_JohnsonAuthor Commented:
Thank you!
0
Marc_JohnsonAuthor Commented:
That looks like it will do it, thank you my friend!
0
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Networking Hardware-Other

From novice to tech pro — start learning today.