CIS383 Lab 08 After reading chapter 08 in the textbook, complete the following and upload the results to D2L. Take only the screenshots of your work as indicated below and save them to a single Word or PDF document. D2L makes it really tough to grade PNG and other image files, so I will only accept Word/PDF.

You will need to replace the computer names and account names to those appropriate for your virtual environment. Review the screenshots standards document for any work requiring the use of a virtual machine. You may do this lab in your IA Lab VM or your own desktop. If you chose to do this in your own desktop, make sure to include your name in the screenshot (type it somewhere or whatever you need to do).

Installing a Linux OS 1. In the IA lab, create a new VM inside of the vApp that you have been using so far. This is the vApp with the windows machines, a pfSense firewall, and a blank Ubuntu VM. Note: You will need to either: create a new VM, install over the existing Ubuntu VM, or if all else fails, use the projects environment at http://projects.ialab.us. 2. When creating the VM, make sure to include your name in the machine name (e.g. mham-linux).

8-1: Navigating the Windows FS with CLI 1. Go through the lab 8-1 in the textbook. This lab can be done on your host computer or in one of the IA lab VMs. 2. When you finish the lab, take a screenshot of your command history. The command history can be gathered by typing doskey /history into the command prompt. 8-2: Navigating the Linux File System 1. On your newly created Linux VM, perform lab 8-2 from the textbook. 2. If you have not dealt with the Linux CLI before, this will be a good primer. Some of you have taken CSC150 and CSC250, so this may be a bit of a review.

8-3: Using Windows Task Manager 1. Go through lab 8-3 in the textbook. You can use your VM or local host machine for this lab. 2. When you get to step 10, where you are showing the CPU and Memory usage, open up Performance Monitor and create a graph that shows the same information. 3. Take a single screenshot of both the Performance Monitor and Task Manager windows side by side. 8-4: Displaying Linux Processes The most common way people view Linux processes and CPU usage is through the command line. This lab shows you how to do it through the GUI (which happens to be seemingly resource intensive) and through the CLI. 1. On your newly created Linux VM, go through lab 8-24 from the textbook. 2. When you get to step 7, you are introduced to the top command. Unfortunately, top does not show your output in a human friendly way (everything is displayed in kilobytes) Figure out how to make top show Megabytes instead. 3. Take a screenshot of your humanly readable top output. 8-5: Viewing DHCP Client and DNS Client Status 4. Go through lab 8-5 in the textbook. You can use your VM or local host machine for this lab. 5. Take a screenshot of the history of commands you used in the command prompt (steps 9-10). Remember, to show your command history you can use

doskey /history or simply press F7.

8-7: Mapping a Drive Letter This lab has you create a shared folder and connect to it from the same machine where you created it. That is a strange thing to do, so we are going to modify this to make it more realistic. Rather than connecting to the share from the machine it resides on, you will use a second machine to connect to the shared folder remotely. Think of it this way:

We have to machines: WIN01 and WIN02 The book will have you create the share on WIN01 Rather than connecting to the share from WIN01 (since its the same machine where the share is) we will connect to it from WIN02. While connecting to the share form WIN02, in the instructions, replace

localhost in the share path with the IP address of WIN01. 1. Go through Lab 8-7 from the textbook. For this lab, you should use your virtual machines in the IA lab. 2. On step 4, where you are connecting to localhost, log into your second Windows machine. Connect to the share from your second windows machine (replacing localhost with the IP address of the first windows machine). 3. When you reach step 12, take a screenshot of the mapped drive letter in My Computer before disconnecting from it.

WIN01 192.168.2.100 WIN02 192.168.2.101