Local Area Connection numbers changing on recently virtualized server.
Posted on 2013-05-31
We recently did a physical to virtual virtualization of an HP Proliant DL380 G3 server ( Windows 2003 Enterprise SP2) to VMWare vSphere 5.1.0-7997.
When we virtualized it the network adapters were still in the hardware list and the virtual NICs got put in as Local Area Connections 4 and 5.
We have an application (Crystal Enterprise 10) that has to use NIC #1 for certain tasks (saving/updating reports)
So last night we removed ALL the NICs from Device Manager and the VM properties including the HP NIC team, rebooted, (re)added virtual production and backup NICs and rebooted.
Everything was fine, everything was working with the virtual NICs as 1 and 2.
When we rebooted again to put the machine back into production the NICs assigned themselves as 3 and 4.
I only see two NICs in Device Manager (the correct ones) but Network Connections show Local Area Connections 3 and 4.
I see Hex entires named Local Area Connection 0-6 in HKLM\System\CurrentControlSet(prime through 2)\Control\Network with their Pnp instance IDs.
We have not yet cleared out these keys as we are in production.
How can I set the NIC order/numbers and keep them that way?
We are all very tired after a long night battling this and are having trouble braining.