Hello everyone. Welcome to this recording of my theater session at Microsoft 825 migrating VMs from VMR or HyperV to Ashure local with ash migrate. My name is Yanto Person. I'm a managing consultant and spearhead here in Norway. I'm also a Microsoft cloud and data center MVP and Ashure hybrid. So what I'm going to be talking to you today is just a migrate and what it can do for you when it comes to migrating from VMware or HyperV and mostly of this session will be demo. So let's get into it. There are different options when migrating uh from via from VMR. You can migrate to the cloud as either SAS or pass to start modernizing. But that's not what we're going to be talking about. We want to talk about migrating to Ashure local and you do have a few options but mainly what we're going to talk about is Azure migrate but you do have options like third party products to migrate even backing up and restoring with certain backup vendors do work. Yeah. So what Asher Migrate actually does is and if you're familiar with with Ashure migrate mig migrating to Ashure this is basically the same appliance functionality. It's a seamless migration from VMware to Ashure local where you deploy an appliance on your VMware environment but you also deploy a appliance on the Asher local which is then the target appliance. There is no need for you to do anything uh prior to migrating unless you want to keep your private IP address. I'll talk a little bit about that and going forward in the demo and then and everything is a guided workflow from Ashure and it's quite well documented how to deploy this and how to work with with this. When migrating there are a certain principles you need to adhere to. It's like you need to plan the migration. You need to of course provision your ashure local environments before you start doing anything. You need to connect your Ashure migrate appliances and then migrate the workloads and at the end attach any Azure services that you want to use uh with the newly migrated VMs. Since you when you're using Azure migrates, the machines will be ARC enabled and available for you to see them in Azure and use uh any Asha services that are available for um Ashure Arc machines. you can do um a listless for the VMware VMs as well and where it can um identify and see what kind of applications you have and find dependencies within this. But you don't need to do this. You can just migrate the VMs as a normal V VM without doing any discovery of what's inside the VM. So let's just jump over to um the process. So you basically just deploy and configure the Azure migrate appliance. You start the rep the replication and then you do the test migration and migrate over. This is just a brief overview of what the um what uh the appliance does and what the different components within the entire process does. And if you look at the appliance uh down on the left side for the on-remise from your V for from your VMware you can see that any traffic of storage goes directly between the two action migrate appliances. It says it goes from the migrate appliance source to the storage but it goes through the target appliance and then gets uh downloaded to the uh storage. And as you know, if you're familiar with Astra Migrate, the uh migration will be continuously running until you've you decide to do a failover or a planned migration over to um to Azure local. There are of course some limitations that I talked about for uh guest management has to be enabled post migration. If you want to use static IP migration, this must be configured on the VMs prior to migration for a non-SDN Azure local instance. Um, secure boot is not maintained across migrations and any previous ARC agents has to be uninstalled. So if you've got if your VMs are ARC enabled uh that has to be uninstalled prior to the m to the migration as um it will read the machine and if there is an object with the same name it will fail to uh do the migration. So let's dive into the demo. Now since this session was 25 minutes I had to uh do a recording as the the the task here takes about an hour to hour plus to go through. Uh so let's just start in so let's go to a migrate and let's create a project. Let's uh create a new resource group. Let's uh call the project something and let's place it in the region where you want to have it. for me that was uh Europe. And then let's just click create. Now this takes a while. Uh and that's why the recording is um sped up a bit. Once it's um created, we can go into all projects and have a look at it and see what we have here. As this is brand new, we don't have anything. So let's click on start discovery and look for using an appliance for ashure local and let's click that we want to do from VMware. Let's create a name for the appliance and generate the key. Oh, and of course there's some name limitations here on the length. So, yep. Now, I recommend you download the OVA file uh to um to set this up. This is a predefined Windows Server appliance uh with the um with with the migration appliance already um configured and installed. You can do the zip file and and install it yourself, but it's quite a lot more uh work to do to do that. So let's jump into the appliance. Let's copy the file over the one you downloaded and let's create the appliance in uh vsenter. So find the file where you stored it. and then just follow the wizard. For most of you are familiar with this. So let's just go through this. Well, hope hopefully you're familiar with this. If not, then this is pretty straightforward. So next, next finish done. Then power on the appliance. and let's connect to it. Now remember if you download the um install files there is a limitation. You cannot use anything newer than Windows Server 2019 as the um the Ashure Migrate appliance files are limited to that version at the moment. So let's log in set the static IP on the um on the machine. Yep. Now the appliance has started. You can see the um the web browser here. It checks connectivity to Azure. Now it is important that you have the correct firewall rules open to Azure. So if so if you have strict um strict firewall rules uh it is important that you find the correct firewall ports to open for the IP address of the appliances. Now copy the key that was generated and put that into the um browser here and verify that code. Ah, of course since the VM I can't paste that through the console, you should log in, of course. Now, when you first uh verify the code, it will start doing um update of the appliance if it needs to. As you see, it's um it has the auto update status. Now, you have to log in to Ashure. So, copy code and login. Um, I do the URL and copy that out into a um, separate browser that has already been log logged into and then just paste the code in here. Now, another thing you need to do is you need the the the VMware uh virtual disc development kit and you need an active uh VMware license or and support or support contract to be able to get this and uh you need at least 8.0 to be downloaded. Um and 8 8.3 works fine, which was the latest one during this demo. And then you need to copy the the DL file to the correct path. Then verify it is fine. Now that's done. Let's provide the credentials for the Vsenter appliance. Make a name for it and to use the username and password. Let's add the the Vsenter appliance as well. Um the FQDN and then of course make sure that the correct uh credentials are mapped but since we only have one uh that will be the default one. Now it will validate the connection to Vsenter that was fine worked fine guest services is enabled by default but you need to uh add credentials for that. So I just disable that. We don't need that for just a pure VM migration. And now we can start the discovery. Uh the discovery uh of the VMs can take a while depending on the number of VMs you have and so on. So let's onboard do the onboarding to Azure local as well. Just add the information of the the cluster and then the domain and username. Yep, the discovery. You can see that everything is green. So, it says that uh the discovery is completed successfully. So, let's go back to the uh Astra migrate and we can close this and go back. And if we go now into the project, we should now see that um we have some information here. Sometimes you need to refresh the the the Asha migrate and go back in in and out and then you should be able to see uh what you have. Sometimes the portal is not always updating correctly. And as you can see here, we have eight virtual machines uh indexed and showing. The previous one we saw was the new version and this is the old version. So now we have all our inventory here. So now that we have all the machines um imported, we can actually set up the the the migration the target uh the target upline. So let's click on the replicate and say we want the virtual machine we want to do to ashure local the virtual but it says it says is not supported, right? So let's let's see why why that is because we need to configure the um the target appliance right it we don't have a target appliance uh configured so let's do that as well it is basically the same way as with the um with the VMware appliance but now we will just download a VHD file instead and we need to import that into the HyperV server and the appliance should be on the um the appliance should be on the uh ashure local cluster nodes on one of them. So what you do is you copy the the folder and then you import the VM from HyperV manager. So you browse to the folder where the uh on the cluster share volume where the um where you copied the files to. So I go into virtual machines here and click select folder then click next. Next. Yep. Just register the machine, connect it to a network switch, and then click finish. And if you get the question about disks, then you can uh browse to the to the path where the VHD file is. But as you can see here, it is okay. Let's add um a network adapter to it or just started. So let's see here. Let's add an IP address to this machine as well. Um it's nice to have an a static IP address. Now this machine we didn't set the VLAN because it will be on the same subnet as the um as the HyperV host. Let's log into it because we need to do the same thing here with the uh web browser and go through the setup of the of the appliance. And again it checks uh connectivity to Ashure and checks if the time is synced with the correct time. It will do an update which takes it says around 5 minutes but my experience is it takes more than 15 minutes sometimes to do it. Now add the information about the um Asha local cluster. And if you enter the the information correctly, it will uh then become green here because it will automatically really fast say validated because the credentials and everything is okay. And now we can click on configure here. But we haven't logged in. That's the thing. You saw it was gray down there because we jumped over a step and that was we had we didn't log into Asher. So, let's log into Asher. Do the same thing as before. Copy the code and then copy the uh then go to the um the the URL where you paste that um code into. you will need certain permissions on the resource groups where you are installing these appliances. So I recommend you check what the prerequisites are for um for permissions. I use um I used the contributor here and that works fine. Now the now the it's configured to ashure migrate. So, let's go back to the uh appliance and go back and forward here. And as you can see, it doesn't this doesn't work. You have to go out and then go back in again. Now, you can see we have two appliances on the right. So, let's click replicate. Here we are from VMware and we are migrating nothing on HyperV, right? But we're migrating with from VM from VMware. So let's find the target um the target appliance. You need to create of course uh click of course the correct target system and it will come up with the appliance itself directly. Here you can see list of the VMs that are available for M migration. Anything that is already replicating is in gray. Now we're doing the ignite demo v3. There we can choose which subscription and resource group the VM should be the arc object should be put into. And this is also important to know if you have different resources with different um rules and arbback and so on. You you should put them into different resource groups. You can change uh the OS disc here. You can target how much uh vCPUs if you want dynamic memory or not and what the starter value of the the dynamic should be. Now it will do a validation here and then you can start replication. The replication takes a certain time amount of time depending on the size of the v of the VM, but anything from like 15 to several hours is my um so let's migrate the VM. So yes, if you want to shut down the VM and I recommend you do that and then identify where you want to do that. So now the VM is migrating. Um and normally uh when you migrate a VM it takes about 15 to 20 minutes. Um and 15 is the shortest I've seen. Sometimes it takes well mainly it takes about 20 minutes. You can see this failed right. There's a failed error here and it tells you why. It says that the nick failed. It's outside of the scope. So, let's do again. And now it's connected. And the job is running. So, let's go back and look at the job. Let's go into overview. Let's look at replications jobs. And now it's running. It's started running. And like I said, this takes a while. Um, it's starting the failover. So, let's see what it does. Be interesting to see how long it takes this time. And it's done. The duration was in total 23 minutes to migrate this VM over. So let's have a look at the VM inside the uh HyperV host. Let's see if it's available as a VM. If we go into the cluster and you will now see Ignite demo VM1 and we can connect to it and see that it's actually running up and running. Now if you have VMware tools installed, they have to be uninstalled after uh the VM is migrated. So you can either do that manually or you might have scripts that you want to use to uh remove the VMware tools from the from the machine. Now I talked about the the thing with uh static IP addresses. you have there's some things you need to do to be get that to work and it is very well documented how you do the um how you do the um uh static IP address migration. So that's the end of the demo. So thank you very much for listening to this and watching this uh session recording. Thank you. Thank you very much and have a nice day.