VM agent status stuck on not ready

Kaushal Pathak 0 Reputation points
2024-03-08T04:59:46.29+00:00

Hi All,

We are in the process of migrarting servers using azure migrate and encourered two persistent issues where we made multiple attempts but no luck.

  1. Windows Servers Shows up vm agent not ready post migration. To mitigate we installed vm agent via rescue vm and swapped os disk on affected vm but still same behaviour
  2. Win 10 VM's when migrated shows up vm agent issue with booting issue and stuck in automatic startup repair
Windows 10
Windows 10
A Microsoft operating system that runs on personal computers and tablets.
11,083 questions
Azure Virtual Machines
Azure Virtual Machines
An Azure service that is used to provision Windows and Linux virtual machines.
7,479 questions
Azure Migrate
Azure Migrate
A central hub of Azure cloud migration services and tools to discover, assess, and migrate workloads to the cloud.
745 questions
Windows Server
Windows Server
A family of Microsoft server operating systems that support enterprise-level management, data storage, applications, and communications.
12,525 questions
0 comments

1 answer

Sort by: Most helpful
Most helpful Newest Oldest
  1. vipullag-MSFT 25,616 Reputation points
    2024-03-08T05:48:16.4833333+00:00

    Hello Kaushal Pathak

    Welcome to Microsoft Q&A Platform, thanks for posting your query here.

    For the first issue, it is important to ensure that the Azure VM agent is installed on the migrated VMs. If the machine is running version 9.7.0.0 or later of the Site Recovery Mobility service, the Azure VM agent is automatically installed by the Mobility service on Windows VMs. On earlier versions of the Mobility service, you'll install the agent manually. If you're running a version of the Site Recovery mobility service earlier than 9.7.0.0, or you have some other need to install the agent manually, you can download the VM Agent installer and run the installer file.

    For the second issue, it is important to ensure that the Azure VM agent is installed on the migrated VMs. If the VM is migrated without the required changes, the VM may not boot, or you may not have connectivity to the migrated VM. You can try to install the VM agent manually on the affected VM. If the issue persists, you can try to boot the VM in safe mode and check if the VM agent is running. If it is not, try to start the service manually. If the issue still persists, you can try to uninstall and reinstall the VM agent.

    If you have tried all the above steps and still facing the same issue, it is recommended to contact Azure support for further assistance.

    Hope that helps.