Windows Server 2012 R2 Hyper-V Network Virtualization With System Center 2012 R2 VMM Test Lab_RTM

5/27/2018 Windows Server 2012 R2 Hyper-V Network Virtualization With System Center 2012 R...

http:///reader/full/windows-server-2012-r2-hyper-v-network-virtualization-with-syst

Test Lab Guide: Windows Server 2012R2 Hyper-V Network Virtualization

with System Center 2012 R2 VMM

Microsoft Corporation

Published: September, 2013

Abstract

This Microsoft Test Lab Guide (TLG) provides you with step-by-step instructions to create the

Windows Server 2012 R2 Network Virtualization with System Center 2012 R2 Virtual Machine

Manager (VMM) test lab, using computers running Windows Server 2012 R2. This test lab is

based on four physical computers, each hosting multiple virtual machines.



Copyright InformationThis document is provided for informational purposes only and Microsoft makes no warranties,

either express or implied, in this document. Information in this document, including URL and

other Internet Web site references, is subject to change without notice. The entire risk of theuse or the results from the use of this document remains with the user. Unless otherwise noted,

the example companies, organizations, products, domain names, e-mail addresses, logos,

people, places, and events depicted herein are fictitious, and no association with any real

company, organization, product, domain name, e-mail address, logo, person, place, or event is

intended or should be inferred. Complying with all applicable copyright laws is the responsibility

of the user. Without limiting the rights under copyright, no part of this document may be

reproduced, stored in or introduced into a retrieval system, or transmitted in any form or by any

means (electronic, mechanical, photocopying, recording, or otherwise), or for any purpose,

without the express written permission of Microsoft Corporation.

Microsoft may have patents, patent applications, trademarks, copyrights, or other intellectual

property rights covering subject matter in this document. Except as expressly provided in any

written license agreement from Microsoft, the furnishing of this document does not give you

any license to these patents, trademarks, copyrights, or other intellectual property.

2013 Microsoft Corporation. All rights reserved.

Date of last update: September 13, 2013

Microsoft, Windows, Active Directory, Internet Explorer, and Windows Server are either

registered trademarks or trademarks of Microsoft Corporation in the United States and/or other

countries.

All other trademarks are property of their respective owners.



Contents

Introduction ..................................................................................................................................... 7

In this guide .................................................................................................................................. 7

Test lab overview ......................................................................................................................... 8

Hardware and software requirements ...................................................................................... 12

Steps for Configuring the Hosternet subnet ................................................................................. 12

Step 1: Configure HNVHOST1 .................................................................................................... 12

Install the operating system on HNVHOST1 ........................................................................... 13

Configure TCP/IP properties on HNVHOST1 ........................................................................... 13

Rename the computer to HNVHOST1 .................................................................................... 14

Configure HNVHOST1 as a domain controller and DNS server .............................................. 15

Create a user account in Active Directory on HNVHOST1 ...................................................... 16

Install the Hyper-V server role on HNVHOST1 ....................................................................... 18



Configure TCP/IP properties on HNVHOST2 ........................................................................... 19

Rename the computer to HNVHOST2 and join the hnv.adatum.com domain ...................... 20


Steps for Configuring the Internet Subnet .................................................................................... 22



Configure TCP/IP properties on HNVHOST4 ........................................................................... 23Rename the computer to HNVHOST4 .................................................................................... 24


Create virtual switches on HNVHOST4 ................................................................................... 26

Create virtual machines on HNVHOST4 .................................................................................. 27

Step 2: Configure INET1 ............................................................................................................. 28

Install the operating system on INET1 .................................................................................... 29

Configure TCP/IP properties on INET1 ................................................................................... 29

Rename the computer to INET1 ............................................................................................. 30

Install the DNS Server and Web Server (IIS) server roles on INET1 ........................................ 31

Create DNS records on INET1 ................................................................................................. 32

Install and configure DHCP on INET1 ...................................................................................... 33

Configure the NCSI web site on INET1 .................................................................................... 35



Configure network connections on HNVHOST3 ..................................................................... 36



Rename the computer to HNVHOST3 and join the hnv.adatum.com domain ...................... 38


Steps for Configuring the Contoso Corpnet Subnet ...................................................................... 40

Step 1: Configure DC1 ................................................................................................................ 40

Install the operating system on DC1 ....................................................................................... 41Configure TCP/IP properties on DC1 ...................................................................................... 41

Configure DC1 as a domain controller and DNS server .......................................................... 43

Install and configure DHCP on DC1......................................................................................... 44

Create a user account in Active Directory on DC1 ................................................................. 46

Step 2: Configure APP1 .............................................................................................................. 47

Install the operating system on APP1 ..................................................................................... 47

Configure TCP/IP properties on APP1..................................................................................... 47

Join APP1 to the CORP domain ............................................................................................... 49

Install the Web Server (IIS) role on APP1 ............................................................................... 50

Create a shared folder on APP1 .............................................................................................. 50Step 3: Configure EDGE1 ............................................................................................................ 51

Install the operating system on EDGE1 .................................................................................. 52

Configure TCP/IP properties on EDGE1 .................................................................................. 52

Join EDGE1 to the CORP domain ............................................................................................ 54

Step 4: Test access to resources on APP1 .................................................................................. 55

Steps for Configuring the Fabrikam Corpnet Subnet .................................................................... 56

Step 1: Configure DC1 ................................................................................................................ 56

Install the operating system on DC1 ....................................................................................... 57

Configure TCP/IP properties on DC1 ...................................................................................... 57Configure DC1 as a domain controller and DNS server .......................................................... 58

Install and configure DHCP on DC1......................................................................................... 60

Create a user account in Active Directory on DC1 ................................................................. 61

Step 2: Configure APP1 .............................................................................................................. 62

Install the operating system on APP1 ..................................................................................... 63

Configure TCP/IP properties on APP1..................................................................................... 63

Join APP1 to the CORP domain ............................................................................................... 64

Install the Web Server (IIS) role on APP1 ............................................................................... 65

Create a shared folder on APP1 .............................................................................................. 66

Step 3: Configure EDGE1 ............................................................................................................ 67Install the operating system on EDGE1 .................................................................................. 67

Configure TCP/IP properties on EDGE1 .................................................................................. 67

Join EDGE1 to the CORP domain ............................................................................................ 70

Step 4: Test access to resources on APP1 .................................................................................. 71

Steps for Installing and Configuring System Center 2012 R2 Virtual Machine Manager .............. 71



Step 1: Install Windows Assessment and Deployment Kit (ADK) .............................................. 72

Install Windows Assessment and Deployment Kit (ADK) on HNVHOST2 ............................... 72

Step 2: Install and configure SQL Server 2012 ........................................................................... 72

Install SQL Server 2012 on HNVHOST2 ................................................................................... 73

Step 3: Install and configure System Center 2012 R2 Virtual Machine Manager ...................... 74

Install System Center Virtual Machine Manager on HNVHOST2 ............................................ 74

Configure System Center Virtual Machine Manager on HNVHOST2 ...................................... 77

