VMware Communities: Keep the IP settings

Up to Discussions in Converter

This Question is Answered

2 "helpful" answers available (6 pts)

6 Replies Last post: Apr 15, 2009 10:29 AM by snootalope

Keep the IP settings

Apr 13, 2009 10:54 AM

snootalope 47 posts since
Oct 25, 2007

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!

Reply Re: Keep the IP settings Apr 13, 2009 11:15 AM

Lightbulb 1,389 posts since
Aug 15, 2008

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).

Reply Re: Keep the IP settings Apr 13, 2009 1:26 PM

hstagner 111 posts since
Oct 16, 2008

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

Reply Re: Keep the IP settings Apr 14, 2009 6:09 AM

in response to: hstagner

IamTHEvilONE 1,385 posts since
Apr 1, 2008 VMware

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.

Reply Re: Keep the IP settings Apr 14, 2009 6:30 AM

in response to: IamTHEvilONE

hstagner 111 posts since
Oct 16, 2008

Yep, you are correct.

Reply Re: Keep the IP settings Apr 15, 2009 10:03 AM

Ashmai 32 posts since
Oct 26, 2007

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!

Reply Re: Keep the IP settings Apr 15, 2009 10:29 AM

in response to: IamTHEvilONE

snootalope 47 posts since
Oct 25, 2007

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!

Actions

View as PDF

Up to Discussions in Converter