Forum Discussion
Hyper-V Default switch IP address range change. Ver 1809 Build 17763.1
HotCakeX
Very informative thread for this newb. Like many, I'd consider the behavior of the default switch a bug and not an enhancement.
1) Installed automatically (not optional).
2) Can't be removed.
3) Can't be modified.
4) No persistent state except unconfigured.
5) Defaults to "Public" on a Domain machine and reconfiguration of state doesn't stick.
VBox and VMWare user attempting to learn Hyper-V and decipher the lack of logic in the above configuration.
Because it's "Public" or doesn't allow the option of a network type selection the Default Switch kills PowerShell WinRM and MS Admin Center on my domain, even when all VMs are using a second manually configured external switch and there is nothing using it - it's still in the registry in the default default configuration after reboot and PowerShell DSC is useless with the Default Switch registering.
I've read the arguments that it's "for amateurs" etc and there to make networking easy. My experience is exactly the opposite, that it's inexplicably configured to keep professionals from accomplishing their work. It breaks workflows that would otherwise be successful and that is a substantive meaning of a 'bug' in the software.
I've temporarily gone back to VMWare, which works flawlessly managing my virtual lab because default switch just doesn't work in my situation.
If someone can, please help me find workarounds to the 5 points above I'd greatly appreciate both your time and the knowledge. Very frustrating to have a simple configuration be this difficult to get working.
FYI - problems listed above are on 1909.
Thanks