Step 5: Install and configure the Microsoft Software Gateway ................................................. 93

Configure the HNVHOST3 server as a dedicated gateway host ............................................. 93

Install the gateway as a network service ................................................................................ 93

Create Tenant VM Networks .................................................................................................. 94

Create IP Pools for the VM Networks ..................................................................................... 97

Step 6: Install and configure IPAM on HNVHOST2 .................................................................... 98

Install the IPAM feature .......................................................................................................... 98

Deploy IP Address Management ............................................................................................ 99

Add the User1 account to the IPAM Administrators local group ......................................... 100

Deploy the IPAM VMM plugin .............................................................................................. 101

Access the virtualized address space in IPAM ...................................................................... 102

Steps for Implementing and Testing Hyper-V Network Virtualization and HNV Gateway ......... 102

Step 1: Establish site-to-site VPN connections ........................................................................ 103

Install RRAS on Contoso EDGE1 and create a site-to-site VPN connection to GatewayVM1

running on HNVHOST3 ...................................................................................................... 103

Install RRAS on Fabrikam EDGE1 and create a site-to-site VPN connection to HNVHOST3 . 106

View the site-to-site VPN connections on GatewayVM1 ..................................................... 108

Step 2: Deploy Tenant Virtual Machines ................................................................................. 110

Deploy the APP2 tenant virtual machines on the datacenter VMM host ............................ 110

Verify network connectivity for the APP2 virtual machines ................................................. 113

Step 3: Relocate Virtual Machines to the Service Provider Network ...................................... 115

Shut down VMs on HNVHOST4 and move VHD files to HNVHOST2 .................................... 115

Deploy the APP1 tenant virtual machines on the datacenter VMM host ............................ 116

Step 4: Test Connectivity and HNV S2S VPN Operation........................................................... 118

Test access from Contoso APP1 to the Contoso Corpnet ..................................................... 119

Test access from Fabrikam APP1 to the Fabrikam Corpnet ................................................. 119

Test access to Contoso APP1 from the Contoso Corpnet ..................................................... 120

Test access to Fabrikam APP1 from the Fabrikam Corpnet ................................................. 120

Step 5: Demonstrate HNV Gateway NAT connectivity to Internet resources ......................... 121

Create a new host record on Contoso DC1 .......................................................................... 121

Access an Internet web resource from Contoso APP1 ......................................................... 122

Create a NAT rule to publish the Contoso APP1 web server ................................................ 122

Determine the NAT external IP address assigned to the Contoso VM Network .................. 123



Test access to Contoso APP1 from the Internet subnet ....................................................... 124

Step 6: Demonstrate HNV Forwarding Gateway ..................................................................... 124

Configure and deploy a VMM service template for GatewayVM2 ...................................... 125

Configure network connections on GatewayVM2 ............................................................... 126

Connect the third virtual adapter on GatewayVM2 ............................................................. 127

Install GatewayVM2 as a network service ............................................................................ 128

Create a VM network for the Adatum service provider ....................................................... 129

Create an IP Pool for the Adatum VM Network ................................................................... 130

Deploy a VM in the virtualized Adatum VM network .......................................................... 130

Create a route to the CA space through the forwarding gateway ....................................... 131

Test network connectivity between physical and virtual address spaces ............................ 132

Additional Resources ................................................................................................................... 133

Appendix ...................................................................................................................................... 133

Create a Windows Server 2012 R2 virtual hard disk ................................................................ 133

Install Windows ADK on an offline computer. ......................................................................... 135



7

IntroductionServer virtualization enables multiple server instances to run concurrently on a single physical host; yet

server instances are isolated from each other. Each virtual machine essentially operates as if it is theonly server running on the physical computer. Network virtualization provides a similar capability, in

which multiple virtual network infrastructures run on the same physical network (potentially with

overlapping IP addresses), and each virtual network infrastructure operates as if it is the only virtual

network running on the shared network infrastructure.

Hyper-V Network Virtualization (HNV) provides virtual networks to virtual machines similar to how

server virtualization (hypervisor) provides virtual machines to the operating system. Network

virtualization decouples virtual networks from the physical network infrastructure and removes the

constraints of VLAN and hierarchical IP address assignment from virtual machine provisioning. This

flexibility makes it easy for customers to move to IaaS clouds and efficient for service providers anddatacenter administrators to manage their infrastructure, while maintaining the necessary multi-tenant

isolation, security requirements, and supporting overlapping Virtual Machine (VM) IP addresses.

The Windows platform provides public APIs for datacenter management software to manage Hyper-V

Network Virtualization. Microsoft System Center Virtual Machine Manager (VMM) is one such

datacenter management product. The management software contains all of the Hyper-V Network

Virtualization policies. Because the virtual machine manager must be aware of virtual machines and

more importantly provisions virtual machines and complete customer virtual networks in the datacenter

and must be multi-tenant aware, managing Hyper-V Network Virtualization policy is a natural extension

for policy-based networking.

In this guide

This document contains instructions for setting up the Windows Server 2012 R2 Hyper-V Network

Virtualization with System Center 2012 R2 VMM test lab by deploying four (4) physical server computers

running Windows Server 2012 R2 and twelve (12) virtual machines running Windows Server 2012 R2.

The resulting configuration simulates two customer private intranets, one simulated service provider

datacenter environment, and the Internet.

Note: The Windows Server 2012 R2 Hyper-V Network Virtualization with System Center

2012 R2 VMM test lab can be built using the "Steps for Configuring the Corpnet

Subnet" and "Steps for Configuring the Internet Subnet" sections of theTest Lab

Guide: Windows Server 2012 R2 Base Configurationas its base. If you have already

built the Windows Server 2012 R2 Base Configuration using virtual machines, you

can use the INET1, DC1, EDGE1, and APP1 computers for the Internet and Contoso

Corpnet subnets. Instructions for configuring these virtual machines are also

included in this document where appropriate.
http://www.microsoft.com/en-us/download/details.aspx?id=39638http://www.microsoft.com/en-us/download/details.aspx?id=39638http://www.microsoft.com/en-us/download/details.aspx?id=39638http://www.microsoft.com/en-us/download/details.aspx?id=39638http://www.microsoft.com/en-us/download/details.aspx?id=39638http://www.microsoft.com/en-us/download/details.aspx?id=39638


http:///reader/full/windows-server-2012-r2-hyper-v-network-virtualization-with-sys

8

Important

The following instructions are for configuring the Windows Server 2012 R2 Hyper-V Network

Virtualization with System Center 2012 R2 VMM test lab. Individual computers are needed to

separate the services provided on the network and to clearly show the desired functionality.

This configuration is neither designed to reflect best practices nor does it reflect a desired or

recommended configuration for a production network. The configuration, including IP addresses

and all other configuration parameters, is designed only to work on a separate test lab network.

Note: If you are able to work from a computer-based copy of this document during the lab

exercises, leverage the Hyper-V clipboard integration feature to paste commands.

This will minimize potential errors with mistyped command strings.

Highlight and right-click a command from this document listed in boldtext. Click Copy. From the virtual machine menu bar, click Clipboard, and then click Type

