Microsoft Azure AZ-801 — Section 15: Migrate on-premises servers to Azure Part 2

88. Installing an Azure Migration appliance virtual machine

And I want to look at migrating a server into Azure using Azure Migrate now. This is a bit tricky because in this case I’m running Hyper-V on a Windows client operating system in my virtual machines are running server.

So, what I actually need to do is I need to set up a server inside of a server, in other words, a nested server. I’ve already enabled nested virtualization the DC here and I’ve installed Hyper-V that was done previously. What I need to do though is I need to give this machine a lot more memory.

So, I’ve shut down my Server1 which had four gigs of RAM and I’m going to right click my DC here and go to Settings and we’re going to give it eight gigs of RAM. All right. Roughly. So, we’re use Intune Udacity put an 8000 here. And then what we’re going to do is start this up and we’re going to install a virtual machine on this server. All right. After booting up my NYC-DC1 here, I’ve got to download an ISO for installing a server, so I’m going to open up my web browser and we’re going to go to exam lab practice.com/ISO download. And I’m actually going to install a Windows Server 2019.

So, I’m going to click to download that ISO. And as you can see, it’s now downloading and I’ll just pause this recording while it’s downloading. All right.

So, that is officially downloaded now, and I’m going to go to my Server Manager tool. I’m going to go Tools and we’re going to go to Hyper-V, so we’ll go down here to Hyper-V manager. And as you can see, I don’t have any VMs. I’ve gotten rid of any VMs I had, and I’m going to create a new VMs, so I’m just going to click new virtual machine. I’m going to click Next and I’m just going to call this Server2019. Next, Choose Generation 1 or 2. All right. I’m going to go with Generation 1. I’m going to give this three roughly three gigs of RAM. We’re going to click Next. I’m going to connect it to my network adapter which is basically going to give it network access. We’ll click Next. It’s going to create a little virtual hard drive. That’s fine. Click Next and then ask me about the ISO for the operating system. So, we’re going to browse to the downloads folder. And there is the ISO. So, we’ll click Next and we’re going to click Finish. All right, so it’s now setting up the VM. And I will have to, of course, install the operating system. Right. So, we’re going to go right here and we’re going to right click and we’re going to start this up here. All right.

So, as you can see, it’s now officially starting. All right. That’s loading up. I’m just going to check the settings real quick. Right. And we’re going to do standard checkpoints. All right. And so I’m just going to let this boot up to the welcome screen. All right. From there, I’m going to click Next. We’re going to click Install. All right. Just waiting on it. The load here. All right, Now I’m going to choose to install server 2019 data center evaluation desktop experience. We’re going to click Next on that. All righty. Except the license agreement. Custom install. Take the default on partitioning. All right. And now it’s just copying the files over. I’ll go ahead and pause the recording while that’s happening. All right. My server, 2019 Virtual Machine, is booted up here, and I’m just going to put a password in for the admin. All right. That resolution is just a little bit crazy here just because. I’m performing Virtual Machine Inception here, Virtual Machine inside of a virtual machine. But it looks like it’s moving along just fine. All right. I’m going to go ahead and log on. Keep in mind, when I do that, I did have to hit the control, the lead up here. To trigger that. And we’re just going to log on as an administrator. And we’ve now officially got our server 2019 virtual machine set up and installed here. All right.

So, I’m logged on to my virtual machine. You’ll notice the is a little bit crazy. The resolution can be adjusted by right clicking the desktop and going to display settings. You can also go to the View menu and do the zoom level. But I’ll kind of I’m also going to warn you the configuration to get this computer, if you’re trying to connect this virtual machine to the Internet, it’s a little tricky. You actually have to set up a virtual switch and you have to enable NAT network address translation, which is going to allow the host, which of course is my NYC-DC1, which is actually sitting on another host, which is a Windows client operating system running Hyper-V. You’re going to allow this machine to be a NAT router to get your virtual machine out to the Internet. This server 2019, if I want to get it out to the Internet NYC-DC1’s got to act as a NAT router, so I had to actually configure this to make sure I had all my settings correct. And now I’m going to show you how to do it. All right. So, what I did is I went to I’m here on my NYC-DC1 Hyper-V go to my Hyper-V settings. Sorry, not Hyper-V settings, go to virtual switch manager and then I created a switch. So, I choose internal and I created a switch just called Internal Switch. And then I clicked. Okay, after that I right clicked my server 2019 box go to settings and I went down to network adapter and I connected it to the internal switch. Clicked. Okay. All right. The next thing I need to do is run some PowerShell commands.

So, I opened up PowerShell and I typed is you can right click start and go to PowerShell admin. That’s how I got in there. Then these are the commands that have to be ran to set this up. The first is the get network interface, net IP interface. And if I click this little link here after highlighting it, it’s going to show that. And then I need to know the exact alias name of my internal switch. So, that is the name of the internal switch.

