Networking issue with Hyper-V External Virtual Network

Pretty much like Virtual Server 2005, Hyper-V has options to create virtual network cards for guest machines that directly maps with a physical network adapter on the host machine. There is  an important issue that may surprise you, however, especially if you are working on a remote server.

When you create a virtual network and map it to a physical Network Adapter (External Virtual Network), Hyper-V automatically removes all protocols from the physical Network Adapter on the host machine and enables Virtual Network Switch Protocol. This means TCP/IP protocol is also removed! The host server will appear disconnected/offline from the outsite world. If you were working over remote desktop, you will be kicked out, and won't be able to connect anymore.

All you have to do is re-enable TCP/IP on the physical Network Adapter in order to bring the server back online. Which of course you can't do unless you are logging in locally.

It is not a big deal if you have a second network card that is also connected to the Internet. In fact thats how I was saved, twice.

Why does Hyper-V remove all protocols from the physical network adapter except virtual networking? Is there some stability issues? Security issues? poor performance? I have yet to check the documentation on this.

But if you are reading this before it is too late, at least you can be prepared.