clipboard text.

Test lab overview

The Windows Server 2012 R2 Hyper-V Network Virtualization with System Center 2012 R2 VMM test lab

consists of the following:

One physical server computer running Windows Server 2012 R2 named HNVHOST1 that isconfigured as a Hyper-V host, Domain Controller and DNS Server for the simulated service provider

datacenter domain, hnv.adatum.com. HNVHOST1 is also configured to host the following virtual

machines in the simulated service provider datacenter:

One virtual machine computer running Windows Server 2012 R2 named APP1 that isconfigured as a datacenter hosted application and web server for the Contoso tenant

network.

One virtual machine computer running Windows Server 2012 R2 named APP1 that isconfigured as a datacenter hosted application and web server for the Fabrikam tenant

network.

One virtual machine computer running Windows Server 2012 R2 named APP1 that isconfigured as an Adatum service provider application server hosted using Hyper-V

Network Virtualization within the service provider datacenter.


http:///reader/full/windows-server-2012-r2-hyper-v-network-virtualization-with-sys

9

One physical server computer running Windows Server 2012 R2 named HNVHOST2 that isconfigured as a Hyper-V host, SQL server, IPAM server, and System Center 2012 R2 Virtual Machine

Manager. HNVHOST2 is also configured to host and manage the virtual network environment in the

simulated service provider datacenter, and to host the following virtual machines in the simulatedservice provider datacenter:

One virtual machine computer running Windows Server 2012 R2 named APP2 that isconfigured as a datacenter hosted application and web server for the Contoso tenant

network.

One virtual machine computer running Windows Server 2012 R2 named APP2 that isconfigured as a datacenter hosted application and web server for the Fabrikam tenant

network.

One physical server computer running Windows Server 2012 R2 named HNVHOST3 that isconfigured as a Hyper-V Network Virtualization Gateway. HNVHOST3 is also configured to host the

following virtual machines in the simulated service provider datacenter:

One virtual machine computer running Windows Server 2012 R2 named GatewayVM1that is configured as a cross-premise Site-to-Site (S2S) VPN and NAT gateway for the

hosted tenant networks.

One virtual machine computer running Windows Server 2012 R2 named GatewayVM2that is configured as a HNV forwarding gateway for the Adatum service provider

datacenter.

One physical server computer running Windows Server 2012 R2 named HNVHOST4 that isconfigured as a Hyper-V host. HNVHOST4 is also configured to host the following virtual machines in

the simulated Internet and simulated customer on-premises networks:

One virtual machine computer running Windows Server 2012 R2 named INET1 that isconfigured as an Internet Domain Name System (DNS) server and web server.

One virtual machine computer running Windows Server 2012 R2 named DC1 that isconfigured as a Contoso customer private intranet domain controller and DNS server.

One virtual machine computer running Windows Server 2012 R2 named APP1 that isconfigured as a general application and web server for the Contoso domain.

One virtual machine computer running Windows Server 2012 R2 named EDGE1 that isconfigured as an Internet edge server for the Contoso domain.


http:///reader/full/windows-server-2012-r2-hyper-v-network-virtualization-with-syste

10

One virtual machine computer running Windows Server 2012 R2 named DC1 that isconfigured as a Fabrikam customer private intranet domain controller and DNS server.

One virtual machine computer running Windows Server 2012 R2 named APP1 that isconfigured as a general application and web server for the Fabrikam domain.

One virtual machine computer running Windows Server 2012 R2 named EDGE1 that isconfigured as an Internet edge server for the Fabrikam domain.

The Windows Server 2012 R2 Hyper-V Network Virtualization with System Center 2012 R2 VMM test lab

consists of seven subnets that simulate the following:

The Internet, referred to as the Internet subnet (131.107.0.0/24). An intranet, referred to as the Hosternet subnet (192.168.0.1/24) connected to the Internet

subnet via a second network adapter on the HNV Gateway server HNVHOST3.

An intranet, referred to as the Contoso Corpnet subnet (10.0.0.0/24), separated from theInternet subnet by Contoso EDGE1.

An intranet, referred to as the Fabrikam Corpnet subnet (10.0.0.0/24), separated from theInternet subnet by Fabrikam EDGE1.

A Hyper-V Network Virtualization virtual network, referred to as the Contoso VM Network(10.0.1.0/24), hosted on the simulated service provider datacenter servers HNVHOST1 and

HNVHOST2.

A Hyper-V Network Virtualization virtual network, referred to as the Fabrikam VM Network(10.0.1.0/24), hosted on the simulated service provider datacenter servers HNVHOST1 and

HNVHOST2.

A Hyper-V Network Virtualization virtual network, referred to as the Adatum VM Network(10.0.1.0/24), hosted on the simulated service provider datacenter server HNVHOST1

Computers on each subnet connect using a physical hub, switch, or virtual switch. See the following

figure for the configuration of the Windows Server 2012 R2 Hyper-V Network Virtualization with System

Center 2012 R2 VMM test lab.



11

Figure 1 Windows Server 2012 R2 Hyper-V Network Virtualization with System Center 2012 R2 VMM test lab

This document describes how to build out the Windows Server 2012 R2 Hyper-V Network Virtualization

with System Center 2012 R2 VMM test lab in six sections:

Steps for configuring the Hosternet subnet (HNVHOST1, HNVHOST2) Steps for configuring the Internet subnet (INET1 on HNVHOST4, and HNVHOST3) Steps for configuring the Contoso Corpnet subnet (DC1, APP1, and EDGE1 on HNVHOST4) Steps for configuring the Fabrikam Corpnet subnet (DC1, APP1, and EDGE1 on HNVHOST4) Steps for installing and configuring System Center 2012 R2 Virtual Machine Manager

(HNVHOST2)

Steps for implementing and testing Hyper-V Network Virtualization and HNV GatewayThis test lab demonstrates operation of Hyper-V Network Virtualization in a simulated service provider

datacenter using Hyper-V virtualization and System Center 2012 R2 Virtual Machine Manager. Simulated

on-premises customer networks are used to demonstrate access to hosted cloud resources over a

simulated Internet connection. The two customer networks share the same computer names and IP

addresses to demonstrate the secure isolation provided by Hyper-V Network Virtualization. A third



12

virtual network also shares this address space, and is used to demonstrate secure isolation of resources

within the service provider datacenter.

Hardware and software requirementsThe following are the minimum required components of the test lab:

The product disc or files for Windows Server 2012 R2. The Windows Assessment and Deployment Kit (ADK) 8.1 source files.Windows ADK is available

at theMicrosoft Download Center.To install the Windows ADK on a computer that does not

have Internet access, first download the installer files and copy them to the offline computer.

Then run ADKSetup.exe using either the GUI or the command line.

The product disc or files for Microsoft SQL Server 2012. The product disc or files for Microsoft System Center 2012 R2 Virtual Machine Manager. Four computers that meet the minimum hardware requirements for Windows Server 2012 R2

and that support Windows Server 2012 R2 64-bit virtual machines. The server hardware must

support the amount of RAM required to run the virtual operating systems included in the test