So, then I type this command here and it’s creating. So, the real network that I’m on uses a one 9 to 168. I wanted to use a different IP address system than what I’m using on my real network, so there’s no conflicts. So, I set up a 172.162.1.1. So, it’s going to assign this switch, this IP address, 255.255.250. That’s the 24 prefix. And then it’s assigning it to that switch name. So, I did that in quotation marks.

So, I ran that command. Then I enabled NAT, which is this command here, new-net Nat-name my NAT network-internal IP address or it’s our internal IP interface address prefix and then the 172.162.1.0/24 network. And so at that point I hit Enter our I ran that. And that set all of it up. Now, after I’ve ran all that, I’m ready to go to my virtual machine and configure the IP address on the virtual machine.

So, here I am on server 2019. I’m going to right click down here in the lower right where the network icon is. I’m going to go to open network and Internet. And I’m going to go to change network or change adapter options. There is my adapter. Go to properties, I’m going to disable IP version six. I do that on all my interfaces because sometimes it interferes with what we’re doing here.

So, I’m going to do IP version four, go to properties and I gave it this address. 172.162.1.2. All right, 255.255.255.0. The gateway is my server 2022 server which is NYC-DC1. How do I know that? Well, if I go back over here and I do an IP config on my host computer, you can see that it’s the 172.162.1.1 which was actually set by this PowerShell command.

So, we’ll go back into our virtual machine here and that’s our gateway. And then I just set a DNS Google’s DNS server, which is 8.8.8.8, and that gives me Internet access. I should be able to even ping that 8.8.8.8 address. And that’s going to allow me to test to make sure I have an Internet connection. And I do. All right.

So, now I have got all of that network configuration stuff set up on my server 2019 box. All right. Next thing I’m going to do is just change the server’s name. So, I’m going to go down here to Server Manager. We’ll go to local server and you can see it gives it this name right here, like a random name, but I’m going to rename it to Server 2019. So, we’ll go to change and change the name to Server 2019. Click Okay. And of course it is going to need to reboot once this is officially done. All right, so I’ll click. Okay, click Close. I’m going to tell it to restart and I’ll pause recording while it’s restarting. Okay. The server is rebooted now and I did.

I’d failed to mention other thing that I did. Also disable the firewall on this machine. You can go in and create firewall rules for what you want to allow, but since I’m not really covering firewalls in this video a whole lot, I just disabled it. And the way I did that is I just went start and I went to settings. And then we’re going to go down here to update and security. And then to Windows security. All right. And then we’re going to go into firewall and network protection. And once that pops up, I’m going to scroll down and I’m going to go to allow an app through the firewall. Close out of this. And then I’m going to click right here where it says Windows Defender Firewall. And then turn windows to fire of Windows Defender Firewall off. And I just did that. All right. So, I did want to mention that. All right.

So, now we’ve got all of that set up and we’re just going to open up Server Manager. Okay? Now we’re going to install IIS Web services on this machine. So, we’re going to go to manage add roles and features next, next and next. And you’ll see this option here for Web server. So, we’re going to go ahead and select that. We’re going to click Next, next, next, next and install. It’s going to go ahead and let that get installed. All right. is officially done installing.

So, I’m going to hit Close and we’re just going to create a very simple little HTML web page just to make sure things are working.

So, I’m just going to hit start and type notepad. And we will open up notepad here, which for some reason is not showing up in my search but. That could just be because. My virtual machine is just a bit slow because it doesn’t have a lot of memory.

So, I just went to command prompt, went to went there to just type notepad. I’m just going to create a very simple little website web page. Using some HTML tags. It’s going to title is going to be Azure Migration. And we will do a closing tag and then a body tag. And we’ll go ahead and just make that bold and we’ll also make it big font. All right. We’ll say this is my theme from on-premises. All right. And then we’ll do a closing bold tag and a closing h one tag. And a closing body tag. There we go. And then we’re going to do a Closing Loops. We’re going to do a closing HTML tag. So, /html. And I think that should do it.

Now, we’re going to go file. We’re going to say save as. And we’re just going to save this to where the IIS Web service throws all its websites by default, which is in the c:drive\net\pub\w www\rootfolder. And we’re going to call this indexhtml. All right.

So, we’ll hit save close out of it. Let’s open up Internet Explorer. And I’m going to go to local host, which is my just a default server name here. And as you can see, it is working. This is my VM from on-premises. So, our little website is responding. Our web service is responding with the help of Internet information services.

Now, one thing I am going to do on my virtual machine so that my Internet Explorer will keep popping up messages about Internet Explorer needing to add a rule to the to the safe list for websites. So, I’m going to go to the local server here. We’re going to disable the IP enhanced security configuration.

