I’m building a demo lab on my “beast” laptop and want to make it as mobile as possible, independent of IP addresses, while retaining Internet access. I do that by placing the VMs on an internal virtual switch and running a proxy on the parent partition or in a VM (dual homed on external virtual switch). I accidentally built my VMs on an external virtual switch and wanted to switch them to an internal virtual switch called Internal 1. I could spend a couple of minutes going through every VM and making the change. Or I could just run this in an elevated PowerShell window, as I just did on my Windows 8 (client OS) machine:
Connect-VMNetworkAdapter –VMName * –SwitchName Internal1
Every VM on my PC was connected to the Internal1 virtual switch.
This blog post is the property of Aidan Finn (@joe_elway / http://www.aidanfinn.com) and may not be reused in any manner without prior consent of Aidan Finn. You may quote one paragraph from this blog post if you link to the original blog post.
- Windows Server 2012 NIC Teaming Part 3 – Switch Connection Modes
- Windows Server 2012 Hyper-V & The Hyper-V Extensible Switch
- Create A Windows Server 2012 Hyper-V Cluster Using PowerShell
- Create Lots Of Hyper-V Virtual Machines From A CSV File Using PowerShell
- Unveil Of Cisco Nexus 1000V Distributed Switch For Windows Server 2012 Hyper-V