TestOut Server Pro 2016: Networking Labs

he CampusDHCP_1 server is currently the only DHCP server for clients on the 10.10.10.0/24 subnet. between 10.10.10.1 and 10.10.10.254 with an exclusion for static addresses for servers from 10.10.10.1 to 10.10.10.29. To provide DHCP fault tolerance for this subnet, you plan to configure DHCP Failover requests between subnets. In this lab, your task is to complete the following: Explore the DHCP configuration on CampusDHCP_1. Which scopes, exclusions, and options are currently configured? Explore the DHCP configuration on CampusDHCP_2. Which scopes, exclusions, and options are configured? On CampusDHCP_1, configure failover of the Campus1 scope with the CampusDHCP_2 server. Failover mode: Load balanced Load balance percentage for the local server: 75% Load balance percentage for the partner server: 25% Shared secret: HelpMyDHCP123. Which scopes, exclusions, and options have been added to the CampusDHCP_2 server?

1. Explore the DHCP configuration for CampusDHCP_1 as follows: From Hyper-V Manager, select CAMPUSSERVER1. Under Virtual Machines, right-click CampusDCHP_1 and select Connect. In Server Manager, select Tools > DHCP. In the left pane, expand CampusDHCP_1.PartnerNet.com. Expand IPv4. Expand Scope [10.10.10.1] Campus1. Select Address Pool. There is currently an address range of 10.10.10.1 to 10.10.10.254 and an exclusion for 10.10.10.1 to 10.10.10.29 to allow for static server addresses. Select Scope Options. There are currently options configured for 003 Router, 006 DNS Servers, and 015 DNS Domain Name. 2. Explore the DHCP configuration for CampusDHCP_2 as follows: From the top navigation tabs, select the location icon. Under Campus2, select CampusServer2. In Hyper-V Manager, select CAMPUSSERVER2. Right-click CampusDCHP_2 and select Connect. From Server Manager, select Tools > DHCP. From the left pane, expand CampusDHCP_2.PartnerNet.com. Expand IPv4. Expand Scope [10.10.20.1] Campus2. Select Address Pool. There is currently an address range of 10.10.20.1 to 10.10.20.254 and an exclusion for 10.10.20.1 to 10.10.20.29 to allow for static server addresses. Select Scope Options. There are currently options configured for 003 Router, 006 DNS Servers, and 015 DNS Domain Name. PART 2 BELOW

part 3

Configure a RADIUS client as follows: From the top navigation tabs, select Sites. Select the server to be configured as a RADIUS Client. In Server Manager, select Tools > Routing and Remote Access. Right-click the server and select Properties. Select the Security tab. In the Authentication provider drop-down list, select RADIUS Authentication. Select Configure. Select Add. In the Server name field, enter CorpNPS. Select Change. In the New secret field, enter J51nj3T% as the secret. This password must be identical to the one that was entered on the NPS server. In the Confirm new secret field, re-enter the shared secret; then select OK. Click OK to add the RADIUS server. Click OK to close the RADIUS Authentication dialog. In the Accounting provider drop-down list, select RADIUS Accounting. Select Configure. Select Add. In the Server name field, enter CorpNPS. Select Change. In the New secret field, enter J51nj3T% as the secret. This password must be identical to the one that was entered on the NPS server. In the Confirm new secret field, re-enter the shared secret; then select OK to add the RADIUS server. Click OK to close the RADIUS Accounting dialog. Click OK to close server properties. Repeat step 4 to add additional RADIUS Clients.

You work as the IT Administrator for a small corporate network. You recently installed Windows Server 2016 on CorpRTR in order to use the server as a router between your test network and the production network. The system has two network adapters, one connected to each network. You have assigned static addresses to the network adapters as shown in the Exhibit. The router can communicate with hosts on either network, but hosts cannot communicate outside their own networks. To correct the problem, you need to enable routing on the server. In this lab, your task is to enable LAN routing on the server using the Configure and Enable Routing and Remote Access wizard. You do not need to configure static routes or a routing protocol on the server at this time.

From Server Manager, select Tools > Routing and Remote Access. From the left pane, right-click CorpRTR (local) and select Configure and Enable Routing and Remote Access. From the wizard's Welcome window, click Next. Select Secure connection between two private networks. Click Next. Select No to configure the router for LAN routing only. Click Next. Click Finish. Click OK.

You are experiencing network throughput issues on your lab router server. It appears that one of the processors is pegged, but the remaining processors have plenty of cycles available. Set the maximum number of RSS queues to the same number as the number of processors (8). In this lab, your task is to complete the following: Enable RSS on the Network 2 adapter with the following parameters: Receive Side Scaling: Enabled Max Number of RSS Processors: 8 Maximum Number of RSS Queues: 8 Receive Buffer Size: 4MB RSS Base Processor Number: 0 RSS Profile: Closest Processor Enable RSS on the TestLAN adapter with the following parameters: Receive Side Scaling: Enabled Max Number of RSS Processors: 8 Maximum Number of RSS Queues: 8 Receive Buffer Size: 4MB RSS Base Processor Number: 8 RSS Profile: Closest Processor

In Server Manager, select Local Server. Select the link for one of the network cards. Right-click a network connection and select Properties. Select Configure. Select the Advanced tab. Under Property, select the property identified in the scenario. Under Values, select the value identified in the scenario. Click OK. Select OK to close the Network2 Properties dialog. Repeat steps 3-7 to configure the other network connection.

You work as the IT administrator for a small corporate network. The server CorpDC is your domain controller and DNS server. This server hosts the CorpNet.com zone. For name resolution requests in other zones, you want CorpDC to forward requests to name servers at the ISP. In this lab, your task is to configure the DNS service on CorpDC using the following settings: Forward name resolution requests outside of the CorpNet.com domain to the following ISP DNS servers: 163.128.80.93 163.128.78.93 Use root hints for requests if the ISP DNS servers are unavailable.

Complete this lab as follows: 1. Connect to the CorpDC virtual machine as follows: From Hyper-V Manager, select CORPSERVER. From the Virtual Machines pane, right-click CorpDC and select Connect. 2. Create the forward name resolution requests as follows: From Server Manager, select Tools > DNS. From the left pane, right-click CORPDC and select Properties. Select the Forwarders tab. Click Edit. With Click here to add an IP Address or DNS Name highlighted, add an IP address to the list. Click in a blank area below the IP addresses shown and verify that a server is located. Click Click here to add an IP Address or DNS Name and enter the additional IP address. Click in a blank area below IP the addresses shown and verify that a server is located. Click OK to exit the Edit options. Ensure that Use root hints if no forwarders are available is marked. Click OK to exit the Properties window.

You are the IT administrator for a small corporate network. The company has obtained the registered globally unique IPv6 /48 network address 2620:14F0:45EA. You need to configure your server with this address so you can begin testing IPv6 in your internal network. This is your first network, so you will use a subnet address of 0001. Your network router is not configured for IPv6 yet, so you must manually configure the address for now. To simplify the configuration, use the server's IPv4 address to create the interface ID. In this lab, your task is to configure the external vEthernet network adapter with the following IPv6 address: Prefix: 2620:14F0:45EA:0001 Interface ID: 192:168:0:10 Subnet prefix length: 64 Use ipconfig to verify the information.

In the notification area, right-click the Network icon and select Open Network and Sharing Center. On the left, select Change adapter settings. Right-click the vEthernet (External) adapter and select Properties. Select Internet Protocol Version 6 (TCP/IPv6). Select Properties. Select Use the following IPv6 address. In the IPv6 address field, enter 2620:14F0:45EA:0001:192:168:0:10 as the IPv6 address. In the Subnet prefix length field, enter 64. Click OK. Click Close. In the Search the web and Windows field, enter cmd. Under Best match, right-click Command Prompt and select Run as Administrator. At the command prompt, type ipconfig /all and press Enter to view the IPv6 address.

You are a network technician for a small corporate network. The network is connected to the internet and uses DHCP for address assignment. Employees in Office 1 and the Executive Office have reported problems with their network connections. The IP address for the ISP/internet is 65.86.1.1. In this lab, your task is to explore, diagnose, and fix the reported TCP/IP configuration problems using the following troubleshooting tools: Command line utilities: ping (ping IP address or host name) ipconfig (ipconfig /all; ipconfig /renew) tracert (tracert IP address or host name) The Network and Sharing Center Network & Internet settings The DHCP server console in the Windows 2016 operating system The network diagram and schematic as found in Exhibits Use the following guidelines to explore, diagnose, and fix any TCP/IP configuration problems.

long one with the 20 questions

You work as the IT administrator for a small corporate network. A partner company has asked you to help configure their DNS server. PartnerServer is a Windows Server 2016 server that holds the primary copy of the PartnerNet.org domain. The server is in a demilitarized zone (DMZ) and provides name resolution for domain's internet hosts. The partner company wants to prevent PartnerServer from performing name resolution requests for domains other than the PartnerNet.org domain. In other words, they do not want internet hosts to be able to obtain name resolution from PartnerServer for domains outside the company. In this lab, your task is to perform the following: Create a root zone on PartnerServer. Create a primary forward lookup zone named . (a dot to represent the root zone). Do not allow dynamic updates. Verify that root hints are no longer configured on the server.

In Server Manager, select Tools > DNS. Expand PARTNERSERVER. Right-click Forward Lookup Zones and select New Zone. Click Next. Make sure Primary zone is selected and then click Next. Type . (a dot to represent the root zone) for the zone name and then select Next. Make sure Create a new file with this file name is selected and click Next. Make sure Do not allow dynamic updates is selected and then select Next. Click Finish to complete the New Zone wizard. Right-click the DNS Server and select Properties. Select the Root Hints tab. Verify that there are no root hints and then click OK.

You are the IT administrator for a growing corporate network. You need to configure DNS settings on CorpDC. In this lab, your task is to configure the server as follows: Delegate permission to create zones to the Sub Admins group. Enable BIND secondaries so the server can respond to a group of Linux clients. Enable netmask ordering to make sure users get a response from the closest server. Secure the DNS cache against pollution. Enable event logging for errors and warnings.

