1,576
edits
Changes
Undo revision 155869 by Chris.johnson (talk)
# Click on the '''Go to resource''' button at the bottom left of the page and move on to the next section of the lab.
== Part 2: Accessing Your Windows VM Remotely Using Bastion RDP ==
[[Image:Ops705_lab2_fig6.png|thumb|right|275px|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's browswer. It's a very simple process.# In the ''Overview'' tab for the Virtual Machine created in Part 1, click the '''Browser connectConnect''' button. This will download an RDP profile file (usually ''vmname.rdp'').# A new dialog blade pops up asking for Open the RDP file. It should launch the Remote Desktop application and automatically try to connect to your VM.# Upon opening, the VM's URL, port number, and username and passwordare automatically provided. # Type in the ones password you used to create this when creating the VM in Part 1.# It will launch browser tab and automatically try to connect to your VMAccept the certificate warning. (If your username and/or password are wrong, it will fail. Try againClick yes.)
# You should see a login progress screen, and a Windows Server desktop after a few moments.
# Congratulations! You've set up a Windows Server VM and logged in remotely.
# Open Notepad, and write <code>My name is ''insertFullName'', and I've completed the Lab 1 5 Windows Server VM investigation!</code> Save the file to your VM's desktop, with the filename ''yourSenecaUsername.txt''.# '''Do not skip Part 3 at this stage! Otherwise, you'll be bleeding money funds by leaving the VM running.'''
== Part 3: Fully Stopping Your Windows Virtual Machine ==