Why Does the “Migrate” Button Become Disabled in VMware vCenter?
During routine maintenance operations, such as performing firmware upgrades or installing new ESXi host updates, you might suddenly notice a frustrating issue: some virtual machines cannot be migrated between different ESXi hosts. When you right-click the specific virtual machine, you will see that the “Migrate” button is entirely greyed out or completely inactive.
In most enterprise environments, this particular problem is frequently caused by third-party backup software integrations. After a virtual machine backup job is completed, the backup software is supposed to remove the hidden locks or tags it temporarily placed in the vCenter database. When it fails to clear these flags correctly, the virtual machine gets stuck in a locked state, preventing any vMotion or migration tasks. Below, we explain step-by-step how to safely resolve this database lock issue.
Step-by-Step Solution Guide:
1. Log into your vCenter Environment: As the first step, log in to your vCenter Server using the vSphere Web Client. Navigate through your inventory and select the specific virtual machine where the “Migrate” button is currently greyed out.
2. Copy the Browser URL to Find the MOID: Once you are on the summary page of the affected virtual machine, check your browser’s address bar and copy the URL. An example of this URL structure is shown below:
https://vcenter.tolgakaya.local/ui/#?extensionId=vsphere.core.vm.summary&objectId=urn:vmomi:VirtualMachine:vm-158:321d44-b617-4b32-be19-3445123c5ba&navigator=vsphere.core.viTree.hostsAndClustersView
Take a careful note of the value indicating the Managed Object ID (MOID), which looks like “vm-158” (or “vm-244” depending on your VM) in the highlighted section of your link.
3. Access the AuthorizationManager Page: Open a new tab in your web browser and enter the following address. Make sure to replace the domain with your own vCenter server’s FQDN or IP address:
https://vcenter.tolgakaya.local/mob/?moid=AuthorizationManager&method=enableMethods
Upon reaching this address, a prompt will appear. Log in using your vCenter administrative credentials (for example, [email protected]).
4. Edit the MOID Entity: On the screen that appears, you will see an “Entity” field. You need to replace the default MOID number with the exact ID of the virtual machine you noted down in Step 2. It should be formatted exactly like this example:
<entity type=”ManagedEntity” xsi:type=”ManagedObjectReference”>vm-158</entity>
5. Fill in the Method Field: Next, you must specify the exact task you want to re-enable. Go to the “Method” field on the same page and add the following code snippet:
<method>RelocateVM_Task</method>
6. Confirm and Execute the Process: After filling in both fields correctly, click the “Invoke Method” button to execute the command and apply the changes directly to the vCenter database.
Conclusion and Final Results:
Once you have successfully completed these steps, the database lock will be cleared, and the “Migrate” button will become active again. You will immediately be able to migrate the virtual machine between other ESXi hosts seamlessly. If the migrate option still remains inactive after applying this method, you might need to try restarting the core services of your vCenter Server.
Important Additional Notes: In such scenarios, resolving the problem without removing the virtual machine from the vCenter inventory is the healthiest and most recommended approach. Removing virtual machines from the inventory and re-registering them can cause irreversible loss of historical task data and performance history metrics. Proceeding with Managed Object Browser (MOB) solutions ensures your data remains intact and prevents any operational history loss.
Read More: https://sysarticle.com/how-to-bypass-the-microsoft-account/
Visit Vmware