In Server Manager, select Tools > DNS. Right-click CORPDC and select Properties. Select the Security tab. Select Add. In the Enter the object names to select field, enter Sub Admins. Select Check Names. Click OK. In the Allow column, select Create all child objects. Select the Advanced tab. Under Server options, select BIND secondaries. Select Enable netmask ordering. Make sure Secure cache against pollution is selected. Select the Event Logging tab. Select Errors and warnings. Click OK.

You have been trying to track down a problem related to dynamic DNS in your environment. You need more information about what is happening with dynamic updates. To troubleshoot the problem, you would like to enable DNS debug logging. In this lab, your task is to complete the following: Enable DNS debug logging on CampusDC2 and configure logging as follows: Log outgoing UDP and TCP packets. Log updates and responses. To prevent the file from getting too large, don't log any other options. Send the debug information to C:\DNSDebug.log and configure a maximum log size of 200000000 bytes

In Server Manger, select Tools > DNS. In the left pane, right-click CAMPUSDC2 and select Properties. Select the Debug Logging tab. Select Log packets for debugging. Under Packet direction, make sure Outgoing is selected. Unmark Incoming. Under Transport protocol, make sure UDP is selected. Make sure TCP is selected. Under Packet contents, unmark Queries/Transfers. Make sure Updates is selected. Make sure Notifications is not selected. Under Packet type, unmark Request. Make sure Response is selected. In the File path and name field, enter C:\DNSDebug.log as the path and file name. In the Maximum size field, enter 200000000 (8 zeros). Click OK.

You work as the IT administrator for a small corporate network. The receptionist in your office has a laptop that runs Windows 10. She took it home and configured a static connection to her home network. Now she can't connect to the office network, which uses a DHCP server for IP address configuration. You need to configure the laptop to work on both networks. In this lab, your task is to configure the Internet Protocol Version 4 (TCP/IPv4) properties with the following settings: On the General tab, set the following parameters: Obtain an IP address automatically Obtain DNS server address automatically On the Alternate Configuration tab, set the following parameters: IP Address: 172.16.0.12 Subnet Mask: 255.255.0.0 Default Gateway: 172.16.255.254 Preferred DNS Server: 198.60.22.2

In the notification area, right-click the Network icon and select Open Network & Internet settings. Select Change adapter options. Right-click Wi-Fi and select Properties. Select Internet Protocol Version 4 (TCP/IPv4). Select Properties. Select Obtain an IP address automatically. Select Obtain DNS server address automatically. Select the Alternate Configuration tab to define an alternate configuration for TCP/IP addressing. Select User configured to configure alternate IP settings. Enter the IP address. Enter the subnet mask. Enter the default gateway. Enter the preferred DNS server. Click OK. Click Close. Select the Network icon in the notification area to view the currently connected network.

You are a network technician for a small corporate network. The network is connected to the internet and uses DHCP for address assignment. The owner of the company in the Executive Office and a temporary employee in IT Administrator office both report that their workstations can communicate with some computers on the network, but not on the internet. The IP address for the ISP and the internet is 65.86.1.1. In this lab, your task is to diagnose and fix the problem. Use the following troubleshooting tools: Command line utilities:ping(ping IP address or host name)ipconfig(ipconfig /all; ipconfig /renew)tracert(tracert IP address or host name) Network and Sharing Center Network & Internet settings The DHCP server console in the Windows Server 2016 operating system The network diagram and schematic found in Exhibits

1. Under Executive Office, select Exec. In the Search field on the taskbar, enter cmd. Under Best match, right-click Command Prompt and select Run as Administrator. At the command prompt, type ping itadmin and press Enter. Notice that ITAdmin is translated to 169.254.201.12, and the ping is returned. The IP address for ITAdmin is in the APIPA range (169.254.0.1 to 169.254.255.254). Since Exec can communicate with ITAdmin, it is likely that Exec is has been assigned an APIPA IP address also. Type ping corpserver and press Enter. The request times out. Type ping 65.86.1.1 and press Enter. The request times out. There is probably no default gateway configured so that the workstation can send traffic to another network. Type ipconfig /all and press Enter. Notice that DHCP is enabled, but there is no default gateway address or DHCP Server entry. Notice that the Autoconfiguration IPv4 Address is 169.254.201.10. This confirms that Exec is using an APIPA IP address. It also indicates that there is a problem getting IP configurations from a DHCP server. 2. From the top navigation tabs, select Floor 1 Overview. Under IT Administration, select ITAdmin. In the Search field on the taskbar, enter cmd. Under Best match, right-click Command Prompt and select Run as Administrator. At the command prompt, type ping exec and press Enter. Notice that Exec is translated to 169.254.201.10, and the ping is returned. Type ping corpserver and press Enter. The request times out. Type ping 65.86.1.1 and press Enter. The request times out. Type ipconfig /all and press Enter. Notice that DHCP is enabled, but there is no default gateway address or DHCP Server entry. Notice that the Autoconfiguration IPv4 Address is 169.254.201.12. This is the same problem occurring with the Exec workstation. part 2 below

You are the IT administrator for a small corporate network. You need to simplify file access for various departments using the Distributed File System (DFS). Your implementation should be configured as follows: The CorpDC2 server will host a domain namespace and several replicated folders. The server will replicate with other servers running DFS. In this lab, your task is to complete the following: Add DFS Namespace role services. Add DFS Replication role services. Create a namespace using the following parameters: Use the CorpDC2 server. Use the name SharedFiles. Use domain-based namespace. Configure the namespace to use access-based enumeration. Create folders with targets as follows: Folder Name Target Accounting \\CorpFiles\Accounting Marketing \\CorpFiles16\Marketing Sales \\CorpFiles16\Sales

1. Add DFS role services as follows: In Hyper-V Manager, select CORPSERVER. Maximize the window to view all virtual machines. Right-click CorpDC2 and select Connect. In Server Manager, select Manage > Add Roles and Features. Click Next to begin the Add Roles and Features Wizard. Make sure Role-based or feature-based installation is selected and then click Next. Make sure Select a server from the server pool is selected. Under Server Pool, make sure CorpDC2.CorpNet.com is selected and then click Next. Expand File and Storage Services. Expand File and iSCSI Services. Select DFS Namespaces. Select Add Features to include management tools. Select DFS Replication and then select Next. Click Next. Click Install. After the role services install, select Close. 2. Create a domain-based DFS namespace as follows: From Server Manager, select Tools > DFS Management. Right-click Namespaces and select New Namespace. In the Server field, enter CorpDC2 and then click Next. In the Name field, enter SharedFiles and then click Next. Make sure Domain-based namespace is selected. Select Enable Windows Server 2008 mode to allow access-based enumeration. Click Next. Click Create. Click Close. 3. Add folders as follows: Right-click \\CorpNet.com\SharedFiles and select New Folder. In the Name field, enter the folder name. Select Add. Enter the path to the target folder. Select OK. Click OK. Repeat steps 8-11 to add additional folders.

You installed the DHCP service on CorpDCHP. You configured two scopes. One is for your original building on 192.168.0, and one is for a new building connected to your network on 192.168.10. Each building is shown in the building diagram. Clients on Subnet2 are receiving IP addresses in the range of 169.254.0.0/16. You realize that DHCP messages are not being forwarded through the router. In this lab, your task is to complete the following: Use Routing and Remote Access to configure CorpServer2 as a DHCP relay agent as follows: Add the DHCP relay agent routing protocol. Add the Ethernet adapter as a DHCP relay agent interface and set the boot threshold to 0. Configure the DHCP relay agent properties to identify 192.168.0.14 as the DHCP server. Renew the TCP/IP information on Exec2 (the client machine in Bldg B) and verify that it has a network connection.

1. Add the DHCP relay agent protocol as follows: From Server Manager, select Tools > Routing and Remote Access. From the left pane, expand IPv4. Right-click General and select New Routing Protocol. Select DHCP Relay Agent. Click OK. 2. Add and configure a relay agent interface as follows: From the left pane, right-click DHCP Relay Agent and select New Interface. Select Ethernet. Click OK. Make sure Relay DHCP packets is selected. In the Boot threshold field, enter 0. Click OK. 3. Identify the DHCP server as follows: From the left pane, right-click DHCP Relay Agent and select Properties. In the Server address field, enter 192.168.0.14. Select Add. Click OK. 4. Renew the TCP/IP address as follows: From the location tabs at the top, select Building B. Under Building B, select Inside. Under Manager Office, select Exec2. In the Search the web and Windows field, enter command and press Enter. In the command prompt, type ipconfig /renew and press Enter. The computer should receive an address on the 192.168.10 network. In the navigation area, select the Network icon to view the connection status and verify that CorpNet.com is connected.

You work as the IT administrator for a small corporate network. Your Windows Server 2012 router named CorpRTR provides a measure of isolation for your test network. In this lab, your task is to complete the following: Install the Network Address Translation (NAT) IP routing protocol. Identify Network2 as the public interface and enable NAT. Configure the Network2 interface to allow access to an internal secure web server on 10.0.10.10. Configure the NAT router to act as a DHCP server:Dynamically configure client computers using an IP address on the 10.0.10.0 subnet and the subnet mask of 255.255.255.0.Configure an exclusion for the internal web server on 10.0.10.10. Configure the NAT router to act as a DNS proxy. Do not configure the router to connect automatically to the internet when a DNS name needs to be resolved. Configure TestLAN as the private interface.

1. Add the Network Address Translation (NAT) IP Routing Protocol From Server Manager, select Tools > Routing and Remote Access. Expand IPv4. Right-click General and select New Routing Protocol. Select NAT. Click OK. 2. Identify the Public and Private NAT Interfaces Right-click NAT and select New Interface. Select Network2. Select OK. Select Public interface connected to the Internet. Select Enable NAT on this interface. Select the Services and Ports tab. Select Secure Web Server (HTTPS). In the Private address field, enter 10.0.10.10. Click OK. Click OK to close the interface properties dialog. Right-click NAT and select New Interface. Select TestLAN and then click OK. Make sure Private interface connected to private network is selected. Click OK. 3. Configure the NAT Router Right-click NAT and select Properties. Select the Address Assignment tab. Select Automatically assign IP addresses by using the DHCP allocator. In the IP address field, enter 10.0.10.0. Make sure that 255.255.255.0 appears on the Mask field. Select Exclude to configure an address exclusion. Select Add. Enter 10.0.10.10 to excluded it. Click OK. Click OK to close the Exclude Reserved Address window. Select the Name Resolution tab. Select Clients using Domain Name System (DNS). Click OK.

