I am running a Windows 2019 Hyper-V core (Level 0) hosting 2 2019 Windows 2019 Standard Servers (Level 1). One is the DC, etc. the other hosts RDS, Hyper-V, etc. I have RD Gateway up and running to authenticate with the DC to connect to internal machines, but would like to implement a full VDI deployment. I have the golden image and collection created with a couple VMs of Win10 Enterprise (Level 2). At first I was connecting remotely to them fine, however, they had no internet access. While tinkering with that issue, I lost all network connectivity from Level 2 and can now only connect through the Level 1 (or a remote) HV Manager console. The Level 1 default virtual switch is now missing and adding a new Level 1 external switch, attaching it to the Level 2 VMs, only assigns an APIP to them. There's just no way out from there. From the documentation, I can't quite see how that the Level 1 external virtual switch connects to the Level 1 Hyper-V Network Adapter and performs the NAT to Level 2. I see that the recommended method is through the MAC spoofing, but there is still the lack of connectivity between the Level 1 virtual switch and the Level 1 network adapter. I have tried a second subnet for the Level 2 VMs, but there's still a disconnect. What is the best setup to accomplish this and route the traffic throughout the nesting? There are probably all sorts of issues with this setup, but I'd like to see if I could get it set up this way if for no other purpose than for experimentation. Any pointers?
