How to: Configure or Reconfigure Network Isolation
[This documentation is for preview only, and is subject to change in later releases. Blank topics are included as placeholders.]
You can use network isolation in Visual Studio Team System Lab Management to enable multiple copies of a lab environment to run at the same time without causing network conflicts, such as conflicts in computer names and Domain Name System (DNS) registration.
You can configure Lab Management by using either the administration console for Team Foundation or the TFSConfig command-line tool. For more information about how to use the administration console, see How to: Open the Team Foundation Administration Console. For more information about the command-line tool, see Managing Server Configuration with TFSConfig.
To configure or change the network isolation settings
In IP range, type the range of Internet Protocol (IP) addresses to be assigned to the virtual machines in an environment when an isolated network is created.
The addresses that you specify are used only for internal routing among virtual machines and are not exposed beyond the boundaries of an environment. Therefore, you can specify any address range that is not used within your public network. In most cases, you can use the default range of 192.168.1.0 – 255.
In DNS suffix, type the suffix of the domain name to be assigned to the environment when an isolated network is created.
Each virtual machine in a network-isolated environment is registered with a unique external name and DNS suffix that you specify. You should use a suffix that is configured to support non-secure updates in your DNS server. To confirm that the suffix is correctly configured in the DNS hierarchy, contact your network administrator.
Click Test to determine whether Visual Studio Team System Team Foundation Server can use the suffix.
If the suffix is valid, a green check mark appears. Click OK.
If the suffix is not valid, a red x and an error message appear. You must fix the error before you can continue.