The CorpRTR server is connected to the networks as shown in the Exhibit. Routing has been enabled on the server. Your test network now includes two additional subnets, 10.0.10.0/24 and 10.0.20.0/24. In this lab, your task is to complete the following: Use the Routing and Remote Access console to configure two new static routes on the CorpRTR server, making the two additional networks accessible. Configure network 10.0.10.0 with a metric of 2. Configure network 10.0.20.0 with a metric of 3.

From Server Manager, select Tools > Routing and Remote Access. From the left pane, expand CorpRTR > IPv4. Right-click Static Routes and select New Static Route. From the Interface drop-down, select TestLAN. For the selected destination, enter: Destination address Subnet mask: 255.255.255.0 Gateway: 10.0.0.254 Metric Click OK. Repeat steps 3 - 5 to add the additional route.

Due to the success of your remote access solution, you now have several remote access servers on your network. To centralize administration of network policies, you need to configure the CorpNPS server as a RADIUS server. In this lab, your task is to complete the following: Add the necessary server role and role service(s) to allow CorpNPS to be a RADIUS server. This server will not respond to remote access client requests. Do not add any unnecessary role services. Identify the following servers in NPS as RADIUS clients: Server/Friendly name IP address CorpVPN1 192.168.0.20 BranchVPN1 192.168.20.20 Shared secret: J51nj3T% Vendor: RADIUS standard Configure a network policy to allow members of the Sales team to connect using the following settings:

1. Add the Network Policy and Access Services Role as follows: In Server Manager, select Manage > Add Roles and Features. Click Next to begin the Add Roles and Features Wizard. Make sure Role-based or feature-based installation is selected and then click Next. Make sure Select a server from a server pool is selected. Make sure CorpNPS.CorpNet.com is selected; then click Next. Select the Network Policy and Access Services role. Select Add Features to include management tools and then click Next. Click Next. Click Next. Make sure Network Policy Server is selected; then click Next. Select Install. After the installation completes, click Close. 2. Configure clients on the RADIUS server as follows: From Server Manager, select Tools > Network Policy Server. Expand RADIUS Clients and Servers. Right-click RADIUS Clients and select New. Enter the Friendly name. Enter the Address (IP or DNS). In the Shared secret field, enter J51nj3T% as the shared secret. In the Confirm shared secret field, re-enter the shared secret. Select the Advanced tab. In the Vendor name field, Make sure Radius Standard is selected. Click OK. Repeat 2c-2j for additional Radius clients. Part 2 below

CampusDHCP_3 is currently the only DHCP server for clients on the 10.10.30.0/24 subnet. It has a scope that distributes addresses between 10.10.30.1 and 10.10.30.254 with an exclusion for static addresses for servers from 10.10.30.1 to 10.10.30.29. To provide DHCP fault tolerance for this subnet, you want to configure DHCP failover for the scope with the CampusDHCP_2 server (located on subnet 10.10.20.0/24 in Campus 2). Routers have been configured to pass DHCP requests between subnets. In this lab, your task is to complete the following: On CampusDHCP_3, configure failover of the Campus3 scope with the CampusDHCP_2 server. Failover mode: Hot Standby Role of Partner Server: Standby Addresses reserved for the standby server: 10% Shared Secret: HelpMyDHCP456 Which scopes, exclusions, and options have been added to the CampusDHCP_2 server?

1. Configure DHCP failover as follows: In Hyper-V Manager, select CAMPUSSERVER3. Under Virtual Machines, right-click CampusDCHP_3 and select Connect. In Server Manager, select Tools > DHCP. In the left pane, expand CampusDHCP_3. Expand IPv4. Right-click Scope [10.10.30.1] Campus3 and select Configure Failover. Click Next to accept the default to configure all scopes. Select Add Server. Select This authorized DHCP server. Select CampusDHCP_2. Press Ctrl and select CampusDHCP_3. Click OK. Click Next. From the Mode drop-down list, select Hot Standby. In the Role of Partner Server field, make sure Standby is selected. In the Addresses reserved for standby server field, enter 10%. In the Shared Secret field, enter HelpMyDHCP456 as the shared secret. Click Next. Select Finish. Click Close. 2. Explore the new scope as follows: From the top navigation tabs, select the navigation icon. Under Campus2, select CampusServer2. In Hyper-V Manager, select CAMPUSSERVER2. Maximize the window for easier viewing. From the left pane, expand CampusDHCP_2.PartnerNet.com. Expand IPv4. Notice the new copy of the Campus3 scope on this server. In the left pane, expand Scope [10.10.30.1] Campus3. Select Address Pool. The address range of 10.10.30.1 to 10.10.30.254 has been duplicated. From the left pane, select Scope Options. Scope options have been duplicated.

You have opened a new branch office. The branch office is connected to the main offices with a dedicated T1 line. The branch office also has a connection to the internet. You want to configure DNS services in the branch office to enable hosts on the private network so you can connect to both hosts in the CorpNet.com domain and on the internet. You've configured the BranchDC1 server as a caching-only DNS server. In this lab, your task is to configure DNS on BRANCHDC1 as follows: Configure the server with a conditional forward for the CorpNet.com domain to BRANCHDC1 using 192.168.0.11. Configure the server with a server-level standard forward for all other requests to the ISP's DNS servers at the ISP using 163.128.78.93 and 163.128.80.93.

1. Configure a conditional forward as follows: Select Start. Select Administrative Tools. Select DNS. Expand BRANCHDC1. Right-click Conditional Forwarders and select New Conditional Forwarder. In the DNS domain field, enter CorpNet.com. Select Click here to add an IP Address or DNS Name. Enter 192.168.0.11. Click away from the IP address; then click OK. 2. Configure a standard forward as follows: Right-click BRANCHDC1 and select Properties. Select the Forwarders tab. Select Edit. Select Click here to add an IP Address or DNS Name. Enter 163.128.78.93. Click away from the IP address; then click OK. Select Click here to add an IP Address or DNS Name. Enter 163.128.80.93. Click away from the IP address; then click OK. Unmark Use root hints if no forwarders are available to disable root hints. Click OK to apply the changes.

You are assisting the IT administrator for PartnerNet.com. The PartnerNet.com main campus has experienced a lot of growth. The DHCP scope, which provides addresses to the campus, is frequently unable to assign IP addresses because of the high demand from clients. You need to configure an additional TCP/IP scope for the site and then combine it with the existing scope to create a superscope. Switches and routers in the environment have already been configured for the additional address range. In this lab, your task is to complete the following: Configure and activate an IPv4 scope: Name: Campus1b Address range: 10.10.11.1 to 10.10.11.254 Subnet mask: 255.255.255.0 (24-bit length) Lease duration: 15 days Configure a new superscope: Name: Campus1-Super Scopes: Campus1 and Campus1b

1. Configure and activate a scope as follows: In Hyper-V Manager, select CAMPUSSERVER1. Under Virtual Machines, right-click CampusDCHP_1 and select Connect. In Server Manager, select Tools > DHCP. In the left pane, expand CampusDHCP_1.PartnerNet.com. Right-click IPv4 and select New Scope. Click Next to start the New Scope wizard. In the Name field, enter Campus1b and click Next. In the Start IP address field, enter 10.10.11.1. In the End IP address field, enter 10.10.11.254. In the Subnet mask, enter 255.255.255.0. Click Next. Click Next to ignore any exclusions and delays. Under Days, enter 15 as the lease duration. Click Next. Select No, I will configure these options later to postpone configuring other DHCP options and click Next. Click Finish to close the wizard and create the scope. Right-click Scope [10.10.11.1] Campus1b and select Activate. 2. Configure a superscope as follows: In the left pane, right-click IPv4 and select New Superscope. Click Next to start the New Superscope wizard. In the Name field, enter Campus1-Super and click Next. Select Campus1. Press Shift and select Campus1b. Click Next. Click Finish to close the wizard and create the Superscope.

Your partner company is increasing security as they prepare to launch a web server. They want to implement DNSSEC so users of the partner website have a high degree of confidence that they are communicating with the host they expect to communicate with, PartnerNet.com. In this lab, your task is to use DNSSEC to sign the PartnerNet.com zone as follows: Make CampusDC1 the Key Master. Add a Key Signing Key with the following non-default parameters: Key length (Bits): 1024 Rollover frequency (days): 730 Add a Zone Signing Key with the following non-default parameters: Key length (Bits): 1024 Rollover frequency (days): 730 Use NSEC3 to generate and use a random salt length of 10. Enable the distribution of trust anchors. Configure Signing and Polling parameters as follows: DS record TTL (seconds): 4800 DNSKEY record TTL (seconds): 4800 Refresh the zone to make sure the records have been signed.

1. Configure the Key Master as follows: In Server Manager, select Tools > DNS. Expand CampusDC1. Expand Forward Lookup Zones. Maximize the window for easier viewing. Right-click PartnerNet.com and select DNSSEC > Sign the Zone. Click Next. Make sure Customize zone signing parameters is selected and click Next. Make sure The DNS server CampusDC1 is the Key Master is selected and click Next. Click Next. 2. Configure the Key Signing Key as follows: In the Key Signing Key window, select Add. Under Key Properties, select 1024 from the Key length drop-down list. In the Rollover frequency field, enter 730. Click OK. Click Next. Select Next. 3. Configure the Zone Signing Key as follows: In the Zone Signing Key window, select Add. Under Key Properties, select 1024 from the Key length drop-down list. In the Rollover frequency field, enter 730. Click OK. Click Next. 4. Use NSEC3 to generate and use a random salt of length as follows: Select Generate and use a random salt of length. In the Generate and use a random salt of length field, enter 10. Click Next. 5. In the Trust Anchors windows, select Enable the distribution of trust anchors for this zone and click Next. 6. Configure Signing and Polling parameters as follows: In the DS record TTL field, enter 4800. In the DNSKEY record TTL field, enter 4800. Click Next. 7. In the DNS Security Extensions window, click Next. Click Finish. 8. Right-click PartnerNet.com and select Refresh to view the signed zone records.

