Lab answer key: Implementing and configuring virtualization in Windows Server

Note: An interactive lab simulation is available that allows you to click through this lab at your own pace. You may find slight differences between the interactive simulation and the hosted lab, but the core concepts and ideas being demonstrated are the same.

Exercise 1: Creating and configuring VMs

Task 1: Create a Hyper-V virtual switch

1. Connect to SEA-ADM1 and, if needed, sign in as CONTOSO\Administrator with a password of Pa55w.rd.
2. On SEA-ADM1, select Start, and then select Server Manager.
3. In Server Manager, select All Servers.
4. In the Servers list, select the SEA-SVR1 entry, display its context menu, and then select Hyper-V Manager.
5. In Hyper-V Manager, ensure that SEA-SVR1.CONTOSO.COM is selected.
6. In the Actions pane, select Virtual Switch Manager.
7. In the Virtual Switch Manager, in the Create virtual switch pane, select Private, and then select Create Virtual Switch.
8. In the Virtual Switch Properties box, specify the following settings, and then select OK:
   • Name: Contoso Private Switch
   • Connection type: Private network

Task 2: Create a virtual hard disk

1. On SEA-ADM1, in Hyper-V Manager connected to SEA-SVR1, select New, and then select Hard Disk. The New Virtual Hard Disk Wizard starts.
2. On the Before You Begin page, select Next.
3. On the Choose Disk Format page, select VHD and then select Next.
4. On the Choose Disk Type page, select Differencing, and then select Next.
5. On the Specify Name and Location page, specify the following settings, and then select Next:
   • Name: SEA-VM1
   • Location: C:\Base
6. On the Configure Disk page, in the Location box, enter C:\Base\BaseImage.vhd, and then select Next.
7. On the Summary page, select Finish.

Task 3: Create a virtual machine

1. On SEA-ADM1, in Hyper-V Manager, select New, and then select Virtual Machine. The New Virtual Machine Wizard starts.
2. On the Before You Begin page, select Next.
3. On the Specify Name and Location page, enter SEA-VM1, and then select the check box next to Store the virtual machine in a different location.
4. In the Location box, enter C:\Base, and then select Next.
5. On the Specify Generation page, select Generation 1, and then select Next.
6. On the Assign Memory page, enter 4096, and then select Next.
7. On the Configure Networking page, select the Connection drop-down menu, select Contoso Private Switch, and then select Next.
8. On the Connect Virtual Hard Disk page, select Use an existing virtual hard disk, and then select Browse.
9. Browse to C:\Base, select SEA-VM1.vhd, select Open, and then select Next.
10. On the Summary page, select Finish. Notice that SEA-VM1 displays in the Virtual Machines list.
11. Select SEA-VM1, and then in the Actions pane, under SEA-VM1, select Settings.
12. In the Hardware list, select Memory.
13. In the Dynamic Memory section, select the check box next to Enable Dynamic Memory.
14. Next to Maximum RAM, enter 4096, and then select OK.
15. Close Hyper-V Manager.

Task 4: Manage Virtual Machines using Windows Admin Center

1. On SEA-ADM1, select Start, and then select Windows PowerShell (Admin).
   

   Note: Perform the next two steps in case you have not already installed Windows Admin Center on SEA-ADM1.

2. In the Windows PowerShell console, enter the following command. and then press Enter to download the latest version of Windows Admin Center:
   CodeCopy

   Start-BitsTransfer -Source https://aka.ms/WACDownload -Destination "$env:USERPROFILE\Downloads\WindowsAdminCenter.msi"
   

3. Enter the following command, and then press Enter to install Windows Admin Center:
   CodeCopy

   Start-Process msiexec.exe -Wait -ArgumentList "/i $env:USERPROFILE\Downloads\WindowsAdminCenter.msi /qn /L*v log.txt REGISTRY_REDIRECT_PORT_80=1 SME_PORT=443 SSL_CERTIFICATE_OPTION=generate"
   

   Note: Wait until the installation completes. This should take about 2 minutes. If the web page does not respond, open services.msc and verify that the Windows Admin Center server is Started.

