Distributed vSwitch Uplink Rename Broke Things

Today I moved my standard vSwitch networking over to a distributed switch. It went well. Ok. I lie, it didn't go well at all. To be fair the main part of the work had gone very well. I've migrated all my virtual machines over successfully to the new port group. I've even migrated my ESXi management network vmkernel port over too. All was looking great until I renamed the dvUplinks.

The first time I saw the VMware distributed switch I wondered what all that 'dvThis' and 'dvThat' business was about. I understand now that it is just to differentiate from any port groups that may be configured on standard vSwitches. Fine. I just don't like the dv prefix. So I decided to rename the uplinks to 'TrunkA', 'TrunkB' etc. This was clearly a Bad Plan:

Oddly enough, one of the servers is still up as I can connect to a Windows terminal server that is running on it. I am sat about sixty miles away from my ESXi servers and I need to hurry home to fix the problem I caused. I'll have to dive on the console and restart the management network I think. Anyone have a spare IP KVM that they can let me have?