1,576
edits
Changes
→Lab Submission
In this lab, you will learn how to create Windows and Linux virtual machines using a pre-built image, how to remotely connect to each, and basic management of these VMs from the Azure web interface. These two VMs will be used extensively in your later labs. This lab assumes you have completed [[OPS705_Lab_1 | Lab 1]] successfully. Refer back to that lab for reminders on the basics of the Azure Dashboard interface.
While you are working through this lab, it is highly recommended that you write notes down in your OPS705 Lab Logbook. These are general notes and commands to help you remember how to do this lab. Each lab has its own page in the logbook. You may use this logbook your notes during all quizzestests, so fill it out accordingly!
If you encounter technical issues, please contact your professor via e-mail or in your section's Microsoft Teams group.
# Your Seneca Azure login credentials
# Your linked mobile device for 2FA
= INVESTIGATION 1: Managing a Windows Server 2016 VM in Azure =
== Part 2: Accessing Your Windows VM Remotely Using RDP ==
[[Image:Ops705_lab2_fig6.png|thumb|right|250px275px|Figure 2. The ''Remote Desktop Connection'' application on Windows.]]
In this section, we'll discover how to remotely connect to the Windows Server's desktop environment over the Internet from your computer.
# In the ''Overview'' tab for the Virtual Machine created in Part 1, look for the '''IP address or FQDN''' entry. This is the address you will use to connect later in this section. Write it down (Hover over the URL, and you'll see a ''Copy to clipboard'' icon).
# '''Do not skip Part 3 at this stage! Otherwise, you'll be bleeding funds by leaving the VM running.'''
== Part 3: Shutting Down Fully Stopping Your Windows Safely Virtual Machine ==[[Image:Ops705_lab2_fig7.png|thumb|right|400px375px|Figure 3. The Overview page blade for the winserv VM. Notice its status as ''Stopped (Deallocated)''.]]
This section is fairly simple. The one thing to never forget: Ensure your VM's status is set to '''Stopped (Deallocated)'''.
# In the ''Overview'' blade of your Windows Server VM, click on the '''Stop''' button.
# Don't worry about going into the Windows OS and shutting down first. Azure sends a signal to the VM to shut down safely.
# If your VM status says stopped, but does not include the '''(Deallocated)''' text, then resources are still being held by the VM and we're still being charged. The stop button will still be available, so click it.
= INVESTIGATION 2: Managing a CentOS Linux VM in Azure =
# '''Choose a base:''' CentOS-based 7.8
# '''Virtual machine name:''' yourSenecaUsername-lnx# '''User name:''' yourSenecaUsername-lnx
# '''Authentication type:''' Password
# '''Use a saved secret:''' Unchecked
# In the password field, type the password you gave when creating the VM. (You won't see anything as you type here; that's normal.)
# If login is successful, you should see a prompt like this: <code>[cjohnson30@cjohnson30-lnx ~]$</code>
# To prove you've completed this section, run the following: <code>echo "My name is ''insertFullName'', and I've completed the CentOS investigation!." > ~/lab2.txt</code># To quit, type <code>exit</code>. '''Don't do this, yet! Move to Part 3.'''
On macOS/Linux Using Terminal:
# When prompted for a password, use the one you gave when you created the VM. (You won't see anything as you type here; that's normal.)
# If login is successful, you should see a prompt like this: <code>[cjohnson30@cjohnson30-lnx ~]$</code>
# To prove you've completed this section, run the following: <code>echo "My name is ''insertFullName'', and I've completed the CentOS VM investigation!." > ~/lab2.txt</code># To quit, type <code>exit</code>. '''Don't do this, yet! Move to Part 3.'''
== Part 3: Shutting Down Fully Stopping your CentOS Safely VM ==As with the Windows Server VM, shutting down safely fully deallocating your VM is paramount for keeping your data and OS safeessential to responsible usage.
That's it!
In this quick investigation, we'll walk through how to directly manage virtual machines from the Azure Dashboard interface on a basic level. This is useful for starting up VMs, shutting them down when unresponsive, and deleting them when you're finished. ('''Warning:''' Do not delete either VM created in this lab!)
== Part 1: Powering On / Restarting A Virtual Machine ==
From the ''DevTest Labs'' blade:
# Click on the ''My virtual machines'' menu bar item.
# Click on the virtual machine you'd like to manageto move to its ''Overview'' blade.
# Click the '''Start''' menu button near the top.
From the ''DevTest Labs'' blade:
# Click on the ''My virtual machines'' menu bar item.
# Click on the virtual machine you'd like to manageto move to its ''Overview'' blade.
# Click the '''Stop''' menu button near the top.
== Part 35: Deleting A Virtual Machine Note About Resource Usage ==As mentioned during our lecture and throughout this lab, using resources responsibly is incredibly important. We pay for what we use. While we have a failsafe in place to stop all VMs at 2:00am EST daily, don't rely on it! Fully stop your VMs when you're not using them.
= Lab Submission =
[[Category:OPS705]]
[[Category:Digital Classroom]]
[[Category:Fall 2020]]
