VMware Cloud Community
dwilli
Enthusiast
Enthusiast
Jump to solution

Static IP's not stored

When I run a cold clone of a server it does not bring over the static IP's for the server. It will recognize all the NIC's but when I logon to the server the IP is set to auto after a cold clone. I think I also saw the same issue with a hot clone. I am running Converter 3.0.2.

0 Kudos
1 Solution

Accepted Solutions
rriva
Expert
Expert
Jump to solution

sorry but .... which services ? maybe binded with phisical NIC MAC ?

Bye

R

If you found this information useful, please consider awarding points for "Correct" or "Helpful". Thanx!

RRiva | http://about.me/riccardoriva | http://www.riccardoriva.com

View solution in original post

0 Kudos
7 Replies
shaka
Enthusiast
Enthusiast
Jump to solution

If you run converter from the command line using an xml script you can specify it to preserver the NIC settings (IP and MAC address).

0 Kudos
dwilli
Enthusiast
Enthusiast
Jump to solution

No options for not running command line?

0 Kudos
rriva
Expert
Expert
Jump to solution

Your static IP Address is written in Windows Registry, binded with your phisical NIC.

If you clone a machine, the new NIC is a Virtual NIC qand is different than the original one, so it will be normal (and is a good thing) that the system don't keep the same ip on the NIC

Why you can't convert the machine and configure the static IP after conversion ?

Bye

R

If you found this information useful, please consider awarding points for "Correct" or "Helpful". Thanx!

RRiva | http://about.me/riccardoriva | http://www.riccardoriva.com
dwilli
Enthusiast
Enthusiast
Jump to solution

I can make the adjustments to the NIC after the conversion, that is not abig deal. I also found the articel for clearing the entry for the physical NIC. I was concerned because I converted a terminal server and cleared the production NIC and there were services still tied to the refernce that failed.

0 Kudos
rriva
Expert
Expert
Jump to solution

sorry but .... which services ? maybe binded with phisical NIC MAC ?

Bye

R

If you found this information useful, please consider awarding points for "Correct" or "Helpful". Thanx!

RRiva | http://about.me/riccardoriva | http://www.riccardoriva.com
0 Kudos
theanykey
Virtuoso
Virtuoso
Jump to solution

This is normal. If you were to take a physical NIC out of a physical machine and replace it with a new NIC. The new NIC defaults to DHCP ready. The same goes for a conversion where we litterally replace the physical NIC with a virtual one - we do not "convert" the NIC.

0 Kudos
jaganpjames
Enthusiast
Enthusiast
Jump to solution

so this is not a problem with hot clone alone.., a question i have raised.. http://communities.vmware.com/thread/114774

what i have tried is to do a manual sysprep after the migration.. and that gets the ip and adds the machine to domain. soo much of being automated.

0 Kudos