lab.

Important

Run Windows Update on all computers or virtual machines either during the installation or

immediately after installing the operating systems. After running Windows Update, you can isolate

your physical or virtual test lab from your production network.

Note

You must be logged on as a member of the Domain Admins group or a member of the local

Administrators group on each computer to complete the tasks described in this guide.

Steps for Configuring the Hosternet subnetThere are two steps to setting up the Hosternet subnet of the Windows Server 2012 R2 Hyper-V

Network Virtualization with System Center 2012 R2 VMM Test Lab.

1. Configure HNVHOST1.2. Configure HNVHOST2.Step 1: Configure HNVHOST1

HNVHOST1 is a physical server configured as a Windows Server 2012 R2 Hyper-V host, Domain

Controller and DNS Server for the simulated service provider datacenter domain, hnv.adatum.com,
http://go.microsoft.com/fwlink/p/?LinkID=263698http://go.microsoft.com/fwlink/p/?LinkID=263698http://go.microsoft.com/fwlink/p/?LinkID=263698http://go.microsoft.com/fwlink/p/?LinkID=263698



13

connected to a shared physical switch used to simulate a service provider datacenter connection.

HNVHOST1 configuration consists of the following:

Install the operating system Configure TCP/IP Rename the computer Configure HNVHOST1 as a DC and DNS server for hnv.adatum.com Create a user account for User1 Install the Hyper-V server role

Install the operating system on HNVHOST1

To install the operating system on HNVHOST1

1. Start the installation of Windows Server 2012 R2 Datacenter (Server with a GUI).2. Follow the instructions to complete the installation, specifying a strong password for the

local Administrator account. Log on using the local Administrator account.

3. Connect HNVHOST1 to a network that has Internet access and run Windows Update toinstall the latest updates for Windows Server 2012 R2.

4. Connect HNVHOST1 to a shared physical switch to which HNVHOST2 is also connected.This connection will be used to simulate the Hosternet subnet.

Configure TCP/IP properties on HNVHOST1

To configure TCP/IP properties on HNVHOST1

1. In Server Manager, click Local Serverin the console tree. Click the link next toEthernetin the Properties tile.

2.

Rename the Ethernet connection connected to the shared physical switch toHosternet.

3. In the Network Connectionswindow, right-click Hosternet, and then clickProperties.

4. Click Internet Protocol Version 4 (TCP/IPv4), and then click Properties.



14

5. Select Use the following IP address. In IP address, type 192.168.0.1. In Subnetmask, type 255.255.255.0.InPreferred DNS server, type127.0.0.1.

6. Click Advanced, and then click the DNStab.7. In DNS suffix for this connection, type hnv.adatum.com , and then click OK.8. Click OKtwice to close the Hosternet Propertiesdialog box.9. Close the Network Connectionswindow.10.From the Toolsmenu in Server Manager, click Windows PowerShell.11.To disable the Windows Firewall on HNVHOST1, type the following command and

press ENTER.

Set-NetFirewallProfile -Profile Domain,Public,Private -Enabled False

Windows PowerShell equivalent commands

The following Windows PowerShell cmdlet or cmdlets perform the same function as the preceding procedure.

Enter each cmdlet on a single line, even though they may appear word-wrapped across several lines here

because of formatting constraints.

Rename the interface connected to the shared physical switch to Hosternet prior to running the cmdletsbelow.

New-NetIPAddress -InterfaceAlias Hosternet -IPAddress 192.168.0.1 -AddressFamily IPv4 -

PrefixLength 24

Set-DnsClientServerAddress -InterfaceAlias Hosternet -ServerAddresses 192.168.0.1

Set-DnsClient -InterfaceAlias Hosternet -ConnectionSpecificSuffix hnv.adatum.com


Rename the computer to HNVHOST1

To rename the computer to HNVHOST1

1. In Server Manager, click Local Serverin the console tree. Click the link next to Computernamein the Properties tile.

2. In the System Propertiesdialog box, click the Computer Name tab. On the Computer



15

Nametab, click Change.

3. In Computer Name, type HNVHOST1. Click OK.4. When you are prompted that you must restart the computer, click OK.5. On the System Propertiesdialog box, click Close.6. When you are prompted to restart the computer, click Restart Now.7. After the computer restarts, log on with the local administrator account.





Rename-Computer -NewName HNVHOST1

Restart-Computer

Configure HNVHOST1 as a domain controller and DNS server

Next, configure HNVHOST1 as a domain controller and DNS server for the hnv.adatum.com domain.

To configure HNVHOST1 as a domain controller and DNS server

1. Launch Server Manager.

2. On the Dashboardscreen, under Configure this local server, click Add roles and

features.

3. Click Nextthree times to get to the server role selection screen.

4. In the Select Server Rolesdialog, select Active Directory Domain Services. Click Add

Featureswhen prompted, and then click Next.

5. In the Select featuresdialog, click Next.

6. In the Active Directory Domain Servicesdialog, click Next.

7. In the Confirm installation selections dialog, click Install. Wait for the installation to



16

complete.

8. In the Installation Progressdialog, click the Promote this server to a domain controller

link.

Note: If you close the "Installation Progress" dialog before it presents the promotion

link, click the gray Tasksflag in the upper right section of Server Manager. When the

installation is complete you will seethe Promote this server to a Domain Controller

link.

9. In the Deployment Configurationdialog, select Add a new forest. In the Root domain

namefield, type hnv.adatum.com. Click Next.

10. In the Domain Controller Optionsdialog, leave the default values, specify a strong

DSRM password twice, and then click Next four times to accept default settings for DNS,NetBIOS, and directory paths.

11. In the Review Optionsdialog, review your selections and then click Next.

12. In the Prerequisites Checkdialog, allow the validation to complete and verify that no

errors are reported. Since this is the first DNS server deployment in the forest, you can

safely ignore all warnings regarding DNS delegation. Click Installto start the domain

controller promotion. Allow the installation to complete.

13. Allow the domain controller to restart. After the server restarts, logon using the

HNV\Administrator credentials.





Install-WindowsFeature AD-Domain-Services -IncludeManagementTools

Install-ADDSForest -DomainName hnv.adatum.com

Create a user account in Active Directory on HNVHOST1

Next, create a user account in Active Directory that will be used when logging in to HNV domain

member computers.



17

To create a user account in Active Directory

1. From Server Manager, click the Toolsmenu item, and then click Active DirectoryAdministrative Center.

2. In the console tree, click the arrow to expand HNV (local), and then double-click Users.This adds Users as a recent navigation link in the console tree.

3. In the Taskspane, click New, and then click User.4. In the Create User dialog, type User1next to Full nameand type User1next to User

SamAccountName logon: HNV\.

5. In Password, type the password that you want to use for this account, and in Confirmpassword, type the password again.

6. Under Password options, select Other password options, and select Password neverexpires.

7. Scroll down to access the Member ofsection of the Create User dialog, and click Add.Type Domain Admins; Enterprise Admins, and then click OK.

8. Click OKto close the Create User dialog.9. Exit the Active Directory Administrative Center.





