So, I've solved this issue, but was hoping that someone would provide me a
little insight on the 'whys'.

I recently received a VMC file that had a network adapter (well, two
actually) set to 'Internal'. However, when importing this into my machine,
I saw the following message in the VS Admin Console under Network Adapters:



"The virtual network for this virtual network interface could not be found.
This network interface will be left unplugged."

So, I took a look at the original VMC file and saw the following:

<ethernet_adapter>
<controller_count type="integer">2</controller_count>
<ethernet_controller id="0">
<ethernet_card_address type="bytes">0003FFE619EA</ethernet_card_address>
<id type="integer">4</id>
<virtual_network>
<id type="bytes">D53071426B5B4E2C995346E38771AFB8</id>
<name type="string">Internal Network</name>
</virtual_network>
</ethernet_controller>
<ethernet_controller id="1">
<ethernet_card_address type="bytes">0003FFE719EA</ethernet_card_address>
<id type="integer">5</id>
<virtual_network>
<id type="bytes">D53071426B5B4E2C995346E38771AFB8</id>
<name type="string">Internal Network</name>
</virtual_network>
</ethernet_controller>
</ethernet_adapter>

Note the <name> node. I removed this <name> node and tried again. Presto.
Imported with no problems. I was experiencing this very same issue with
moving machines to a German box. I presume the failure was due to
internationalization of the <name> string.

So, it looks like <name> is a string based override of the <id> node (like
in VPC).

My question is, why do I see this node at all? When I create a VMC file, I
never see this <name> node?

Cheers,
-Mezz