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:
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?
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?