Note that the first command results in a prompt to supply the user password.

New-ADUser -SamAccountName User1 -AccountPassword (read-host "Set user password" -

assecurestring) -name "User1" -enabled $true -PasswordNeverExpires $true -ChangePasswordAtLogon $false

Add-ADPrincipalGroupMembership -Identity

"CN=User1,CN=Users,DC=HNV,DC=adatum,DC=com" -MemberOf "CN=Enterprise

Admins,CN=Users,DC=HNV,DC=adatum,DC=com","CN=DomainAdmins,CN=Users,DC=HNV,DC=adatum,DC=com"



18

Install the Hyper-V server role on HNVHOST1

Next, install the Hyper-V role on HNVHOST1, which will act as a host for virtual machines that are

connected to the virtualized Contoso and Fabrikam tenant networks.

To install the Hyper-V server role

1. On the Server Manager Dashboardscreen, under Configure this local server, click Addroles and features.

2. Click Nextthree times to get to the server role selection screen.3. On the Select Server Rolespage, select Hyper-Vand clickAdd Features when

prompted.

4. Click Nextsix times to accept the default settings for features and Hyper-V, and thenclick Install.

5. Verify that the installation was successful, and then click Close.6. Restart the HNVHOST1 server after Hyper-V installation completes. After the computer

restarts, click the Switch User arrow icon, then click Other Userand log on to the HNV

domain with the User1account.





Install-WindowsFeature Hyper-V -IncludeManagementTools

Restart-Computer

Step 2: Configure HNVHOST2

HNVHOST2 is a physical server configured as a Windows Server 2012 R2 Hyper-V host, SQL server, andSystem Center 2012 Virtual Machine Manager, connected to a shared physical switch used to simulate a

service provider datacenter connection (Hosternet). HNVHOST2 configuration consists of the following:

Install the operating system Configure TCP/IP



19

Rename the computer and join the hnv.adatum.com domain Install the Hyper-V server role



1. Start the installation of Windows Server 2012 R2.2. Follow the instructions to complete the installation, specifying a strong password for the



4. While HNVHOST2 is connected to the Internet, install .NET 3.5 by running the followingcommand from an elevated Windows PowerShell prompt:

Install-WindowsFeature -Name NET-Framework-Core

Note: If HNVHOST2 does not have an Internet connection, you can install .NET

framework from the Windows source files by using the following command:

DISM /Online /Enable-Feature /FeatureName:NetFx3 /All /LimitAccess

/Source:E:\sources\sxs

5. Connect HNVHOST2 to a shared physical switch to which HNVHOST1 is also connected.This connection will be used to simulate the Hosternet subnet.



1. In Server Manager, click Local Serverin the console tree. Click the link next to Ethernetin the Properties tile.

2. Rename the network adapter connected to the Hosternet shared physical switch toHosternet.

3. In the Network Connectionswindow, right-click Hosternet, and then click Properties.4. Click Internet Protocol Version 4 (TCP/IPv4), and then click Properties.5. Select Use the following IP address. In IP address, type 192.168.0.2. In Subnet mask,



20

type 255.255.255.0.InPreferred DNS server, type192.168.0.1.

6. Click Advanced, and then click the DNStab.7. In DNS suffix for this connection, type hnv.adatum.com, and then click OK.8. Click OKthree times to close the Hosternet Propertiesdialog box.9. Close the Network Connectionswindow.10.From the Toolsmenu in Server Manager, click Windows PowerShell.11.To disable the Windows Firewall on HNVHOST2, type the following command and press

ENTER.






Rename the interface connected to the shared physical switch to Hosternetprior to running the cmdlets

below.

New-NetIPAddress -InterfaceAlias Hosternet -IPAddress 192.168.0.2 -AddressFamily IPv4 -

PrefixLength 24




Rename the computer to HNVHOST2 and join the hnv.adatum.com domain

To rename the computer to HNVHOST2 and join the hnv.adatum.com domain


2. In the System Propertiesdialog box, click the Computer Name tab. On the ComputerNametab, click Change.

3. In Computer Name, type HNVHOST2. Under Member of, click Domain, and then type



21

hnv.adatum.com.

4. Click OK.5. When you are prompted for a user name and password, type User1and its password,

and then click OK.

6. When you see a dialog box welcoming you to the hnv.adatum.com domain, click OK.7. When you are prompted that you must restart the computer, click OK.8. On the System Propertiesdialog box, click Close.9. When you are prompted to restart the computer, click Restart Now.10.After the computer restarts, click the Switch User arrow icon, then click Other Userand

log on to the HNV domain with the User1account.





Supply the credentials for the User1 domain account when prompted after running the first command.

Add-Computer -NewName HNVHOST2 -DomainName hnv.adatum.com

Restart-Computer



connected to the virtualized Contoso and Fabrikam tenant networks.






22

prompted.


5. Verify that the installation was successful, and then click Close.6. Restart the HNVHOST2 server after Hyper-V installation completes. After the computer

restarts, log on to the CORP domain with the User1account.


The following Windows PowerShell cmdlet or cmdlets perform the same function as the preceding procedure.Enter each cmdlet on a single line, even though they may appear word-wrapped across several lines here



Restart-Computer

Steps for Configuring the Internet SubnetThere are four steps to setting up the Internet subnet of the Windows Server 2012 R2 Hyper-V Network

Virtualization with System Center 2012 R2 VMM Test Lab.

1. Configure HNVHOST4.

2. Configure INET1.

3. Configure HNVHOST3.Step 1: Configure HNVHOST4

HNVHOST4 is a physical server configured as a Windows Server 2012 R2 Hyper-V host connected to a

physical switch used to simulate an Internet connection. Virtual machines running on HNVHOST4 are

used to simulate customer on-premises resources for the Contoso and Fabrikam corporate networks.HNVHOST4 configuration consists of the following:

Install the operating system Configure TCP/IP



23

Rename the computer Install the Hyper-V server role Create a Hyper-V external virtual switch to simulate a connection to the Internet Create two Hyper-V internal virtual switches to simulate the Contoso and Fabrikam corporate

networks

Create virtual machines on HNVHOST4 for INET1, Contoso DC1, Contoso APP1, Contoso EDGE1,Fabrikam DC1, Fabrikam APP1, and Fabrikam EDGE1






4. Connect HNVHOST4 a shared physical switch to which HNVHOST3 is also connected.This connection will be used to simulate the Internet subnet.




2. Rename the adapter that is connected to the shared physical switch to Internet.3. In the Network Connectionswindow, right-click Internet, and then click Properties.4. Click Internet Protocol Version 4 (TCP/IPv4), and then click Properties.5. Select Use the following IP address. In IP address, type 131.107.0.40. In Subnet mask,


6. Click Advanced, and then click the DNStab.



24

7. In DNS suffix for this connection, type isp.example.com, and then click OK.8. Click OKtwice to close the Internet Propertiesdialog box.9. Close the Network Connectionswindow.10.From the Toolsmenu in Server Manager, click Windows PowerShell.11.To configure the firewall to allow ICMPv4 ping packets, type the following commands

