- [Instructor] One of the original functionalities and likely one of the most popular functionalities of Azure are virtual machines. And the ability to create these virtual machines in a cloud solution. A virtual machine, essentially a virtual computer, that lives in this cloud environment is completely accessible and can be used exactly in the same way that you would use any type of computer in your internal environment. The only difference is virtual.
It doesn't have any hardware specifically associated to it. It can reside on many different types of hardware and it can moved around from one piece of hardware to another. Virtual machines can exist on your on premises network, using virtualization solutions such as vmware or Microsoft Hyper-V. You can have these virtual machines move around on your host virtual servers, on your internal network. But in the cloud we can create these virtual machines and have them live virtually in our Azure environment.
So let's go ahead and see how easy it is to create a virtual machine in Azure. All I have to do is click on my plus sign over here. Go under my Compute solution and go ahead and create a virtual machine. Now I can go ahead and click on one of these, or click on See all to see the complete list. But I'm going to X this out right now to show you a different way of creating virtual machines. Which will lead me to the same place, but has a second option that I want to highlight quickly.
See under Virtual machines, I can click here and then create a new virtual machine, which I will do in a minute. But right above, I've got another option called Virtual machines (classic). You'll remember from the previous video that we discussed the difference between resource manager or Azure RM solutions and classic deployment. A classic deployment where each object, or each resource is managed individually. And an Azure resource management solution were they can be grouped together. I like this solution because it allows me to put all of my resources into a single entity and then manage them as a single entity.
So again I'm going to click on Virtual machines, click on Add. And I'm being brought exactly in the same place that I would've been if I'd clicked on the Add button in the previous interface. Again here, I have different options of virtual machines that I can select. I can select Windows Server virtual machines. And if I click on this, it'll be a list of available Windows server operating systems. I can have non Microsoft operating systems like Red Hat and Ubuntu. So you can have your Linux servers run in Microsoft Azure cloud.
You can have complete solutions, were the machine is already pre-loaded with a SQL server. So SQL server, the Microsoft database server solution is installed on a Windows server. And that server could already be preloaded and preconfigured. I can also have Azure containers, will allows me to use the new virtualization solution of container services. So I can go down through this list of various solutions. Some of these are not provided by Microsoft.
You see some are provided by Microsoft, such as this Windows Server, some of them are not. Were you have complete solutions that are non Microsoft solutions that are built into virtual machine. For example I've got one below that you may recognize, which is Cisco. So you can have your Cisco routers run as virtualized solutions within your Azure deployment. You have non Microsoft database servers, you have anti spam servers, you have firewalls, you have automation solutions.
You have development servers. You have all of these various types of services that can be Microsoft or non Microsoft that can live within these virtual machines. Or can live as completely configured and self contained virtual machines. Some of those are for deployment and some of those are meant to be production. Like a SharePoint server, used for document managing. Some of them are used only for testing and they are meant to be a test version of a hardware solution.
So that you can completely run it as a virtualized solution to test it out and then you can buy the actual hardware from the provider and then deploy that hardware on your on premise network. So I'm going to go ahead and create a Windows Server type of virtual machine. I'm going to go down my list here, and you'll notice that I have various versions of operating system. Windows Server 2012, 2012 R2. I also have the brand new Windows Server 2016 and in that comes into the Nano Server edition, which utilizes very little resources.
That is a headless server. And I have also complete servers like Essentials Experience, which is essentially Windows server 2016 version of small business server. Although not as hefty a functionality, but it has a few little added on products. So I'm going to go ahead and create a Windows Server 2016 Datacenter server. Click on that. It asks me for my deployment model, which I'm going to pick my Resource Manager model.
Click Create. And then it gives me my basic settings. Now here I'll be able to go and configure and define the basic settings for this machine. First I'm going to give it a Name. So I'm going to call it LinkedINSRV1 and the type of disk that I want to be using SDD or typical hard disk drives, I'm going to go with SSD. I'm going to give it a name. Delfassy's going to be my User name and then I'm going to put my administrator password.
And notice that it verifies the security. Now, actually, I don't have enough characters here, so I'm going to increase the number of characters. And then confirm my password. Noted that this password will then be used in order to log on to the machine. That will be the administrator password of the machine. I'm going to use my existing resource group, that I've created in a previous task inside this course.
My location of where this virtual machine will be. Click OK. Then I get to choose the size of my virtual machine. So again it's going to go back to how much do I want to spend on this type of virtual machine? So I'm going to go with the lowest cost here, which is the DS1 Standard virtual machine. By the way V2 stands for a version two virtual machine. If I'm deploying a virtual machine in classic mode, I'd be selecting a version one virtual machine.
Then I've got my Storage account and here I've got my storage account that I created in a previous exercise. Or actually it's going to create a new storage account for me because it requires a premium. So you'll see that I specified an SSD type disk. So SSD type disk is going to create a new storage account. The previous storage account that I had created was a standard storage account and that one only supports hard disk drive. Which is why it's requiring me to create a premium storage account.
Next I've got my Network. So it's actually going to create a network for me. A Subnet, an IP address that will be used to access this virtual machine. A Network security group is essentially a set of rules for a firewall for security to the virtual machine. Then I can define a High availability set and I will talk about that in a later video on this course. And I'm going to to click on OK. I have my Summary window here. Which summarizes all of the settings that I picked. Including the User name I'll be using for log on to this virtual machine.
The type of tier for this virtual machine, that I have set, as well as the networks that are going to be automatically create for this virtual machine. I'm going to click on OK and the deployment is going to begin for this virtual machine. And I can take a little bit of time. I'm going to let this go and then in a later video in this course, we will actually go ahead and manage this virtual machine, after it's been created.
- Understanding Azure subscriptions
- Managing Azure with portals and PowerShell
- Configuring Azure web apps
- Deploying virtual machines
- Configuring virtual machines for high availability
- Managing Azure Active Directory
- Creating Azure virtual networks
- Implementing a VPN
- Performing Azure backups