4. On SEA-ADM1, start Microsoft Edge, and then go to https://SEA-ADM1.contoso.com.
   

   Note: If the link does not work, on SEA-ADM1, open File Explorer, select Downloads folder, in the Downloads folder select WindowsAdminCenter.msi file and install manually. After the install completes, refresh Microsoft Edge.

   Note: If you get NET::ERR_CERT_DATE_INVALID error, select Advanced on the Edge browser page, at the bottom of page select Continue to sea-adm1-contoso.com (unsafe).

5. If prompted, in the Windows Security dialog box, enter the following credentials, and then select OK:
   • Username: CONTOSO\Administrator
   • Password: Pa55w.rd
6. On the All connections pane, select + Add.
7. On the Add or create resources pane, on the Servers tile, select Add.
8. In the Server name text box, enter sea-svr1.contoso.com.
9. Ensure that the Use another account for this connection option is selected, enter the following credentials, and then select Add with credentials:
   • Username: CONTOSO\Administrator
   • Password: Pa55w.rd

   Note: After performing step 8, if an error message that says You can add this server to your list of connections, but we can’t confirm it’s available. appears, select Add. In the All Connections pane, select sea-svr1.contoso.com, and then select Manage as. In the Specify your credentials dialog box, ensure that the Use another account for this connection option is selected, enter the Administrator credentials, and then select Continue.

   Note: To perform single sign-on, you would need to set up Kerberos constrained delegation.

10. On the sea-svr1.contoso.com page, in the Tools list, select Virtual machines, select the Summary tab, and then review its content.
11. Select the Inventory tab and verify that it contains SEA-VM1.
12. Select SEA-VM1 and review its Properties pane.
13. Select Settings, and then select Disks.
14. Scroll to the bottom of the pane and select + Add disk.
15. Select New Virtual Hard Disk.
16. On the New Virtual Hard Disk pane, in the Size (GB) text box, type 5, leave other settings with their default values, and then select Create.
17. Select Save disks settings, and then select Close.
18. Back on the Properties pane of SEA-VM1, select Power, and then select Start to start SEA-VM1.
19. Scroll down and display the statistics for the running VM.
20. Refresh the page, select Power, select Shut down, and then select Yes to confirm.
21. In the Tools list, select Virtual switches and identify the existing switches.

Exercise 1 results

After this exercise, you should have used Hyper-V Manager and Windows Admin Center to create a virtual switch, a virtual hard disk, a virtual machine, and then manage the virtual machine.

Exercise 2: Installing and configuring containers

Task 1: Install Docker on Windows Server

1. On SEA-ADM1, in the Tools listing for SEA-SVR1, select PowerShell. When prompted, type Pa55w.rd to authenticate using the CONTOSO\Administrator user account, and then press Enter.
   

   Note: This establishes a PowerShell Remoting connection to SEA-SVR1.

   Note: The Powershell connection in Windows Admin Center may be relatively slow due to nested virtualization used in the lab, so an alternate method is to run Enter-PSSession -ComputerName SEA-SVR1 from a Windows Powershell console on SEA-ADM1.

2. In the Windows PowerShell console, enter the following commands, and then press Enter to force the use of TLS 1.2 and install the PowerShellGet module:
   CodeCopy

   [Net.ServicePointManager]::SecurityProtocol = [Net.ServicePointManager]::SecurityProtocol -bor [Net.SecurityProtocolType]::Tls12
   Install-PackageProvider -Name NuGet -Force
   Install-Module PowerShellGet -RequiredVersion 2.2.4 -SkipPublisherCheck
   

3. When prompted to confirm the installation of modules from an untrusted repository, press the A key, and then press Enter.
4. After the installation completes, enter the following command, and then press Enter to restart SEA-SVR1:
   CodeCopy

   Restart-Computer -Force
   

