Tag Archives: Hyper-V

VM Version Upgrade | Windows Server 2016 & Windows 10

If you have recently upgraded your datacentre infrastructure to Windows Server 2016 (or your client device to Windows 10) you can benefit from the latest Hyper-V features available on your virtual machines by upgrading their configuration version. Before you upgrade to the latest VM version make sure;

  • Your Hyper-V host are running latest version of Windows or Windows Server and you have upgraded the cluster functional level.
  • You are not going to move back the VMs to a Hyper-V host that is running a previous version of Windows or Windows Server.

The process is fairly simple and involves only four steps. First check the current VM configuration version.

  • Run Windows PowerShell as an administrator.
  •  Run the Get-VM cmdlet as below  and check the versions of Hyper-V VMs. Alternatively the configuration version can be obtained by selecting the virtual machine and looking at the Summary tab in Hyper-V Manager.

Get-VM * | Format-Table Name, Version

  • Shutdown the VM.
  • Select Action > Upgrade Configuration Version. If you don’t see this option for any VM that means that  it’s already at the highest configuration version supported by that particular Hyper-V host.

If you prefer PowerShell you can run the below command to upgrade the configuration version.

Update-VMVersion <vmname> 

Introducing Technical Preview 4 | Windows Server 2016 & System Center 2016

With dawn of the year 2016 almost upon us, Microsoft has released another build for it’s upcoming Windows Server & System Center 2016 suite of products. This Technical Preview 4 contains much new advancements and fixes based on customer feedback on the product clearly making it’s way as the cloud OS for next generation of computing.

Nano Server gets a new touch

Nano server, a headless installation option like server core which is going to be one of the installation option for Windows Server 2016 has improved a lot since last preview. In this release IIS & DNS server roles can be installed in Nano server in addition to existing Hyper-V & Scale-out File Server features.

Introducing Hyper-V Containers

Providing additional layer of isolation for Windows Containers, Hyper-V containers can be now deployed as virtual sandboxes to host application workloads. This technology utilizes the nested virtualization capability introduced in Windows Server TP4. Also you can use both docker & PowerShell to create, deploy and manage Windows Containers.

System Center 2016 Improvements

Another milestone is the System Center 2016 TP4 release with some awesome features for private cloud management. Now you can use the SCOM agent to monitor your Nano Servers in TP4. SCCM 2016 TP4 has introduced some new functionality to improve Windows 10 deployment experience via SCCM.

  • Mobile Device management (MDM): enhanced feature parity with Intune standalone – Many of the  MDM feature that are supported via Intune standalone (cloud only) are also enabled for Configuration Manager integrated with Intune (hybrid) in this release.

  • Integration with Windows Update for Business – Now you can view the list of devices that are controlled by Windows Update for Business.

  • Certificate provisioning for Windows 10 devices managed via on-premises mobile device management

You can download Windows Server 2016 Technical Preview 4 & System Center 2016 Technical Preview 4 evaluation bits from here.

Library Server Failure in SCVMM 2012 R2

Few days back I was working with my colleague Law Wen Feng on a SCVMM Managed Hyper-V Cluster. The idea was to update the environment from SCVMM 2012 R2 UR 2 to UR 7. We noticed a strange issue where the Library Server (VMM Server itself) was complaining about a refresh failure. It seemed like the VMM agent was no longer functioning properly in the VMM Management Server.

WinRM Issue  (1)

As a poor man’s alternative we removed the library server from VMM. Then we tried to re-add the same VMM server as a library server which resulted in bizarre output. Nevertheless the VMM rejected another file share in a different server which we were hoping to add an alternative.

WinRM Issue  (2)

The error reads as the VMM Agent was no longer functional on the target server. But it was indeed running without any issue.

WinRM Issue  (3)

WinRM Issue  (4)