So, we’re just going to turn that off so that it doesn’t keep popping up and having to deal with the little add button. That’s one of the things you’ll notice when you try to browse the Internet using Internet Explorer with this server 2019 box. So, I’ve just turn that off. Which should begin showing off here shortly. Currently, it’s still there it goes. So, now we are good to go there. All right.

Now, what I’m going to do is I’m going to just minimize my server 2019 box that’s going to bring you back to my NYC-SVR1 host machine. I’m sorry, NYC-DC1 host machine, and I am going to open up my web browser and I’m going to go back to portal.azure.com. All right. And we’re going to open up our Azure Migrate project here, which again, you can always go to menu, do all services and do a search for that and you can find it.

So, we’ll go into Azure migrate. All right. And once that is loaded up, we’ll go to here. It says servers, database and web apps. And I have my project that I’ve already created. All right. And we’ll scroll down. And so we have our Azure Migrate discovery and assessment or migrate modernization. We’re going to go to this Azure Discovery and assessment. So, right here we’re going to click Discover. All right. This would help us doing a discovery.

So, are you are your servers virtualize? So, yes, if it was VMs, VMware, vSphere Hypervisor. Yes. If it’s just Hyper-V physical. If you want to do physical, you would choose that. But I’m going to go with. Yes, with Hyper-V. All right. And the next thing is telling me is start by giving your appliance a name and generate the project key. The project key is needed during the configuration of the Azure migrate appliance. Additionally, during the step, some Azure resources will be created. Ensure that you have the required permissions. So, I’m going to call this migrationappelp. There we go. We’ll click Generate. And it is now going to generate this key.

Now, while that’s happening, I’m also going to download the Azure Migrate Appliance, which is a VHD file. This is about 12 gigs in size. So, this is going to take just a bit to download, but I’m going to go ahead and do that as well. All right, so we’ll click download. And I’ll pause the video while all that is happening.

The appliance VHD is now officially downloaded. I’m going to open up the File Explorer and go to downloads and there is the zip file for it. So, I’m going to double click on that and. I’m going to basically extract this folder you see here. So, we’re going to hit copy and we’re just going to paste it right here on our C drive. All right.

So, we’re still unzipping here. But what I’m going to do is I’m going to shut down my virtual machine, my Server 2019 Virtual machine, because we are going to have to adjust some memory in order to make this work, because we have kind of a limited amount of memory.

Now, we’ll tell you that in the real world, they tell you here that you really want to have at least 16 gigs of RAM for this appliance, but that’s if you are going to be doing a lot of migration and all that. In our case, since we’re just doing a small environment here, we’re not going to have to have that much memory.

So, I’m going to go over here and my server 2019 box is now shut down. I’m going to take that down on memory. All right. And we’re going to we’re going to try to we’re going to try to get away with. 1.5 gigs roughly. And I’m going to click New Virtual Machine. All right. And the virtual machine. This is going to be our appliance, right? So this Migrate app LP is going to be the name of my appliance. All right.

So, I’m just going to paste that in. I’m going to click Next Generation1. And then we’re going to do this 1500. On space. Not turning on dynamic memory. We’ll connect this to the internal switch. At that point, this is where we would point to the existing hard drive. All right. So, our zip is complete here.

So, now what we’re going to do is click browse on this and we are going to point to our C drive Azure Migrate appliance. We’ll go here to where it says virtual hard disk and double click on the hard drive. We’ll click Next, we’ll click Finish. And it’s now setting up that virtual machine, which is going to be our appliance. So, we’re going to go ahead and. Start that up. And it also checks the checkpoints on this real fast.

So, go down here. We’ll set this to standard check point. All right. And now I’m just going to let this boot up. It’s going to boot up to allow me to put a password in here shortly. All right, Now I’m just going to put my admin password in here that I want to use. All right. And we’re going to click Finish and it’s going to now finalize its settings.

Now, I’m putting in my admin credentials to log on to the appliance. All right. My virtual appliance is finally logged on here. And you can see there’s a couple of things right here on the desktop involving that, including the appliance configuration manager. But first thing I’m going to do is give it some Internet capability.

So, we’re right click the network icon down here, open network and sharing. I’m going to go to change adapter settings. And we’re going to configure. Static address on this box here.

So, that it matches our internal network, right? Just like we’ve done on our Server 2019 box. I’m also going to disable IP version six. I’m going to go to properties and we’re going to do 172.162.1.3. And then 255.255.255.0. Our gateway is 172 162.1.1 and our DNS server will just be the 8.8.8.8. We’ll click Okay. Let’s see if our gateway is not on the same network segment. What did I do wrong there? Oh, I put 168. That’s not good. We’ll click. Okay. We’ll hit Close. Uh, and. The next thing I want to do is. I want to. Check our connectivity. So, go in here and we’re just going to try pinging. 8.8.8.8. And I do have connectivity, so we’re good. All right.

