Azure Site Recovery fails to deploy mobility agent, cannot enable replication

Hi, we have an on-prem VMWare environment which we need to replicate to Azure using site recovery so that we can do failovers if necessary. However, we are unable to start replication as each time it fails with generic errors that have not really helped.

To date, we have successfully deployed a recovery vault and enabled ASR. We have deployed the OVA and successfully registered the appliance with Azure and all components are verified as up to date. The account being used to log in to Azure from the appliance is both an owner on the subscription and a global administrator. The attempt to enable replication takes 15 to 20 minutes, failing each time. We've verified that the OS disk is basic, Bitlocker is not enabled, and the VMs are not encrypted. All VMs on the ESXi host are found. A domain credential has been provided to the ASR appliance to connect to the VMs. Installing manually isn't an option for us as we need to deploy to multiple VMs at scale. Below is the error we receive after trying to enable replication, followed a screenshot showing the steps from Azure:

Error ID

539

Error Message

The requested action couldn't be performed by the Replication Provider.

Possible causes

The Provider action failed. Check other errors for more information.

Recommendation

Resolve the issue and retry the operation.

First Seen At

8/20/2024, 9:39:06 AM

Error ID

322003

Error Message

Mobility agent installation failed on the source machine (Name: Locator-2018 IP: 172.18.245.69)

Possible causes

      Unable to copy mobility agent on to source machine because of one of the following reasons

      1. File and Printer sharing services are not enabled

      2. Windows Management Instrumentation(WMI) for private, public and domain profiles is not enabled

Recommendation

      1. Enable file and Printer sharing services for successful completion of this step (https://aka.ms/installation_File_printer_failures)

      2. To prevent additional issues, enable Windows Management Instrumentation(WMI) for private, public and domain profiles before proceeding further. (https://aka.ms/installation_WMI_errors)

      3. OR You can install mobility agent on the source machine through simple manual installation process (https://aka.ms/manualinstall) or by using Software deployment tools like SCCM (https://aka.ms/install-mobility-service-using-sccm)

Related links

https://aka.ms/installation_File_printer_failures

https://aka.ms/installation_WMI_errors

https://aka.ms/manualinstall

https://aka.ms/install-mobility-service-using-sccm

First Seen At

8/20/2024, 9:39:06 AM