You work as the IT administrator for a small corporate network. You want to let users connect to the branch office LAN through the internet. You need to configure the BranchVPN2 server as a Virtual Private Network (VPN) remote access server. In this lab, your task is to complete the following: Configure the BranchVPN2 server to accept VPN remote access connections. Set the internet connection for the VPN server to Public. Configure the VPN server to assign addresses to clients in the range of 192.168.200.200 to 192.168.200.250. Use Routing and Remote Access for authentication. Configure the VPN server to accept only 15 VPN connections that use the SSTP port. Disable remote access for all other port types (L2TP, PPTP, and IKEv2).

1. Configure the VPN server as follows: From Server Manager, select Tools > Routing and Remote Access. From the left pane, right-click BranchVPN2 and select Configure and Enable Routing and Remote Access. In the Wizard, select Next. Make sure Remote access (dial-up or VPN) is selected and then click Next. Select VPN and then click Next. Under Network interfaces, select Public and then click Next. Select From a specified range of addresses and then click Next. Select New to enter the range of addresses. In the Start IP address field, enter 192.168.200.200. In the End IP address field, enter 192.168.200.250. The number of addresses will be 51. Click OK. Click Next. Make sure No, use Routing and Remote Access to authenticate connection requests is selected is selected and then click Next. Select Finish to complete the Routing and Remote Access Server Setup wizard. Click OK to acknowledge the DHCP Relay Agent message. Appropriate VPN ports will be automatically created and enabled to accept remote access connections. 2. Configure the VPN ports as follows: In the Routing and Remote Access dialog, expand BranchVPN2. Right-click Ports and select Properties. Select WAN Miniport (SSTP). Select Configure. In the Maximum ports field, enter 15 and click OK. Click Yes to confirm the reduction of the number of ports on this device. Select a port type. Select Configure. Clear all options to disable remote access for all other port types. Click OK. Repeat step 2g-2j to disable access for the remaining port types. Click OK.

You work as the IT administrator for a small corporate network. The marketing department wants to create an intranet site that is only accessible from the private network. You have selected mrktg.private as the domain name that will hold all records for the zone. Because security is important, you need to make sure that only the computer that created the DNS record can update the record. You also need to create an Active-Directory-integrated zone so you can store the zone data in Active Directory. You can only create Active-Directory-integrated zones on DNS servers that are domain controllers. In this lab, your task is to complete the following: Create the mrktg.private zone on the CorpDC DNS server. Configure the mrktg.private zone as a Primary zone. Configure the mrktg.private zone as an Active-Directory-integrated zone. Replicate data to all DNS servers in the forest. Allow only secure dynamic updates.

1. Connect to the CorpDC virtual machine as follows: From Hyper-V Manager, select CORPSERVER. From the Virtual Machines pane, right-click CorpDC and select Connect. 2. Create zones as follows: In Server Manager, select Tools > DNS. Expand CORPDC. Right-click Forward Lookup Zones and select New Zone. In the New Zone wizard, click Next. Make sure Primary zone is selected as the zone type. Make sure Store the zone in Active Directory is selected and then click Next. Select how DNS data is replicated throughout your network. Click Next. Enter the zone name and then click Next. Make sure Allow only secure dynamic updates is selected and then click Next. Click Finish.

The sales department wants to create an intranet for all sales employees. Internet Information Services (IIS) is installed on CorpWeb and will be used to host the intranet site. Employees need the ability to access the web server using any of the following URLs: http://sales.private http://intranet.sales.private http://www.sales.private You created the sales.private zone on the CorpDC server. Now you need to allow clients to connect to the web server by creating the following records in the zone: Create an ALIAS (CNAME) record leaving the name blank. (This allows users to connect to the server using the sales.private URL.) Create an ALIAS (CNAME) record named: intranet Create an ALIAS (CNAME) record named: www

1. Connect to the CorpDC virtual machine as follows: From Hyper-V Manager, select CORPSERVER. From the Virtual Machines pane, right-click CorpDC and select Connect. The virtual machine is opened. 2. Create three CNAME (ALIAS) records in the sales.private domain as follows: From Server Manager, select Tools > DNS. Expand CORPDC > Forward Lookup Zones. Right-click sales.private and select New Alias (CNAME). In the Alias Name field, enter the alias name as found in the scenario. To use the parent domain name for the alias, leave the field blank. In the Fully qualified domain name field, enter CorpWeb.CorpNet.com. Click OK. Repeat steps 2c - 2f to create the additional records as outlined in the scenario.

The CorpDHCP server is the only DHCP server for clients on the 192.168.0.0/24 subnet. In this lab, your task is to complete the following: Explore the DHCP configuration on CorpDHCP and identify which scopes, exclusions, and options are currently configured. Add the CorpDHCP2 server to the DHCP console. Explore the DHCP configuration on CorpDHCP2 and identify which scopes, exclusions, and options are configured. On CorpDHCP, use the Split-Scope wizard to split the Subnet1 scope between CorpDHCP and CorpDHCP2. Configure the Host DHCP Server (CorpDHCP) to handle 85 percent of the IP addresses. Configure the Added DHCP Server (CorpDHCP2) to handle 15 percent of the IP addresses. Configure the Added DHCP Server (CorpDHCP2) with a 2-millisecond delay for the server response. Identify which exclusions have been added to the CorpDHCP server. Identify which scopes, exclusions, and options have changed on the

1. Explore the DHCP configuration as follows: In Server Manager, select Tools > DHCP. Maximize the window for easier viewing. In the left pane, expand CorpDHCP.CorpNet.com. Expand IPv4. Expand Scope [192.168.0.1] Subnet1. Select Address Pool. Notice the address range for distribution of 192.168.0.1 to 192.168.0.254 and the excluded IP addresses of 192.168.0.1 to 192.168.0.29 (to allow for static server addresses). Select Scope Options. Notice the options configured for 003 Router, 006 DNS Servers, and 015 DNS Domain Name. 2. Add a server to the DHCP console as follows: In the left pane, right-click DHCP and select Add Server. Select This authorized DHCP server. Select CorpDHCP2.CorpNet.com and click OK. 3. Explore the DHCP configuration as follows: In the left pane, expand CorpDHCP2.CorpNet.com. Expand IPv4. Expand Scope [192.168.10.1] Subnet2. Select Address Pool. Notice the address range for distribution of 192.168.10.1 to 192.168.10.254 and the excluded IP addresses of 192.168.10.1 to 192.168.10.29 (to allow for static server addresses). Select Scope Options. Notice the options configured for 003 Router, 006 DNS Servers, and 015 DNS Domain Name. part 2 below

CorpDC is the DNS server for the 192.168.0.0/24 subnet. CorpDHCP is the DHCP server for the same subnet. All clients are running Windows 10 and receive their IP addresses and other TCP/IP configuration information from the CorpDHCP server. You want DNS to be updated automatically with the A and PTR records for all hosts in the CorpNet.com domain. When you check the DNS server, you discover that although host records have been created automatically, the corresponding PTR records have not been created. In this lab, your task is to examine the DNS and DHCP configurations to diagnose and correct the problem. The zone can be a standard primary or an Active-Directory-integrated zone. Enable dynamic updates on the zone.

1. Connect to the CorpDC virtual machine as follows: From Hyper-V Manager, select CORPSERVER. To view all of the virtual machines, maximize Hyper-V Manager. From the Virtual Machines pane, right-click on CorpDC and select Connect. 2. Create the reverse lookup zone as follows: From Server Manager, select Tools > DNS. From the left pane, expand CORPDC. Select Reverse Lookup Zones. Notice that there is no reverse lookup zone for the 192.168.0.x network. Right-click Reverse Lookup Zones and select New Zone. Click Next to begin the New Zone wizard. Make sure the Primary zone and Store the zone in Active Directory options are selected. Click Next. Select how you want to replicate data and click Next. Make sure that IPv4 Reverse Lookup Zone is selected and click Next. In the Network ID field, enter 192.168.0 and click Next. Specify the type of dynamic updates that will be accepted for the DNS zone. Click Next. Click Finish.

You work as the IT Administrator for a small corporate network. Building B is on a separate subnet than the Main office in Building A. Some users in Building B run programs that need to look up the DNS name of certain computers based on their IP addresses. You need to configure a reverse lookup zone for these users. In this lab, your task is to create a new IPv4 Primary reverse lookup DNS zone on CorpDC3 for the 192.168.10.0/24 subnet used in Building B that meets the following parameters: Use a Primary zone type. Store the zone information in Active Directory. Replicate the data to all DNS servers on Domain Controllers in the domain. Allow only secure dynamic updates.

1. Connect to the CorpDC3 virtual machine as follows: From Hyper-V Manager, select CORPSERVER2. From the Virtual Machines panel, right-click CorpDC3 and select Connect. 2. Create an IPv4 Primary reverse lookup DNS zone on CorpDC3 for the 192.168.10.0/24 subnet as follows: From Server Manager, select Tools > DNS. From the left pane, expand the CORPDC3 DNS server. This server will host the zone. Right-click Reverse Lookup Zones and select New Zone. Click Next to begin the New Zone wizard. Make sure that Primary zone is selected. Click Next. Make sure that To all NDS servers running on domain controllers in this domain: CorpNet.com is selected and click Next. Make sure that IPv4 Reverse Lookup Zone is selected and click Next. In the Network ID field, enter 192.168.10. Click Next. Make sure that Allow only secure dynamic updates is selected and click Next. Click Finish.

You have authorized the CorpDHCP server to assign IP addresses to client workstations on the 192.168.10.0 subnet. Now you need to create an IPv4 scope on the CorpDHCP server for an address range on this subnet. In this lab, your task is to complete the following: On CorpDHCP, create an IPv4 scope using the following parameters: IPv4 scope name: MySubnet Address range: 192.168.10.21 to 192.168.10.199 Router (default gateway): 192.168.10.5 DNS Servers: 198.28.56.108 and 163.128.78.93 Activate the new scope upon completion.