and press ENTER after each command.

New-NetFirewallRuleDisplayName Allow ICMPv4-In Protocol ICMPv4

New-NetFirewallRuleDisplayName Allow ICMPv4-Out Protocol ICMPv4

Direction Outbound

12.Close the Windows PowerShell window.





Note: Prior to running the following commands, name the network connection attached to the shared physicalswitch Internet.

New-NetIPAddress -InterfaceAlias Internet -IPAddress 131.107.0.40 -AddressFamily IPv4 -

PrefixLength 24

Set-DnsClientServerAddress -InterfaceAlias Internet -ServerAddresses 131.107.0.1

Set-DnsClient -InterfaceAlias Internet -ConnectionSpecificSuffix isp.example.com

New-NetFirewallRule DisplayName Allow ICMPv4-In Protocol ICMPv4

New-NetFirewallRule DisplayName Allow ICMPv4-Out Protocol ICMPv4 Direction

Outbound

Rename the computer to HNVHOST4

To rename the computer to HNVHOST4


2. In the System Propertiesdialog box, click the Computer Name tab. On the Computer



25

Nametab, click Change.

3. In Computer Name, type HNVHOST4. Click OK.4. When you are prompted that you must restart the computer, click OK.5. On the System Propertiesdialog box, click Close.6. When you are prompted to restart the computer, click Restart Now.7. After the computer restarts, log on with the local administrator account.





Rename-Computer -NewName HNVHOST4

Restart-Computer



connected to the Contoso Corpnet, Fabrikam Corpnet, and Internet subnets.




prompted.


5. Verify that the installation was successful, and then click Close.



26






Restart-Computer

Create virtual switches on HNVHOST4

To create Internet, Contoso Corpnet, and Fabrikam Corpnet virtual switches on HNVHOST4

1. From Server Manager, click the Toolsmenu item, and then click Hyper-V Manager.2. In Hyper-V Manager console, select HNVHOST4, and then click Virtual Switch Manager

in the Actions pane.

3. Verify that Externalis selected, and then click Create Virtual Switch.4. Under Name, type Internet. Under External network, select the adapter connected to

the Internet physical switch. Select the checkbox for Allow management operating

system to share this network adapter. Click Apply.

5. In the Virtual Switch Manager window, click New virtual network switch. Under Whattype of virtual switch do you want to create?, select Private, and then click Create

Virtual Switch.

6. Under Name, type Contoso_Corpnet, and then click Apply.7. In the Virtual Switch Manager window, click New virtual network switch. Under What

type of virtual switch do you want to create?, select Private, and then click Create

Virtual Switch.

8. Under Name, type Fabrikam_Corpnet, and then click Apply.9. Click OKto close Virtual Switch Manager.



27




New-VmSwitch -Name Internet -AllowManagementOS 1 -NetAdapterName Internet

New-VmSwitch -Name Contoso_Corpnet -SwitchType Private

New-VmSwitch -Name Fabrikam_Corpnet -SwitchType Private

Create virtual machines on HNVHOST4

To create Internet, Contoso Corpnet, and Fabrikam Corpnet virtual machines on HNVHOST4

1. In Hyper-V Manager console Actions pane, point to New, and then click VirtualMachine.

2. The New Virtual Machine Wizard opens. Click Next.3. Name the new virtual machine INET1. Click Next.4. Select Generation 1as the virtual machine generation, and then click Next.5. Assign memory to allocate to the new VM, and then click Next.6. On the Configure Networking page select a connection to the Internetvirtual switch.

Click Next.

7. On the Connect Virtual Hard Disk page, select an option to create a new virtual hard diskor specify a path to an existing virtual hard disk for INET1. Click Next.

8. On the Installation Options page, select the appropriate options to access the operatingsystem setup media. Click Next.

9. On the Summary page, click Finish.10.Repeat the previous steps to create additional virtual machines as listed in the following

table:

Virtual Machine Name Network Connections

INET1 One virtual adapter connected to the Internet virtual switch



28

Contoso_DC1 One virtual adapter connected to the Contoso_Corpnet virtual

switch

Contoso_APP1 One virtual adapter connected to the Contoso_Corpnet virtualswitch

Contoso_EDGE1 Two virtual adapters, one connected to the Contoso_Corpnet

virtual switch, one connected to the Internet virtual switch

Fabrikam_DC1 One virtual adapter connected to the Fabrikam_Corpnet

virtual switch

Fabrikam_APP1 One virtual adapter connected to the Fabrikam_Corpnet

virtual switch

Fabrikam_EDGE1 Two virtual adapters, one connected to the Fabrikam_Corpnet

virtual switch, one connected to the Internet virtual switch

Step 2: Configure INET1


2012 VMM test lab can be built using the "Steps for Configuring the Corpnet Subnet"

and "Steps for Configuring the Internet Subnet" sections of theTest Lab Guide:

Windows Server 2012 R2 Base Configurationas its base. If you have already built the

Windows Server 2012 R2 Base Configuration using virtual machines, you can use the

INET1 computer for the Internet subnet in place of the instructions below.

INET1 configuration consists of the following:

Install the operating system Configure TCP/IP Rename the computer Install the Web Server (IIS) and DNS server roles Create DNS records Install DHCP



29

Configure the NCSI web siteInstall the operating system on INET1

To install the operating system on INET1



3. Connect INET1 to a network that has Internet access and run Windows Update to installthe latest updates for Windows Server 2012 R2.

4. Connect the INET1 virtual machine to the Internet virtual switch on HNVHOST4.Configure TCP/IP properties on INET1

To configure TCP/IP properties on INET1


2. In the Network Connectionswindow, right-click Ethernet, and then click Properties.3. Click Internet Protocol Version 4 (TCP/IPv4), and then click Properties.4. Select Use the following IP address. In IP address, type 131.107.0.1. In Subnet mask,


5. Click Advanced, and then click the DNStab.6. In DNS suffix for this connection, type isp.example.com, and then click OK.7. Click OKtwice to close the Ethernet Propertiesdialog box.8. Close the Network Connectionswindow.9. From the Toolsmenu in Server Manager, click Windows PowerShell.10.To configure the firewall to allow ICMPv4 ping packets, type the following commands

and press ENTER after each command.

New-NetFirewallRuleDisplayName Allow ICMPv4-In Protocol ICMPv4



30

New-NetFirewallRuleDisplayName Allow ICMPv4-Out Protocol ICMPv4

Direction Outbound

11.Close the Windows PowerShell window.





Note that the "Ethernet" interface name may be different on your computer. Use ipconfig /allto list out the

interfaces.

New-NetIPAddress -InterfaceAlias Ethernet -IPAddress 131.107.0.1 -AddressFamily IPv4 -

PrefixLength 24

Set-DnsClientServerAddress -InterfaceAlias Ethernet -ServerAddresses 127.0.0.1

Set-DnsClient -InterfaceAlias Ethernet -ConnectionSpecificSuffix isp.example.com

New-NetFirewallRule DisplayName Allow ICMPv4-In Protocol ICMPv4

