sherlock1
asked on
Migrate a VMDK to Azure and management certificate thumbprint issue
Hi Experts,
I have a vmdk file (VmWare virtual machine disk) from which I would like to upload as an Azure Image (and/or a VM) and attempting to upload to a page blob in the format as follows:
https://storageaccount1.blob.core.windows.net/vhds/TBI-269/Srv-winbld_CLONE-disk1.vmdk
I am using the Microsoft Virtual Machine Converter 3.0 tool but looks like this requires some Azure login information (management certificate thumbprint)
I am not receiving an error message, I just cannot complete all the information in one of the screens of the Microsoft Virtual Machine Converter 3.0 tool so it won’t let me continue – it requires the management certificate thumbprint to move to the next page. Any ideas what could be causing this issue & how to resolve?
Thanks
I have a vmdk file (VmWare virtual machine disk) from which I would like to upload as an Azure Image (and/or a VM) and attempting to upload to a page blob in the format as follows:
https://storageaccount1.blob.core.windows.net/vhds/TBI-269/Srv-winbld_CLONE-disk1.vmdk
I am using the Microsoft Virtual Machine Converter 3.0 tool but looks like this requires some Azure login information (management certificate thumbprint)
I am not receiving an error message, I just cannot complete all the information in one of the screens of the Microsoft Virtual Machine Converter 3.0 tool so it won’t let me continue – it requires the management certificate thumbprint to move to the next page. Any ideas what could be causing this issue & how to resolve?
Thanks
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
Also looks like Azure Site Recovery is for creating a replica of a VM rather than moving / migrating to Vsphere?
Not sure if an existing Vmware Vsphere VMDK file can be migrated over to Azure with this tool?
Not sure if an existing Vmware Vsphere VMDK file can be migrated over to Azure with this tool?
So in your view Microsoft Virtual Machine Converter 3.0 tool should no longer be used since its not supported anymore?
Defunct as of 2016. It not longer works, waste of time trying.
Is a replica of a VM, once replicated to Azure, and the original turned off - not migrated to Azure!
You've got to have a Virtual Machine. (and that is not a flat file!).
(this is not about Migrating to vSphere, it's from vSphere)
ASKER
thanks for the clarification Andrew. I guess by flat file you mean it cannot be a VMDk file - you have to replicate the VM from Vsphere to Azure first and then if you dont want the VM to still be in Vsphere it can be removed from Vsphere after?
Do you know If Azure Site Recovery a different tool to Azure Migrate?. maybe Azure migrate is the replacement to Azure site recovery?
Do you know If Azure Site Recovery a different tool to Azure Migrate?. maybe Azure migrate is the replacement to Azure site recovery?
It still works I did it the other week here, but as stated MVMC is not really supported any more, Ive got it all scripted out in PowerShell if you're really interested.
As already pointed out ASR is the best option, Using Azure Site Recovery for Migrations. But if you're lucky enough to use Veeam then that's the simplest way I've found. Veeam: Restore / Migrate a VM to Azure
Pete
As already pointed out ASR is the best option, Using Azure Site Recovery for Migrations. But if you're lucky enough to use Veeam then that's the simplest way I've found. Veeam: Restore / Migrate a VM to Azure
Pete
ASKER
Thanks a lot all for your help with this, some real useful feedback and we blinks
ASKER
Shreedhar - thanks for weblink, although not getting an error message, maybe its a permissions related issue. Does the account needed to do the steps using the Microsoft Virtual Machine Converter 3.0 tool need to be an Azure Global admin?
Andrew - in regards to Azure Site Recovery is that part of Azure Migrate?: https://azure.microsoft.com/en-gb/services/azure-migrate/
Maybe Azure Migrate is whats needed?
So in your view Microsoft Virtual Machine Converter 3.0 tool should no longer be used since its not supported anymore?
Thanks