Welcome back to Cyber Aires. Microsoft Azure Administrator A Z one of three course I'm Will Carlson. And this has Episode 29 Lennox Virtual machines.
In today's episode, we're going to clean up our previous Windows deployment to make room within our quotas. Remember quotas from a previous episode
to make room within our quotas for our linen lab set up,
we're gonna configure and deploy that Lennox workload. And then we're gonna go ahead and connects to that Lennox workload from albeit,
believe it or not from a Windows machine
getting right here into Azure to clean up our previous work, we can take advantage of resource groups. I'm gonna click on resource groups and you can see I have a whole host of resource groups here in my virtual in my lab environment. Rather.
And if you'll remember from the previous episode, Virtual Machine RG is the resource group that I set up in that episode, and you can see the virtual machine, a disc network interface public I, p address the network security group and the virtual network. And remember
azure armed templates and resource groups set all of this up
for me. All I had to do was walk through the Wizard and deleting all of these things is just a Z Z All I have to do this select elite resource group. Now you'll notice that there is an additional step here just to make sure this is an accidental dilation.
And now I can go ahead and delete. And although this takes a little bit of time, Azure is gonna go through via the arm a p I and delete all of these. Resource is
as soon as all these resource is air deleted, we're gonna jump back in and create our first linen virtual machine.
And now we can see that the resource group we created in the previous episode has been deleted along with all of the resource is contained in it.
So for a different approach to accomplish the same thing, we're gonna go ahead and create a resource group from the resource groups. Blade,
we're gonna leave that in my free trial subscription.
We're gonna call this Lennox RG.
We're gonna leave this U S central. Now I will point out again as a reminder that the region for the resource group is not where the resource is within that resource group are going toe live,
I can put Resource is within this resource group and regions all across the globe, and that is completely allowed.
All this means the region of the resource group is where the metadata for the resource group is going to exist again. If you have data location requirements for your organization, this is gonna be particularly relevant. Otherwise,
it's a semantic item that you'll probably never really encounter or need to mess with.
We're gonna go ahead and review and create this resource group,
and then we're gonna go back into virtual machines.
We're going to add a virtual machine, same as we did before. We're gonna leave this free trial, and we're going to select the resource group that we just created Lennox RG.
Now, this whole process is largely the same.
Except instead of a Windows
image, we're going to select Ellen Ex image.
We're gonna leave. This is a boon to server 18 0 for lt s
I'm gonna leave this d s to V three
and we're gonna come down to authentication type now for Lennox v EMS. We have a couple of different options. We can make this S S H Public Key. Or we can switch back to the more Windows centric password with password, recreate a user name and then username and password that we plug in.
Or we can leave it a more Lennox centric approach and create sssh public keys.
Now, here on a Windows machine, there are a number of different ways we can do this. However, if we were on a linen or a Mac OS machine, there would be built in command line tools already installed on those machines
for Windows machines, a great tool that you can download and uses going be Putty Jin. It comes along with the installer version of the Putty. Sssh tool. We're gonna skip that today. You can look up how to do that and how to use Putty Jin to generate an SS h key.
Where to keep that and how that all works. If you would like, we're gonna go ahead and leave this password for now. Although that's not the typical way you would connect to a Lennox work. Look,
we do need to go ahead and allow inbound ports very similar to the way we did with our Windows workload. But this time, we're not gonna open 33 89. We're gonna open. Sshh.
Now you'll remember hopefully from the previous video that we made. The only change we made here two discs was changing to standard Hard describes. We're gonna go ahead and do that now. No data disk for now.
Networking. We're going to leave it default
management. We're gonna go ahead and turn off boot diagnostics.
And now we're ready to review and create.
Now that we passed validation, we can go ahead and create this virtual machine and let the arm template do its magic.
Now that our resource group is all finished deploying, we can go to resource, just like we did with the Windows machine.
We were to go up here and click on Connect.
We don't care about our dp ing to this particular machine. Instead, we're going to connect Sshh!
And to do that from a Windows machine, we're going to use the putty utility. It's all I have to do here is type in the I P address.
I need to accept their certificate
and mark to log in as the credential that I set up during the creation of the virtual machine
you'll see in true form, regardless of an image I have to package that are currently needing to be updated, even though we just put up this virtual machine from a boot image.
But in spite of that, we were able to configure the virtual machine of Lennox Virtual Machine here in Azure, and we were able to use the Putty tool to connect to it from a Windows computer. So in today's episode, we step through the process of cleaning up our previous work from the Windows Virtual Machine episode, using the power of resource groups.
We also step through the process of configuring Olympics virtual machine talking about the one
primary area where that's going to be different. And that's the option of using an SS H key to allow us to access the virtual machine. Discuss that for the Windows side. Putty Jen is a good tool to use to do that,
and we also used putty to connect to that Lennox virtual machine from a Windows host.
Coming up next, we're going to talk about the concept of virtual machine extensions and how they can help us do some of the post of deployment work. So the configuration steps after we've created a virtual machine don't have to all be manual. You can use a number of extensions
to go ahead and get that additional configuration work done as well,
obviously, with a goal here of automating as much of the process as it is possible. Thanks for joining me today, and I'm excited about the virtual machine extension episode coming up next.