1. Connect to the CorpDHCP as follows: In Server Manager, select Tools > Hyper-V Manager. In Hyper-V Manager, select CORPSERVER. Maximize the window for easier viewing. Under Virtual Machines, right-click on CorpDCHP and select Connect. 2. Create a scope as follows: In Server Manager, select Tools > DHCP. In the left pane, expand CorpDHCP.CorpNet.com. Right-click IPv4 and select New Scope. Click Next. In the Name field, enter MySubnet and click Next. In the Start IP address field, enter 192.168.10.21. In the End IP address field, enter 192.168.10.199. Click Next. In the Add Exclusions and Delay dialog, click Next. In the Lease Duration dialog, click Next. Make sure Yes, I want to configure these options now is selected and click Next. Under IP address, enter 192.168.10.5 for the router (default gateway). Select Add. Click Next. Under IP address, enter 198.28.56.108 for the DNS server. Select Add. Under IP address, enter 163.128.78.93 for the second DNS Server. Select Add. Click Next. In the WINS Servers dialog, click Next. 3. Activate the scope as follows: Make sure Yes, I want to activate this scope now is selected. Click Next. Click Finish to complete the process of creating the DHCP scope.

You work as the IT Administrator for a growing corporate network. CorpDHCP has an IPv4 scope to service the 192.168.0.0/24 subnet. Company policy that clients are also assigned IPv6 addresses. You need to configure a scope that will provide a unique local IPv6 address to clients. Routers are already configured for a stateful DHCPv6 configuration. In this lab, your task is to complete the following: Configure an IPv6 scope as follows: Name: Subnet1-IPv6 Prefix: FD00:0:0:1:: Preference: 0 Exclusion: 0:0:0:1 through 0:0:0:FF Preferred Lifetime: 20 days Valid Lifetime: 30 days Activate the scope Configure Scope Options for following DNS servers (in the order shown): FD00:0:0:1::11 FD00:0:0:1::12

1. Connect to the CorpDHCP virtual machine as follows: From Hyper-V Manager, select CORPSERVER. To view all of the virtual machines, maximize Hyper-V Manager. From the Virtual Machines pane, right-click CorpDCHP and select Connect. The virtual machine is opened. 2. Configure an IPv6 scope as follows: From Server Manager, select Tools > DHCP. From the left pane, expand CorpNet.com. Right-click IPv6 and select New Scope. Click Next to start the New Scope wizard. In the Name field, enter Subnet1-IPv6 and then click Next. In the Prefix field, enter: FD00:0:0:1:: Make sure that the Preference option is configured for 0. Click Next. Enter the starting and ending addresses for the exclusion. Click Add. Click Next. Configure the scope lease durations. Click Next. To activate the scope, select Yes. Click Finish to create the scope. 3. Configure the DHCPv6 Scope options as follows: From the left pane of the DHCP window, expand and select IPv6 > Scope [fd00:0:0:0:1::] > Scope Options. Right-click Scope Options and select Configure Options. From Available Options, mark 00023 DNS Recursive Name Server IPV6 Address List. In the New IPv6 address field, enter the first IPv6 address of the DNS server. Click Add. In the New IPv6 address field, enter the second IPv6 address of the DNS server. Click Add. Click OK to save the options you have defined.

Part 2

4. Configure a DHCP split-scope as follows: Right-click Scope [192.168.0.1] Subnet1 select Advanced > Split-Scope. Click Next to begin the DHCP Split-Scope Configuration Wizard. Select Add Server to select the target DHCP server. Select This authorized DHCP server. Select CorpDHCP2.CorpNet.com. Click OK. Click Next. In the Host DHCP Server field, enter 85. In the Added DHCP Server field, verify that 15 is entered and click Next. In the Added DHCP Server field, enter 2 for the response delays. Click Next. Click Finish. From the summary pane, verify that the split-scope configuration was created successfully Click Close. Under Scope [192.168.0.1] Subnet1, select Address Pool. Notice the new exclusion for 192.168.0.217 to 192.168.0.254, excluding 15 percent of the address range. 5. Explore and activate the new scope as follows: Under CorpDHCP2.CorpNet.com, expand Scope [192.168.0.1] Subnet1. Select Address Pool. The address range of 192.168.0.1 to 192.168.0.254 has been duplicated, and an exclusion for 192.168.0.1 to 192.168.0.216 has been created to exclude 85 percent of the address range. Select Scope Options. Notice that the scope options were duplicated. Right-click Scope [192.168.0.1] Subnet1 and select Activate to enable the backup scope.

You have just configured a scope on the CorpDHCP server to service the 192.168.0.0/24 subnet. You need to configure additional TCP/IP parameters for all clients serviced by the CorpDHCP server. In this lab, your task is to complete the following: Configure the following DHCP options for the CorpDHCP server (not on the Subnet1 scope): 006 DNS Servers = 192.168.0.11 and 192.168.10.11 (in the order shown) 015 DNS Domain Name = CorpNet.com Configure Subnet1 scope options as follows: 003 Router (default gateway) as 192.168.0.5

1. Connect to the CorpDHCP virtual machine as follows: From Hyper-V Manager, select CORPSERVER. To view all of the virtual machines, maximize Hyper-V Manager. From the Virtual Machines pane, right-click CorpDCHP and select Connect. The virtual machine is opened. 2. Configure the DHCP server options as follows: From Server Manager, select Tools > DHCP. From the left pane, expand CorpDHCP.CorpNet.com. Expand IPv4. Right-click Server Options and select Configure Options. Under Available Options, mark 006 DNS Servers. In the IP Address field, enter the IP address as found in the scenario. Click Add to add the IP address to the list. Repeat steps 1i-1j to add additional IP addresses. Click Apply. Under Available Options, mark 015 DNS Domain Name. In the String value field, enter CorpNet.com. Click OK to save the options you have defined. 3. Configure the DHCP scope options as follows: Expand Scope [192.168.0.1] Subnet1. Right-click Scope Options and select Configure Options. Under Available Options, mark 003 Router. In the IP address field, enter 192.168.0.5. Click Add to add the IP address to the list. Click OK to save the options you defined.

You work as the IT administrator for a small corporate network. You previously configured the BranchVPN1 server as a remote access server to allow VPN connections. In this lab, you task is to create and configure a network policy to allow members of the Development department to connect using the following parameters: Name the policy Development. Use a Remote Access Server. Set Add membership of the Research-Dev Windows group as a condition. Deny access to any account that is not configured in Active Directory. Configure permissions to use settings in the Active Directory user accounts (User Dial-in properties). User account settings will be configured by an Active Directory user account administrator. Use the secured password (EAP-MSCHAP v2). As a constraint, allow access only from 7:00 a.m. to 8:00 p.m., Monday-Friday. Make the policy first in the list of policies.

1. Create a network policy as follows: In Server Manager, select Tools > Network Policy Server. Expand Policies. Right-click Network Policies and select New. In the Policy name field, enter Development. From the Type of network access server drop-down list, select Remote Access Server and then click Next. 2.Add a condition to the network policy as follows: Select Add to add group membership as a condition. Select Windows Groups. Select Add. Select Add Groups. Under Enter the object names to select, enter Research-Dev. Click OK. Select OK to close the Windows Groups dialog. Click Next. Select Access denied. Select Access is determined by User Dial-in properties. Click Next. Under EAP Types, select Add. Select Microsoft: Secured password (EAP-MSCHAP v2); then click OK. Under Less secure authentication methods, unmark all the authentication methods and then click Next. 3. Configure policy constraints as follows: Under Constraints, select Day and Time restrictions. Select Allow access only on these days and at these times. Select Edit. Select the appropriate restrictions and then click OK. Click Next. In the Configure Settings dialog click Next. Click Finish. 4. Under Policy Name, right-click Development. 5. Select Move Up or Move Down to change the order of a network policy.

You have configured the BranchVPN2 server as a remote access server to allow VPN connections. Members of the sales team will connect to the remote access server to enter daily orders and check the status of orders. You need to use the Network Policy Server console to configure a network policy on BranchVPN2 to allow members of the sales team to connect. In this lab, your task is to complete the following: Create a network access policy called Sales that will configure a remote access server. Configure Sales policy with a condition where the membership in the Sales Active Directory user group causes the policy to be evaluated. Grant access if the condition is met regardless of the setting in the Active Directory user account. Accept only a smart card or other certificate as authentication, making sure all other authentication methods are not allowed. Make sure the policy is listed first in the list of policies.

1. Create a new network policy as follows. In Server Manager, select Tools > Network Policy Server. Maximize the window for easier viewing. In the left pane, expand Policies. Right-click Network Policies and select New. In the Policy name field, enter Sales. 2. Configure the network access server type as follows: From the Type of network access server drop-down list, select Remote Access Server (VPN-Dial up). Click Next. 3. Add membership to the Sales group as a condition as follows: Add Add to add a condition. Select User Groups. Select Add. Select Add Groups. In the Enter the object names to select, enter Sales. Select Check Names. Click OK. In the Windows Groups dialog, click OK. Click Next. 4. Grant access through the policy as follows: Make sure Access granted is selected. Click Next. 5. Configure smart card and certificate authentication as follows: Select Add. In the Add EAP dialog, make sure Microsoft: Smart Card or other certificate is selected. Click OK. Under Less secure authentication methods, unmark Microsoft Encrypted Authentication version 2 (MS-CHAP-v2). Unmark Microsoft Encrypted Authentication (MS-CHAP). Click Next. 6. In the Configure Constraints window, click Next. 7. In the Configure Settings window, click Next. Click Finish. 8. Under Network Policies, make sure Sales appears at the top of the list of policies.

The Sales department would like single-label name resolution for the CorpNet intranet web server called CorpWeb.CorpNet.com. A DNS zone is needed to support single-label name resolution when they type innerweb or intranet. GlobalNames support has been enabled on the server. In this lab, your task is to configure DNS on the CorpDC server as follows: Create a DNS zone named GlobalNames. Make the zone an Active Directory-integrated zone. Replicate the zone to all DNS servers in the domain. Do not allow dynamic updates. Create a resource record that will resolve innerweb or intranet to the intranet web server.

1. Create a primary forward lookup DNS zone as follows: From Server Manager, select Tools > DNS. Expand CORPDC (the server node that will host the new zone). Right-click Forward Lookup Zones and select New Zone. Click Next. Make sure that Primary zone has been selected as the zone type Verify that the Store the zone in Active Directory option is marked. Click Next. Make sure that To all DNS servers running on domain controllers in this domain is selected. Click Next. In the Zone Name field, enter GlobalNames and then click Next. Select Do not allow dynamic updates and then click Next. Click Finish. 2. Create the Alias (CNAME) resource record that will resolve innerweb as follows: From DNS Manager, expand CORPDC > Forward Lookup Zones. Right-click GlobalNames and select New Alias (CNAME). In the Name field, enter innerweb. In the Fully qualified domain name field, type CorpWeb.CorpNet.com. Click OK. 3. Create the Alias (CNAME) resource record that will resolve intranet as follows: From DNS Manager, expand CORPDC > Forward Lookup Zones. Right-click GlobalNames and select New Alias (CNAME). In the Name field, enter intranet. In the Fully qualified domain name field, type CorpWeb.CorpNet.com. Click OK.

