Hosting the Corpnet Subnet for Public Cloud Test Lab with Windows Server 2012 Hyper-V

  • Article

The Corpnet subnet for public cloud test lab consists of three computers (DC1, APP1, and CLIENT1) that are directly connected to your organization network, but form a logical Corpnet subnet through DNS configuration and the presence of the corp.contoso.com Active Directory Domain Services (AD DS) domain. This is in contrast to the Corpnet subnet defined for the Base Configuration test lab, in which the Corpnet subnet is isolated from your organization network. The Corpnet subnet for public cloud test lab allows the computers on the logical Corpnet subnet to access Internet resources directly, enabling public cloud technology configurations and scenarios.

This figure shows the computers and their connections to the organization. You can implement this configuration using physical computers, virtual machines, or a combination.

If you are using Windows Server 2012 and the Hyper-V server role for your virtualization solution, you can configure the Corpnet subnet for public cloud in Hyper-V on a single server as shown in the following figure:

The key elements of this configuration are the following:

  • The Hyper-V server has at least one physical network adapter that connects to your organization intranet and the Internet.
  • All three computers (DC1, APP1, and CLIENT1) are virtual machines running on the Hyper-V server.
  • All three computers connect to the organization network through the virtual switch defined by the Hyper-V server's physical network adapter. You do not need to create an additional virtual switch.

Create the computers of the logical Corpnet subnet in Windows Server 2012 Hyper-V with the following:

  1. Create a new virtual machine named DC1 with a single network adapter that uses the virtual switch corresponding to the Hyper-V server's physical network adapter. For the steps to do this, see Creating a new virtual machine.
  2. Create a new virtual machine named APP1 with a single network adapter that uses the virtual switch corresponding to the Hyper-V server's physical network adapter.
  3. Create a new virtual machine named CLIENT1 with a single network adapter that uses the external virtual switch corresponding to the Hyper-V server's physical network adapter.
  4. Follow the instructions in Configuring the Corpnet Subnet of the Base Configuration Test Lab for Public Cloud Technologies. To install Windows Server 2012, Windows Server 2008 R2, Windows 8, or Windows 7 on a virtual machine, see Installing an operating system on a new virtual machine.

 

Windows PowerShell commands
The following Windows PowerShell cmdlet or cmdlets perform the same function as steps 1-3 of the preceding procedure. You must supply values for the –MemoryStartupBytes, -NewVHDSizeBytes, and –SwitchName parameters for each virtual machine. Enter each cmdlet on a single line, even though they may appear word-wrapped across several lines here because of formatting constraints.
New-VM –Name DC1 –MemoryStartupBytes <MemorySize> -NewVHDSizeBytes <DiskSize> –SwitchName <ExternalVirtualNetwork> New-VM –Name APP1 –MemoryStartupBytes <MemorySize> -NewVHDSizeBytes <DiskSize> –SwitchName <ExternalVirtualNetwork>
 New-VM –Name CLIENT1 –MemoryStartupBytes <MemorySize> -NewVHDSizeBytes <DiskSize> –SwitchName <ExternalVirtualNetwork>

For additional information about configuring test labs with Windows Server 2012 Hyper-V, see Hosting Test Lab Guide environments in Windows Server 2012 Hyper-V.

For more information, see Test Lab Guides.

For the latest developments in the Test Lab Guides initiative, see the Microsoft Test Lab Guides blog.