In case your Windows server has more than one network card installed, it's generally a good idea to name every connection (giving it a descriptive name), to determine at once which is which.
This approach can especially be useful when troubleshooting network connectivity; using non-standard names (different from Local Area Connection N) can allow you to pinpoint the problem quickly.
It is also very convenient if parameters of a certain network card are to be changed quickly or if it is necessary to disable an interface quickly.
Along with using netsh-based backup of the entire network configuration, it can save you precious time when you need to restore a configuration to a known state.
This approach can especially be useful when troubleshooting network connectivity; using non-standard names (different from Local Area Connection N) can allow you to pinpoint the problem quickly.
It is also very convenient if parameters of a certain network card are to be changed quickly or if it is necessary to disable an interface quickly.
Along with using netsh-based backup of the entire network configuration, it can save you precious time when you need to restore a configuration to a known state.