Part 3

5. Renew ITAdmin's IP address configurations on the Ethernet adapter as follows: From the top navigation tabs, select Floor 1 Overview. Under IT Administration, select ITAdmin. At the command prompt, type ipconfig /renew and press Enter. Type ipconfig /all and press Enter. Notice that the IPv4 address is now 192.168.0.31, the default gateway address is now 192.168.0.5, and the DHCP Server is now 192.168.0.14. Type ping corpserver and press Enter. Notice the reply from CorpServer. Type ping 65.86.1.1 and press Enter. Notice the reply from the ISP address. Type ping exec and press Enter. Notice the reply from Exec.

You work as the IT administrator for a small corporate network. You have two servers and a DNS server that use static IP addresses on the 192.168.0.0/24 subnet. You plan to install three more servers soon, so you need to create DNS records for these servers on the CorpDC server. In this lab, your task is to complete the following: Create an IPv4 Active-Directory-integrated primary reverse lookup zone for subnet 192.168.0.0/24. Be sure to accept the default replication and dynamic updates settings. Create A records and PTR records for the following hosts: Host Name IP Address CorpServer 192.168.0.10 CorpFiles16 192.168.0.12 CorpFiles12 192.168.0.13 CorpDHCP 192.168.0.14 CorpWeb 192.168.0.15

1. Create a primary reverse lookup zone as follows: In Hyper-V Manager, select CORPSERVER. Right-click CorpDC and select Connect. In Server Manager, select Tools > DNS. Expand CORPDC. Right-click Reverse Lookup Zones and select New Zone. Click Next. Make sure Primary zone is selected. Make sure Store the zone in Active Directory is selected and then click Next. Keep the default replication scope setting and click Next. Keep the default reverse lookup zone settings and click Next. Enter 192.168.0 as the network ID. Omit any trailing zeroes that are excluded based on the subnet mask. For example, type 192.168.1 for subnet 192.168.1.0/24. Type 10.1 for subnet 10.1.0.0/16. Click Next. Keep the default dynamic update settings and then click Next. Click Finish. 2. Create a host (A) and associated pointer (PTR) record as follows: In DNS Manager, expand Forward Lookup Zones. Right-click CorpNet.com and select New Host (A or AAAA). In the Name field, enter the host name. In the IP address field, enter the IP address. Select Create associated pointer (PTR) record as needed. The reverse lookup zone must exist for this record to be created. Click Add Host. Click OK. Repeat steps 2c - 2g to add additional host records. Click Done.

You work as the IT administrator for a small corporate network. You want to enable dynamic DNS in order to minimize administration of the CorpNet.com DNS zone. DNS is running on CorpDC, and CorpDHCP is running DHCP. In this lab, your task is to complete the following: On CorpDC, configure the CorpNet.com DNS zone to accept only secure dynamic updates. On CorpDHCP, configure the Subnet1 and Subnet2 DHCP scopes to always dynamically update information in DNS, even if DHCP clients do not explicitly request dynamic updates or do not support dynamic DNS.

1. Enable Dynamic DNS updates on a zone as follows: In Hyper-V Manager, select CORPSERVER. Under Virtual Machines, right-click CorpDC and select Connect. In Server Manager, select Tools > DNS. In the left pane, expand CORPDC. Expand Forward Lookup Zones. Right-click CorpNet.com and select Properties. From the Dynamic Updates drop-down select Secure only. Click OK. Close DNS Manager Close the Virtual Machine Connection window. 2. Enable Dynamic DNS updates for a scope as follows: In Hyper-V Manager, select CORPSERVER. Maximize the window for easier viewing. Under Virtual Machines, right-click CorpDHCP and select Connect. In Server Manager, select Tools > DHCP. In the left pane, expand CorpDHCP.CorpNet.com. Expand IPv4. Right-click the desired scope and select Properties. Select the DNS tab. Make sure Enable DNS dynamic updates according to the settings below is selected. Select Always dynamically update DNS A and PTR records. This configures the server to update records for all clients, regardless of whether they request it or not. Make sure Discard A and PTR records when lease is deleted is selected. This configures the DHCP server to notify the DNS server to remove the host record when the IP address is no longer assigned to the client. Select Dynamically update DNS A and PTR records for DHCP clients that do not request updates. This configures the DHCP server to update all DNS records for clients that do not support dynamic DNS updates. Click OK. Repeat steps 2g-2m for the additional scope.

Your partner company is preparing to launch a web server. They expect heavy traffic to the website, so they would like your assistance with configuring a load balancing solution. As a temporary measure, you have decided to replicate the static web content from one server to two other servers and then use DNS round robin to load balance requests to the web server. In this lab, your task is to complete the following: Enable round robin for the PartnerServer DNS server. Create three host (A) records in the PartnerNet.org zone using the following information: Host name IP address www.PartNernet.org 73.44.216.5 73.44.216.6 73.44.216.7 Create the associated pointer (PTR) records for each host record.

1. Enable Round Robin as follows: From Server Manager, select Tools > DNS. From the left pane, right-click PARTNERSERVER and select Properties. Select the Advanced tab. In Server Options panel, mark Enable round robin. Click OK. 2. Create three host (A) records in the PartnerNet.org zone as follows: From the left pane, expand PARTNERSERVER > Forward Lookup Zones. Right-click PartnerNet.org and select New Host (A or AAAA). In the Name field, enter www. In the IP address field, enter IP address (see table). Mark Create associated pointer (PTR) record to create the PTR record automatically. (The reverse lookup zone must exist for this record to be created.) Click Add Host. Click OK. The New Host dialog is still open. Repeat steps 2c -2g to add the additional two hosts. Click Done to close the New Host dialog.

You work as the IT Administrator of a small corporate network. After enabling dynamic updating, your zones are accumulating unnecessary resource records. You want to ensure that these stale records don't degrade DNS server performance. In this lab, your task is to complete the following: Enable automatic scavenging of stale records on the CorpDC DNS server. Scavenge records every 10 days. Enable scavenging of stale resource records on all Active Directory zones. Set the no-refresh interval to 5 days. Set the refresh interval to 5 days. Apply the setting to existing Active Directory-integrated zones.

1. Enable and configure scavenging of stale records as follows: From Server Manager, select Tools > DNS. From the left pane, right-click CORPDC and select Properties. Select the Advanced tab. From the lower portion of this tab, mark Enable automatic scavenging of stale records. In the Scavenging period field, enter 10. Make sure that its accompanying field is configured for days. Click OK. 2. Configure Aging/Scavenging for All Zones as follows: From the left pane, right-click CORPDC and select Set Aging/Scavenging for All Zones. Select Scavenge stale resource records. Configure the no-refresh interval to 5 days. Configure the refresh interval to 5 days. Click OK. Select Apply these settings to the existing Active Directory-integrated zones. Click OK.

The CorpRTR server is connected to the test networks as shown in the Exhibit. It is currently configured with static routes to the non-directly connected test networks. You realize that maintaining static routes will quickly become difficult as the test network grows. You would like to configure dynamic routing on the server. In this lab, your task is to complete the following: Enable the RIP routing protocol on the server. Enable RIP on the TestLAN interface. Configure the interface to use periodic updates. Configure the interface to use version 2 broadcasts for outgoing updates and only version 2 for incoming updates. Delete all static routes.

1. Enable the RIP routing protocol on the server as follows: From Server Manager, select Tools > Routing and Remote Access. From the left pane, expand CorpRTR > IPv4. Right-click General and select New Routing Protocol. Select RIP Version 2 for Internet Protocol and click OK. 2. Configure RIP Routing as follows From the left pane, under IPv4, right-click RIP and select New Interface. Select TestLAN and click OK. Ensure that Operation mode is configured for Periodic update mode. Ensure that Outgoing packet protocol is configured for RIP version 2 broadcast. Change incoming packet protocol to RIP version 2 only. Click OK. 3. Delete all Static Route as follows: From the left pane under IPv4, select Static Routes. From the right pane, delete each route by right-clicking the route and selecting Delete.

You are the administrator for the CorpNet domain. The CorpDC and CorpDC3 servers are the DNS servers for the domain. You are responsible for CorpDC, which resides in Building A. Users report that they are unable to contact the CorpWeb server. In this lab, your task is to complete the following: Ping the CorpWeb server using its full name (CorpWeb.CorpNet.local). What happens? Ping the CorpWeb server using its IP address (192.168.0.15). What happens? Create any DNS records needed to fix the problem. Use the ping command to verify that the problem has been fixed.

1. From CorpServer, use the ping command to troubleshoot the connection to the CorpWeb server as follows: In the Search the web and Windows field, enter cmd. Under Best match, right-click Command Prompt and select Run as Administrator. At the command prompt, type ping corpweb.corpnet.local and press Enter. Notice that the ping is unable to find CorpWeb. At the command prompt, type ping 192.168.0.15 and press Enter. The ping succeeds using the IP address, indicating a problem with the CorpWeb DNS record. 2. Create the host record for CorpWeb as follows: In Hyper-V Manager, select CORPSERVER. Under Virtual Machines, right-click CorpDC and select Connect. In Server Manager, select Tools > DNS. In the left pane, expand CORPDC. Expand Forward Lookup Zones. Right-click CorpNet.local and select New Host (A or AAAA). In the Name field, enter CorpWeb. In the IP address field, enter 192.168.0.15. Select Create associated pointer (PTR) record to automatically create the PTR record for the new host. Select Add Host. Click OK. Click Done to close the New Host dialog. 3. From CorpServer, verify that the new host record fixed the connection issue as follows: At the command prompt on CorpServerping, type ping corpweb.corpnet.local and press Enter. The ping now succeeds.

