LAB6 - Applications and Hyper-V Virtualization ANSWER KEY.pdf

# LAB6 - Applications and Hyper-V This lab will guide you through the following tasks: - Compatibility Mode - Hyper-V - Hyper-V Networking # COMPATIBILITY MODE Download a copy of the \\192.168.215.30\Volume 1\Course Material\Networks 1\OLD APPS folder onto your desktop and install all 3 applications. Right click any of the 3 programs shortcut or .EXE → properties → Compatibility tab - Run Compatibility Troubleshooter - Tell the troubleshooter that the program will not run properly - Pick any reasons you want and allow the Compatibility Troubleshooter to make changes - Does the program shortcut or .EXE → properties → Compatibility tab have some boxes checked off now? - NOTEPAD++ > REQUIRE ADDITIONAL PERMISSIONS > WORKS - RUN AS ADMINISTRATOR Play with the Compatibility options with the other applications by opening and closing the applications with different Compatibility options selected. - Are you able to find any combinations of Compatibility setting on an application that changes the way the application is displayed or runs? | Program | Compatibility Option | Result | | ---------- | -------------------------------------------- | ----------- | | NOTEPAD++ | Run in 640x480 SCREEN RESOLUTION | BIG SCREEN | # HYPER-V We will use Virtualization to create some Virtual Machines that will be used to explore all of the cool features and benefits of using Virtualization. First, we need to check and make sure our computer is compatible with the required supporting technology. Configure your STATIC IPv4 address on your Host Network Card before continuing. 192.168.215.x (x = 50 + computer number) Check each component to make sure your computer is compatible with Hyper-V and write down how you checked. | REQUIREMENT | WHAT WE HAVE\HOW YOU FOUND OUT | MEETS SPEC | | ---------------------------------- | ---------------------------------------------- | ----------- | | X64 Windows PRO, ENT or EDUC | WinVER > WINDOWS 11 ENT x64 | YES | | SLAT Processor | Task Manager > Performance > CPU > Virtualization = ENABLED | YES | | > 4GB RAM | MSINFO32 > INSTALLED PHYSICAL MEMORY > 8GB | YES | | Virtualization Enabled in BIOS | BIOS > OVERCLOCKING > ADVANCED CPU > (DEL) > SUM MODE = ENABLED | YES | ## Install Hyper-V - Type "appwiz.cpl" in your Search bar - Turn Windows Features On or Off - Select all Hyper-V boxes and OK - Hyper-V GUI Management Tools - Hyper-V Module for Windows PowerShell - Hyper-V Hypervisor - Hyper-V Services - Reboot your computer! All components of Hyper-V should now be enabled and the Hypervisor Service will support the virtual environments. We will create TWO virtual machines and then create all THREE types of VM NETWORKS. You must create 2 70 GB Partitions on your hard disk. 1 for each Virtual Machine to use. - WINDOWS (E:): 83.57 GB NTFS, Healthy (Primary Partition) - WIN C1 (H:): 70.00 GB NTFS, Healthy (Primary Partition) - WIN_C2 (I:): 70.00 GB NTFS, Healthy (Primary Partition) # CREATE YOUR FIRST VIRTUAL MACHINE! Make sure you READ each screen and try to relate what each option is talking about before making your decision. We will make a second one later. 1. Download a copy of ANY of the .ISO files located at \\192.168.215.30\Volume 1\Course Material\Networks 1\ISO onto your desktop. - (Windows 7, Windows 8, Window10) / (Server 2016, Server 2019, Server 2022) 2. Type "hyper-V Manager” into the Search Window and set three methods of having the tool available for future use: - Open file location and drag a copy of the shortcut to your desktop. - Pin to Desktop - Pin to Taskbar 3. Open Hyper-V Manager, click on New in the right Actions pane, then select Virtual Machine. a. Before You Begin: (NEXT) b. Specify Name and Location: 1. Name: = WIN_C1 2. Check the box for Store the virtual machine in a different location → BROWSE to your first 70GB partition and create a folder on the root of that drive named WIN_C1 → SELECT FOLDER → NEXT c. Specify Generation: - Choose Generation 2 for modern operating systems that support UEFI. - Check the chart on the bottom of the notes to answer your question. d. Assign Memory: - Startup memory: = 4096 MB - Check Use Dynamic Memory for this virtual machine - This will allow the VM to adjust memory based on demand. e. Configure Networking: - Connection: = Default Switch f. Connect Virtual Hard Disk: - Create a virtual hard disk: - Startup memory : = 4096 MB - Location: = BROWSE to your folder named WIN_C1 - Size: = 70GB g. Installation Options: - Install an operating system from a bootable → IMAGE FILE → BROWSE → Select the .ISO you copied to your desktop. - Startup memory: = 4096 MB 4. Review your settings and click Finish to create the VM. # CONFIGURE YOUR FIRST VIRTUAL MACHINE! 5. Right click your Virtual Machine in the Virtual Machines Windows of Hyper-V Manager → Settings - i. Processor - a. Number of virtual processors: = 2 - b. APPLY # START YOUR FIRST VIRTUAL MACHINE! We have created our first Virtual Machine. We need to configure 1 more option and start the machine. Once we start the virtual machine it will quickly begin to take away from our host computer systems RAM, CPU and DISK resources! OPEN TASK MANAGER > PERFORMANCE TAB → Monitor RAM, CPU and DISK activity when your Virtual Machines are running 6. Install your Operating System on your VM: - i. User Account: Student - ii. Password: Room215 # USE YOUR VIRTUAL MACHINE TO ANSWER THE FOLLOWING QUESTIONS" - How do you insert CTRL – ALT – DELETE on a Virtual Machine? - [Icon] - TOP LEFT TOOLBAR - Right click your Virtual Machine in the Virtual Machines window of Hyper-V Manager → Checkpoint - In the Checkpoints window, rename the newly created Checkpoint = FRESH INSTALL - Make some changes to your desktop by adding files and dragging shortcut icons - Right click your FRESH INSTALL CHECKPOINT → APPLY - Where would this feature be useful in terms of a student performing lab work? - Making a checkpoint at start of course before critical changes to the VM. (Time machine) # HYPER-V NETWORKING You may need to manage your available disk space on your host so that we can squeeze a second Virtual Machine on your disk to play with Hyper-V Networking. Follow the EXACT steps as you did when creating your first Virtual Machine except for: - b. Specify Name and Location: - 1. Name: = WIN_C2 - 2. Check the box for Store the virtual machine in a different location → BROWSE to your second 70GB partition and create a folder on the root of that drive named WIN_C2 → SELECT FOLDER → NEXT - c. Connect Virtual Hard Disk: - Create a virtual hard disk: - a. Startup memory: = 4096 MB - b. Location: = BROWSE to your folder named WIN_C2 - c. Size: = 70GB You can manage your Hyper-V Networks by selecting Virtual Switch Manager in the Actions window of Hyper-V Manager console. Change both Virtual Machines to use each type of Networking (Internal, Private, External) before answering each question. Make sure ALL FIREWALLS ARE OFF on all Virtual Machines and your Host computer ## INTERNAL (DEFAULT SWITCH) | DEFAULT SWITCH | WIN_C1 | WIN_C2 | HOST COMPUTER IPV4 ADDRESS | | ----------------- | ----------------------------- | ----------------------------- | ----------------------------- | | IP ADDRESS | 172.30.125.205 | 172.30.143.32 | 172.30.128.1 | | SUBNET MASK | 255.255.240.0 | 255.255.240.0 | 255.255.240.0 | | DEFAULT GATEWAY | 172.30.128.1 | 172.30.128.1 | ----------------------------- | | DNS SERVER | 172.30.128.1 | 172.30.128.1 | ----------------------------- | - Can your Virtual Machines ping each other? YES - Can your Virtual Machines and Host ping each other? YES - Can your Virtual Machines ping the internet by 8.8.8.8? YES - Can your Virtual Machines ping the internet by DNS? YES - Can your Host Machine ping the internet by 8.8.8.8? YES - Can your Host Machine ping the internet by DNS? YES This does not look like the results we should get. The INTERNAL (DEFAULT SWITCH) uses NAT to use the Host computer as a router. Remove the INTERNAL (DEFAULT SWITCH) and create a new INTERNAL SWITCH named INT SWITCH. Change all your Virtual Machines to use this new switch. You may have to release and renew the IP addresses to get the desired changes on the Virtual Machines. ## INTERNAL (INT SWITCH) | DEFAULT SWITCH | WIN_C1 | WIN_C2 | HOST COMPUTER IPV4 ADDRESS | | ----------------- | ----------------------------- | ----------------------------- | ----------------------------- | | IP ADDRESS | 169.254.184.53 | 169.254.210.17 | 169.254.44.46 | | SUBNET MASK | 255.255.0.0 | 255.255.0.0 | 255.255.0.0 | | DEFAULT GATEWAY | ----------------------------- | ----------------------------- | ----------------------------- | | DNS SERVER | ----------------------------- | ----------------------------- | ----------------------------- | - Can your Virtual Machines ping each other? YES - Can your Virtual Machines and Host ping each other? YES - Can your Virtual Machines ping the internet by 8.8.8.8? no - Can your Virtual Machines ping the internet by DNS? no - Can your Host Machine ping the internet by 8.8.8.8? YES - Can your Host Machine ping the internet by DNS? YES This is the way an INTERNAL VM Switch is supposed to work! Remove the INTERNAL (INT SWITCH) and create a new PRIVATE SWITCH named PRI SWITCH. Change all your Virtual Machines to use this new switch. You may have to release and renew the IP addresses to get the desired changes on the Virtual Machines. ## PRIVATE (PRI SWITCH) | DEFAULT SWITCH | WIN_C1 | WIN_C2 | HOST COMPUTER IPV4 ADDRESS | | ----------------- | ----------------------------- | ----------------------------- | ----------------------------- | | IP ADDRESS | 169.254.184.53 | 169.254.210.17 | ----------------------------- | | SUBNET MASK | 255.255.0.0 | 255.255.0.0 | ----------------------------- | | DEFAULT GATEWAY | ----------------------------- | ----------------------------- | ----------------------------- | | DNS SERVER | ----------------------------- | ----------------------------- | ----------------------------- | - Can your Virtual Machines ping each other? YES - Can your Virtual Machines and Host ping each other? no - Can your Virtual Machines ping the internet by 8.8.8.8? no - Can your Virtual Machines ping the internet by DNS? no - Can your Host Machine ping the internet by 8.8.8.8? YES - Can your Host Machine ping the internet by DNS? YES This basically uses APIPA to accomplish its goal of isolating the Virtual Machines away from the Host machine and the internet. Remove the PRIVATE (PRI SWITCH) and create a new EXTERNAL SWITCH named EXT SWITCH. Change all your Virtual Machines to use this new switch. You may have to release and renew the IP addresses to get the desired changes on the Virtual Machines. ## EXTERNAL (EXT SWITCH) | DEFAULT SWITCH | WIN_C1 | WIN_C2 | HOST COMPUTER IPV4 ADDRESS | | ----------------- | ----------------------------- | ----------------------------- | ----------------------------- | | IP ADDRESS | 192.168.215.149 | 192.168.215.150 | 192.168.215.112 | | SUBNET MASK | 255.255.255.0 | 255.255.255.0 | 255.255.255.0 | | DEFAULT GATEWAY | 192.168.215.1 | 192.168.215.1 | 192.168.215.1 | | DNS SERVER | 192.168.215.10 | 192.168.215.10 | ----------------------------- | Use NCPA.CPL to check your network settings on your Host machine. What changed? PHYSICAL NEW HAS NO IPV4 SETTINGS. A VETHERNET (EXT_SWITCH) IS CREATED AND HAS MY STATIC IPV4 CONFIGURATION. What piece of information is missing from the “new” network adapter on your host machine? no DNS! This will happen EVERY time you create an External Virtual Switch. Fix this now before continuing. - Can your Virtual Machines ping each other? YES - Can your Virtual Machines and Host ping each other? YES - Can your Virtual Machines ping the internet by 8.8.8.8? YES - Can your Virtual Machines ping the internet by DNS? YES - Can your Host Machine ping the internet by 8.8.8.8? YES - Can your Host Machine ping the internet by DNS? YES # BONUS QUESTIONS Try some of the features of Hyper-V. - Remove 1 machine completely from your system - Configure 1 machine to have 8192 MB of RAM and 4 processors - Configure your virtual machine to have a second network card installed - Try exporting your virtual machine and importing onto another computer in the classroom

LAB6 - Applications and Hyper-V Virtualization ANSWER KEY.pdf

Document Details

Related

Full Transcript

Upgrade to continue