Isolated lab impacted the production environment

[cfizz34]

Has anyone every brought up a domain controller in the isolated lab and it have a negative impact on the production environment particular with DNS resolution?

[Virtuollie]

How could it impact the production environment if running isolated?

[jmmarton]

Yes I can't think of any reason why bringing up a DC in a Data Lab (Virtual Lab) would have any impact on production.

Joe

[segfault]

We have not had an issue. We use the multi-host vDS based Virtual labs validate all of our DR replication policies. We have 250 VM's being replicated and 50+ Application Groups with two virtual labs and have not had an issue yet. Each app group includes the full application stack including AD, SQL, App, and a Win 10 VM with the client applications on them.

We did, however, first test the integrity of the isolation of the lab with a few test VMs.

In general, you absolutely must make sure that the distributed port groups used by your virtual labs are not in any way linked to the production systems, otherwise your isolated lab is not really isolated and will cause all sorts of issues. Doing things like specifying the same vlan id for both the production and virtual lab side will cause issues.

--john

[cfizz34]

Be very careful with the VLAN tagging of your lab vs your production environment. I assumed the proxy would isolate the traffic on the lab side but it actually killed the production side since the VLAN tag was the same.