New-NetFirewallRule DisplayName Allow ICMPv4-Out Protocol ICMPv4 Direction

Outbound

Rename the computer to INET1

To rename the computer to INET1



3. In Computer Name, type INET1. Click OK.4. When you are prompted that you must restart the computer, click OK.5. On the System Propertiesdialog box, click Close.6. When you are prompted to restart the computer, click Restart Now.7. After the computer restarts, log on with the local administrator account.



31




Rename-Computer -NewName INET1

Restart-Computer

Install the DNS Server and Web Server (IIS) server roles on INET1

Next, install role services for INET1, which will act as an Internet web and DNS server for computers that

are connected to the Internet subnet.

To install the IIS and DNS server roles


2. Click Nextthree times to get to the server role selection screen.3. On the Select Server Rolespage, select DNS Serverand clickAdd Features when

prompted.

4. Select Web Server (IIS)and then clickNext.5. Click Nextfour times to accept the default DNS server and web server settings, and then

click Install.

6. Verify that the installations were successful, and then click Close.





Install-WindowsFeature DNS -IncludeManagementTools

Install-WindowsFeature Web-WebServer -IncludeManagementTools



32

Create DNS records on INET1

Next, create DNS records for the INET1 and EDGE1 IPv4 addresses on the Internet subnet and for the

Network Connectivity Status Indicator (NCSI).

To create A records

1. From Server Manager, click the Toolsmenu item, and then click DNS.2. In the console tree of DNS Manager, expand INET1, and click Forward Lookup Zones.3. Right-click Forward Lookup Zones, click New Zone, and then click Next.4. On the Zone Typepage, click Next.5. On the Zone Namepage, type isp.example.com, and then click Next.6. Click Nexttwice to accept defaults for zone file and dynamic update, and then click Finish.7. In the console tree, expand Forward Lookup Zones, right click isp.example.com, and then click

New Host (A or AAAA).

8. In Name, type INET1. In IP address, type 131.107.0.1. Click Add Host.9. Click OK, and then click Done.10. In the console tree, right-click Forward Lookup Zones, click New Zone, and then click Next.11.On the Zone Typepage, click Next.12.On the Zone Namepage, type contoso.com, and then click Next.13.Click Nexttwice to accept defaults for zone file and dynamic update, and then click Finish.14. In the console tree, right click contoso.com, and then click New Host (A or AAAA).15. In Name, type EDGE1. In IP address, type 131.107.0.2.16.Click Add Host. Click OK.17. In the console tree, right-click Forward Lookup Zones, click New Zone, and then click Next.18.On the Zone Typepage, click Next.19.On the Zone Namepage, type msftncsi.com, and then click Next.



33

20.Click Nexttwice to accept defaults for zone file and dynamic update, and then click Finish.21. In the console tree, right click msftncsi.com, and then click New Host (A or AAAA).22. In Name, type www. In IP address, type 131.107.0.1.23.Click Add Host. Click OK.24. In Name, type dns. In IP address, type 131.107.255.255. Click Add Host. Click OK. Click Done.24. Close the DNS Manager console.





Add-DnsServerPrimaryZone -Name isp.example.com -ZoneFile isp.example.com.dns

Add-DnsServerResourceRecordA -ZoneName isp.example.com -Name inet1 -IPv4Address

131.107.0.1

Add-DnsServerPrimaryZone -Name contoso.com -ZoneFile contoso.com.dns

Add-DnsServerResourceRecordA -ZoneName contoso.com -Name edge1 -IPv4Address

131.107.0.2

Add-DnsServerPrimaryZone -Name msftncsi.com -ZoneFile msftncsi.com.dns

Add-DnsServerResourceRecordA -ZoneName msftncsi.com -Name www -IPv4Address131.107.0.1

Add-DnsServerResourceRecordA -ZoneName msftncsi.com -Name dns -IPv4Address

131.107.255.255

Install and configure DHCP on INET1

Next, configure INET1 as a DHCP server so that DHCP clients can automatically configure themselves

when connecting to the Internet subnet.

To install and configure the DHCP server role on INET1

1. On the Server Manager Dashboardscreen, under Configure this local server, click Add rolesand features.

2. Click Nextthree times to get to the server role selection screen.3. In the Select Server Roles dialog, select DHCP Server, click Add Featureswhen prompted, and



34

then click Next.

4. In the Select features dialog, click Next.5. Click Nexton the Introduction screen, and then click Install.6. Allow the installation to complete, and then in the Installation progress window, click the link

for Complete DHCP configuration.

7. In the DHCP Post-Install configuration wizard, click Commit, and then click Close.8. In the Installation progress window, click Close.9. From the Toolsmenu in Server Manager, click DHCP.10. In the DHCP console tree, expand INET1. Right-click IPv4, and click New Scope.11.Click Nextin the New Scope Wizard.12.Type Internetfor scope name, and then click Next.13.Next to Start IP Address, type 131.107.0.100, next to End IP Address, type 131.107.0.150, and

next to Subnet Mask, type 255.255.255.0.

14.Click Nextfour times to accept default settings for exclusions, delay and lease duration.15.On the Router (Default Gateway)dialog, type 131.107.0.1. Click Add, and then click Next.16.On the Domain Name and DNS Serverspage, next to Parent domain, type isp.example.com.

Under IP address, type 131.107.0.1. Click Add, and then click Next.

17.On the WINS Servers page, click Next.18.On the Activate Scope page, click Next, and then click Finish.19.Close the DHCP Manager console.







35

Install-WindowsFeature DHCP -IncludeManagementTools

Add-DhcpServerv4Scope -name "Internet" -StartRange 131.107.0.100 -EndRange

131.107.0.150 -SubnetMask 255.255.255.0

Set-DhcpServerv4OptionValue -DnsDomain isp.example.com -DnsServer 131.107.0.1 -

Router 131.107.0.1

Configure the NCSI web site on INET1

Windows clients attempt to connect to the URL http://www.msftncsi.com/ncsi.txt and resolve the name

dns.msftncsi.com to determine if they have Internet connectivity. In the following procedure, you create

the ncsi.txt file and place it in the WWWROOT directory on INET1.

To configure the NCSI web site on INET1

1. On INET1, launch File Explorer, and then navigate to C:\inetpub\wwwroot.2. In the details pane, right click an empty area, point to New, and then click Text Document.3. Rename the document to ncsi.4. Double-click on ncsi.5. In the Notepadwindow, type Microsoft NCSIand do notpress ENTER to add a new line.6. Click File, and then click Exit. In the Notepaddialog box, click Save.7. Close the Windows Explorer window.


The following PowerShell commands perform the same steps to write the Ncsi.txt file without a new line after

the "Microsoft NCSI" string:

$filename = "C:\inetpub\wwwroot\ncsi.txt"

$text = "Microsoft NCSI"

[System.IO.File]::WriteAllText($fileName, $text)



36

Step 3: Configure HNVHOST3

HNVHOST3 is a physical server configured to host Hyper-V Network Virtualization Gateway virtual

machines, with two network adapters. One adapter is connected to a physical switch used to simulate