I’ve reached out to my fellow MVP colleagues Krisitan Nese, Stanislav Zhelyazkov & Daniel Neuman for some suggestions. They suggested that we do re-associate the VMM Agent with VMM Server. Yes it sound like chicken and egg situation. But this is no ordinary Hyper-V host but the VMM server itself.

Register-SCVMMManagedComputer cmdlet can be used to re-associate a managed computer on which VMM agent software is installed with a different VMM management server. But here we chose to add it to the same VMM server.

WinRM Issue  (5)Now it was complaining about WinRM was no longer functional. For those who are familiar WinRM is necessary component that is needed for you to remotely manage Windows Server. By default during the installation SCVMM takes care of enabling and running the WinRM service. Rebuilding the VMM server with retain DB option was not an option as we were middle of preparing demo lab and as I always believe needed to get to the bottom of it.

The evil WinRM GPO

We checked the GPO settings for the domain and found out WinRM was forced to all computers in our domain by a GPO. We moved the VMM server to a test OU and then disabled inheritance for that particular GPO and guess what, after a gpupdate /force in the VMM server we were able to add the library server back again.

WinRM Issue  (6)

Is that All? No it is not.

But I suspected it couldn’t be the only solution or the issue. So some digging into the default WinRM behavior in SCVMM I noticed that infact there was an actual configuration item that has been missed in the GPO itself.

According to Microsoft, there are some consideration for WinRM when you adda Hyper-V host to a VMM environment. Following has been extracted from above TechNet Article the highlighted section focuses on configuring WinRM listeners for both IPv4 & IPv6.

If you use Group Policy to configure Windows Remote Management (WinRM) settings, understand the following before you add a Hyper-V host to VMM management:

  • VMM supports only the configuration of WinRM Service settings through Group Policy, and only on hosts that are in a trusted Active Directory domain. Specifically, VMM supports the configuration of the Allow automatic configuration of listeners, Turn On Compatibility HTTP Listener, and Turn on Compatibility HTTPS Listener Group Policy settings. VMM does not support configuration of the other WinRM Service policy settings.
  • If you enable the Allow automatic configuration of listeners policy setting, you must configure it to allow messages from any IP address. To verify this configuration, view the policy setting and make sure that the IPv4 filter and IPv6 filter (depending on whether you use IPv6) are set to *.
  • VMM does not support the configuration of WinRM Client settings through Group Policy. If you configure WinRM Client Group Policy settings, these policy settings may override client properties that VMM requires for the VMM agent to work correctly.

I had a look at the Allow Automatic Configuration of Listeners policy setting under Computer Configuration\Administrative Templates\Windows Components\Windows Remote Management node in the GPO and the IPv6 filter was set to null, we changed that to accept from any IP address by putting an asterisk (*). Of course IPv6 was enabled in all Hyper-V hosts and the VMM Server by default.

WinRM Issue  (7)

Now it was about time to move back the VMM Server to it’s original OU with the GPO applied and execute a gpupdate /force. Surprisingly it did the trick. We were able to re-add the library server (in VMM) and couple of other file share as library shares without any issue.

WinRM Issue  (8)

Amazing isn’t it? We may never gaze upon TechNet for such trivial issues when they happen but it was worth all the trouble without rebuilding the VMM server. I must thank all who helped by sharing their ideas to sort this issue out. That is what I love about the community. When all is lost somewhere far away in the world, there will always be good people to help you out.

CSV Access Redirected in Hyper-V Cluster

I’ve been working with Hyper-V for quite sometime. During a recent Hyper-V Cluster deployment that myself and my colleague Hasitha Willarachchi (Enterprise Client Managament MVP) were working with, we have come across an issue which was really interesting to troubleshoot.

For some odd reason one of three Cluster Disks in a 3-Node Hyper-V 2012 R2 Cluster was in Redirected Access status.

CSV GFI Filter 1

When we were going through the cluster event noticed a bunch of 5125 Events complaining about an active system filter driver which is not compatible with CSV. Basically the I/O access to that volume has been redirected through another Hyper-V Node.