You work as the IT administrator for a small corporate network. You recently expanded the network to a second building. In doing so, you removed the consumer-grade internet router and installed a network router. You have decided to use CorpDHCP as a DHCP server to replace the DHCP service provided by the consumer-grade router. In this lab, your task is to complete the following: Install the DHCP role. Authorize CorpDHCP as a DHCP server. Configure the DHCP scope as follows: Name: Subnet1 Address range: 192.168.0.1 to 192.168.0.254 Subnet mask: 255.255.255.0 Length: 24 Lease duration: 5 days Activate the DHCP scope. Do not configure exclusions or options at this time.

1. Install a DHCP role as follows: From Hyper-V Manager, select CORPSERVER. Maximize the window to view all virtual machines. Right-click CorpDCHP and select Connect. From Server Manager, select Manage > Add Roles and Features. In the Add Roles and Features wizard, click Next. Make sure Role-based or feature-based installation is selected; then click Next. Make sure CorpDHCP.CorpNet.com is selected in the Server Pool area; then click Next. Select the DHCP Server role. Select Add Features. Click Next. Click Next because no additional features are required for the DHCP Server. In the DHCP Server window, click Next. Select Install to add the selected role. 2. Authorize CorpDHCP as a DHCP server as follows: In the center area, select Complete DHCP configuration to begin the DHCP Post-Install configuration wizard. In the DHCP Post-Install configuration wizard, click Next. Verify the credentials; then select Commit. Click Close to close the DHCP Post-Install configuration wizard. Click Close to close the Add Roles and Features wizard. 3. Configure and activate a DHCP Scope as follows: From Server Manager, select Tools > DHCP. Expand CorpDHCP.CorpNet.com. Right-click IPv4 and select New Scope. In the New Scope wizard, click Next. In the Name field, enter the name of the scope and then click Next. Enter the start IP address. Enter the end IP address. Make sure the subnet is 255.255.255.0. Make sure the length is 24; then click Next. 4. Click Next to ignore any exclusions and delays. 5. Enter 5 days as the lease duration and then click Next. 6. Select No, I will configure these options later to postpone configuring other DHCP options and then click Next. 7. Click Finish to close the wizard and create the scope. 8. Activate the DHCP scope as follows: Expand IPv4. Right-click Scope [192.168.0.1] Subnet1 and select Activate.

The Accounting department is testing a new payroll system server. To facilitate their tests, they would like to add the server to DNS to support name resolution. You would like to place a copy of this zone on the DNS server in Building B. In this lab, your task is to complete the following: Create a forward lookup zone on CorpDC using the following information: Create the zone as a Primary forward lookup zone. Do not store the zone in Active Directory. Name the zone acct.CorpNet. Use the default name for the zone file. Do not allow dynamic updates. Configure the acct.CorpNet zone to allow zone transfers to any server. Create a forward lookup zone on CorpDC3 using the following information: Create the zone as a Secondary forward lookup zone. Name the zone acct.CorpNet. Specify CorpDC (192.168.0.11) as the master DNS server for the zone.

1. Open the CorpDC virtual machine as follows: In Hyper-V Manager, select CORPSERVER. Under Virtual Machines, right-click CorpDC and select Connect. 2. Create a primary forward lookup zone on CorpDC as follows: In Server Manager, select Tools > DNS. In the left pane, expand CORPDC. Right-click Forward Lookup Zones and select New Zone. Click Next to begin the New Zone Wizard. Make sure Primary zone is selected as the zone type. Unmark Store the zone in Active Directory and then click Next. In the Zone name field, enter acct.CorpNet. Click Next. Make sure Create a new file with this file name is selected and click Next. Make sure Do not allow dynamic updates is selected and click Next. Click Finish. 3. Configure the acct.Corpnet zone to allow zone transfers to any server as follows: Under CorpDC, expand Forward Lookup Zones. Right-click acct.Corpnet and select Properties. Select the Zone Transfers tab. Make sure Allow zone transfers is selected. Select To any server and click OK. 4. Create a Secondary forward lookup zone on CorpDC2 as follows: In the left pane, expand CORPDC3. Right-click Forward Lookup Zones and select New Zone. Click Next to begin the New Zone Wizard. Select Secondary zone and click Next. In the Zone name field, enter acct.CorpNet. Click Next. Under IP Address, select Click here to add an IP address or DNS Name and enter 192.168.0.11. Press Enter. After the IP address is validated, click Next. Click Finish to complete the New Zone Wizard.

You are a network technician for a small corporate network. The network is connected to the internet and uses DHCP for address assignment. The employees in the Support Office and Office 2 report that their workstations can communicate with some computers on the network, but not on the internet. The IP address for the ISP and internet is 65.86.1.1. In this lab, your task is to diagnose and fix the problem using the following troubleshooting tools: Command line utilities:ping(ping IP address or host name)ipconfig(ipconfig /all; ipconfig /renew)tracert(tracert IP address or host name) Network and Sharing Center Network & Internet settings The DHCP server console in the Windows Server 2016 operating system The network diagram and schematic found in Exhibits

1. Use Office2 to verify the connectivity problem by pinging Support, CorpServer, and the Internet Service Provider (ISP) as follows: In the Search field on the taskbar, enter cmd. Under Best match, right-click Command Prompt and select Run as Administrator. At the command prompt, type ping support and press Enter. Notice that Support is translated to 192.168.0.35 and the ping is returned. Type ping corpserver and press Enter. Notice that CorpServer is translated to 192.168.0.10 and the ping is returned. Type ping 65.86.1.1 and press Enter. The request times out. 2. Use Support to verify the connectivity problem by pinging Office2, CorpServer, and the Internet Service Provider (ISP) as follows: From the top navigation tabs, select Floor 1 Overview. Under Support Office, select Support. In the Search field on the taskbar, enter cmd. Under Best match, right-click Command Prompt and select Run as Administrator. At the command prompt, type ping office2 and press Enter. Notice that Office2 is translated to 192.168.0.34 and the ping is returned. Type ping corpserver and press Enter. Notice that CorpServer is translated to 192.168.0.10 and the ping is returned. Type ping 65.86.1.1 and press Enter. The request times out. Part 2 below

part 3

5. Renew the IP address configurations on the Ethernet adapter for the Support workstation as follows: From the top navigation tabs, select Floor 1 Overview. Under Support Office, select Support. At the command prompt, type ipconfig /renew and press Enter. Type ipconfig /all and press Enter. Notice that the default gateway address is now correctly configured as 192.168.0.5. Type ping 65.86.1.1 and press Enter. Notice the reply from the ISP address. 6. Renew the IP address configurations on the Ethernet adapter for the Office2 workstation as follows: From the top navigation tabs, select Floor 1 Overview. Under Office 2, select Office2. At the command prompt, type ipconfig /renew and press Enter. Type ipconfig /all and press Enter. Notice that the default gateway address is now correctly configured as 192.168.0.5. Type ping 65.86.1.1 and press Enter. Notice the reply from the ISP address.

You are the IT security administrator for a small corporate network. You plan to use the CorpServer server as your production server, and you need to have the most throughput possible. As a result, you must configure NIC Teaming. In this lab, your task is to configure a NIC team on CorpServer as follows: View the current IP configuration for the primary adapter. Create a NIC team with all adapters as members using the following parameters: Team name: NetTeam Teaming Mode: Switch Independent Load balancing mode: Address Hash Standby adapter: Ethernet 3 Configure the NIC team to use same IP address as the primary adapter using the following parameters: IP Address: 192.168.0.10 Subnet mask: 255.255.255.0 Default gateway: 192.168.0.5 Preferred DNS server: 192.168.0.11 Alternate DNS server: 192.168.10.11 Verify the status of the team and your network connection in Network and Sharing Center.

1. View the current IP configuration for the primary adapter as follows: Right-click the network icon and select Open Network and Sharing Center. Select Ethernet. Select Details. Click Close. Click Close. 2. Create a NIC team as follows: In Server Manager, select Local Server from the menu on the left. Next to NIC Teaming, select Disabled to configure NIC Teaming. In the Teams panel, select Tasks > New Team. Enter the team name. Select the adapters to be included in the team. Select Additional Properties. Make sure Switch Independent is selected as the teaming mode. Make sure Address Hash is selected as the load balancing mode. In the Standby adapter drop-down list, select Ethernet 3; then click OK. 3. Configure the NIC team to use the same IP address as primary adapter as follows: In the Network and Sharing Center, select Change adapter settings. Right-click NetTeam and select Properties. Select Internet Protocol Version 4 (TCP/IPv4). Select Properties. Select Use the following IP address. Enter the IP address. Enter the subnet mask. Enter the default gateway. Make sure Use the following DNS server addresses is selected. Enter the preferred DNS server address. Enter the alternate DNS server address. Click OK. Click Close. 4. Verify the status of the NIC team and your network connection as follows: Right-click the network icon and select Open Network and Sharing Center. Make sure NetTeam is displayed by Connections.

part 2

