Andy Fox | 1 February 2013
Since vSphere 5.0 was released, a feature previously available was found to not work anymore. Essentially, after a successful storage vMotion migration a renamed virtual machines’ files were no longer renamed to match. This feature has been restored in vSphere 5.0 update 2, however must be enabled.
Having upgraded to vSphere 5.0 update 2, the option
provisioning.relocate.enableRename must be set in the advanced
vCenter Server settings.
Using the vSphere Client, navigate to the Home Page, and select vCenter Server Settings (under Administration), then select Advanced Settings from the left. The parameter needs to be added with the value true as below:
The vCenter Service (or vCenter Server) will now need to be restarted. Afterwards Storage vMotion should now rename the files when the virtual machine has been renamed.
This currently is not available for vSphere 5.1, but will be included in a future update.