So, when the virtual appliance actually starts up, it immediately pops open the Edge browser and tries to run a prerequisite check. But I’m just going to refresh it. And it couldn’t run the prereq against Azure because of the fact that it had no Internet connection.

So, we’re going to go ahead and just refresh something else we need to do here. We can we’ve refresh and everything it wants to know, the project key and all that. But we also need to make sure that our appliance is named this name right here, migrateappelp, which is what I called it.

So, I need to go back over here and we’re going to go back into Server Manager. Going to go here to local server and then click on computer name. And then click change. And let’s double check the name one more time, migrateappelp. All right.

So, let’s go ahead and do that. Migrateappelp. We’re going to click Okay. And of course it is going to want to reboot, so. We will have to do that. So, go ahead and wait on this. And then when it’s ready, I’m going to reboot it. Now, real quick, as I’m rebooting my server, I did want to point out that I did turn the server off and then I added up to 2048 megs, which is two gigs. So, it was just going a bit too slow and I wanted to give it just a little bit more memory. So, we’ll give that a shot and see if it moves a little smoother. All right. The virtual machine is rebooted and I open up edge and I’m visiting the I just opened up, went to the appliance little website here that’s built into the appliance which is https :// migrateappelp:. And then the port number is 443, 68. It did its connectivity check with Azure. Check time is in sync with Azure and then it wants to know my project, Project Key.

So, if you remember when we set up our project, went over here to servers on Azure.com in the in the Azure migrate. All right. And then we let’s just scroll down right here. And what we did is we click on Discover, right? And in Discover. We told it that were going to be doing this with a Hyper-V. Yes, with Hyper-V and then we generate a key. Well, we already have a key, so we can click manage existing appliance. All right. And this should detect the existing key. Yeah.

So, see appliance name is the migrateappelp. And then here’s the project key. Right? So I should be able to copy that. Right. And we’ll jump back over to this Tab and we’re just going to paste that in here. All right. Did take just a moment for this verify button to be able to be clicked. But now that it’s available, I’m going to go ahead and click it. And we will wait on this to get validated. All right. I’m finally ready to link this all with Azure.

So, here we are. We’re going to log in. Click the login button here and wait on that to continue. And that is it. We have finally linked our appliance to our project.

So, we’ve officially set up our Azure migration appliance here. All right. And so it’s a lot of steps took. It’s a long process, but that is how you actually can set up an Azure migration appliance.

89. Perform an Azure Migration discovery using a Migration appliance

So, I have my appliance connected here. And one thing I’ve done is I went here to add credentials and I added administrator and then administrator username, and then the password saved that. And then I clicked on add discovery source here. And I clicked on single item and I put in the IP address.

Now, there was one thing I did need to fix here. I need to make sure that my appliance is pointing to my NYC-DC1, my real IP address for DNS. So, if I actually jump back over to my NYC-DC1 box and if I go to Command Prompt or PowerShell or something like that, I can run IP config. And this is my real IP address right here. So, I’m going to put that in for DNS. Because it’s got to be able to resolve that name and get out to the Internet as well. It’s got to be able to do both.

So, what I did here? Is I just right. I’m back in my virtual machine now. I’m back in my appliance. I went to change adapter settings properties, and I changed. Put this to 192.168.1.1/27. All right. At that point. I clicked to validate that it had connectivity and all that. And I’m not doing anything with SQL Server instances, so I disabled that feature right here.

So, you’ll see this feature here. I disabled it, I don’t need that. And now I am ready to tell it to do a start discovery. I tried this just to test it out before and it failed. And the reason that it failed originally was because I did not have it pointed to DNS. I’ve forgotten to do that.

So, I went back and changed it. And now we’re going to hit start Discovery. All right. And we will let that run. And I will pause the recording while that’s happening. All right. So, our discovery has finally completed.

Now, I do recommend any time you do this in the real world, or even if you’re doing it in a lab environment, when this gets done, give it about 10 minutes after it finishes. Then you should be able to go into Azure and go to the Azure migrate. Right here and then go to servers and database web apps. And you should see that all this is starting to populate here. It’s still says Discovery is in progress, but I can see my appliances there. And the agent and all that is working properly registered appliances. And so all that looks good. Any assessments and all that’s been ran, Nothing’s been assessed just yet. I haven’t run any kind of assessments, but I can see my virtual machine. There’s two virtual machines running on that Hyper-V box server 2019 and migrate. I haven’t supplied any credentials for connecting into those. That’s why you’re seeing these little messages here. And I don’t have SQL or any of that. So, but everything is showing up just like it should.

So, that’s how you do a discovery.