The mobility agent on the machine is not yet registered with Proxy server.

Question

The mobility agent on the machine is not yet registered with Proxy server.

Mohamed Mahmoud Mohamed Zain aldin 0

I am trying to migrate an Azure VM between subscriptions across different tenants using Azure Site Recovery (ASR) by treating the source VM as a physical server.

I have attempted two methods to install and register the Mobility Agent on the source VM:

Automatic installation through ASR by enabling replication (which pushes the agent automatically).
Manual installation and registration using the command prompt with the appropriate parameters.

In both methods, I encounter the same issue:

“The mobility agent on the machine is not yet registered with Proxy server.”

I have verified the installation steps, network connectivity, and proxy configuration, but the problem persists.

Siva shunmugam Nadessin 10,905 Reputation points Microsoft External Staff Moderator

2025-10-16T13:32:47.37+00:00
Hello Mohamed Mahmoud Mohamed Zain aldin,

Kindly reply to below question for us to investigate further?

Have there been any changes in network configuration that might affect connectivity between the source VM and the Proxy server?

Can you confirm that the Mobility Agent installation was attempted with administrator permissions?

Are there any specific error codes in the logs that you could share?
Mohamed Mahmoud Mohamed Zain aldin 0 Reputation points

2025-10-16T13:45:43.5466667+00:00
Hello @Siva shunmugam Nadessin

Please find the details below:

Network Configuration: There have been no recent changes in the network configuration. The source VM and the appliance (Proxy) VM are in the same virtual network. I also verified that the Proxy server is reachable from the source VM.

Administrator Permissions: Yes, the Mobility Agent installation and registration were performed with full administrator privileges.

The log files related to running and registering the Mobility Agent on the source VM do not show any specific errors.
Anonymous

2025-10-31T06:53:14.69+00:00

Hi Mohamed Mahmoud Mohamed Zain aldin,

Thanks for posting your question in Microsoft Q&A forum

The Mobility Agent must register with the ASR proxy server to be recognized and start replication. Even if installed and network reachable, this registration can fail silently without explicit errors. Ensure the Mobility Agent service is running on the source VM and restart it to force re-registration.

The source machine registers with the configuration server when you install the mobility agent. You can debug any failures during this step by following these guidelines in Microsoft official document: https://docs.azure.cn/en-us/site-recovery/vmware-azure-troubleshoot-configuration-server#registration-failures

I hope the provided answer is helpful, do let me know if you have any further questions on this Please accept as Yes if the answer is helpful so that it can help others in the community.
Anonymous

2025-11-03T05:32:09.3366667+00:00

Hello Mohamed Mahmoud Mohamed Zain aldin,

Just checking to see if you have a chance to check my previous response and helped, do let me know if you have any further questions on this.
Anonymous

2025-11-05T06:07:08.4833333+00:00

Hello Mohamed Mahmoud Mohamed Zain aldin,

Following up to see if you have a chance to check my previous response and helped, do let me know if you have any further questions on this.

Your answer

Siva shunmugam Nadessin 10,905 Reputation points Microsoft External Staff Moderator

2025-10-16T13:32:47.37+00:00

Hello Mohamed Mahmoud Mohamed Zain aldin,

Kindly reply to below question for us to investigate further?

Have there been any changes in network configuration that might affect connectivity between the source VM and the Proxy server?

Can you confirm that the Mobility Agent installation was attempted with administrator permissions?

Are there any specific error codes in the logs that you could share?
Mohamed Mahmoud Mohamed Zain aldin 0 Reputation points

2025-10-16T13:45:43.5466667+00:00

Hello @Siva shunmugam Nadessin

Please find the details below:

Network Configuration: There have been no recent changes in the network configuration. The source VM and the appliance (Proxy) VM are in the same virtual network. I also verified that the Proxy server is reachable from the source VM.

Administrator Permissions: Yes, the Mobility Agent installation and registration were performed with full administrator privileges.

The log files related to running and registering the Mobility Agent on the source VM do not show any specific errors.
Anonymous

2025-10-31T06:53:14.69+00:00

Hi Mohamed Mahmoud Mohamed Zain aldin,

Thanks for posting your question in Microsoft Q&A forum

The Mobility Agent must register with the ASR proxy server to be recognized and start replication. Even if installed and network reachable, this registration can fail silently without explicit errors. Ensure the Mobility Agent service is running on the source VM and restart it to force re-registration.

The source machine registers with the configuration server when you install the mobility agent. You can debug any failures during this step by following these guidelines in Microsoft official document: https://docs.azure.cn/en-us/site-recovery/vmware-azure-troubleshoot-configuration-server#registration-failures

I hope the provided answer is helpful, do let me know if you have any further questions on this Please accept as Yes if the answer is helpful so that it can help others in the community.
Anonymous

2025-11-03T05:32:09.3366667+00:00

Hello Mohamed Mahmoud Mohamed Zain aldin,

Just checking to see if you have a chance to check my previous response and helped, do let me know if you have any further questions on this.
Anonymous

2025-11-05T06:07:08.4833333+00:00

Hello Mohamed Mahmoud Mohamed Zain aldin,

Following up to see if you have a chance to check my previous response and helped, do let me know if you have any further questions on this.