Sharing of thoughts and information is what blogging is all about. This way we can learn from each other. Post A Comment!These postings are provided "AS IS" with no warranties, and confers no rights. You assume all risk for your use.
Anthony Bartolo Twitter | LinkedIn
Pierre Roman Twitter | LinkedIn
Update: Many readers of CANITPRO.Net have reached out and requested the PowerShell cmdlets be posted amidst the steps. As per everyone's request, below is the updated Step-By-Step including the PowerShell cmdlets.
Back in March, we at CANITPRO.NET published a post entitled Step-By-Step: Migrating From VMware to Microsoft Hyper-V Server 2012. This post has now become the first step to an even larger endeavour. With the advent of the cloud becoming more and more accepted as best practice for seamless scalability and redundancy, it might be a good time to take the next step and begin pondering moving your organizations to the cloud.
Disclaimer: This post has not been written to slight any other virtualization offering
As stated previously, virtualization is a great way to extend the utilization of hardware one's organization and as you all know there are a great many product offerings available to fulfill that requirement. This post, like any of the other "Step-By-Step" post, are meant to be a resource should the need arise or for conducting labs.
Step 1: Complete Step-By-Step: Migrating From VMware to Microsoft Hyper-V Server 2012
This previous Step-By-Step is important as it provides guidance as to converting your VMware VM into a Hyper-V VM.
Step 2: Run your newly converted VMs in Hyper-V and update the drivers
Once the VM conversion process has completed, the Hyper-V Integration Services drivers inside the VM should be upgraded. Hyper-V Manager is required to complete this step.
Step 3: Provisioning the VM in Windows Azure
Once the drivers within the VM have been update, the VM needs to be copied to Windows Azure Storage to be provisioned on Windows Azure Infrastructure Services. PowerShell will be utilized to do this utilizing the Windows Azure PowerShell Module.
Ensure that the newly provisioning VM is listed on the Virtual Machines page in the portal with a status of Running.