Hi all,
I'm working on a project where several (40+) machines have to be moved from a VMWare ESX 4.1 platform to Azure. Because of the large amounts of VM's that are being moved a bit of automation is required.
I've got some powershell scripting in place which will do a few things sequentially
1. Migrate the VM from VMWare to Hyper-V 2012 using the New-SCV2V cmdlet from Virtual Machine Manager 2012
2. Store the migrated VM in the VMM library
3. Move the VHD's (usually 2, 1 OS and 1 data disk) to Azure and create disks
4. Create a new VM in Azure using the uploaded disks.
The problems I'm having now is that the migrated VM's will boot up on the Hyper-V platform but not in Azure. The VM in Azure will start and display as 'Running' in the Azure portal, but I can't connect to the VM using RDP (pinging the machine doesn't work either).
I've booted the VM on Hyper-V without problems, logging on works as well (through the VM console and RDP), I've installed the latest (Hyper-V 2012) integration services on the VM. But as far as I know there is no real way of troubleshooting an unresponsive VM on the Azure platform.
Any hints or tips?