VMware Communities: Message List - Keep the IP settings

Re: Keep the IP settings

snootalope — Wed, 15 Apr 2009 17:29:29 GMT

I just went the sysprep route. When importing, just do a customization of the vm and set the name, domain, and IP settings again. This seems to work just fine. I'm a bit nervous how this will affect an Exchange import though..

Thanks!

Re: Keep the IP settings

Ashmai — Wed, 15 Apr 2009 17:03:02 GMT

I'm not sure if your question was answered, I read it differently than the rest I believe. Are you asking if you can keep the same IP address as the physical, for the newly P2V'ed VM? As long as they are on the same subnet, you should be fine. However, if you are P2V'ing a pyhsical that is in a different subnet (ie, different DataCenter, etc) you will need to make use of vLAN's presented to the hosts in your environment. Then when you create the network adapter, you would specify the vLAN at that point.

Hope that was helpful If not, disregard!

Re: Keep the IP settings

hstagner — Tue, 14 Apr 2009 13:30:57 GMT

Yep, you are correct.

Re: Keep the IP settings

IamTHEvilONE — Tue, 14 Apr 2009 13:09:52 GMT

This is probably even scriptable (hmmm... sounds like a new project).

Why create a script when SysPrep can do this automatically and already exists? We can use sysprep, as part of the converter wizard, to specify the IP Settings for the resulting virtual machine.

To see how to do this:
http://www.vmware.com/pdf/VMware_Converter_Standalone_guide40.pdf
Page 51: Customize the Guest Operating System

Regards,

EvilOne
VMware vExpert 2009

NOTE: If your problem or questions has been resolved, please mark this thread as answered and award points accordingly.

Re: Keep the IP settings

hstagner — Mon, 13 Apr 2009 20:23:30 GMT

Snootalope,

I always use netsh to backup the IP settings before the conversion as well. The reason the IP settings do not stay is that Windows sees the vNIC as a new NIC (which it is because it is a completely different set of virtual hardware with its own drivers). This is probably even scriptable (hmmm... sounds like a new project).

Don't forget to use the buttons on the side to award points if you found this useful (you'll get points too).

Regards,

Harley Stagner

Re: Keep the IP settings

Lightbulb — Mon, 13 Apr 2009 18:15:17 GMT

You can use netsh to backup the config prior to conversion

http://www.windowsnetworking.com/kbase/WindowsTips/Windows2003/AdminTips/Network/UsingNetshtoBackupandRestoreNetworkConfiguration.html

I just do the following from a cmd window ipconfig /all > C:\ipbak.txt then RE-IP when conversion is done (If needed).

Keep the IP settings

snootalope — Mon, 13 Apr 2009 17:54:41 GMT

Just started using the converter to import physical machines. Works good (little slow). When it's finished and I power on the VM, the vnic is set to use DHCP. This isn't a huge problem for me yet as I'm just importing test boxes. But, what happens when I import domain controllers, exchange, and sql boxes and the ip's are different on their first startup? I'm thinking that could be ugly. Is there anyway to keep the IP settings after the machine is converted to virtual? They're all 2k3 server boxes.

thanks!