Learn how to provision an Azure virtual machine and add it to your Azure account. Walk through the steps of creating and logging in to a basic virtual machine.
- [Instructor] Now that we know about many of the options that we have when provisioning an Azure virtual machine, it's time to create one on our own. From the main Azure dashboard, we're going to come over and click on the Virtual machines button, which is this one here that looks like a computer monitor. If you need to, go ahead and press the show text labels button here at the top and you can see the text label there is Virtual machine. I'll go ahead and click on it and this where it will display a listing of all the virtual machines that I currently have provisioned on my account. Now I don't have any right now, so I'd either go up to the Add button here at the top, or I can scroll down on my screen and click on the Create virtual machines button at the bottom.
When I click on either of those buttons, it brings up a window here called Compute, and I can scroll through and see all the different virtual machines that I can add into my account. The Azure marketplace includes many virtual machine configurations to choose from, and some that already include a license for SQL server, for instance, this one here called SQL Server 2016 Enterprise. Now I just want to start with a blank canvas first though. So I'm going to get started with a simple virtual machine that only includes the Windows Server operating system and nothing else. I'm going to come over here to the far left, and just click on the one that says Windows Server.
Then we'll get a listing over on the right of all the different configurations that include just Windows Server. Let's go ahead and scroll all the way to the very bottom and find the group of them that say small disk. The one that I want to load here is called Windows Server 2016 Data Center, and it's on a small disk. Let's click on that to see its details. This version of Windows Server 2016 only includes a 30 gigabyte OS disk, and that's going to be plenty for our needs here. Notice that I don't want to get the one that just says server core. If you click on that one, you'll see that this one only includes the core of Windows Server.
It doesn't include the graphical user interface. So let's go ahead and make sure I clicked on this one and then I'll press the Create button. Then I'll start the process of configuring the virtual machine and I've got four steps to move through, Basics, Size, Settings, and Purchase. Let's go ahead and start with Basics. Here we'll give our virtual machine a name, and remember this needs to be global-unique. I'll go ahead and type in the name kinetico, and just to make sure that it's unique, I'll just append a dash and then my initials aw at the end.
Then we can choose what type of disk we want to use, either a solid state drive or a hard disk drive. This is going to be the equivalent of the premium storage versus the standard storage. I'll go ahead and leave it on SSD. Then we'll set up a user name and password for the default user, and I'll go ahead and type in just a couple of characters for this password and you'll see that the password must have three of the following, a lowercase character, an uppercase character, a number, and one special character that's not a slash or a hyphen. Let's go ahead and type in a password that matches.
Then we'll go ahead and confirm that password. We'll choose our subscription type, either Pay-As-You-Go or the Free Trial. We'll establish this on the existing resource group that we created earlier in the course, and for me that's just called KinetEcoRG. Let's scroll down to Location where we'll choose our data center, and I'm closest to West US 2. Once those are all filled in, I'll press the OK button, it'll validate everything, and move us down to step two, Size. At the top of the Choose a size blade, we can choose our disk type that we want to use.
I'm just going to leave it on SSD. We can use a slider here to adjust the minimum number of vCPUs that we're interested in and they have the slider here for the minimum memory amount. Down below, we'll see different categories or different sizes of virtual machines that we can create that correspond to the choices that we made up above. Right now it's filtering to just the recommended, but if I wanted to, I could say View all. This will be a much more comprehensive list. Let's go ahead and just scroll back up to the top, I'll click back on Recommended, and I'm just going to choose the cheapest one here, which is going to be the DS1_V2 standard option.
This will include one vCPU and 3.5 gigabytes of memory which is going to be plenty for our needs. So we'll select that and press the Select button. That will finish step two and move us down to step three, Settings. At the top, we can configure a high availability setting if we want to. I'm going to go ahead and leave it set to None. For storage, I do want to use managed disks and that's the default option, so I'll make sure that's still selected as Yes. Here are our network settings, and I can change any of these just by clicking on them. Let's go ahead and use all the defaults and scroll down.
I'm not going to add any extensions. I don't want to enable auto-shutdown every day so I'll make sure that stays as off. Under Monitoring, I'm going to leave Boot diagnostics set to Enabled, and if I hover my mouse over this eye icon, we can see what that means. It's going to capture serial console output and screenshots to help us diagnose startup issues. I'll leave the default here for Guest OS diagnostics as Disabled, and scroll down just a little bit further, and that'll set up a diagnostics storage account, where I'll just choose that default name there. Let's go ahead and press the OK button.
Okay, it's been about five minutes or so and my deployment is now finished. Let's go ahead and close the notifications window and that leaves us with the overview screen for our new virtual machine. Now if you need to get back to this window, let's go ahead and close it real quick here, and start from the dashboard, if you click back over here onto Virtual machines, you'll see the listing of all the virtual machines that we have including the one that we just created. Let's go ahead and click on that, and that'll bring us back into the overview screen. Now to connect to this virtual machine and start using it, I'll come up to top and press the Connect button.
That'll download an .rdp file to my Downloads folder and if I click on that, that'll automatically load Windows Remote Desktop. I'll get this connection verification window that's saying that the publisher of the remote connection can't be identified. Do I want to go ahead and connect anyway? And I do, so I'll go ahead and press the Connect button. Then we'll type in the credentials that we established when we created the virtual machine, and this is going to be different from your Windows user account probably, so I'm going to click on More choices. Then we'll use a different account, and just type in the user name and password that we set up.
I'll press the OK button. Then I'll get another dialog box that says the identity of the remote computer can't be verified. Do I want to connect to it anyway? And again, it's talking about the certificates here, and we're just going to go ahead and say Don't ask me again for connections for this computer and press the Yes button. That'll launch Remote Desktop and connect me into my virtual machine. And now we can see that I'm connected to a Windows Server 2016 machine. It's going to automatically load the Server Manager here for me.
I don't need to configure any networks right now, so I'm just going to press the No button, and this is when we would use Server Manager to start configuring our Virtual Machine. When we're done working on it, go ahead and just close out of the Server Manager, and when we're done working with our virtual machine, you can just close Remote Desktop. Clicking on the X on the menu button will disconnect us from the remote session, I'll press the OK button, and that'll go ahead and close the session and return me back to my Azure dashboard. So that's how you can get started creating a new virtual machine and working with it in Remote Desktop.
This course is also ideal for anybody preparing for the Provisioning SQL Databases (70-765) exam, one of two exams necessary to earn an MCSA: SQL 2016 Database Administration certification.
- Deploying a Microsoft Azure SQL Database
- Planning for a SQL Server installation
- Planning for an IaaS or on-premises deployment
- Evaluating best practices for installation
- Provisioning an Azure virtual machine
- Deploying SQL Server using templates
- Managing SQL Server instances
- Migrating SQL Server databases to Azure VM
- Migrating client applications