We have a windows 2003 application server that we have P2V'd.
We are working on getting rid of our 2003 boxes, so this is just a temporary step until we get everything up to 2008/2012. The issue I am facing with this particular server is this.
On our Physical servers we have our primary LAN connection, then a Microsoft Loopback Adapter with a static IP for our load balancer. Beneath that we have some static routes on the server which go out through the primary LAN connection.
After the P2V, the static routes are there, but they are now set to go out the Loopback connector which won't work.
We've tried deleting the static routes, then re-adding them which is fine, but once the server reboots the static routes move back to the loopback.
Even if we do the route add -P and add the interface at the end, the route will still jump back to using the loopback as it's interface after a reboot.
I've tried a netsh int ip reset, and we've also tried removing the loopback and then re-installing the loopback but no matter what, the static routes keep setting themselves to use the loopback adapter rather than our LAN connection.
Anyone ever seen this before?