5. After SEA-SVR1 restarts, use the PowerShell tool again to establish a new PowerShell Remoting session to SEA-SVR1.
6. In the Windows PowerShell console, enter the following command, and then press Enter to install the Docker Microsoft PackageManagement provider on SEA-SVR1:
   CodeCopy

   Install-Module -Name DockerProvider -Repository PSGallery -Force
   

7. At the NuGet Provider prompt, press the Y key, and then press Enter.
8. In the Windows PowerShell console, enter the following command, and then press Enter to install the Docker runtime on SEA-SVR1:
   CodeCopy

   Install-Package -Name docker -ProviderName DockerProvider
   

9. When prompted to confirm, press the A key, and then press Enter.
10. After the installation completes, enter the following commands, and then press Enter to restart SEA-SVR1:
    CodeCopy

    Restart-Computer -Force
    

Task 2: Install and run a Windows container

1. After SEA-SVR1 restarts, use the PowerShell tool again to establish a new PowerShell Remoting session to SEA-SVR1.
2. In the Windows PowerShell console, enter the following command, and then press Enter to verify the installed version of Docker:
   CodeCopy

   Get-Package -Name Docker -ProviderName DockerProvider
   

3. Enter the following command, and then press Enter to identify Docker images currently present on SEA-SVR1:
   CodeCopy

   docker images
   

   Note: Verify that there are no images in the local repository store.

4. Enter the following command, and then press Enter to download a Nano Server image containing an Internet Information Services (IIS) installation:
   CodeCopy

   docker pull nanoserver/iis
   

   Note: The time it takes to complete the download will depend on the available bandwidth of the network connection from the lab VM to the Microsoft container registry.

5. Enter the following command, and then press Enter to verify that the Docker image has been successfully downloaded:
   CodeCopy

   docker images
   

6. Enter the following command, and then press Enter to launch a container based on the downloaded image:
   CodeCopy

   docker run --isolation=hyperv -d -t --name nano -p 80:80 nanoserver/iis 
   

   Note: The docker command starts a container in the Hyper-V isolation mode (which addresses any host operating system incompatibility issues) as a background service (-d) and configures networking such that port 80 of the container host maps to port 80 of the container.

7. Enter the following command, and then press Enter to retrieve the IP address information of the container host:
   CodeCopy

   ipconfig
   

   Note: Identify the IPv4 address of the Ethernet adapter named vEthernet (nat). This is the address of the new container. Next, identify the IPv4 address of the Ethernet adapter named Ethernet. This is the IP address of the host (SEA-SVR1) and is set to 172.16.10.12.

8. On SEA-ADM1, switch to the Microsoft Edge window, open another tab and go to http://172.16.10.12. Verify that the browser displays the default IIS page.
9. On SEA-ADM1, switch back to the PowerShell Remoting session to SEA-SVR1, and then, in the Windows PowerShell console, enter the following command, and then press Enter to list running containers:
   CodeCopy

   docker ps
   

   Note: This command provides information on the container that is currently running on SEA-SVR1. Record the container ID because you will use it to stop the container.

10. Enter the following command, and then press Enter to stop the running container (replace the <ContainerID> placeholder with the container ID you identified in the previous step):
    CodeCopy

    docker stop <ContainerID>
    

11. Enter the following command, and then press Enter to verify that the container has stopped:
    CodeCopy

    docker ps
    

Task 3: Use Windows Admin Center to manage containers

1. On SEA-ADM1, in the Windows Admin Center, in the Tools menu of sea-svr1.contoso.com, select Containers. When prompted to close the PowerShell session, select Continue.
2. In the Containers pane, browse through the Overview, Containers, Images, Networks, and Volumes tabs.

Exercise 2 results

After this exercise, you should have installed Docker on Windows Server, downloaded a Windows container image containing web services, and verified its functionality.