We're utilizing TFS and Hyper-V with SCVMM for our testing environments, but unfortunately we don't have any network separation right now. We had to create our own domain in order to most effectively use SCVMM deployment and TFS management without having to get domain access to the entire corporate network.
This is problematic for us for a few reasons. For one, we're spamming network discovery with our VMs (can't be disabled, it's needed for certain TFS functions). For two, we have to manually go in to each VM on creation, statically set the DNS to the TFS, join the test domain, reset to DHCP, and reboot the machine. This makes deployment a nightmare, as well as adding any additional Hyper-V hosts or build controllers.
We don't want total isolation, we still need internet access to pull files from Azure during build-deploy-test cycles, but we need to have more control over the environment. Is the easiest solution to this moving everything onto its own subnet?
The biggest issue I see with that is connecting to the TFS or any of the Hyper-V hosts for maintenance or test case access.
The second, and I'm told this is a terrible idea, is to add the test domain into the primary DNS for the network. But that would leave us with two domain discoverable domains on one network subnet.