vSphere 5.x Storage vMotion does not rename virtual machine files on completing migration (2008877)
- You rename a virtual machine in the VMware vSphere Client, but the
.vmdkdisks are not renamed following a successful Storage vMotion task.
- You perform a Storage vMotion of the virtual machine to have its folder and associated files renamed to match the new name. The virtual machine folder name changes, but the virtual machine file names do not change.
- VMware vCenter Server 5.0 Update 2, for further details see: VMware vCenter Server 5.0 Update 2 Release Notes - Resolved Issues.
- VMware vCenter Server 5.1 Update 1, for further details see: VMware vCenter Server 5.1 Update 1 Release Notes - Resolved Issues.
To download these updates, see the VMware Download Center.
To fully resolve this issue after updating the vCenter Server, add the
provisioning.relocate.enableRenameadvanced parameter to vCenter Server and set its value to
Note: The default value for
- Log into the vSphere Client as an Administrator.
- Click Administration > vCenter Server Settings.
- Click Advanced Settings.
- Add this advanced parameter Key:
- Set the value to:
- Click OK.
- Restart the VMware VirtualCenter Server service for the changes to take effect. For more information, see Stopping, starting, or restarting vCenter services (1003895).
Note: The .nvram file does not get renamed when virtual machine is powered on during Storage vMotion. The oldname.nvram will remain.
For information regarding renaming the .nvram file, see Renaming a virtual machine and its files in VMware ESXi and ESX (1029513)
To be alerted when this article is updated, click Subscribe to Document in the Actions box.