Hosting the Windows Server 2012 Base Configuration test lab in Hyper-V
Articles,  Blog

Hosting the Windows Server 2012 Base Configuration test lab in Hyper-V


Let’s step through the process of hosting the Windows Server 2012 base configuration test lab on a Windows Server 2012 Hyper-V server. The logical configuration of the base configuration test lab consists of three servers, DC1, APP1, and EDGE1, that are connected to the Corpnet subnet. Two servers, EDGE1 and INET1, are connected to the Internet subnet. A client computer, CLIENT1, can connect to either subnet. The key elements of hosting the base configuration test lab on a single Hyper-V server are the following: All five computers (DC1, APP1, EDGE1, INET1, and CLIENT1) are virtual machines running on the physical Hyper-V server computer. The Corpnet subnet is implemented as the Corpnet private virtual switch. The Internet subnet is implemented as the Internet private virtual switch, and CLIENT1 can be connected to either switch. The Hyper-V server has at least one physical network adapter that connects to your organization intranet and the Internet. You can use this connection and an external virtual switch on the Hyper-V server to temporarily connect a test lab computer to the real Internet (rather than the isolated Internet subnet), for example, to install software or updates.Now, let’s build it out, starting with the Corpnet subnet. In step 1, you create a private virtual switch named Corpnet. You can do this in the Hyper-V Manager snap-in with the Virtual Switch Manager or with the New-VMSwitch Windows PowerShell cmdlet. In step 2, create a new virtual machine named DC1 that is connected to the Corpnet virtual switch. You can do this in the Hyper-V Manager snap-in with the New Virtual Machine wizard or with the New-VM Windows PowerShell cmdlet. In step 3, you create a new virtual machine named APP1 that is connected to the Corpnet virtual switch. In step 4, you create a new virtual machine named CLIENT1 that is connected to the Corpnet virtual switch. In step 5, you configure DC1, APP1, and CLIENT1 using the “Steps for Configuring the Corpnet Subnet” section of the Windows Server 2012 Base Configuration test lab guide. This includes installing Windows Server 2012 and Windows 8 on the virtual machines. The Corpnet subnet is complete. Now let’s build out the Internet subnet. In step 1, you create a private virtual switch named Internet. In step 2, you create a new virtual machine named EDGE1 that is connected to the Corpnet virtual switch. You then add a network adapter to EDGE1 that is connected to the Internet virtual switch. You can do this in the Hyper-V Manager snap-in through the settings of the EDGE1 virtual machine or with the Add-VMNetworkAdapter Windows PowerShell cmdlet. In step 3, you create a new virtual machine named INET1 that is connected to the Internet virtual switch. In step 4, you configure EDGE1 and INET1 using the “Steps for Configuring the Internet Subnet” section of the Windows Server 2012 Base Configuration test lab guide. The resulting base configuration test lab has the four server computers on the Corpnet and Internet virtual switches, and the CLIENT1 computer can be connected to either one depending on what you want to test. For more information about hosting test lab guide environments in Windows Server 2012 Hyper-V, see the resources at aka.ms/hvtlgs. Also visit microsoft.com/testlabguides.

One Comment

Leave a Reply

Your email address will not be published. Required fields are marked *