CSV GFI Filter 2

We tried changing the ownership of the particular CSV to another node, followed by trying to Turn off the Restricted Access Mode by right clicking the CSV and selecting that option. Changing the ownership was no success and for our surprise the operation to turn off the redirected access mode always failed with Set Operation Failed error.

After doing some research we decided to check up the CSV state and what are the active system filters in that particular volume. So we decided to run below commands in the current node owning the CSV.

CSV GFI Filter 3

We noticed a filter called esecdrv60 was having a frame value of Legacy. The nest command confirms that in all three nodes the CSV access is redirected. Then we immediately checked rest of the nodes with fltmc instances command and found out that same legacy filter was present there as well.

The Culprit aka GFI EndPoint Security

esecdrv60 filter actually belongs to GFI EndPoint Security software, which was installed and running in all three Hyper-V nodes. This software was pushed through it’s default policies and somehow Hyper-V cluster was not excluded in deployment list.

CSV GFI Filter 4

Uninstalling GFI was not possible locally so therefore we worked with GFI administrator to uninstall the software from all three hosts. Remember uninstalling GFI  requires a reboot and therefore we had to live migrate all the VMs and reboot one server at a time.

After uninstalling GFI and rebooting  all three hosts executed fltmc instances again to see whether GFI legacy filters were present or not. As you can see below all legacy filters were gone and CSV was back to normal operation mode without any error.

CSV GFI Filter 5

Following references were really helpful to identify and rectify the issue.

  1. Troubleshooting ‘Redirected Access’ on a Cluster Shared Volume (CSV)
  2. Cluster Shared Volume Diagnostics

Replication Failure in Azure Site Recovery

Azure Site Recovery is a great product for those who want to setup their DR environment with a minimal cost. It is based on Hyper-V replica technology for Hyper-V workloads and supports replication VMware & Physical server workloads to DR as well. Today I’m going to discuss a common issue one can encounter when enabling ASR replication to the cloud.

I’ve been working on an ASR setup during couple months and encountered strange issue when I enabled replication in protected VMs.

The enable protection job fails with below error.

Job ID: f9f84765-b18c-4002-96a4-d420dfb76ea6-2015-05-14 10:00:29Z

Start Time: 5/14/2015 3:30:29 PM

Duration: 10 MINUTES

Protection couldn’t be enabled for the virtual machine. (Error code: 70094)

Provider error: Unable to complete the request. Operation on the <Hyper-V Node>  timed out.

Try the operation again. (Provider error code: 2924)

Possible causes: Protection can’t be enabled with the virtual machine in its current state. Check the Provider errors for more information.

Recommendation: Fix any issues in the Event Viewer logs (Applications and Service Logs – MicrosoftAzureRecoveryServices) on the Hyper-V host server. If this virtual machine is enabled for replication on the Hyper-V host, disable this setting. Then try to enable protection again.

UTC Time: Thu May 14 2015 10:15:59 GMT+0530 (Sri Lanka Standard Time)

