VM migrated using Azure Site Recovery missing OSprofile and Azure VM agent

Question

_{Friday, December 9, 2016 12:25 PM}

We migrated VM's form Hyper-V VMM using Azure Site Recovery.

The VM's are running fine and I have installed the Azure VM agent MSI. I tried enabling the VM agent using

$vm = Get-AzureRmVM -ResourceGroupName $rg -Name $name $vm.OSProfile.windowsConfiguration.provisionVMAgent = $True Update-AzureRmVM -ResourceGroupName $rg -VM $vm

But I get an error message saying " 'provisionVMAgent' cannot be found on this object. Verify that the property exists and can be set."

When I try to get the OSProfile using

$vm.OSprofile i just get a blank result. It seems this has never been set during migration. How do I set this value and how do I get the Azure VM agent installed and registered?

All replies (4)

_{Saturday, December 10, 2016 8:30 AM}

Greetings!

Thank you for posting here!

For clarification, I would like to know the following:

1. Did you install the Azure VM agent on the On-premise machine before failover? As outlined in the documentation here: “Prepare to connect to Azure VMs after failover”
2. Does this issue occur on all the VMs that you replicated or a few specific VMs?
3. Azure has two different deployment models for creating and working with resources – Azure Resource Manager and Classic. did you replicate the VMs from Azure classic portal or the Azure portal?

Get-AzureRmVM – cmdlet gets the model view and instance view of an ARM Azure virtual machine.

Get-AzureVM - cmdlet retrieves information about Classic Azure virtual machines.

You may want to test failover a VM with Azure VM agent pre-installed and then check to see if that makes any difference.

/en-us/azure/site-recovery/site-recovery-vmm-to-azure#step-7-test-your-deployment

Hope this helps!

Regards,
Ajay

Kindly click "Mark as Answer" on the post that helps you, this can be beneficial to other community members reading the thread and ‘Vote as Helpful’

_{Monday, December 12, 2016 9:56 AM}

Hello.

1. The Azure VM agent was not installed on the VMs before migration. Too late for that now. I need a way to install the agent Post migration.

2. The issue seems to be with 6 out of 7 VMs. One VM get's contact with the Azure VM agent for some reason.

3. The VMs are running in ARM.

_{Thursday, December 15, 2016 7:28 PM}

I'm having this same issue too - RM virtual machines.  Very similar circumstances and the same error.  I need to get the Azure agent on the guests to use Azure Backup.

Any updates?

Thanks!

_{Friday, December 16, 2016 4:32 PM}

Greetings!

Apologies for the delayed response!

There is discussion on similar issue here, kindly follow the steps outlined in the link and see if it helps.

Hope this helps!

Regards,
Ajay