3. Activate the scope as follows: From the top navigation tabs, select Floor 1 Overview. Under Networking Closet, select CorpServer. In Hyper-V Manager, CORPSERVER. Maximize the window for easier viewing. Under Virtual Machines, right-click CorpDHCP and select Connect. In Server Manager, select Tools > DHCP. In the left pane, expand CorpCHCP.CorpNet.com. Select IPv4. In the center pane, notice that the Scope [192.168.0.1] Subnet1 is inactive. It has a small red down arrow added to the folder icon. Right-click Scope [192.168.0.1 Subnet1 and select Activate 4. Use Exec to renew the IP address configurations on the Ethernet adapter as follows: From the top navigation tabs, select Floor 1 Overview. Under Executive Office, select Exec. At the command prompt, type ipconfig /renew and press Enter. Type ipconfig /all and press Enter. Notice that the IPv4 address is now 192.168.0.30, the default gateway address is now 192.168.0.5, and the DHCP Server is now 192.168.0.14. Type ping corpserver and press Enter. Notice the reply from CorpServer. Type ping 65.86.1.1 and press Enter. Notice the reply from the ISP address. Type ping itadmin and press Enter. The request times out. This is expected because ITAdmin has not renewed its IP addresses. part 3 below

PART 2

3. Configure failover of the Campus1 scope with the CorpDHCP_2 server as follows: From the top navigation tabs, select the location icon. Under Campus1, select CampusServer1. Right-click Scope [10.10.10.1] Campus1 and select Configure Failover. Unmark Select all. Under Available scopes, select 10.10.10.0. Click Next. Select Add Server. Select This authorized DHCP server. Select CampusDHCP_2.PartnerNet.com. Click OK. Click Next. In the Mode field, make sure Load balanced is selected. Under Load Balance Percentage, enter 75% for the Local Server. Make sure 25% is showing for the Partner Server. In the Shared Secret field, enter HelpMyDHCP123. Click Next. Read the sentence at the top to verify that failover will be set up between CampusDHCP_1 and CampusDHCP_2. Select Finish. Click Close. 4. Explore the new scope as follows: From the top navigation tabs, select the location icon. Under Campus2, select CampusServer2. From the left pane, right-click IPv4 and select Refresh. From the left pane, expand CampusDHCP_2.PartnerNet.com. Expand IPv4. Verify that a copy of the Campus1 scope on this server From the left pane, expand Scope [10.10.10.1] Campus1. Select Address Pool. The address ranges have been duplicated. Select Scope Options. The applicable scope options have been duplicate

part 2

3. Create a network policy and add a group as follows: In the left pane, expand Policies. Right-click Network Policies and select New. In the Policy name field, enter Sales. From the Type of network access server drop-down list, select Remote Access Server; then click Next. Select Add to add group membership as a condition. Select User Groups. Select Add. Select Add Groups. Under Enter the object names to select, enter Sales. Click OK. Click OK. Click Next. Make sure Access granted is selected. Click Next. Click Add. Make sure Microsoft: Smart card or other certificate is selected; then click OK. Under Less secure authentication methods, unmark all the authentication methods and then click Next. In the Configure Constraints dialog, click Next. In the Configure Settings dialog, click Next. Click Finish. Part 3 below

part 2

3. Use ipconfig /all to check the Ethernet adapter configuration as follows: At the command prompt, type ipconfig /all and press Enter. Notice that the Ethernet adapter is configured with DHCP Enabled, and the DHCP Server has the IP address 192.168.0.14. This is the correct IP address. The Ethernet adapter is receiving its IP address, default gateway address, and DNS addresses from the correct DHCP server. Notice that the default gateway address is incorrectly configured as 192.168.0.4. The Exhibit shows that the default gateway should be 192.168.0.5. The DHCP server must be giving out the wrong default gateway address. This is probably why the workstation can't communicate with the ISP and the internet. 4. Use CorpServer to access CorpDHCP and reconfigure the default gateway settings for the DHCP scope as follows: From the top navigation tabs, select Floor 1 Overview. Under Networking Closet, select CorpServer. In Hyper-V Manager, select CORPSERVER. Maximize the window for easier viewing. Under Virtual Machines, right-click CorpDHCP and select Connect. In Server Manager, select Tools > DHCP. Maximize the window for easier viewing. In the left pane, expand CorpCHCP.CorpNet.com. Expand IPv4. Expand Scope [192.168.0.1] Subnet1. Select Scope Options. In the center pane, right-click 003 Router and select Properties. Under IP address, select 192.168.0.4. Select Remove. In the IP address field, enter 192.168.0.5. Select Add. Click OK. par 3 below

You are the IT administrator for a small corporate network. You want to add DNS to the CorpDC3 server. In this lab, your task is to add the DNS Server Role service.

Complete this lab as follows: In Server Manager, select Manage > Add Roles and Features. Click Next to begin the Add Roles and Features Wizard. Make sure Role-based or feature-based installation is selected; then click Next. Make sure Select a server from the server pool is selected. Under Server Pool, make sure CorpDC3.CorpNet.com is selected; then click Next. Select the DNS Server role service. Select Add Features to include management tools. Click Next. Click Next. Click Next. Select Install. After the installation completes, click Close.

Several printers on Subnet1 need static IP addresses assigned to them. In this lab, your task is to configure the CorpDHCP server so that these machines always get the same IP addresses. Additionally, configure each reservation for DHCP only. Use the values in the table below to configure the reservations. Reservation Name IP Address MAC Address LaserJet4240-1 192.168.0.101 aa-61-82-df-04-54 LaserJet4240-2 192.168.0.102 ce-fd-48-90-06-23 KonicaColor 192.168.0.103 c8-ba-99-cd-80-12 AcctPrinter 192.168.0.104 f1-a9-3e-f7-7d-3b SalesPrinter 192.168.0.105 df-a9-99-cd-80-61

From Hyper-V Manager, select CORPSERVER. Expand the window to view all virtual machines. Right-click CorpDCHP and select Connect. From Server Manager, select Tools > DHCP. In the left pane, expand CorpDHCP.CorpNet.com. Expand the IPv4 protocol. Expand the Scope folder. Right-click Reservations and select New Reservation. In the Reservation name field, enter a reservation name (such as the computer name). In the IP address field, enter the IP address. In the MAC address field, enter the MAC address. For Ethernet, the MAC address will look like c8ba99cd8012 or c8-ba-99-cd-80-12. Under Supported types, select DHCP only as needed. Select Add to create the client reservation. Repeat steps 9- 13 for additional reservations. Select Close.

You have just configured a scope on the CorpDHCP server to service the 192.168.0.0/24 subnet. You defined a scope to distribute IP addresses between 192.168.0.1 and 192.168.0.254. Now you need to prevent the DHCP server from assigning addresses to the servers and network devices. In this lab, your task is to create an exclusion range to exclude addresses 192.168.0.1 to 192.168.0.29.

From Hyper-V Manager, select CORPSERVER. Expand the window to view all virtual machines. Right-click CorpDCHP and select Connect. From Server Manager, select Tools > DHCP. In the left pane, expand CorpDHCP.CorpNet.com. Expand the IPv4 protocol. Expand the Scope folder. Right-click the Address Pool node and select New Exclusion Range. In the Start IP address field, enter the starting IP address. In the End IP address field, enter the ending IP address. Click Add. Click Close to close the Add Exclusion Range dialog.

You work as the IT administrator for a small corporate network. The company is growing and has acquired additional space in an adjacent building. You have set up a router between the buildings and have connected a Windows Server 2016 server named CorpServer2 to the network. You have just installed the Hyper-V role on this server, which requires you to manually configure the Hyper-V adapter with a server IP address. In this lab, your task is to complete the following: Configure the TCP/IP properties for the vEthernet (External) network to use the following static values for the network in Building B: IP Address: 192.168.10.10 Subnet mask: default subnet mask Default gateway: 192.168.10.5 Preferred DNS server: 192.168.10.11 Alternate DNS server: 192.168.0.11 Use ipconfig to verify the address changes to the server.

From the taskbar, right-click the Network icon and select Open Network and Sharing Center. On the left, select Change adapter settings. Right-click vEthernet (External) and select Properties. Select Internet Protocol Version 4 (TCP/IPv4). Select Properties. Select Use the following IP address. In the IP address field, enter 192.168.10.10. Click in the Subnet mask field to allow the default subnet mask to populate the field. In the Default gateway field, enter 192.168.10.5. Make sure Use the following DNS server addresses is selected. In the Preferred DNS server field, enter 192.168.10.11. In the Alternate DNS server field, enter 192.168.0.11. Click OK. Click Close. In the Search the web and Windows field, enter cmd. Under Best match, right-click Command Prompt and select Run as Administrator. At the command prompt, type ipconfig /all and press Enter. Make sure vEthernet (external) is configured as specified above.

The CorpWeb server is running Windows Server 2016. You previously configured the server with a static IP address. Now you need to configure a DNS server address. You also want to use sales.private, mrktg.private, and private as search suffixes when simple names are submitted for DNS name resolution. In this lab, your task is to complete the following: Configure 192.168.0.11 as the DNS server address. Configure the following domain suffixes so that the server searches the domains: sales.private mrktg.private private

In Hyper-V Manager, select CORPSERVER. Maximize the window to view all virtual machines. Right-click CorpWeb and select Connect. In the notification area, right-click the Network icon and select Open Network and Sharing Center. In the left pane, select Change adapter settings. Right-click Ethernet and select Properties. Select Internet Protocol Version 4 (TCP/IPv4). Select Properties. Select Advanced. Select the DNS tab. Click Add. Type the IP address of the DNS server you want to use. Click Add. Select Append these DNS suffixes. Click Add. Type the domain suffix you want to use. Click Add. Repeat steps 15 - 17 for additional suffixes. Click OK twice.

The CorpDC server currently stores the sales.private standard primary DNS zone. You need to configure the sales.private zone to store all the data in Active Directory. In this lab, your task is complete the following: Convert the sales.private zone to an Active-Directory-integrated zone. Change the replication scope to store data on all DNS servers in the domain.

In Hyper-V Manager, select CORPSERVER. Right-click CorpDC and select Connect. In Server Manager, select Tools > DNS. Expand CORPDC. Expand Forward Lookup Zones. Right-click the zone and select Properties. Under Type, select Change. Make sure that Primary zone is selected. Select Store the zone in Active Directory. Select OK. Select Yes to confirm Active Directory integration. Under Replication, select Change. Select To all DNS servers in this domain. Click OK. Click Yes to confirm your changes. Click OK.

Some of your virtual machines are struggling with network bandwidth. You have decided to use hardware acceleration and have purchased a physical network adapter that supports virtual machine queue. You have created a new virtual machine called CorpTest to test this feature. The OS is not installed yet on CorpTest. In this lab, your task is to enable virtual machine queue on the CorpTest virtual machine.

In Hyper-V Manager, select CORPSERVER2. Expand the window as needed to view all virtual machines. Right-click CorpTest and select Settings. In the left pane, under Network Adapter, select Hardware Acceleration. Select Enable virtual machine queue. Click OK.

You work as the IT administrator for a small corporate network. You need to create a separate subnet to use for testing. The test subnet needs access to the rest of the network through a router, but it should not have any local access to production machines. You have installed Windows Server 2016 on CorpRTR, which you plan to use to isolate the test segment from the rest of the network. You'll use traditional routing or NAT. In this lab, your task is to add the necessary role and role services to meet the stated requirements. Do not add unnecessary role services.

In Server Manager, select Add roles and features. Select Next. Make sure Role-based or feature-based installation is selected; then click Next. Make sure CorpRTR.CorpNet.com server is selected; then click Next. Select Remote Access. Select Add Features; then click Next. In the Select Features window, click Next. In the Remote Access window; click Next. Select Routing; then click Next. In the Web Server Role (IIS) window; then click Next. In the Role Services windows; click Next. Select Install. Click Close.