Windows Conversion and IP Address

[JCS725]

When I do conversions on physical Windows systems, my ip address gets lost in the mix. When I assign the new virtual network adapter the same address it gives me the "Theres already an adapter with this address blah blah blah" error.

Is there a trick to retaining my ip address on conversions?

Thanks

[JoJoGabor]

Are you using something like HP Teaming utilitiy?

Are you performing customisation during the conversion?

During the conversion check how many NICs it is including in the conversion. Compare this to how many LAN Connections were in the physical box

[JCS725]

No I'm not using any teaming utility.

I'm not performing any customization during the conversion.

There is only one active connection on the physical box, there is usually more empty network ports though.

[Vasil Ilinski]

You should try customizing the target VM.

On the view/edit options page there is an advanced section. Selecting the customization option will allow you to configure the virtual adapter with a static IP.

[Rockapot]

This is because a new network interface is found after the P2V conversion. The new interface is that of the VMware network adaptor.

It sounds like in your case that the old network interface is still on the VM. As such you will need to remove this.

You need to complete the following steps, which by the way are considered best practices for any P2V task as a post P2V step

1. Go to Start, right-click My Computer, and select Properties.

2. In the System Properties dialog box, select the Advanced tab and click the Environment Variables button.

3. In the Environment Variables dialog box, locate the System Variables panel and click New.

4. In the New System Variable dialog box, type
   DEVMGR_SHOW_NONPRESENT_DEVICES in the Variable Name text box and type 1
   in the Variable Value text box.

5. Click OK twice.

6. To view the non-present devices, go to Start, right-click My Computer, and select Manage.

7. Click Device Manager, pull down the View menu, and select Show Hidden Devices

Now that these steps are complete remove the old network adaptor from the VM and restart the VM. You should not be able to configure the VM's nic with the IP address.

Carl

If this helps please consider awarding points for helpfull or correct answers :smileywink:

[Rockapot]

You should also uninstall any hardware agents from the VM as these are no longer required.

If you are using Platespin you can have these services disabled during the P2V stage.

Carl

[vm-au-user]

Using this process i've found a lot a phatom devices, should they all be removed?

Can you automate this using a script of some sort doing them one-by-one on multiple guests?

[AndreTheGiant]

Using this process i've found a lot a phatom devices, should they all be removed?

Yes (for old NIC and SCSI)

But VM works also with phantom device, you have only a warning for existing UP.

Can you automate this using a script of some sort doing them one-by-one on multiple guests?

No idea.

Andre

[AndreTheGiant]

When I do conversions on physical Windows systems, my ip address gets lost in the mix.

It's a common issue.

Driver will change, but your old driver and the old nic remain as phantom.

See how to remove it in the post above.

Andre