Browser: Mozilla/5.0 (Windows NT 6.3; WOW64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/42.0.2311.135 Safari/537.36

Language: en-us

Portal Version: 5.4.00298.11 (rd_auxportal_stable.150511-1702)

PageRequestId: a04f08ed-8932-43f2-95bc-2faab60ed958

Email Address: xxxxxx@outlook.com (MSA)

Subscriptions: xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxx

In the particular Hyper-V host following error has been logged in Event logs.

Enable replication failed for virtual machine ‘XXXXXX’ due to a network communication failure. (Virtual Machine ID 807780f6-bb7c-48d5-937d-4857a654dec3, Data Source ID 2256321007502018113, Task ID 8c1a5d7d-0693-4d6b-9243-37cc5e96a7d6)

This ASR setup was a on-premise to Cloud scenario with a single SCVMM server.

After spending a good number of troubleshooting hours I finally figured out what went wrong. The Hyper-V Hosts themselves need Internet connectivity to replicate the VMs to ASR. If you cannot enable direct Internet connectivity on the Hyper-V hosts you should do so via a proxy setup. You can change the proxy settings in ASR Provider in Hyper-V Host.

ASR replication requires traffic to be sent over port 443 (SSL) and in my case only the SCVMM server was configured with Internet access. If you are using a proxy server you may need to consider allowing below for successful replication.

  • *.hypervrecoverymanager.windowsazure.com
  • *.accesscontrol.windows.net
  • *.backup.windowsazure.com
  • *.blob.core.windows.net
  • *.store.core.windows.net
  • Allow the IP addresses in Azure Datacenter IP Ranges and HTTPS (443) protocol. Also your IP address whitelist should contain that of your primary region and  West US IP address ranges.

Protect your Private Cloud with 5Nine Cloud Security

When it comes to virtualization lot of people start asking questions about how they can secure their environment against security threats. Installing an AV solution inside individual VMs looks like the correct answer but what will happen in case of a network related security threat? Let’s explore the best answer for these issues in Hyper-V context.

5nine Cloud Security is an agentless security solution for Hyper-V which uses the extensible Hyper-V switch capabilities. This solution is capable of providing VM isolation, compliance and antivirus features.

5Nine also offers firewall, AV & IDS functions out of the box. The most important thing about this is it is an agent;less solution where you do not install any agent inside VMs to achieve these goals.

For hosters using Windows Azure Pack 5Nine offers Azure Pack extension which allows them to bring true IDS capabilities to their tenants. As the number of tenants increase security becomes the number one concern of any hoster. Not only that the 5Nine Cloud Security SCVMM plugin let you to deploy all these features via SCVMM if you are only focused about managing your own environment through SCVMM, making it easier to integrate both solutions.

All these features come at an attractive price $199/2 CPUs per host. If you are interested you can visit www.5nine.com for more information. Below is a short demonstration of what 5Nine Cloud Security can do to protect your Hyper-V Hosts, Private Cloud or Service Provider Cloud.

In a future post I’m going to discuss how to configure 5Nine Cloud Security to protect your Microsoft virtualization solution.

Microsoft Virtual Machine Converter 3.0

Recently Microsoft has announced the latest release of MVMC 3.0, a standalone product by Microsoft for P2V & V2V conversion. After System Center 2012 SP1 there were no built in support for P2V conversion in the VMM so as IT PROs we had to rely on MVMC & Disk2VHD.

What’s new?

  • P2V conversion of Windows 2008/ Windows Vista or above operating systems has been included in this version. Being said that those who want to convert legacy Windows OS up to Windows Advanced Server 2000 SP4 can still leverage Disk2VHD.
  • Native PowerShell capability that can be integrated with System Center Orchestrator workflows.
  • Conversion of Linux guest operating systems from VMware to Hyper-V

Prerequisites for MVMC 3.0 Installation

  • Windows Server 2012 R2/Windows Server 2012/or Windows Server 2008 R2 SP1
  • Microsoft .NET Framework 3.5 and .NET Framework 4 (MVMC on Windows Server 2008 R2 SP1)
  • Microsoft .NET Framework 4.5 (MVMC on Windows Server 2012/R2 or Windows 8/8.1)
  • For PowerShell cmdlets released with MVMC 3.0 requires Windows PowerShell Runtime 3.0 and these will only function on Windows Server 2012 R2 or Windows 8.1 or above.
  • Bits Compact server windows feature should be installed
  • Visual C++® Redistributable for Visual Studio® 2012 Update 1

What MVMC can do?

  • P2V Conversion (Windows Server 2008/Windows Vista or above)
  • V2V Conversion (VMware to Hyper-V)
  • V2V Conversion (Hyper-V to Microsoft Azure)

You can download and try this great tool from here.

Azure Site Recovery | Things you should keep in mind

Hi folks, we have successfully deployed an ASR solution throughout this series and today we are going to look at some FAQs people have. First lets take a look at how to clean the demo environment that we setup for ASR.

Cleanup your ASR Deployment.

There are actually two ways to do this.

  1. Remove the VMM server from registered servers in ASR Vault. This will disassociate the VMM server with your ASR vault. But yet again you will need to remove storage account and ASR vault manually from Azure portal if you don’t require them any longer. Although you may need to remove obsolete registry entries of the VMM server as described in here.
  2. Use the Cleanup script from TechNet. This is useful when you no longer have access to the Azure account. It’s quite simple actually. All you have to do is run the PowerSehll Script in the VMM server that has been registered with ASR. Actually this script will remove the registration information and cloud pairing information  of the protected clouds of the  VMM Server from Azure. Assuming you are not the administrator of the Azure account using this script is much more safer.

Also you can disable the protection of VM separately. Refer this article from TechNet in order to achieve this.

Lets take a look on some common FAQs related to ASR

Q. I have a existing VMware environment. Can I leverage ASR for DR in my environment?

A. Yes & No. For VMware workloads Microsoft has a separate product called Microsoft Migration Accelerator. You can use this to move your VMs to the cloud from AWS or VMware. In order to provide replication Inmage Scout by Microsoft is the best tool.

Q. What are the system requirements for ASR?

A. Note that ASR doesn’t support VHDX file format yet as it is not available is Azure still. Also there are number of compliant Linux distros that are supported as Guest OS.

  • An Azure Subscription
  • Management certificate
  • System Center Virtual Machine Manager 2012 R2
  • Windows Server 2012 R2 Hyper-V – used as VM host
  • Gen 1, fixed disk .vhd VMs in Hyper-V
  • Guest OS Windows Server 2008 or later

Q. I have full System Center suite deployed in my environment. How can I leverage that with ASR?

A. As all our system center products support Microsoft Azure, this depends on how you want use them with Azure. For an example you can use Orchestrator runbooks for automatic fail over to Azure, SCOM to generate alerts during fail over window etc…

Q. How can I get the pricing information for ASR?

A. Visit this link to learn more about the product and pricing

Azure Site Recovery is a emerging and continuously evolving product. With the announcement of vNext of System Center & Windows Server platform we can expect lot of new & exciting features with Azure pretty soon.

Azure Site Recovery | Testing & Configuring Fail over to the Cloud

To test the ASR fail over you can create a Recovery Plan which contains multiple VMs or test the fail over for a single VM. However it is important that you create recovery plans for your production environment in order to specify how the fail over should happen. Let’s take each scenario and see how we can address them.


  • Should your require to RDP after you fail-over your VM to Azure, you must enable Remote Desktop Connection in on-premise VM before you do test or actual fail over. This is a MUST. Also same should be done with SSH access for Linux VMs.
  • After the test fail over you’ll use a public IP address to remote into the Azure VM. In this case make sure your firewall doesn’t restrict that address. If you have configured the network mapping then you’ll get a private IP from your on-premise network. So you still RDP into LAN. I’d use this only after I have created a production recovery plan and use same for actual fail over.

Test Fail over from on-premise to Azure

In a test fail over you simulate the actual fail over sequence before you move it into production. For that you’ll need to choose between an existing isolated VM network or you can select NONE so that your test fail over will be done in an isolated environment without a VM network attached. Note that once you complete the test, Microsoft Azure will remove all the items like the test  VM that was used to simulate the test.

Test Failover (1)

  • Select the VM network that you want to test the ASR. This should be a separate VM network or you can select NONE.

Test Failover (2)

  • You’ll need to create an End Point to allow RDP to the test VM. It’s pretty much straight forward as below.

Add End Point Test Failover (1) Add End Point Test Failover (2) Add End Point Test Failover (3)


  • Once RDP end point has been created you can try remote into the test VM and see everything fits.

Test Failover (7)

  • Remember you still need to complete the test in order to clear the test deployment as below.

Test Failover (4)

  • It will prompt you to comment on the test scenario. Select the check box to clean up the environment.

Test Failover (5)

  • Once the environment is cleaned and the test is done you can see the status of the test fail over as all complete.

Test Failover (6)Creating Recovery Plan

For production deployment you’ll have to create a recovery plan. It will run a sequence of actions that you define to perform the fail over. You can customize the plan to include VM groups to specify start sequences, scripts to run once fail over sequence starts etc… Refer this article from TechNet for more information on customizing the recovery plan.

Create Recovery Plan (1)

  • Select Source and Target followed by the VMs that needs to be included in this recovery plan.

Create Recovery Plan (2) Create Recovery Plan (3)Performing a production fail over

Planned fail over is always pre – planned. For an example you want fail over your corporate web site at the end of each month when you update the web site. In such situations you can leverage ASR to plan it first hand, which VMs start first, any clean up tasks that should run etc.. Additionally you can configure an orchestrator workflow to automate same if you are using system center.

Unplanned fail over is more robust. This can be leveraged in a disastrous situation. It is something that you do not expect but you can create  DR recovery plan for this

Let’s see how to work with a planned fail over. Note that steps are same for both planned and unplanned.

  • Select Planned Fail over from the menu. Here I have only select the VM that I need to fail over. You can select a recovery plan that include multiple VMs if you need.

Planned Failover (1)

  • Select the fail over direction. Since this is fail over it would be from on-premise to Azure.

Planned Failover (2)

  • Let the process continue. As this depends on the network speed and size of the VM this may take some time.

Planned Failover (3)

  • Once the fail over is done as above  you’ll have to commit the fail over. Once it is committed your VM will be up and running from the cloud.

Planned Failover (4) CommitFail back to original state

Once you completed the fail over  you’ll need to move back to on-premise VM. Let’s see how you can do that. I have done this is again for a single VM not for a recovery plan to save time.

  • You may notice that the VM in on premise VMM is in a halt status once the fail over has been done.

Reverse Fail over (1)

  • Select the VM from Recovery Services and select the fail over accordingly. If you did planned before select planned again. I have selected the second option to minimize the fail over time but it’s up to you whether you want to go back to pre – fail over state or not.

Reverse Fail over (2)


  • You’ll notice that several actions are skipped in the fail back job as we are syncing only the data that has been changed during the fail over window.

Reverse Fail over (3)Reverse Fail over (4)

  • If you have selected Synchronize data before fail over option additionally you’ll have to select Complete Fail Over button in the job window.

Reverse Fail over (5)

  • To complete the fail over click Commit Button.

Reverse Fail over (8)We have successfully configured fail over scenario from on premise Azure. In the last post of this series lets discuss the best practices, hiccups and how to clean the ASR configuration in VMM in a demo VMM environment.

Azure Site Recovery | Setting up the Environment

In this post we are going to see how to setup ASR for VMM clouds. For this scenario I have used one VMM cloud called ASR Cloud that contains one Windows Server 2012 R2 Standard VM. Also I have another Linux VM in this cloud that is also protected using ASR.

Create the Azure Site Recovery Vault

  • Login to the Azure Portal
  • Click NEW
  • Click Recovery Services
  • Select Site Recovery Vault
  • Give it a proper name and select your region of preference. Make sure you use the same region across all your ASR components to avoid sync issues.

Create ASR Vault Creating a Storage account for ASR

Creating a storage account is pretty much straight forward. But make sure you select the same region as your ASR vault and Geo Redundant as the replication type.

Create Storage AccountInstalling the  Azure Site Recovery Provider in VMM Server

  • Click the Site Recovery Provider you just created and select “Between an on-premises site and Microsoft Azure” from the drop down list.
  • Click generate Registration Key and save the registration key.

Generate Registration Key

  • In the Dashboard select and download the Microsoft Azure Site Recovery Provider for Installation VMM servers
  • Double click the setup file and install the Provider.
  • Select the check box to automatically restart VMM service after the installation.

Installing ASR Provider (1)

  • Opt out Windows Update if you don’t wish to proceed with  the automatic ASR provider updates.

Installing ASR Provider (1)

  • If you have a proxy enabled for Internet connect specify the settings.

Installing ASR Provider (3)

  • Select the generated certificate so it will detect the vault automatically.

Installing ASR Provider (4)

  • Select Synchronize Cloud Meta data  check box so that it will sync the metadata of your VMM clouds with ASR. This step is optional so consider this if it doesn’t conflict with your organizational policy. This happens only once and you can sync each cloud in your VMM individually in the cloud properties of VMM.
  • Data Encryption option allows you to provide a SSL certificate that will be used in data decryption between On-premise to Azure. This needs to be kept safe as you will need it to perform a fail over from on-premise to cloud if you supplied one here.

Installing ASR Provider (5)

  • The ASR Provider is complete and the wizard will tell you if your VMM sever has been successfully registered with the ASR service or not.

Installing ASR Provider (6)Installing the ASR Agent for Hyper-V Hosts

  • Click the Site Recovery Provider you just created and download the Agent for Hyper-V Hosts from the main page.
  • Make sure pre-requisites are met before proceeding with the installation.Installing ASR agent for Hyper-V (1)

Configuring Cloud Protection

Now that you have successfully installed everything required it’s time to configure the protection settings for the cloud that you need to be protected by ASR.

  • Click Set up protection for VMM clouds on the quick start page
  • Click the cloud that you need to protect from Protected Items tab and then click Configure.
  • Select Microsoft Azure as the target.
  • Select the storage account you have created for ASR VMs.
  • Turn off Encrypt stored data – whether data should be encrypted and then replicated between the on-premises site and Azure.
  • Leave the default value for Copy frequency – This defines the replication frequency between the two sites. Once this has been set it can be only changed from here itself not from VMM.
  • Leave the default value for Retain recovery point – Zero means that only the latest recovery point for a VM is stored on a replica host server.
  • Leave the default value for Frequency of application-consistent snapshots. – This value defines how often you need to create snapshots for your VMs. If you supply a value here make sure it is always less than the number of recovery points specified earlier.
  • Enter a value for Replication start time for the initial replication of data to Azure.

Configure Cloud Protection (1) Configure Cloud Protection (2)

Once you click save it will start the initial replication between your on-premise VMM server to Azure. Note that this will take some time depending the size of the VHD. If you need to view the status of the replication you can click Jobs tab and see individual details for each job.

Configure Network Mapping

You can safely test the fail over in an isolated environment. However for a planned or unplanned fail-over to happen seamlessly you should map an Azure VM network with your on-premise VMM VM network. You can follow below two guides from Microsoft to setup Network Mapping.

  1. Prepare for network mapping
  2. Configure network mapping

Network Mapping (1)Network Mapping (2)

Enable Protection on VMs

Now we can enable protection on VMs. Please note that some of the below screenshots refer the Linux machine I have on my VMM cloud but don’t worry steps are same for Windows server VMs as well.

  • Select the VM from VMM and click properties
  • Click Configure Hardware section
  • Click Hyper-V Recovery Manager and click the Enable Hyper-V Recovery Manager protection for this VM check box.
  • Select the desired Replication Frequency. This is defined in Protection settings of the Cloud in Azure portal.
  • Click OK to update the configuration change on VM.

Enable Protection on VM (1)

  • Go to Azure portal and select the ASR Service, on the Virtual Machines tab in the cloud in which the virtual machine is located, click Enable protection and then select Add virtual machines.
  • From the list of virtual machines in the cloud, select the one you want to protect.

Enable Protection on VM (2)Enable Protection on VM (3)

Job progress can be viewed from Jobs section.

In the next post I’m going to demonstrate how to configure recovery plans, perform test, planned or unplanned failovers for your VMs.