an Internet connection, and the second adapter is connected to a physical switch used to simulate aservice provider datacenter connection (Hosternet). HNVHOST3 configuration consists of the following:

Install the operating system Configure network connections Rename the computer and join the hnv.adatum.com domain Install the Hyper-V server role






4. Connect one adapter on HNVHOST3 a shared physical switch to which HNVHOST2 is alsoconnected. This connection will be used to simulate the Hosternet subnet.

5. Connect one adapter on HNVHOST3 a shared physical switch to which HNVHOST4 is alsoconnected. This connection will be used to simulate the Internet subnet.

Configure network connections on HNVHOST3

To configure network connection properties on HNVHOST3

1.In Server Manager, click Local Serverin the console tree. Click the link next to Ethernetin the Properties tile.

2.In Network Connections, right-click the network connection that is connected to theshared physical switch to which HNVHOST4 is also connected, and then click Rename.

3.Type Internet, and then press ENTER.



37

4.In the Network Connectionswindow, right-click Internet, and then click Properties.5.Click Internet Protocol Version 4 (TCP/IPv4), and then click Properties.6. Select Use the following IP address. In IP address, type 131.107.0.30. In Subnet mask,


7.Click Advanced, and then click the DNStab.8.In DNS suffix for this connection, type isp.example.com, and then click OK.9.Click OKtwice to close the Internet Propertiesdialog box.10. In Network Connections, right-click the network connection that is connected to the

shared physical switch to which HNVHOST2 is also connected, and then click Rename.

11.Type Hosternet, and then press ENTER.12. In the Network Connectionswindow, right-click Hosternet, and then click Properties.13.Click Internet Protocol Version 4 (TCP/IPv4), and then click Properties.14.Select Use the following IP address. In IP address, type 192.168.0.3. In Subnet mask,


15.Click Advanced, and then click the DNStab.16. In DNS suffix for this connection, type hnv.adatum.com, and then click OK.17.Click OKthree times to close the Hosternet Propertiesdialog box.18.Close the Network Connectionswindow.19.From the Toolsmenu in Server Manager, click Windows PowerShell.20.To disable the Windows Firewall on HNVHOST3, type the following command and

press ENTER.


21.Type ping 131.107.0.1and press ENTER to verify connectivity to INET1 fromHNVHOST3.

22.Type ping 192.168.0.2and press ENTER to verify connectivity to HNVHOST2 fromHNVHOST3.



38





Ensure that the interfaces have been renamed to Hosternetand Internetprior to running the following

commands.

New-NetIPAddress -InterfaceAlias Internet -IPAddress 131.107.0.30 -AddressFamily IPv4 -

PrefixLength 24

Set-DnsClientServerAddress -InterfaceAlias Internet -ServerAddresses 131.107.0.1

Set-DnsClient -InterfaceAlias Internet -ConnectionSpecificSuffix isp.example.com

New-NetIPAddress -InterfaceAlias Hosternet -IPAddress 192.168.0.3 -AddressFamily IPv4 -PrefixLength 24




Rename the computer to HNVHOST3 and join the hnv.adatum.com domain

To rename the computer to HNVHOST3 and join the hnv.adatum.com domain



3. In Computer Name, type HNVHOST3. Under Member of, click Domain, and then typehnv.adatum.com.

4. Click OK.5. When you are prompted for a user name and password, type User1and its password,

and then click OK.

6. When you see a dialog box welcoming you to the hnv.adatum.com domain, click OK.7. When you are prompted that you must restart the computer, click OK.8. On the System Propertiesdialog box, click Close.



39

9. When you are prompted to restart the computer, click Restart Now.10.After the computer restarts, click the Switch User arrow icon, then click Other Userand

log on to the HNV domain with the User1account.





Add-Computer -NewName HNVHOST3 -DomainName hnv.adatum.com

Restart-Computer


Next, install the Hyper-V role on HNVHOST3, which will act as a host for a gateway virtual machine that

is connected to the Internet for site-to-site routing to the Contoso Corpnet and Fabrikam Corpnet

subnets, and a second gateway virtual machine that provides direct routing to the service provider

network.




prompted.


5. Verify that the installation was successful, and then click Close.6. Restart the HNVHOST3 server after Hyper-V installation completes.



40





Restart-Computer

Steps for Configuring the Contoso Corpnet Subnet

The Contoso Corpnet subnet is used to simulate a customer on-premises network infrastructure. Across-premises VPN connection will be established later in order to access the cloud service provider

network. There are four steps to setting up the Contoso Corpnet subnet on HNVHOST4.

1. Configure DC1.2. Configure APP1.3. Configure EDGE1.4. Test access to resources on APP1.The following sections provide details about how to perform these steps.


2012 VMM test lab can be built using the "Steps for Configuring the Corpnet Subnet"

and "Steps for Configuring the Internet Subnet" sections of theTest Lab Guide:

Windows Server 2012 R2 Base Configurationas its base. If you have already built the

Windows Server 2012 R2 Base Configuration using virtual machines, you can use the

DC1, EDGE1, and APP1 computers for the Contoso Corpnet subnet in place of the

instructions below.

Step 1: Configure DC1DC1 is a virtual machine running on the HNVHOST4 server. DC1 provides the following services:

A domain controller for the corp.contoso.com Active Directory Domain Services (AD DS) domain A DNS server for the corp.contoso.com DNS domain



41

A DHCP server for the Corpnet subnetDC1 configuration consists of the following:

Install the operating system Configure TCP/IP Install Active Directory and DNS Install DHCP Create a user account in Active Directory

Install the operating system on DC1

First, install Windows Server 2012 R2 as a standalone server.

To install the operating system on DC1

1. Start the installation of Windows Server 2012 R2.

2. Follow the instructions to complete the installation, specifying Windows Server 2012 R2

Datacenter (Server with a GUI) and a strong password for the local Administrator account. Log

on using the local Administrator account.

3. Connect DC1 to a network that has Internet access and run Windows Update to install the

latest updates for Windows Server 2012 R2.

4. Connect DC1 to the Contoso_Corpnet virtual switch on HNVHOST4.

Configure TCP/IP properties on DC1

Next, configure the TCP/IP protocol with a static IP address of 10.0.0.1 and the subnet mask of

255.255.255.0.

To configure TCP/IP on DC1

1. In Server Manager, click Local Serverin the console tree. Click the link next to Ethernet.Note

The link may not immediately appear. Wait for the network interfaces to be enumerated.

2. In Network Connections, right-click Ethernet, and then click Properties. Note that the"Ethernet" interface name may be different on your computer.



42

3. Click Internet Protocol Version 4 (TCP/IPv4), and then click Properties.4. Select Use the following IP address. In IP address, type 10.0.0.1. In Subnet mask, type

255.255.255.0. In Default gateway, type 10.0.0.2. Select Use the following DNS server

addresses. In Preferred DNS server, type 127.0.0.1.

5. Click OKand then close the Ethe

Windows Server 2012 R2 Hyper-V Network Virtualization With System Center 2012 R2 VMM Test Lab_RTM

Documents